After hearing about the US government and ZTE fiasco, I decided to bite the bullet and install a custom recovery and custom ROM. However, during the process of changing the filesystem of the /data partition, my phone randomly rebooted. Now, TWRP and my custom ROM won't start. I tried going into fastboot mode and re-flashing TWRP, but to no avail. Any help would be much appreciated.
Probably a silly question, but is the bootloader unlocked?
JPJack9 said:
After hearing about the US government and ZTE fiasco, I decided to bite the bullet and install a custom recovery and custom ROM. However, during the process of changing the filesystem of the /data partition, my phone randomly rebooted. Now, TWRP and my custom ROM won't start. I tried going into fastboot mode and re-flashing TWRP, but to no avail. Any help would be much appreciated.
Click to expand...
Click to collapse
uhh, EDL? Lots of EDL
Try reflashing TWRP via EDL, if it doesn't work just reinstall the whole stock ROM though there
Related
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good
Hi!
I made a terrible mistake. I do not know how to solve it. I have been browsing dozens of pages and I am completely stuck.
I flashed a rom with odin and I ticked “Nand Erase All”. Yes, I know what I am, but don’t tell me. Well, after flashing the rom the phone is stuck on Samsung logo. And no matter what you do, it is always stuck on Samsung logo.
I have re-flashed several stock roms and in all possible ways (repartition, pit…), according to what I have read.
And I can’t boot into recovery, only into download. I have read that from recovery, a system format and wipes could solve this problem. But I can’t get into recovery. I have flashed different recoveries: Philz, CWM, TWRP. And no way, it is impossible to boot into recovery.
Please any help appreciated.
perevales said:
Hi!
I made a terrible mistake. I do not know how to solve it. I have been browsing dozens of pages and I am completely stuck.
I flashed a rom with odin and I ticked “Nand Erase All”. Yes, I know what I am, but don’t tell me. Well, after flashing the rom the phone is stuck on Samsung logo. And no matter what you do, it is always stuck on Samsung logo.
I have re-flashed several stock roms and in all possible ways (repartition, pit…), according to what I have read.
And I can’t boot into recovery, only into download. I have read that from recovery, a system format and wipes could solve this problem. But I can’t get into recovery. I have flashed different recoveries: Philz, CWM, TWRP. And no way, it is impossible to boot into recovery.
Please any help appreciated.
Click to expand...
Click to collapse
Take a look: HERE.
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
I tried installing Lineage 14.1 last night, and cannot get past recovery screen now. Not sure what else to do, as I've formatted data and cache both to ext4, and have updated back to TWRP 3.0.3. Any help would be greatly appreciated.
I can still get adb and fastboot to recognize the phone, so that seems to be a good thing. But every time I reboot, I just see the ZTE logo, and then it boots into TWRP.
Format system as ext4 and make sure to be on twrp 3.0.3-1
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Twiggy000b said:
Format system as ext4 and make sure to be on twrp 3.0.3-1
Click to expand...
Click to collapse
Thank you. Will I need to completely reinstall the rom and gapps again after updating TWRP? I'll have to get to a computer again and give it a shot.
P.S. Would have quoted your post in the Lineage forum, but lost my old account information and couldn't post under Development. So, out of curiousuty, how much trouble did you have with this?
xtermmin said:
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Click to expand...
Click to collapse
I did. But am scared that I may have panicked and reinstalled it again. Hoping that won't cause any more trouble for me. Have had to revert to a backup iPhone, and am hating it. Lol.
Updating TWRP worked.
Setting the ROM up now, just had to get back to a computer and try updating recovery. Thanks for the help.
So far there's only a small sample, but I think there's enough of a pattern to constitute an issue. I've tried to flash the latest of both pixel experience (unofficial) and havoc, and each one sends me directly to either recovery or fastboot, depending on the order which I flash/wipe/factory reset. It's been a couple months since I've flashed anything other than an open beta update, but I never had any issues flashing ROMs.
For both I've tried:
Flash OOS. 9.0.13 (or OB13) in both slots
Flashed Twrp installer
Reboot to recovery
Flash custom ROM
Flash Twrp installer
Factory reset (tried full wipe as well)
It's at this point where I attempt to reboot to recovery to flash gapps (for havoc, not PE) I get sent to recovery or fastboot, depending on whether I reset or wipe data.
I can flash OOS and boot stable or open beta and boot into them with no problems. I've even allowed it to boot to the OOS welcome screen and went back to recovery to flash the custom ROM with the same outcome, doing a factory reset before I flash, after I flash, reboot to recover after flashing to factory reset. I've tried a full wipe in place of factory reset and all different combinations, all with the same result...
What am I missing?
lordcheeto03 said:
What am I missing?
Click to expand...
Click to collapse
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
pbergonzi said:
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
Click to expand...
Click to collapse
Everywhere I've read says to flash OOS to both partitions so if there's an issue with the custom ROM there's a fallback.. I don't flash the custom ROM to both partitions, only OOS. Also, I've tried letting OOS boot to the welcome screen, then back to recovery; I didn't do any setup.
I have magisk installed in OOS, though I haven't tried flashing it when flashing the ROMs. When flashing ROMs I've always flashed the ROM and Twrp, reboot straight to recovery, and flash gapps/Magisk. In my experience, I've been able to skip rebooting back to recovery to flash Magisk and gapps and just boot straight to the barebones ROM.
To reiterate, I use the exact same process to flash OOS and it works flawlessly; can flash the stable or open beta, no issues. It's only non-OOS that refuses to work correctly.
I'm wondering if I need to use the unbrick tool and start from a 100% clean slate .. something may be borked that an unbrick may fix, it's about the only option left that I can think of...
lordcheeto03 said:
Everywhere I've read
Click to expand...
Click to collapse
Good luck whatever you do.
pbergonzi said:
Good luck whatever you do.
Click to expand...
Click to collapse
Thank you for the ideas
I ran the unbrick tool and still encountered the issues, but I did learn something, and also finally got havoc to boot, although I'm still unsure exactly what I did. I'm not saying I figured out exactly what is wrong, and I can't say I know the exact solution, but I CAN say I believe the solution lies somewhere within this wall I'm typing.,..
I noticed this earlier but it didn't actually click until I still got the same error after the unbrick tool... I would always boot correctly to OOS on slot b, so after every successful boot, I'd go into recovery and try flashing.. now taking into account the fact that I flashed OOS in both slots is important because on a successful boot, which would be slot b, I'd go into recovery, still on slot b, so that's the first slot to get OOS. Change slots, flash to slot a, then boot to OOS. If I'm remembering how a/b partitions go, since slot A was the last slot to flash, it would automatically fall back to slot b to boot. Hence the successful boot. Go back to recovery, flash havoc on b, it would attempt to boot from a, and fail.. go back to recovery, I'm back on slot b to start the process over.
After still encountering the problem after the unbrick, I really began paying attention to the boot slots. Once I was paying attention to that, I attempted to manually boot from slot a after flashing OOS to both slots and I got sent to a screen that says Qualcomm crashdump mode. Power +vol up/dn to force a reboot, then volume down until the bootloader unlocked splash screen to go to recovery.
Now this is what I think I did... After figuring out it was the slot, I believe I formatted slot a, and due to the way it fell, slot b then began being the slot to mess up so i made sure to flash havoc/twrp installer in the slot a and it booted right up. Went back to recovery to flash magisk and gapps, and finally a factory reset. Boot from slot a, and here I am.
There were times where I would get stuck in fastboot, boot to recovery or system would just send me to fastboot.. I guess that also meant I was booting from the bad slot. I tried fastboot boot twrp.img, it would send it, but fail to authenticate. Fixed that by doing fastboot --set-active=b then I could restart back to recovery no problem.