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.

Trying to get back to stock rom

Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.

Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'

need help, mucked up during installing cm11

I have a Sony Xperia Z1 and I have had cyanogenmod12.1 on my device for a little while now, but there are a couple of bugs and I wanted to go back to cyanogenmod11, so I downloaded the cm11 zip file onto my device and copyed it to the sd card,I then downloaded TWRP manager because the cyanogenmod recvoary does not have a zip file or flash part in the recovary, so I followed the procedures and then I flashed TWRP recovary. Once I got into the TWRP recovary I found the zip file for cm11 I then clicked flash. Not long later it said succesfull and then i had to reboot, i clicked reboot and this is where it whet wrong. My device then went into a bootloop because I left my device for 10mins. I then tried to access the custom recovary but it just came up with the sony logo and no custom recovary has come up since.

Jack Neilson said:
I ave a Sony Xperia Z1 and I have had cyanogenmod12.1 on my device for a little while now, but there are a couple of bugs and I wanted to go back to cyanogenmod11, so I downloaded the cm11 zip file onto my device and copyed it to the sd card,I then downloaded TWRP manager because the cyanogenmod recvoary does not have a zip file or flash part in the recovary, so I followed the procedures and then I flashed TWRP recovary. Once I got into the TWRP recovary I found the zip file for cm11 I then clicked flash. Not long later it said succesfull and then i had to reboot, i clicked reboot and this is where it whet wrong. My device then went into a bootloop because I left my device for 10mins. I then tried to access the custom recovary but it just came up with the sony logo and no custom recovary has come up since. Please help
-Jack
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to the right Q&A so that experts there maybe able to help.
-Vatsal

If you made a backup, flash dual recovery then restore the backup?
Otherwise flash stock and start again

The only solution is to flash your firmware and start from zero point
Since you said there is bootloop and no recovery
Or you can flash twrp img file through fastboot mode
But for safety flash is best

You do not need to do a fresh flash. Doing so without deselected some things might wipe data like photos.
1. If you don't already have the fastboot and ADB drivers, get them here
2. Download a kernel with recovery and extract the boot.img
3. Open up command prompt in the folder the boot.img is in
4. Make sure your device is turned off completely
5. Hold volume down while attaching it to your computer
6a. If you just want to have temporary acces to recovery type in this code:
Code:
fastboot boot boot.img
6b. If you want to keep acces and use the recovery after rebooting type in this code:
Code:
fastboot flash boot boot.img
7. Enter recovery the way you would normally do, backup your important files and/or flash the new rom and kernel you would like to use

Phone goes into fastboot mode after I reboot, can't get into system or recovery

My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?

I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site

Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com

Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually

I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...

OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.

Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good

Pixel 5 is broken after flash

Hello, I wanted to free my pixel 5 (android12) from google and install the e.foundation os. I managed to unlock the bootloader. At further step something must have gone wrong and I came only in the recovery mode. Then I flashed TWRP and wanted to install android 11 from there. I did not know which version for my phone is the right one. TWRP has any errors displayed. I have a few years ago on another phone made a custom rom flash on it and thought I know what I'm doing but thought wrong. I selected all the check marks in the wipe data menu and formatted everything. Then nothing worked and the phone went into bootloop. Now I managed to get into the recovery mode. But I can not flash TWRP or rom. Can someone maybe give me a tip? or do I now have a 500 euro expensive stone here.
I am grateful for any advice. this flashing is very complicated for me a I had it somehow easier in memory.
I speak german and the text was created with deepl
there is a photo of the screen

Okay you can try this
Download ADB AND MINIMAL FASTBOOT
Download TWRP
1. Open ADB AND MINIMAL FASTBOOT
2. Type fastboot flash recovery /path/to/twrp.img
3. Try reboot to recovery mode.
4. If you can reboot to recovery mode (TWRP) - Copy stock rom to device and flash it.

I have also tried this with TWRP but i always get the error message:
FAILED (remote: Not allowed to flash (recovery))
i have also tried several roms to flash after unpacking.
fastboot flash bootloader runs through
fastboot flash radio runs through successfully
fastboot update image but not
and ends with the message:
FAILED (remote: Partition should be flashed in fastbootd).