Best way to reinstall recovery? - G2 Q&A, Help & Troubleshooting

I have the Tmobile G2 d801, with the modified rooted stock KitKat Rom posted by dr87. I tried to flash the zip for Philz recovery through twrp 2.7, but rebooting just brought me to the black screen that said something about Fastboot.
I rebooted back into the ROM and tried using Flashify to flash either one with the same result.
Tried flashing the extracted twrp recovery image using Rom Installer only to get a boot certification verify error and had to do a hardware reset to get the phone to boot back into my ROM.
Is there a way to get a recovery back on my device?

Trying to install the zip through twrp manager also results in a boot certification verify error, but I can boot back into the Rom via the hardware buttons. Any advice?

Never mind, I held my breath and tried Autorec, that fixed it

Related

[Q] Can't boot into recovery after flashing new CW 3.0.2.4 recovery help!!!

So... I was rooted using gfree method and had recovery 2.5.1.4 installed running the ice glacier rom. Then I decided i was going to upgrade to a gingerbread rom so I updated my rom manager and flashed the new CW 3.0.2.4 rom and now it wont boot into recovery. When I try to boot into recovery it shows the mytouch logo for a bit, the screen turns black and the phone reboots. I tried to flash the old recovery again but I get an error message saying: An error occurred while flashing your recovery. I can still flash CW 3.0.2.4 and CW 3.0.0.5 but both will not boot into recovery.
I also tried flashing the 3.0.2.4 recovery manually through fastboot flash recovery recovery.img but I still get the same problem. I couldn't find an active download link for the 2.5.1.4 recovery to try to flash manually so I don't know if it helps to do this.
I read on the forum somewhere to revert back to stock recovery using the stock PD15IMG IMG file and try again. This took me back to stock and I was able to boot into the stock recovery. Then i reran visionary for permroot again, deleted my clockworks folder from my sdcard and tried again, but the problem came back.... Mytouch logo then black screen then auto reboot.
My root access still works fine but I cant get into recovery to flash a new rom.... and now I am stuck on a stock rom. :[ After 6 hours of trying to fix the issue I'm still very confused.
Any help / suggestions would be appreciated Thanks.
Its doing this after you go into hboot and select "Recovery"?
JDV28 said:
Its doing this after you go into hboot and select "Recovery"?
Click to expand...
Click to collapse
Yes, from Hboot and from rom manager, but sometimes if i try from rom manager it will also hang at the white mytouch logo screen.
Update
Ok. So i have a partially functional recovery again i found the recovery image for 2.5.1.2 and flashed it using fastboot flash. I am now able to get into recovery again and install custom froyo roms, but every time i try to upgrade to a higher version like 3.0.0.5 or 3.0.2.5 no matter which method i use, I still get the same reboot while trying to get into recovery.
Please help. Thanks

[Q] Recovery boot fail after updating to 4.1.2

Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...

Lack of recovery

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!

Can not boot into TWRP recovery

Ok here's the situation: I had rooted and installed TWRP and a custom rom (2 actually). I had an issue where the rom is not compatible with my fav alarm app, so I tried to revert back to a stock rom. That's where the trouble began. I unfortunately don't recall the exact steps I took, but I can not boot into recovery either by the button method or the reboot into recovery method. I can always reboot into download mode with no problem. If I go into Odin and either try to reflash the twrp recovery or flash stock recovery (tried both of these multiple times) I can get the phone to boot back to the rom I am trying to uninstall. All I am trying to do is get into TWRP recovery. Any thanks would be appreciated.
T-Mobile G900T Marshmallow 6.0.1 baseband version G900TUVU1GPE1 Rom GROMV6

twrp recovery dissapear after flashing CM11

I succesfully installed TWRP when phone had stock ROM.
I booted into it, and i flashed CM11
And after that, i couldn't go into TWRP anymore.
I tried flashing diffrent versions of TWRP, and even CWM but still it doesn't boot into recovery
I tried to reboot advanced options, to reboot into recovery from CM11, but still, it doesn't reboot into it, it just hangs at "rebooting to recovery"
I know key combinations, because i flashed CM11 via TWRP, but suddenly it dissapeared.
I don't want to reflash stock ROM, because of this, in fact, i just want to flash zip file, fde.ai , but recovery is not available, so i can't flash it.
I tried flashify, and rashr, they all don't do their job as adversited.
So my only fix is , to somehow bring back TWRP into which i can't boot

Categories

Resources