Hello guys
A friend of mine was flashing some roms to try and when tried purity, the phone went inot a black dead screen
Recovery was working,but bootloader gave only black screen and no fastboot commands were working/accepted
THe, maybe for miracle, after reflash a cyanogen rom, the rom has booted and is working.. but sstill no bootloader
He was on stock 4.4.3 before the flashes
Someone can provide me a solution to restore the bootloader or,at least, fastboot commands??
He use TWRP recovery
thanks
bootloader its there , since its the one who starts the kernel/recovery,its more low level than kernel, it controls the buttons etc... .
for some reason its failing to boot into fastboot mode, try using adb reboot bootloader (looks weird to do, but on early nexus 7 2k12 bootloader there was some problems that doing this would do the trick, also do it while system is running or in recovery), if still goes black screen, re flash bootloader using dd comands in the recovery(there is a thread to fix no bootloader things, look at it)
I don't know if it is the case. But it could help you...
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-images-lg-t2713833
erto90 said:
Hello guys
A friend of mine was flashing some roms to try and when tried purity, the phone went inot a black dead screen
Recovery was working,but bootloader gave only black screen and no fastboot commands were working/accepted
THe, maybe for miracle, after reflash a cyanogen rom, the rom has booted and is working.. but sstill no bootloader
He was on stock 4.4.3 before the flashes
Someone can provide me a solution to restore the bootloader or,at least, fastboot commands??
He use TWRP recovery
thanks
Click to expand...
Click to collapse
If the rom was not working and the bootloader just showed black screen and didnt accept fasboot commands, then how on earth you entered recovery to flash cm11?
Because there is only 2 ways to enter recovery:
1: From bootloader you select "reboot recovery"
2: you have a working android and and do the adb reboot recovery command.
Can you tell me how you enter to bootloader? If you press all the buttoms when the phone is on state then the phone goes to qualcomm's download mode, and show a black screen. If you were doing that then now try to press only the volume_down and power buttoms to enter bootloader mode (or fastboot mode)
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
If the rom was not working and the bootloader just showed black screen and didnt accept fasboot commands, then how on earth you entered recovery to flash cm11?
Because there is only 2 ways to enter recovery:
1: From bootloader you select "reboot recovery"
2: you have a working android and and do the adb reboot recovery command.
Click to expand...
Click to collapse
Yeah... I want answers.
DVTeixeira said:
Yeah... I want answers.
Click to expand...
Click to collapse
But I need answers first
Tapatalk-kal küldve az én Nexus 5-el
This is the tread
that opssemnik mentioned http://forum.xda-developers.com/google-nexus-5/help/how-to-fix-bsod-bootloder-t2763370
it could help.
Extract the bootloader file from the factory image and flash it using the secondary bootloader (volume up and down + power).
Related
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!
I'm kind of screwed and It's not even my mistake, I guess.
I clean flashed the Mahdi Update 25/04 yesterday earlier I had 03/03. In the morning I experienced 2 -3 random reboots and later only one random reboot after which my phone won't boot (bootloop). When i enter bootloader, it automatically selects "start" and boots into system and then reboots.
Once i got the chance and my phone booted fully. But then when I selected reboot into recovery so that i can restore a NAND. IT reboots, the team win logo shows up and then the cycle repeats.
Basically, i don't have access to recovery, my bootloader isn't stable (i.e. it automatically boots without selecting) so I'm unable to flash a stock img as of now. If and when my Nexus fully boots into system it stays the same for about 1 hr if i have any luck. PLz help.
From India. Unlocked Bootloader and custom Rom "Mahdi".
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
First thing don't panic. You can't brick a nexus. You should be able to get into bootloader (volume down + power button) use Wugs Nexus Root toolkit from XDA forum. reload stock ROM in fastboot mode. I have done this lots of time. It's a draw back to being a tinkerer just can't leave well enough alone.
It sounds like your power bottom might be stuck to be honest.
Sent from my Nexus 5 using Tapatalk
nyterage said:
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
Click to expand...
Click to collapse
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
scuccria said:
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
Click to expand...
Click to collapse
To use adb pull you have to enter the recovery. You need universal naked usb driver 0.73 to make adb work in recovery. If you are on windows 8 or 8.1 you have to turn off the driver signiture enforcement befote installing the universal naked usb driver 0.73
Tapatalk-kal küldve az én Nexus 5-el
El Daddy said:
It sounds like your power bottom might be stuck to be honest.
Click to expand...
Click to collapse
I agree. It's a malfunctioning power button due to several reasons (moisture, drops, etc.). I had this on my Nexus S.
So I have my bootloader unlocked, but for some reason I can't flash a recovery (CWM or TWRP). I've tried to flash recovery through fastboot using adb fastboot commands, mfastboot commands, and mototool aio. I've also tried to flash recovery through rom manager and rashr. ( I am rooted )
cmd: getvar:max-download--size
cmd: download:007b1800
cmd: flash:recovery
mismatched partition size (recovery)
Click to expand...
Click to collapse
I get
Boot up failed
Click to expand...
Click to collapse
Whenever trying to enter recovery afterwards. I get the warning bootloader unlocked motorolla screen for .1s before going back to fastboot.
Can anyone point me towards what I should be doing please? Thank you
Is the phone being detected when you type "adb devices" in cmd window ?
If not you need to install correct and drivers, then in while in the boot loader type "fastboot flash recovery RECOVERYNAME.img" obviously you change it to your Recovery's image file and it has to be in the directory with adb and fastboot of course.
Sent from my Nexus 5
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
kdbrown5 said:
Yes it is, it is detected as the phone boots ( it still boots to the stock rom ) and detected in fastboot as w ell.
edit:
to clarify, this is on 4.4.3 if it matters
Click to expand...
Click to collapse
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
kdbrown5 said:
I guess I didn't look up as well as I should have. So even with an unlocked bootloader, there are no recoveries out for 4.4.3 ?
Click to expand...
Click to collapse
Yeah, of course there are recoveries for 4.4.3/4.4.4. Try to flash another recovery bro
Sent from my Moto G using XDA Premium 4 mobile app
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
kdbrown5 said:
I've tried like 5 recoveries so far. i just tried cwm 6.0.4.5 and now i can't even get into the bootloader, (adb reboot recovery, as well as holding recovery keys at phone turn on) just goes into the rom now. Does it sound like i have to recover everything to stock now?
Not sure that it matters, but I am rooted if that helps or gives you ideas for any other options
edit: through rom manager i was able to reflash the latest CWM and now i have bootloader access back. I still can't get into any recovery though.
Click to expand...
Click to collapse
You can try to go back to stock, and after, flash a custom recovery and see what happens
Sent from my Moto G using XDA Premium 4 mobile app
Ok, I guess I'll try that tomorrow. The thing I'm wondering is, If it doesn't work flashing through fastboot, outside of the ROM, how would reverting back to stock help at all? A stock flash shouldn't change the bootloader at all?
bump : (
I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not:
Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there. Stupid problem to have right here, lol.
Any thoughts/help is appreciated. TIA.
Okay, so I got around the issue. I'm not sure if TWRP is supposed to be able to fastboot or ADB but mine would not, I was under the impression that I could fastboot or ADB in recovery. Maybe that was just a mistake on my part thinking that.
My workaround:
- Reboot into the bootloader (not TWRP recovery), 3 finger reset, power off, then power button + vol up + vol down until you get the OEM Android bootloader screen (unplug if plugged in, it didn't seem to want to go into bootloader when it was plugged in - maybe I just didn't wait long enough, but unplug if it doesn't want to go into the bootloader).
- From here I was able to fastboot, "fastboot devices" listed it
- I then flashed the bootloader: "fastboot flash bootloader bootloader-hammerhead-hhz12h.img" (may differ if you wan to flash different bootloader)
- I then rebooted into bootloader: "fastboot reboot-bootloader"
- I then flashed recovery: "fastboot flash recovery openrecovery-twrp-2.8.5.2-hammerhead.img" (may differ for different version of recovery)
- I then used vol up/vol down to select "reboot recovery", and hit the power button
- TWRP booted and from there, now that I have the hhz12h.img bootloader flashed I could install the ROM, so I wiped data/dalvik/cache/system again, installed the ROM, installed Gapps, and rebooted, good to go.
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Primokorn said:
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Click to expand...
Click to collapse
Got it. For whatever reason I could not get ADB to see the device while I was in TWRP. I tried the ADB sideload feature in 'advanced' but it just waited and waited and waited forever. I believe ADB is set up properly on my system because it works fine on ROM. Not sure what the deal is with that, but I don't have much reason to go into ADB in recovery anyway aside from this issue, so it's [hopefully] not a big deal.
As for flashing the recovery, yeah, bad habit I guess. On my old phone (Fascinate Galaxy S 1), if you had custom recovery and had to 3-finger reset to bootloader because your phone wouldn't turn on or was bootlooping or whatever the recovery was boned, had to re-odin flash it. So it's stuck in my memory now that if I had to 3 finger it I better flash recovery. I'll try to knock myself out of that habit .
Thanks!
Syndacate said:
Is there a TWRP zip-install hhz12h bootloader I can use?
Click to expand...
Click to collapse
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Wakamatsu said:
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Click to expand...
Click to collapse
Thanks, I'll snag that just in case I ever have a fastboot outage or I'm on a system w/o ADB/fastboot or something.
ldubs said:
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Haha, I didn't even look at the dates, I just went to the "Tools/Utilities" page for the Nexus 5 and it was the top link....I didn't think too much on it, just figured top link = most recent = latest.
http://forum.xda-developers.com/showthread.php?t=2511507
I'll dig around for a thread which has latest and flash that on there, can't expect old versions to work flawlessly, now can we?
EDIT:
That actually might have just been a copy/paste error on my part, as I had the old TWRP lying around for fastboot and copy/pasted the name from that. I used TWRP (ROOT) app to install and I chose latest (or so I thought). Now I have literally NO idea which one I was using -_-.
No worries glad you got it sorted. You can flash an image file in twrp now BTW.
Sent from my Nexus 5 using Tapatalk
I was trying to get the latest twrp '2.8.7.2'. I downloaded it and flashed the img to recovery and nothing seemed to happen so I tried flashing it to boot then I tried to reboot the system. Now when I try to turn it on I get stuck on the Google like it is turning but it just gets stuck. I tried Charging it now when I charge it I get stuck on the battery logo. When I try booting it Booting it into recovery(twrp) I get a black screen. I can tell the Screen is on because of the dim glow it gives off but it is not doing anything. Note: I am some what of a noob when it comes to this stuff, My nexus 5 was running Marshmallow, and I was running the Xtra smooth rom (it is very close to stock). Plz help. I have also just found out that the reason im getting the bootloop is I flashed the wrong version of TWRP need a fix PLZ HELP.
Did you try flashing stock recovery or twrp 2.8.7.1?
audit13 said:
Did you try flashing stock recovery or twrp 2.8.7.1?
Click to expand...
Click to collapse
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Judah04 said:
I cant flash anything because it is stuck. If you can tell me how to do that it would be great. also I gave you the thanks thing.
Click to expand...
Click to collapse
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
When i boot into recovery mode the screen is on but it is black.
asawoszc said:
All you have to do is boot into your bootloader (Power + Volume Up + Volume Down at the same time) and flash the stock recovery.
fastboot flash recovery recovery.img
Chances are you flashed an incorrect version of TWRP meant for another phone hence the boot loop.
Click to expand...
Click to collapse
Also yes i do think I flashed the wrong TWRP. how do I flash the correct TWRP when I can't even get back into a tool to flash it?
Judah04 said:
When i boot into recovery mode the screen is on but it is black.
Click to expand...
Click to collapse
You dont need recovery, you need bootloader.
telep said:
You dont need recovery, you need bootloader.
Click to expand...
Click to collapse
Can you please explain to me exactly what to do. thank you. also my bootloader is unlocked. I also can get to fastboot so what is the diffrence between bootloader and fastboot.
Hold down the volume +, volume -, and power button. You'll be taken to a screen with the word START at the top. Now, connect the phone to your Windows computer using the USB cable, open a command prompt and type "fastboot flash recovery nameof twrpfile.img", press the enter key, use the volume button to select recovery, use the power button to enter recovery, press the power button, press volume + button, and you should enter TWRP.
Thank you but I do not own a windows computer
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
wangdaning said:
Then look up the respective commands. You flashed twrp over your kernel, you need to flash a proper boot.img (kernel) if you want the phone to boot. Fastboot is ran through bootloader. Flash the proper kernel in bootloader using fastboot.
Click to expand...
Click to collapse
Thank you this sounds like it will work. But can you put it in more simple terms and give me links? plz. thx in advance.
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
audit13 said:
Do you have a computer?
Click to expand...
Click to collapse
I have a macbok air running mac os x 10.5.8.
audit13 said:
Do you have access to a Windows computer to flash the commands? How did you flash TWRP?
Click to expand...
Click to collapse
I flashed TWRP using the TWRP app it installed TWRP 2.8.7.1 I also unlocked the bootloader with a similar app.
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
Just cheked it out I tried it and it didn't work but thx anyway. btw I am running android 6.0.
audit13 said:
This might help: http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
Click to expand...
Click to collapse
It might not have been working because I did not enable USB Debuging. :crying:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
audit13 said:
USB debugging is required for adb commands. With fastboot mode, debugging isn't necessary.
Click to expand...
Click to collapse
Can you please walk me through this i am some what of a beginner when it comes to some of these things. I can try the tool kits agin but need help.