Bootloop after Nougat flash, need help. - Moto Z Questions & Answers

Hello!
My moto z xt1650-3 retail reteu (BL90.1A) are in a bootloop after flashing nougat retmx + sideload latest uppdate.
It boots fine, but after a few moments it freezes and reboots.
I have wiped and reflashed, but same story.
Flashing stock reteu MM or restoring my full twrp backup does not help.
MM is fine until i turn off the screen, then the same freeze and reboot.
The nougat sideload did some "repair" om system because it had been rw 2 times.
I dont know if it has something to do with my problem.
Did a fastboot flash partition gpt.bin, but no help there.
I have done all wipe and flash actions i can think of, besides the bootloader.
Can be hardware problems, but it worked fine before nougat flash.
Please help, this stupid phone is killing me..

Related

Z2 won't boot with stock rom after lineageOS?

Hi!
I recently installed lineageOS 14 over stock 6.0, since everyone praised it. However, it randomly rebooted in my pocket during the day hourly, so I decided to go back to stock.
But it neither boots with stock based rom, nor on a freshly installed stock with flashtool. It stucks at the bootanimation for hours, and doesn't reboot like it does in similar situations.
What the hell is that, could anyone help me?
(Btw my Z1C has the same problem)
I also installed Lineage OS, but after having a problems with keyboard i revert to stock with flash tool ver 0.9.18.6. I accidentally installed 5.1.1 uk version then after reboot i download new 6.0.1 ver and installed it over. Phone is working ok, no reboots. Maybe you should try to install again stock rom or change the flash tool version
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
iXaidyiu said:
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
Click to expand...
Click to collapse
Last time I think it did work without wiping userdata, so I didn't check those to wipe, however, to make sure I did a factory reset before from recovery. But I guess apps_log is not erased with a factory reset?
Anyway, thank you very much, I will try again this way.
Ps. It might be the cause that it still didn't boot when I tried a different rom with flashtool.
Update: Thank you, that did the trick, successfully booted!

Bricked the phone by wiping every partition in TWRP

My Redmi 5 plus won't boot as I messed up everything while trying to flash a couple of ROMs. At first the two ROMs that I flashed were working well. But after some time, whatever ROM I flashed, the phone started to restart while setting up the first boot (choosing language, region, etc.) and no further. So I tried wiping every partition there is under the TWRP wipe section (cache, system, vendor, data, internal storage, and so forth). Then flashed a custom ROM again with and without GApps but no success. I noticed that the phone even started to restart before the first boot finished. Also, after flashing stock ROM, TWRP said no OS installed. I even tried flashing stock MIUI ROM in fastboot mode. Although it went well, still bootloop and the device keeps restarting. However, before all of these problems, I did take a backup of every partition, leaving nothing behind, so I restored everything but again the "No OS installed, are you sure to boot?" message. Now I'm freaking out, not knowing what to do. I read somewhere that flashing via QPST tool may help but I'm having problems with installing it.
If I manage to make my phone work again, I will not flash any other ROM, ever.
Try installing new firmware with recovery, if that doesnt help you can try flashing with EDL mode.
Just open your phone and bridge these points ( on photo ) and connect phone to PC.
It should appear in XiaoMiFlash as COM[number].
Good luck!
steve_i7 said:
My Redmi 5 plus won't boot as I messed up everything while trying to flash a couple of ROMs. At first the two ROMs that I flashed were working well. But after some time, whatever ROM I flashed, the phone started to restart while setting up the first boot (choosing language, region, etc.) and no further. So I tried wiping every partition there is under the TWRP wipe section (cache, system, vendor, data, internal storage, and so forth). Then flashed a custom ROM again with and without GApps but no success. I noticed that the phone even started to restart before the first boot finished. Also, after flashing stock ROM, TWRP said no OS installed. I even tried flashing stock MIUI ROM in fastboot mode. Although it went well, still bootloop and the device keeps restarting. However, before all of these problems, I did take a backup of every partition, leaving nothing behind, so I restored everything but again the "No OS installed, are you sure to boot?" message. Now I'm freaking out, not knowing what to do. I read somewhere that flashing via QPST tool may help but I'm having problems with installing it.
If I manage to make my phone work again, I will not flash any other ROM, ever.
Click to expand...
Click to collapse
Did u have the global or Chinese rom installed?
And which twrp version do u have?

Bootlooping after attemping to restore from TWRP backup.

Phone is a frankensteined LG V30, 931, I installed Lineage on it following the correct steps for prepping the phone for an AOSP rom.
I had some issues with Lineage and decided to restore from backup, but when I restored my phone it hung on the splash screen permanently. I factory data reset, no good, still hung.
Wiped everything in TWRP and flashed US990_H, booted up okay but now I'm bootlooping.
Went back into TWRP and wiped data, restored from my backup, rebooted, still bootlooping.
Went back into TWRP, wiped everything and flashed US998E, F, G, H in order, rebooted, still bootlooping.
I'm out of ideas.
oblivion2k said:
Phone is a frankensteined LG V30, 931, I installed Lineage on it following the correct steps for prepping the phone for an AOSP rom.
I had some issues with Lineage and decided to restore from backup, but when I restored my phone it hung on the splash screen permanently. I factory data reset, no good, still hung.
Wiped everything in TWRP and flashed US990_H, booted up okay but now I'm bootlooping.
Went back into TWRP and wiped data, restored from my backup, rebooted, still bootlooping.
Went back into TWRP, wiped everything and flashed US998E, F, G, H in order, rebooted, still bootlooping.
I'm out of ideas.
Click to expand...
Click to collapse
What TWRP are you running? 3.2.3.7 stable from WTF?
What Magisk are you on? 19.x doesn't work well flashing TWRP flashable zips. Boot back into TWRP, uninstall Magisk and install 18.0 or 18.1.
See if that works.
____
Worst comes to worst, you can go into Download mode, flash 20H in Refurbish mode. You're back on pure stock, but still have unlocked bootloader with fastboot flash commands. Reinstall TWRP, flash the three root files again (no encryption, no root check, Magisk).
But then you'll have to manually install some stuff Johnfawkes puts in his TWRP-flashable zips.
ChazzMatt said:
What TWRP are you running? 3.2.3.7 stable from WTF?
What Magisk are you on? 19.x doesn't work well flashing TWRP flashable zips. Boot back into TWRP, uninstall Magisk and install 18.0 or 18.1.
See if that works.
____
Worst comes to worst, you can go into Download mode, flash 20H in Refurbish mode. You're back on pure stock, but still have unlocked bootloader with fastboot flash commands. Reinstall TWRP, flash the three root files again (no encryption, no root check, Magisk).
But then you'll have to manually install some stuff Johnfawkes puts in his TWRP-flashable zips.
Click to expand...
Click to collapse
I was on 3.2.3.7 from WTF, yes, and 19.x, that must have been my problem. I having the idea to refurbish flash 20H myself, and did that successfully. Going to go ahead and get started on installing the other files now. And doing a full system-image TWRP backup to prevent this from happening in the future.
Out of curiosity, what does Magisk do that causes this to happen? I would have thought that once I wiped the system and data partitions magisk would be gone completely.
i have a similar issue going on here and i'm stuck. bootlooping directly back to TWRP regardless of command (bootloader, power off, system). i believe i took all the right steps in WTF thread (unlocked, rooted, updated to latest H FW) then tried to flash lineageOS. even my sequential (unlock, root, update) TWRPs wont boot (they restore properly it just boots back to TWRP). i tried reflashing E,F,G,H no go.
US998, used proper 3.2.3.7 TWRP, Magisk18.
i've been flashing phones for years and this one has been difficult. any help?
EDIT: it seems the aroma installers of gapps was crashing TWRP. i was finally able to get back into bootloader and upon re-flashing TWRP everything seems back to normal. i can also recreate the problem so its def a gapps/TWRP no likey situation.
I think I ran into that once, and I powered-off fully and booted manually and it worked... you could try that. I may have even tried booting into bootloader or something, and then that fixed it too? I forget exactly, but it wasn't too big of a deal, once I got it solved, of course!

Went back to stock to flash a new custom rom but whatever I try I get boot loops.

HD1910 model, I had a working rom and tried various custom kernels to help battery life but decided to change to a rom that I can update via the phone rather than manual fastboot flash.
Chose Carbon rom, went back to latest stock with MSMtool, unlocked bootloader and seemed ok, but got a bootloop.
Thought something was wrong so used MSMtool again and tried various small differences i.e running fastboot -w before I flashed rom, before and after and either got a constant bootloop or a strange occurance where after it bootlooped a few times it went back to a factory reset stock rom.
I attempted to do a slower wipe i.e erase system, boot etc one by one but it said error (I used bootloader fastboot which I can't remember is different) I tried TWRP 3.4.0.2 and 3.4.01
I get FDE error, system_mount and vendor so what is the issue?
I even tried Lineage and same issue, just constant boot logo loops.
I would prefer a custom rom not stock
Is having a custom kernel affecting the install?
"went back to latest stock with MSMtool, unlocked bootloader and seemed ok, but got a bootloop."
This is the only thing that matters, as MSMTool completely resets the phone, if a problem happens after it's not related on what you did before.
My guess, maybe wrong MSMtool?
Or maybe you flashed the room incorrectly?
And what error you did get when you ran fastboot -w?
Pretty much sorted now, I wiped with fastbootd, then installed via a payloaddumper rather than in TWRP, I worked out what was causing bootloop was opengapps, once I used a older version (of the same android 10, pico arm64 etc) it installed and booted.
Only issue now is ctsprofile is false, but at least phone all works.

Can´t upgrade to 34.4.A.2.118 firmware

EDIT: Ignore this!
It just worked this time...
Dear mods, this thread can be deleted.
Hi there,
i really need some help.
Got my hands on a xperia x compact today and it already was on latest stock.
So i unlocked it and flashed LineageOS 19.1
Everything was okay but i had some issues and decided to wipe and start over with lineage 18.1.
After 18.1 bootlooping, it automatically booted into TWRP and from there it hang on splash screen forever.
Also after a reset, it wouldn´t boot into TWRP.
So i tried erasing userdata and cache via fastboot...
After that, TWRP loaded up again but now it had the famous can´t mount data, cache, issue.
So i ended up with a device, that won´t format data, won´t boot any rom (automatically enters recovery mode).
I decided to flash stock via EMMA and accidentally flashed the oldest firmware from the list!
Why is it even on top???
I just noticed it booting up fine and all, but TWRP won´t recognize touch inputs (touch works in stock 7.0 though)
I guess it´s because of the old firmware i just flashed.
So i picked the latest version from the list but unfortunately it seems like it´s still on old android 7 firmware instead of oreo!
The version i flashed is 34.4.A.2.118 which corresponds to oreo, but it seems like something went totally wrong here.
It´s still on the old firmware somehow...
I´m not a noobie flashing phones and stuff but this really is 100% confusing and driving me crazy right now
I actually managed to get 34.3.A.0.252 flashed now, which is slightly newer but still 34.4.A.2.118 won´t upgrade...
Any help is very appreciated
Thank you very much

Categories

Resources