Database Develop

Bootloader version 3.41 problems

I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34

I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.

how do you flash the old bootloader? if you don't mind me asking.

I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.

ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus

You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063

I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.

anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.

Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse

Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.

[Q] stock 4.2.2 - how to root ?

Can someone please help with this ?
I'm want to flash the stock recovery in order to receive the 4.2.2 OTA update (currently I have the stock 4.1.2 + root + TWRP + S-OFF)
Can someone guide me please, what stock recovery do I need to flash and where should I grab it from ?
I've found only this link http://forum.xda-developers.com/showthread.php?t=2158763
Not sure if is the right recovery but the download link from there is broken
Any idea if I need to be S-OFF or ON in order to receive the OTA ?

That's old thread. Run either a ruu or Mike's stock. Be sure u have stock recovery as well.
Sent from my HTC One

where can I have the stock recovery ? (I can't find it)

- Ok after a lot of digging around I've found a stockrecovery.img file , so I've flashed that like this: fastboot flash recovery stockrecovery.img
- the spooky part after doing this was that I was unable to enter into recovery anymore , the screen alway remained in Entering Recovery and that was it ... maybe someone explain why ?
- then I've locked the bootloader like this: fastboot oem lock
- then I've installed a RUU for Europe (also found out here after diggin around) which actually downgraded my firmware to an older version
- after downgrade I've received an OTA update to a newer firmware - did that
- then after I've received the 4.2.2 OTA update , finaly
- then I've performed a bootloader unlock
- then I've flashed a TWRP recovery image in order to root the device
Now here comes the issue, after flashing the TWRP recovery image, while entering into the TWRP recovery I'm not able to click on any menu , is like the touch screen does not take any input so I'm unable to install the SU binaries
Has anyone encountered this issue ?
How did you root your stock 4.2.2 device ?

Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.

dinoc said:
Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.
Click to expand...
Click to collapse
Hi there,
i have the exact same problem, the screen wont register touches. How do i reflash CMW? im a noob

You are going to flash it in the same manner you did with the TWRP.
You put your phone into fastboot then issue a command like :
fastboot flash recovery cwm_image_name
You should search for a cwm recovery image file.
And you need to have the bootloader unlocked

After update to 4.2.2 TWRP wont recocnize touch due to the driver update.
Here is a modified version of TWRP where touch work with 4.2.2 OTA
Download and rename it to howdoyouwant.img then
fastboot flash recovery howdoyouwant.img
fastboot erase cache

Help plzz..

Whenever I try to flash anything or do anything like wipe or backup using twrp 2.8, the phone got restart automatically between the process without doing the task Complete...

Upgrade to version 3.x or reflash recovery via fastboot

I have flashed recovery via fastboot, recovery 3.0.1
But it also turning off the phone while flashing cm12

if you have twrp backup try to restore.........
if not...... flash stock firmware via fastboot

I do have a twrp backup while restoring process it turns off, when it restored 50% it automatically booted and turned off..and if I ll flash stock rom using fastboot then I have to relock bootloader and twrp also will be replaced with stock
...

you don't have to relock bootloader.....i've done this before

Without unlocking bootloader???
Can u plzz tell my step by step how to flash stock rom in unlocked bootloader via fastboot mode??

follow this
http://forum.xda-developers.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1064-restore-t2957167

A Stock ROM and Bootloader that will leave bootloader unlocked?

As per another thread, I am having issues (bootloops at the android/moto logo screen) after replacing my Turbo screen. I am unlocked and rooted. I know this cause I was before I replaced the screen (used Sunshine) and had RR custom ROM installed. Still unlocked because I can get to the bootloader screen (Power + Vol Down) and it says "Phone is Unlocked. Status code: 3".
To try to at least get a booting phone: Is there ANY stock ROM and Bootloader that I can flash that will still keep my phone UNLOCKED? I don't want to re-lock it and then have it locked forever (which I think the latest stock updates does). I am thinking that if I can flash a stock bootloader and ROM, then I can reflash TWRP and custom ROM (and get rid of the bootloop).
I would assume that if I had put something together incorrectly then it wouldn't boot at all and I wouldn't be able to get to the bootloader screen.
Thanks for any info/advice.
P.S. I did try just reflashing TWRP but it still bootloops at the same point; and I can't get into recovery.

So, when you boot to bootloader (Phone off, then power and volume down button at the same time), and you then arrow up to "recovery" when you push the button to go there, what happens? Is TWRP not still installed or something? the only reason it wouldn't be installed is if you flashed stock firmware and wiped it out with stock recovery.
Use the hardware method
First of all, you have to turn off your phone.
Then, you need to press Volume Down button and hit power key.
Bootloader mode will be then displayed on your device.
From there, use volume up and down buttons in order to scroll up and down and power key to select.
Click to expand...
Click to collapse
________
If your Droid Turbo bootloader is unlocked, flashing stock firmware with bootloader won't lock it. The newest firmware is to PREVENT the bootloader from being unlocked by Sunshine. It won't lock it back.
However, with stock Marshmallow you will have to re-root with older SuperSu beta for initial root. Flashing with newer SuperSu causes bootloops. After you have initial root then you can update to newer SuperSu.
But first tell me what happens when you try the hardware method of getting to recovery.
____
---------- Post added at 12:40 PM ---------- Previous post was at 12:23 PM ----------
_______
also you can force the phone to boot to TWRP, even if you don't have TWRP installed on the phone...
fastboot boot recovery.img
Where "recovery.img" is your TWRP file on you PC.
if you named it TWRP.img, then the command would be
fastboot boot TWRP.img
If you need to force the phone to go to the bootloader, the commad is
adb reboot bootloader
and then from there
fastboot boot recovery.img
(where "recovery" is whatever you have named the TWRP file.)
It's basically "temporary" TWRP. It doesn't install TWRP, but makes your phone boot to TWRP from your bootloader screen. It uses the TWRP file (whatever you have named it) from your PC folder. You then will boot into TWRP, can install stuff, make a backup, whatever you want to do. From TWRP, you can even install TWRP!
But you can reinstall your custom ROM, or you can restore a backup -- whatever you want to do from the "temporary" TWRP.
I used this a couple of years ago to use TWRP to make a backup of STOCK Kitkat image. I was booted into TWRP but TWRP was not installed on the phone. The phone was still pure stock, so I could easily make a backup image.
Then I rooted the phone! And made another backup image. It was rooted stock, still with no TWRP installed.
And then last I actually installed TWRP, was rooted and made a backup of that. And posted all those images for people to use. But a lot of people forget that you can BOOT TO TWRP even if TWRP is not installed on the phone. And that "temporary" TWRP (one session) will still allow you to do anything you want.
It's a useful trick to know!
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274

Recovery Bootloop

So I successfully unlocked my bootloader and flashed custom ROM and recovery, first boot it was okay, I was able to setup Android and installed apps, now when I rebooted it, it only boots to recovery. Phone can still be detected by my PC, can also get detected in fastboot when in bootloader. So I think there's really a workaround for this I just didn't know how and I am now hesitant to follow web tutorials if it isn't an official forum just like this.
Things I already did:
Reinstall ROM
Reflashed custom recovery
Cleared Data/Dalvik/Cache
Factory Reset

Flash the stock firmware by SP Flash Tool, it'll help to revert back to stock and stop boot loop!