Develop Bugs

[Q] Boot looping / Corrupted data partition

Been using the Alpha version of CM7 for the t989 for over 2 weeks now. Seems like when I rebooted it today it managed to corrupt the data partition.
Symptoms:
-Normal starts loop just after the kernel screen.
-CWM boots and works
-ODIN boots.
-CWM crashes when doing factory reset or restoring the data partition of a backup or formatting the data partition
This happened to me 2 days after installing CM7, the same version I'm still using. I was similarly stuck, but then I tried restoring my nandroid backup and eventually I could re-apply the CM7 zip and the phone started fine to a blank android.
Is there a way to solve this issue with my partitions? I am not too comfortable with re-partitioning it because I'm awake this can damage the boot sectors and brick it quickly if I don't do it just right.
Advice?

Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011

GBGamer said:
Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011
Click to expand...
Click to collapse
did it work???

Thank you
I'm so glad I found this thread, I thought my phone may be unreparable. I was experiencing exactly the same symptoms as the OP on my skyrocket and had considered using ODIN to restore to stock, but I thought the corrupted data partition could cause it to crash during the restore and hard brick the phone.
The restore was successful, but it boot looped for some reason. I then followed the ODIN root method to flash CWM recovery, flashed CM7 from there, booted and used the ROM Manager app to apply a recent backup. All is well.

Endless Boot Loop Gnex

I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.

Did you try to just reflash the ROM itself that you were using? If that doesn't work just wipe everything again and reinstall. If you have app backups it's no biggie.
Sent from my Galaxy Nexus using Tapatalk 2

codacrawford said:
I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you flash a new bootloader or anything? Flashing the latest JB bootloader might help.

There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.

silow said:
There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.
Click to expand...
Click to collapse
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?

Try this, wipe /system then reflash your old ROM again. Once that's flashed wipe davlik and cache and try a reboot. That should keep your data intact and just reload your old rom. Then you can renandroid and reflash.
Edit: just for safe measures makes sure you have any kernel software or tweaks disabled when you flash the new JB build. Of course if you are doing a clean install this won't matter. You just want to make sure things like overclocking or undervolting aren't crossong over to the new ROM, as say a 1.8 overclock might work on ICS kernel but not on a JB kernel. Hopefully that makes sense.
G-Nexus Sent

If all fails, use adb to pull all the important files, then use adb to push super wipe, and then flash it using your recovery. This will make sure that it wipes EVERYTHING. After that, just use adb to push Rom of your choice and then flash it.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

codacrawford said:
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?
Click to expand...
Click to collapse
1.) Boot into CWM
2.) Go to the "Mounts and Storage Menu" and "mount /data"
3.) Plug in your phone to the PC
4.) adb pull /data/media c:\gnex_sdcard_backup

[Q] boot loop on reboot

Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:

You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img

BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail

In fastboot type fastboot erase cache

Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?

With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?

BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.

Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.

I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.

same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.

boot.img

Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.

BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics

Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!

Stuck in bootloop. Fastboot and recovery working just fine.

Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1

MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.

jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....

Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.

same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again

Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!

this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair

I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...

Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709

I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!

People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.

zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.

MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups

neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me

neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)

I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.

Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.