Develop Bugs

[Q] HELP! Fastboot mode-no boot or recovery img, and can't unlock the bootloader

Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
I can get into download mode, but as soon as the odin starts to flash the ROM, the program crashes.
I tried to erase the boot and the recovery images, but it just says "unknown partition".
Now, why all this did happen?, well I was trying to install the stock firmware that I downloaded from sammobile, and it never installed, the program crashed and my phone got... bricked????
If I could only unlock the bootloader it would be easier, i think.
Any help, please????

If fastboot & odin won't work the only other thing I know of is omap_flash.
[REF] efrant's "Android for Galaxy Nexus" 101 & FAQs
^^Look for the omap link at the bottom of the 2nd post ^^

[Q] can't unlock bootloader

The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?

doss2007 said:
The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?
Click to expand...
Click to collapse
I've seen posts like this here and in other forums gleaned from fairly extensive searching. Nobody has an answer. I think it's a hardware problem, to be honest. The N7 2013 is plagued with them, it seems.
Can you still boot into Android? You could try to root via towelroot. From there, you could flash TWRP, or maybe unlock the bootloader with that app from the play store.
I would send it back to Google, if possible.

Aerowinder said:
I would send it back to Google, if possible.
Click to expand...
Click to collapse
unfortunately i can't boot so i will try sending it back

You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.

HowardZ said:
You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.
Click to expand...
Click to collapse
The OP states that he was unable to unlock the bootloader. I was unaware that you could "fastboot" flash any kind of image without an unlocked bootloader! ; )

bricked phone

So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML

thehappyface said:
So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML
Click to expand...
Click to collapse
Hello guys what is the error in red text please??
You can go to your recovery or not?
Thank

quadeur06 said:
Hello guys what is the error in red text please??
You can go to your recovery or not?
Thank
Click to expand...
Click to collapse
It just shows me a dead android with the words Error! written in red text

thehappyface said:
It just shows me a dead android with the words Error! written in red text
Click to expand...
Click to collapse
For pass this error ..It's just a security ..Tap in the volume + and in the same time to the power button very fast And it's work !!

thehappyface said:
So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML
Click to expand...
Click to collapse
Hello there,
Few days ago, I had the same problem. But luckly I found a way to fix it. I was so desperate.
1) Download "CWM Zenfone_2_Intel"
https://www.mediafire.com/folder/w70...5840/Zenfone_2
Then unzip
2) Go in fastboot mode in your Zenfone 2, and connect it to your PC
3) In the downloaded folder, run "cai_dat_CWM.bat"
4) Type ACCEPT
Then Enter
5) Then if the script is blue, that's perfect. Type T4, Enter, and normally your Zenfone will reboot in CWM Recovery Mode.
6) If that worked, download the ROM stock on the Asus Website, copy it on the SD Card, then flash it from the CWM Recovery Mode.
This method fix my bootloop, but a brick I don't know...
If it didn't work, try to install "15 seconds adb installer"

Bricked my Oneplus 3

Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!

Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.

ghostofcain said:
Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.
Click to expand...
Click to collapse
I can boot it into fasboot and I tried flashing TWRP, OxygenOs and even Cyanogenmod. Still didnt work.

Didn't work how, are you getting errors in console?. Can you flash TWRP and boot into it?

You have successfully bricked your device.
Don't worry use a Oneplus download tool to download stock firmware to your device in download mode.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
The method 2 worked fine for me.
Go ahead..!!
Hope it helps

A bricked device is broken unable to be fixed, this is a soft brick as you can still get it to respond.
For future users if you broke something and want help please supply at least the following.
1. What you did, yes it's embarrassing but maybe someone can undo it.
2. What you are still able to do, can you access recovery, fastboot or adb.
3. What you've tried, if you try and flash something and get an error message let us know.
The more information you supply the better the chances someone can help. A simple my device is bricked help can't achieve much.

So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Edit: If your phone shows the boot messages "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" you need to fully reload your ROM over the unbrick tool. Look for Method 2 in Joyo-rockers link in this post (cant post links yet)

flobiwahn said:
So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Click to expand...
Click to collapse
Had the same issue, method 2 works fine.

Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...

kovacsabesz said:
Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...
Click to expand...
Click to collapse
You didnt download the right tool, method 2 includes every needed partition and should revert you to full stock 3.1.2

Oh,
Done.....
I fixed it! Thanks guys!

Deleted
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
sashamalla said:
Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!
Click to expand...
Click to collapse
Go to the folder where the recovery tool.exe is. Boot your phone into Fastboot.
Search for cache.img, system.img, system_aging.img and put them in your ADB file folder
Type this:
Fastboot devices > doesn't show up? No worries I'll help you later this day just let me now.
Fastboot flash system system.img
Fastboot flash system_aging.img
Fastboot flash cache cache.img
If it boots and you don't have Sim and WiFi. Then reflash Oxygen OS and don't boot it! Boot it into Fastboot and type:
fastboot erase modemst1
fastboot erase modemst2
Now boot it and u can do whatever you want!

Same happened to me, reinstall windows and start again with method two, was a driver issue

TheLoverMan said:
Same happened to me, reinstall windows and start again with method two, was a driver issue
Click to expand...
Click to collapse
Why would you install windows instead fix the driver thing.

Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.

This was already mentioned, as i remember. Just let me search for a minute cause i had this same issue.
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
Flash this TWRP, it is 3.0.2-19 for temporary but i use it as daily.

kovacsabesz said:
Oh,
Done.....
I fixed it! Thanks guys!
Click to expand...
Click to collapse
Hey! Im having the same problem. Please help me with the way you did, Im Stuck . please help

TheLoverMan said:
Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.
Click to expand...
Click to collapse
Ye well there is a driver enforce mode link even in the hardbrick guide... No need to reinstall Windows lol

I Unbricked Successfully
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?

Pratik121 said:
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?
Click to expand...
Click to collapse
You see.. OOS had force encryption. Go to Fastboot and type "fastboot erase userdata" then go to recovery and flash OOS or any other rom.. Password should be gone now.

Can't boot, stuck with "ID: bad key"

Hey guys, so I bought the phone and the first thing was unlocking BL. Then I flashed TWRP (or booted it via fastboot).
Then an accident happened and I flashed the TWRP image over the boot partition with fastboot, since then the phone does not
boot anymore.
I tried flashing the stock images from XDA here via fastboot, but that tells me that some preflash conditions failed...
When I try to start recovery or boot Android, I get the unlocked BL warning screen and "ID: bad key", then nothing.
I managed flashing boot.img and system via dd in TWRP but it does not boot either, something is messed up.
Bootloader tells be I have the montana XT1794 32GB P3 version (from Germany). I guess all firmware I tried may be
for a slightly different version...
I get these messages when flashing boot.img and others via fastboot:
Code:
(bootloader) Image signed with key bad key
or
Code:
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed

I by now means am any kind of expert with this. I too, am learning this on the fly, and only been at this a few days. But I will try to give some advice. (most will be useless advice because Im not 100% on my own experiances even now)
First, again, im not 100%, you may of messed up your OS totally. I have experiance reinstalling my OS from scratch. I have a moto g5s plus sanders phone. 7.1.1 nougat. I went through hell trying to flash my OEM rom. Finding it was a pain, installing it was even more of a pain. Now what monstly, not entirely worked was: --youtube.com/watch?v=-FszZOx2pWU for reflashing.
Also, --xda-developers.com/moto-g5s-plus/development/flash-official-firmware-moto-g5s-plus-t3681018 has some advice to reflash. Now I dont know at all if this is useful for you or not, im sorry The key for reflashing for me was the ADB fastboot files FINDING the right rom. The commands with the xda link...the ones that started with "m" dont work for me. I had to use the youtube commands. Now for me, this was VERY important, TO RELOCK YOUR PHONE. The command to "fastboot oem lock" was a must! If I didnt enable that I too got the message of bad key and never could load into TWRP. I had to reinstall my OEM rom AND relock the phone. Then go through the process again to root. Before rooting your phone, I hightly suggest you get an OS working either custom or original. And relock the phone in the process. That is key, relock the phone, dont keep it unlocked. At least for ME that was true.
Now shouldnt be to hard to find your OEM rom. (im not good enough for custom ROM'ing yet) Then again if its a germany specific phone might be hard. Again im sorry, I dont know.
Now as for the bad key. I too had much experiance with this, that I cant exactly explain how I overcame it. Basically I think youre not installing TWRP correctly that is the bad key message youre getting, i "think" the message should say "N/A" instead, Im not 100%! Once you install ur choice of root'ing (I prefer supersu over magisk. Both work) boot into recovery and install TWRP. If you have the root program of your choice installed install it now. Dont reboot, just load TWRP and install immediately. Now if you cant find your rooting program because you wiped it, didnt transfer it, whatever. You have to do that first. You must, must install root program first. I have a backup sd micro card, I had to format that PORTABLE NOT INTERNAL. With it being internal I had to many problems of apps not working correctly. It being portable made it easier to do anything. So "if" you need to reflash do so. Put root program on your phone however method you choose. I use MTP and install the .zips in both local and external memory.
Go into recovery, load TWRP..."fastboot flash recovery xxxxxxxxxxxxxx.img". Then boot into twrp with "fastboot boot xxxxxxxxxxxxx.img". Or just volume keys into recovery mode. Swipe to allow modifications (i hear that can be a bad thing if you do NOT have ur root program saved on the phone, I dont know) And find the zip and install. Youre done.
I hope this was a little help. If even a little of it is relevant, Im glad. Otherwise sorry that I couldnt help more!

I wanted to mention too "bad key" does not mean your OS is corrupt. Not all. If you did corrupt your OS, that wasnt twrp or rooted program.

Thanks for your reply. I got it working. I flashed the stock fw with mfastboot. I did not know about that before. After flashing everything to stock it worked again.