Phone will boot into twrp but no os - Moto G6 Questions & Answers

Ok so I've had this phone for a while and it's been rooted with magisk and twrp the while time. I tried to flash a new os but I forgot to data wipe first. Now it will only boot into twrp and so i tried to restore it from a few days earlier but still no boot. I was playing in the options beforehand and may have turned off the oem unlock and forgot to turn it back on. I've tried flashing stock firmware and everything else I can think of. Any suggestions?

Related

[Q] Boot loop on Bootloader unlocked screen

Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
atomus12 said:
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
Click to expand...
Click to collapse
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
jayboyyyy said:
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
Click to expand...
Click to collapse
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
atomus12 said:
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
Click to expand...
Click to collapse
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
jayboyyyy said:
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
Click to expand...
Click to collapse
Never even thought about that! I will try those steps as soon as I get home today!
Thanks jay!!

No boot, no recovery, no connection, no anything.

Hi,
so I was about to flash a new ROM to my Z3C, because I was having some trouble connecting the phone to pc (drivers etc are ALL installed and have beend reinstalled too).
Since my phone was already running on .291, I skipped flashing stock rom, went to recovery, did a wipe, flashed 3.1.1.0 TWRP FOTA Kernel, flashed ROM, booted ROM (fine), forgot to flash GApps, went back to reco... Wait? No more recovery? Hmm.. Let's try booting system. OK! Went to settings and did a wipe. It took me into an older version of TWRP (I don't know exactly, something like 3.0.2.8?!), where I did the wipe myself (Data, Cache, System). I did system wipe because I wanted to flash the 3.1.1.0 FOTA TWRP once again (since it seemed to be incorrectly installed) and then install the ROM freshly. So, after installing TWRP (which was "successful") I tried to restart recovery to install the OS. WHAT? Again no recovery? Damn.. Now there's no more system to boot from.
Then I tried to put the phone into Flash-/Fastboot mode, to install the stock rom and start over again. Trying to Hold Vol+/- while plugging in USB doesn't do sh*t. The green/blue LED pops up for a sec and then disappears instantly. Entering recovery with hardbutton method won't work either.
Now I'm stuck with a phone, that can't do anything.. Is there any way to recover the phone?
I appreciate any kind of help & thanks in advice,
furi
NVM! What 'r the chances of 3 different usb cables being broken? LOL. Sorry for being stupid ._________.

Cannot boot into recovery (TWRP)

As the title suggest, I fail to boot into TWRP.
I have unlocked the phone and flashed TWRP (https://dl.twrp.me/raphael/twrp-3.3.1-0-raphael.img).
I could boot into TWRP using Power + Volume Up , wiped everything (except vendor) and pushed a custom rom to the internal storage.
I restarted the phone for some reason and cannot boot into TWRP anymore. Whatever I do, I end up in fastboot. Tried to flash various versions of TWRP with the same result.
Can you guys help me out?
Edit: I flashed the corresponding Xiaomi fastboot image and repeated the process, same problem.
Edit: Solved by repeating again.
flel said:
As the title suggest, I fail to boot into TWRP.
I have unlocked the phone and flashed TWRP (https://dl.twrp.me/raphael/twrp-3.3.1-0-raphael.img).
I could boot into TWRP using Power + Volume Up , wiped everything (except vendor) and pushed a custom rom to the internal storage.
I restarted the phone for some reason and cannot boot into TWRP anymore. Whatever I do, I end up in fastboot. Tried to flash various versions of TWRP with the same result.
Can you guys help me out?
Edit: I flashed the corresponding Xiaomi fastboot image and repeated the process, same problem.
Edit: Solved by repeating again.
Click to expand...
Click to collapse
In future, don't wipe everything. You should only need to do the factory reset in TWRP, which will automatically wipe data, cache and dakvik. If you are flashing over MIUI then you will also need to format data.
There is almost never any need to wipe anything else in TWRP when doing normal custom ROM flashing.

"Unable to decrypt FBE device" I tried everything...

So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
fverdeja said:
So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
Click to expand...
Click to collapse
Try flashing the correct fastboot ROM for your phone, using the Mi Flash Tool.
Then don't wipe everything in future. Stick with wiping just cache, dalvik and data. It's very rare you will need to wipe anything else.
Try this tool to erase and decrypt your internal storage
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Than install rom using usb otg.

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.

Categories

Resources