TWRP/recovery wont boot - Nexus 7 Q&A, Help & Troubleshooting

I have noticed a few people including myself who have had TWRP or the recovery partition some how corrupted after flashing a 5.1/5.1.1 kernel or rom.
Usually what seems to happen is that a 5.1 kernel/rom is flashed (data/cache f2fs for me) which leads to a bootloop. Restarting to bootloader and on to recovery ends up with twrp not loading.
I've noted that this has happened for me with mkernel a75, and also to a user flashing the latest phantom alpha, and to someone who flashed optipop which uses the latest lean kernel.
Flashing twrp again did not fix for me, had to flash the latest factory image.
I have only noticed this after android 5.1 and only on grouper. Anyway, I was just wondering if others are running into this issue. Maybe we can figure out what going on.

I had the same issue when I fully reset the device, it wouldn't even load stock recovery. Flashing TWRP again solved my issue so I can't speak to why it would not flash for you.

Related

Flashed wrong kernel. No touch anymore?

Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.

Stuck while flashing Rom zip [solved]

I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.

Stuck in bootloop in all LOS and OOS based roms

Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state

Lenovo zuk z2 plus vibration died [SOLVED]

I haven't found any references to this and i'd like to share.
I'm on a custom ROM and unlocked bootloader with TWRP installed. I was on my ROM for two months without any modifications. The only things I had tampered with recently were flashing twrp 3.2.0 by the twrp app and flashing an update to my ROM. Two days after that, my phone's vibration went dead.
I did a factory reset (wiped data/davlik/cache)
I clean flashed my ROM
I clean flash a deoexd stock ROM
And i clean flashed again my original ROM.
Nothing fixed the problem and before flashing the stock ROM by qfil, i backed up my ROM's kernel (boot img) by TWRP (idk why I did that) and the problem was fixed out of the blue.
If anything similar occurs give it a try and backup your kernel.
(I didn't flash the kernel again. Once the backup was finished, the problem was magically solved)

can somebody explain flashing roms on a/b devices?

I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Joe199799 said:
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Click to expand...
Click to collapse
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
farhan20 said:
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
Click to expand...
Click to collapse
I flashed OOS 9.0.12 yesterday because I switched ROMS with 9.0.11 and it resulted in a msm flash, turns out switching roms from 9.0.11 is a bad idea. But after updating I flashed havoc OS and everything is all good. We appreciate the answer I understand it a little better now
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good.
Click to expand...
Click to collapse
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Nsane457 said:
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Click to expand...
Click to collapse
That was a very well written and insightful answer thank you. The way you wrote makes everything much easier to understand
I think with the new TWRP recovery flashing is about to be less of a d**k. TWRP 3.3.0-0

Categories

Resources