>I have a Nexus 7
>Rooted, with CWM recovery
>Paranoid Andoid installed, works fine
>Decide to try alternative Rom's
>Download and install CM
>Bootloops
>Flash to stock and unroot using Nexus Root Toolkit
>Root again, install TeamWin recovery
>Try and flash CM again
>Bootloops
>Flash to stock again, install TeamWin recovery
>Try Smooth Rom
>Starts fine
>Reboot
>Bootloops
>Flash to stock again, install CWM recovery
>Decide to flash Paranoid Android as I wish I hadn't changed anything
>Flash PA
>Bootloops
>Flash to stock again, install CWM recovery
>Flash PA
>Boots fine, all going well
>Reboot
>Bootloops
So basically, that is the situation, and I can't figure out why it is happening. I have flashed Rom's before with no problem, but ever since I tried CM, it's all funked up, so yeah, any help at all would be greatly appreciated
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
bftb0 said:
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
Click to expand...
Click to collapse
I kept flashing to stock so I know where I'm at each time, I'm pretty knew to all this so I don't want to confuse myself.
I'm just about to flash stock and see if that bootloops now.
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
okay, so I have flashed stock, and it DOES NOT bootloop
miketino said:
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
Click to expand...
Click to collapse
It does seem unusual. OTOH, a "factory reset" in the custom recovery never re-builds the /data ext4 filesystem - so I suppose if the filesystem itself was bolluxed up, that would persist across a (custom recovery) "factory reset".
The thing is, the sequence you describe involves re-doing things with the factory install, and either
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
or
Code:
fastboot format userdata
fastboot flash userdata userdata.img
seems like they certainly should be rebuilding the ext4 filesystem in the userdata (/data) partition.
I mentioned something like this in a couple other posts, but I have experienced odd troubles with the /system partition where I could occasionally create an empty (and new) filesystem using the "Wipe system" option in TWRP, and immediately after that, if I manually checked it's status using (TWRP's) "e2fsck" program, it would report massive problems
Code:
adb shell e2fsck -f -n /dev/block/mmcblk0p<PARTNUM>
which doesn't make any sense at all - a brand-new & empty filesystem should be perfectly clean!
Anyway, something you might want to try is to run the above e2fsck program as a sanity check just after you flash a ROM and just before you are getting ready to reboot into the normal OS. The "-n" option to "e2fsck" prevents it from altering anything, so this is a nondestructive (no touch/read only) test. (I've never tried to actually use e2fsck for a repair - I just start over either with fastboot or the recovery filesystem formatting).
Note that "e2fsck" needs the partitions to be unmounted, so e.g. in TWRP you would:
Code:
adb shell umount /system
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper system = p3)
adb shell umount /sdcard
adb shell umount /data
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper data = p9)
If they don't come up clean, obviously you need to do something. Because "mount /sdcard" seems to fail when performed manually in TWRP, I just re-boot the recovery from within TWRP to do other tasks, should that be necessary.
Hope this helps.
miketino said:
okay, so I have flashed stock, and it DOES NOT bootloop
Click to expand...
Click to collapse
I wonder if this means something screwy is being caused by the ROM flashing in the recovery. Maybe try the above suggestions just as a sanity check?
BTW, what recovery and version are you using?
Its Clockwork Mod Recovery, version 6.0.2.3
miketino said:
Its Clockwork Mod Recovery, version 6.0.2.3
Click to expand...
Click to collapse
fwiw, I just booted the touch version of CWM 6.0.2.3
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
to make sure that it had e2fsck present in it's /sbin. It does.
e.g. my (32 GB grouper) device:
Code:
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/UDA: 24564/1875968 files (0.4% non-contiguous), 2641387/7503608 blocks
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/APP: 1100/41664 files (1.0% non-contig
uous), 121097/166400 blocks
also, "tune2fs" seems to be present too. You can get a listing of the filesystem creation options using the -l option, as in
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
although I will say I've compared this output before, searching for difference(s) between the way that fastboot formats things and the custom recovery does things and didn't see anything compelling.
[ TWRP might be different than CWM though - it has a utility called "make_ext4fs", whereas I think CWM uses "mke2fs" for fs creation. ]
HTH
Related
tried a new rom, wiped, flashed, rebooted then it had sdcard mount problems thought it was the rom so i wiped and then tried to flash with no luck it says
build: RA-sapphire-v1.5.2H
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-sapphire-v1.5.2H and fastboot just fine
SAPPHIRE PVT 32A
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck
It´s no bricked dude. Try remove ur sdcard and insert again.
Good luck.
Allready tried that and tried several sdcards, all cards worked before and is working on the pc
Try enable sdcard via usb toggle in RA-recovery. Insert usb cable into phone and pc. Check if your pc recognize your sdcard.
Tried to enable USB-MS no luck in windows
Try clicking the flash button a whole bunch of times, sometimes it just takes a while; I've only seen this on the hero recovery, though.
also tried that
Sorry to hear that.
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck
Click to expand...
Click to collapse
If it's any consolation, you're not bricked! You can install everything using fastboot, you'll have to scour the forums or google, but you should be able to find the instructions to flash an install this way. Generically it will be something like:
Code:
./fastboot erase system -w
./fastboot flash boot ./misc/boot.img
./fastboot flash system ./misc/system.img
./fastboot flash userdata ./misc/userdata.img
Sorry, I can't provide more details, right now.
Btw an actual brick is when you can't even fastboot or get into recovery.
Far as the SD card have you tried to format it with a PC via a card reader?
Searched alot if anyone could provide a link it would be great, sound good that i'm not bricked!!!
tried to format 2 different cards on the pc
did you make a nandroid backup before you flashed the new rom? if so then y not try and load the backup.
Should be same if another rom or nandroid backup through fastboot?
1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.
Still nothing
TigerTael said:
1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.
Click to expand...
Click to collapse
Okay,
My situation, after a bad flash (which I did not actually know was a bad flash), my SDcard reader in my phone would not read an SDcard at all. It would detect that one had been inserted, but acted as if nothing was there.
Also, my hboot showed that my bootloader was now 'S-ON' and not 'S-OFF'.
I was getting denied remote flash commands and everything.
After numerous wipes via recovery and then numerous wipes in fastboot, eventually one of the fastboot wipes fixed the problem.
I'm not 100% sure if it was a combination of erasing and then flashing a new ROM to system (via fastboot, not recovery) or what, but eventually my bootloader changed back to 'S-off' (What it always was for me) and then my SDcard could be read in the phone.
The key here was fastboot/hboot, and not recovery.
how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
also tried my nandroid backup with fastboot it says FAILED (remote: signature verify fail)
¤#"%¤#¤
Cronner said:
how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
Click to expand...
Click to collapse
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?
Solimian said:
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?
Click to expand...
Click to collapse
S-ON stands for security on, S-OFF, off. It's not locking to a carrier, but merely a security setting for the phone itself. There's a thread about it somewhere.
I don't think this has anything to do with formatting. As long as the SDcard can be read in another device such as a computer fine, I am still siding with the idea that it was a bad flash. I spent a day stressing that my SDcard reader on my phone was borked and now I would be screwed. Amon_Ra was there to offer support, but at the end of the day, after several wipes, the fastboot erase eventually got it to come right.
Amon_Ra and I summarised that somewhere a byte or a few bytes got written where it shouldn't have and corrupted some base code somewhere.
Solimian > is something wrong with the new radio?
yes adb and fastboot works now...
adb shell also works but can't mount sdcard there either!
C:\android>fastboot flash hboot hboot-1.76.2007.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
also tried: adb shell mount /sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
and:
adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
TigerTael
TigerTael Please remind what you do, i have same problem
Is there a way to completely recover a ThinkPad Tablet as I can with my LePad A1 ?
Would really like to upgrade to ICS, but I am unable to perform a complete factory reset... since even after doing this the tablet takes 10 minutes to boot and start throwing launcher errors when booted.
ThinkPadTablet_A310 (SC)
Still running Android 3.1 as no updates ever came through
Have rooted the device with Thinkpwn @djrbliss
gbraad said:
Is there a way to completely recover a ThinkPad Tablet as I can with my LePad A1 ?
Would really like to upgrade to ICS, but I am unable to perform a complete factory reset... since even after doing this the tablet takes 10 minutes to boot and start throwing launcher errors when booted.
ThinkPadTablet_A310 (SC)
Still running Android 3.1 as no updates ever came through
Have rooted the device with Thinkpwn @djrbliss
Click to expand...
Click to collapse
I can offer a full nandroid backup of a WE Tablet, it this helps
ThinkPad Tablet stuck in reboot-loop after ICS update
emuandco said:
I can offer a full nandroid backup of a WE Tablet, it this helps
Click to expand...
Click to collapse
Always helpful... but seems my problem was related to a broken build.prop. Luckily I had a copy of this file...
Was able to update my tablet from:
ThinkPadTablet_A310_02_0024_0065_SC
to:
ThinkPadTablet_A310_03_0069_0121_SC
But after successfully applying this update the device is in a reboot loop (only shows a static lenovo logo) and turns off, vibrates and turns on.
Iirc, some boot loops can be ended by doing a complete power down, i.e. power off. Press battery-disconnect button next to the SDcard. Then try a regular boot.
Full power down did not help
pwstein said:
Iirc, some boot loops can be ended by doing a complete power down, i.e. power off. Press battery-disconnect button next to the SDcard. Then try a regular boot.
Click to expand...
Click to collapse
Tried this, but did not help. At one stage it stayed on the bootlogo without rebooting, but never progressed. Still same...
Restored a nandroid with CWR
Was able to restore a nandroid with CWR and nvflash:
$ ./nvflash -w --bl ./04.EBT.img --go
$ ./nvflash -r --download 6 ./cwr/cwr-myrecovery.img
Reboot into recovery... and restored the backup ThinkPadTablet_0089_ROW_Root_CWM
Tablet booted and currently at the setup screen.
Note1: when using the recovery from the backup file itself the device rebooted before restoring. had to use my own backup
Note2: essentially I also got rid of the Chinese firmware
ROW image: http://forum.xda-developers.com/showpost.php?p=27981255&postcount=9
nvflash: http://forum.xda-developers.com/showpost.php?p=28148282&postcount=1
CWR: http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1 might be the one I use
Tried to update to ICS and bootloop/stuck again
To apply to ICS update I needed to modify the update.zip a little. When the system is running you enable USB debugging. Connect the tablet
[[email protected] adk]$ adb push ~/TPTRecover/busybox /sdcard/busybox
[[email protected] adk]$ adb shell
$ su
# mount -o rw,remount /system
# cd /system/xbin
# mv busybox busybox.ext
# cp /sdcard/busybox ./busybox
# chown root.shell busybox
# chmod 755 busybox
# exit
$ exit
Removed the indigo assert lines from META-INF/com/google/android/updater-script (maybe even the version check). And applied the update from the recovery menu; in this case this was still CWR (although I had to install my own backup again). Wiped cache before the restore...
The update got applied correctly... but on reboot it was again stuck on the Lenovo logo (no green nvidia tegra logo appeared). I suspected the boot .img does not get applied or flashed correctly. Since restoring this is essential to make the device boot normally again. Can you only update ICS from the stock recovery? Any clue or assistance is appreciated.
Note1: for the moment I restored nandroid again and run Honeycomb 3.1 (ROW)... having a Google market on a Chinese tablet is already a lot better.
Note2: below you can find my partition table. made a dump of all these just in case. Partition 7 seems to be the trouble for me? If so, can anyone provide me with an image for it?
Note3: after updating using CWM I also notice it does NOT remove clockworkmod with the stock recovery... this confirms my suspicions about the boot.img
----
BytesPerSector=4096
2. BCT StartSector=0 NumSectors=1024 Boot Configuration Table
3. PT StartSector=1024 NumSectors=512 Partition Table
4. EBT StartSector=1536 NumSectors=1536 Bootloader Table
5. GP1 StartSector=3072 NumSectors=512 ?
6. SOS StartSector=3584 NumSectors=1536 Recovery
7. LNX StartSector=5120 NumSectors=2048 Kernel
8. APP StartSector=7168 NumSectors=196608 Applications in System/ROM
9. CAC StartSector=203776 NumSectors=230400 CAChe
10. MSC StartSector=434176 NumSectors=512 ?
11. PIA StartSector=434688 NumSectors=131072 Pre-Install APK
12. SEC StartSector=565760 NumSectors=5120 ?
13. USP StartSector=570880 NumSectors=35840 ?
14. PDA StartSector=606720 NumSectors=5120 ?
15. UDA StartSector=611840 NumSectors=3234816 User Data (/sdcard)
16. GPT StartSector=3846656 NumSectors=512 ?
This is my backup made using nvflash.
Hope it helps.
I am using a ROW ICS stock rooted rom.
berbecverde said:
This is my backup made using nvflash.
Hope it helps.
I am using a ROW ICS stock rooted rom.
Click to expand...
Click to collapse
Does not seem to work...
... applied the update (reboot, nothing), flashed 07.lnx.img (reboot, nothing)
Only rolling back the ROW nandroid seems to work at the moment. I have tried pwstein's US image of ICS: http://forum.xda-developers.com/showpost.php?p=30799431&postcount=7 but also to no avail. Same problem... a static lenovo power-up image is shown. Seems more is needed to get ICS running on the tablet than what the nandroid images provide.
Does anyone have the stock recovery image?
gbraad said:
Does not seem to work...
... applied the update (reboot, nothing), flashed 07.lnx.img (reboot, nothing)
Only rolling back the ROW nandroid seems to work at the moment. I have tried pwstein's US image of ICS: http://forum.xda-developers.com/showpost.php?p=30799431&postcount=7 but also to no avail. Same problem... a static lenovo power-up image is shown. Seems more is needed to get ICS running on the tablet than what the nandroid images provide.
Does anyone have the stock recovery image?
Click to expand...
Click to collapse
Maybe if you flash all partitions using nvflash if would be ok.
If you can tell me how to back up all my partitions i can give it a try.
Right now i have the following partitions backed up:
04.ebt.img
06.sos.img
07.lnx.img
08.app.img
berbecverde said:
Maybe if you flash all partitions using nvflash if would be ok.
04.ebt.img
Click to expand...
Click to collapse
Fixed. The solution was to also allow the EBT to update, partition 4. I included an attachment with the files and a small script...
Additional info: http://m.51nb.com/thread-1244385-1-1.html
I wanted to clean flash a new CM10.2 nightly so I made a nandroid in TWRP 2.6.0.0 and then wiped data, system, and caches. But when I went to select the new nightly, ALL of my data was gone, including internal storage /sdcard. I have everything backed up to the cloud, no biggie. I adb push the newest nightly, gapps, and m_plus kernel to /sdcard and flash. It seems to work fine, go through setup wizard, then I reboot my phone again and now it's stuck at the google logo. I hold the power button, hard reboot again and again, but it's just stuck. So I go back into TWRP and try to reflash the ROM, but then it gives this error message:
E:error opening '/data/data/com.google.android.setupwizard'
E:error I/O error
I tried to adb push an older nightly to /sdcard in recovery, then I get this message:
failed to copy 'cm-10.2-20130914-NIGHTLY-mako.zip' to '/sdcard//cm-10.2-20130914-NIGHTLY-mako.zip': Read-only file system
What?! I tried fixing permissions, but it gave the same I/O error as above. I tried formatting internal storage and it gave me this error:
E:Unable to chmod '/data/data/com.android.phasebeam/.'
I am out of ideas and I did not see anyone with this issue after a quick search. What do I need to do to fix this?
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Have you tried to restore the factory image via fastboot?
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk 4
You have to mount /data as read write. Do
adb shell
busybox mount -o remount,rw /data
If that doesnt work, try
mount -o remount,rw /data
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This worked! Turns out that the Format Data option in TWRP (requires you to type 'yes') erases your whole device instead of the /data partition. oops! I'm not sure why this option borked the permissions for /sdcard or the other errors, but fastboot erase seems to have fixed it. Thanks demkantor!
ChemBot said:
This worked! Turns out that the Format Data option in TWRP (requires you to type 'yes') erases your whole device instead of the /data partition. oops! I'm not sure why this option borked the permissions for /sdcard or the other errors, but fastboot erase seems to have fixed it. Thanks demkantor!
Click to expand...
Click to collapse
HELP! that just happened to me, everything seems to be okay, mi device installs the ROM but never starts the phone
I've been reading the recovery and appears that, E: error: data....
How U did the "fastboot"??
Thank you
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much bro....
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
this worked for me too, but 10 seconds into twrp froze ant booted.
My phone has been stck in a bootloop, doesnt pass google screen. OEM unlocked, rooted, PURENEXUS ROM, out of the blue phone booted and has been that way since. I cant side load on ADB because ADB does not reconize device but Fastboot does. I tried eveything i posssibly could in fastboot to get this working and nothing is working.
Other forums state this as a bug from google and not fixable, could also be a hardware issue, so porobably considering getting a new phone
Mefer said:
this worked for me too, but 10 seconds into twrp froze ant booted.
My phone has been stck in a bootloop, doesnt pass google screen. OEM unlocked, rooted, PURENEXUS ROM, out of the blue phone booted and has been that way since. I cant side load on ADB because ADB does not reconize device but Fastboot does. I tried eveything i posssibly could in fastboot to get this working and nothing is working.
Other forums state this as a bug from google and not fixable, could also be a hardware issue, so porobably considering getting a new phone
Click to expand...
Click to collapse
Use nexus root toolkit google it install on a PC and it will fix your phone maybe depending on the cause of the issue worth a try
I'll give it a try, Def will keep you posted
Thanks man
lopezk38 said:
You have to mount /data as read write. Do
adb shell
busybox mount -o remount,rw /data
If that doesnt work, try
mount -o remount,rw /data
Click to expand...
Click to collapse
can you pls tell the commands
Vijayyaru said:
can you pls tell the commands
Click to expand...
Click to collapse
Those are the commands:
Code:
busybox mount -o remount,rw /data
If that doesnt work, try
Code:
mount -o remount,rw /data
Nitin
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working
My Pixel 4 is stuck on "Pixel is starting". This happened after installing Magisk and a custom kernel. I attached the logcat file, if someone could help me identify why it's getting stuck, and a possible solution. I want to grab the internal storage before wiping the device.
Fixes attempted:
Flash the OTA
Flash factory rom without -w option
Downgrade to Android 10
Boot into safemode
Boot stock boot.img
Boot magisk modded boot.img
Tried to access /system partition (By boot twrp -fastboot boot twrp.img and using adb shell while at "Pixel is starting" screen), but been unable to mount it.
I've also created an .img file of the SDB partition, so failed fixes can be reverted.
adb pull /dev/block/sda sda.img
Is there a way to grant su access through adb shell without needing to allow through the user prompt?
Since it would not let me attach the file, I have uploaded it to Google Drive:
logcat.txt
drive.google.com
Why would you remove the fastboot -w ? The very first thing I do usually when I have an issue on my device is format data. Sudo fastboot -w then reboot. That wipes everything clean. Depending on what it is i have happen that's usually one of the things I do right off the bat. And it usually fixes it as crazy as that may sound. When you flashed the factory image in fastboot did it all flash properly? Strange. I would wipe it for sure if I were you and see what happens. Since the Nexus S days, many years ago that's usually what I've always done to my phone's and tablets when something isn't right.
I would do the ./flash-all.sh on wherever factory image you were on when this happened or whatever. I see you say you tried rolling back to A10. I'd throw latest A11 factory image in PC and delete all other stuff far as factory images go so that none of it gets confused with a part from another... Unzip latest and let it do the flash-all and don't remove the -w this time and see what happens. I didn't look at your log yet but sounds like something maybe got corrupted, idk...But that's what I would definitely do. And make sure you use a good USB cable. I have quite a few good cables and mine sometimes stops at "extracting super partition" when phone boots to fastbootd and I have to giggle cord where it plugs in to my USB port on my laptop and it immediately finishes the flash...
(Edit)