Database Users

Help installing 4.1.2

Hi folks im trying to get my google nexus 7 to reboot into recovery mode but no matter what i do it just wont work, i have tried using adb and then using the command "adb reboot recovery" but when it goes to holding down power button and higher volume button ( I have tried other combinations too) nothing happens, it just seems to reboot. Does anybody have a way around this ? Seriously frustrating.

Unfortunately the new bootloader doesn't work correctly on your device. You have to replace the bootloader with the one from the previous version 3.34

I had rooted and installed CWM recovery early on. I installed Rom Manager (free version) and opened it and Flashed Clockwork Recovery. From then on and now with 4.1.2 installed, I can choose Reboot into Recovery from Rom Manager and I go right to CWM recovery. That's what I did to install 4.1.2 after installing Voodoo OTA Rootkeeper. I updated successfully and kept root through the update. I never had to do anything like replacing the bootloader with an earlier version.

Ditto, I got bored waiting for the ota to kick in. Just downloading the update from Google dev then flashing with CWR I just said yes to the don't install new boot loader and retain root worked seamlessly!

Just upgraded to 4.3

So I upgraded to 4.3 from 4.2.2. I followed this guide (http://forum.xda-developers.com/showthread.php?t=2378413&) except with TWRP recovery. It was going according to the guide but it never asked me if I wanted to keep root or recovery. It rebooted just fine but when I shut down and tried to go back into recovery to flash SU I get an android with a red triangle exclamation mark.
I assume this means that I lost TWRP recovery. I'm relatively new to this, so could someone explain to me how to get a custom recovery back? I assume after I get the recovery back that I can flash SU again and regain root. If it matters, my bootloader is still unlocked.
Thanks

mikey331 said:
So I upgraded to 4.3 from 4.2.2. I followed this guide (http://forum.xda-developers.com/showthread.php?t=2378413&) except with TWRP recovery. It was going according to the guide but it never asked me if I wanted to keep root or recovery. It rebooted just fine but when I shut down and tried to go back into recovery to flash SU I get an android with a red triangle exclamation mark.
I assume this means that I lost TWRP recovery. I'm relatively new to this, so could someone explain to me how to get a custom recovery back? I assume after I get the recovery back that I can flash SU again and regain root. If it matters, my bootloader is still unlocked.
Thanks
Click to expand...
Click to collapse
flash twrp recovery via fastboot

[Q] Problem with TWRP in rooted and unlocked nexus 10

Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english

The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.

3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..

All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...

prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app

same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.

[Q] Help with 4.4.4 OTA

I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len

If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492

sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP

Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.

Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.

charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse

charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks

Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505

[Topic can be closed] Phone can't find bootloader? and i can't flash TWRP

Hi all,
I got some strange problem:
I did an ODIN reinstall of complete OREO stock samsung ROM.
I swiped in twrp but i didnt want that so i reflashed twrp with odin.
Then i got a red screen while i wanted to enter TWRP. I retried flashing, no luck still a red screen. Also older versions.
I do however seem to be able to boot into samsung recovery mode.
I tried to flash twrp with adb. But my phone will not boot into Bootloader mode? It just restarts?
(as i understand, Bootloader mode is NOT download mode right?)
It is soft brick something?
Any help would be appriciated very much.
Thx!
Mrmoves
EDIT: I just found out im on Bootloader 3.
I have flashed the newest OREO a lot of times now with ODIN. Its works. Going into recovery works as well.
Still not able to boot into bootloader, or install TWRP for some reason?
EDIT2: I fixed it!. i flashed the newest OREO for the 5th time or smhting and for some reason i was also able to get TWRP on it again =)
Now rooted with Magisk all working =)
TOPIC CAN BE CLOSED