So i have a big problem, i acidentally downloaded the wrong kernel for my Nexus 5 (acidenttly got the nexus 4 versionb of Hells-core instead of the N5 version.) and flashed it, Now my phone wont boot nor can i access recovery or the bootloader. BUT when i plug it into my computer it tries to install drivers but fails because it cant find them, So im pretty sure its not a paper weight. Im running windows xp and was using carbon. If ANYONE can help please let me know.
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
Check this thread out it will probably help. If you can get into it you should be able to fastboot flash your phone back to working condition
Sent from my Google Nexus 5 using Tapatalk
grim489 said:
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
Check this thread out it will probably help. If you can get into it you should be able to fastboot flash your phone back to working condition
Sent from my Google Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i managed to get it into recovery as well as fastboot. but now when i try to do my recovery backup it causes the same error i was having i.e it would be detected by my laptop but i cant see anything. i may have to do a complete factory restore and see what happenes. Its kinda sad my GF with really NO android experience helped me get it into bootloader WHICH for anyone that has an issue similar to mine where your PC detects your device but you cant see anything on the screen hold down both up and down + power to get into bootloader. if it doesnt work at first hold down down + power (while its still connected to your pc so you can hear it feject) as soon as you hear the eject noise press and up down+up+power and you will be in bootloader
This guy had the same problem
http://forum.xda-developers.com/showthread.php?t=2746343
He dd'd his messed up partition back. I guess it's the bootloader that was overwritten but you can dd the secondary bootloader to the primary bootloader partition and it'd fix it hopefully.
Sent from my Nexus 5 using Tapatalk
grim489 said:
This guy had the same problem
http://forum.xda-developers.com/showthread.php?t=2746343
He dd'd his messed up partition back. I guess it's the bootloader that was overwritten but you can dd the secondary bootloader to the primary bootloader partition and it'd fix it hopefully.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
but i cant access adb shell because it tells me adb not found. so i dont know how to fix it.
NVM just went into recovered and then entered that command. Booted Right back up. Im going to make this a thread and HOPEFULLY it can get stickied. Thanks for all your help
No problem [emoji2] would you mind pressing the thanks button though? I'd appreciate it!
Sent from my Nexus 5 using Tapatalk
Related
Hey I'm in need of some serious help. My power button no longer works. It's as thought the phone thinks its constantly being held down. (Put battery in phone boots up by itself). I'm pretty comfortable with flashing roms etc and I need to get the bootloader locked for my warranty. I've tried multiple ways (I've done it in the past for friends). The 'fastboot oem lock' in fastboot via cmd doesnt work. It appears to be due to the power button being held down. It wont progress any further. It is not physically jammed (trust me ive tried fidgeting with it lemme tell you). I'm at a loss. Any ideas?
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Same thing happened to me and I sent it in for warranty with the bootloader unlocked. Samsung fixed it and no charge.
garu12 said:
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Click to expand...
Click to collapse
Dang. I hope u can fix it.
Sent from my Xoom using xda premium
Thanks for the replies. It's impossible to relock in this state! I did manage to unroot and install a stock rom so at least it's gonna look somewhat legit when I bring it in. Going to the Samsung repair center tomorrow (there is one not far from me so I dont need to send it). I'll let you know how it goes. Wish me luck!!
So I went in today to the Samsung repair center and 2 hours later my Nexus is good as new . Pretty classy of them. That's really good service. They didnt even question the unlocked bootloader and it was covered by the warranty. This makes me want to stick with Samsung. When my Nexus One power button died it took like 4 weeks to get it back
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
I have an entirely different issue but it involves me sending in my phone to samsung with an unlocked bootloader. My phone won't boot past the google screen and I can't relock the boot loader via adb. I've already sent the phone but didn't mention anything about it being rooted when I called customer service. Think there's a good chance they'll fix it no questions asked?
bradmikd said:
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
garu12 said:
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
Click to expand...
Click to collapse
or just adb reboot recovery
For starters, if there is already an answer to this question, please point me in the right direction because I have looked all over the forums and cannot find an answer. I was wondering if anyone could help me return my Nexus S 4G back to stock. I was in the middle of using one click stock when my power went out and now my phone just sits at the bootloader saying "fastboot mode-no boot or recovery img" and one click stock does not work.; meaning, it will sit and ask me to put the phone into debugging mode. I have also tried manually flashing the files from fastboot but it sits at sending file but does not flash. Even let it sit at the sending screen for 3 hours but it never flashed.
Maybe a brick. The same thing happened to me once, no img's, fastboot not working and a broken power button. I just got it back from a free repair
Sent from my Nexus S using xda app-developers app
Well, is your bootloader locked/unlocked? and try to do it manually with fastboot, at least you know that things are done correctly.
unlock bootloader is : fastboot oem unlock
lock is: fastboot oem lock
you could try to switch once and try to push the recovery image so you can flash a new rom.
Thanks for the help. I relocked and unlocked the bootloader and it did the trick. I was able to manually flash everything back to the phone
Glad I could be of help
Sent from my Nexus S
FirePoncho86 said:
Maybe a brick. The same thing happened to me once, no img's, fastboot not working and a broken power button. I just got it back from a free repair
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Where did you get the free repair bud?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
So I accidentally dropped my nexus 5 and I need to replace my display but unfortunately I haven't backed up my data (mostly pictures I'm worrying about the most). So is there a way to pull the storage from it? I've tried with adb and it doesn't work because it doesn't list my device.
I really hope there is a way to do it.
If USB works and its not detecting adb, then its set up wrong. Adb is the only way if both touch and display are broken.
Please click the link in my signature and read the adb and fastboot thread. It will tell you how to set it up properly
Sent from my Nexus 5 using Tapatalk
Does it matter if I had an unlock code for my lockscreen?
dndwanted said:
Does it matter if I had an unlock code for my lockscreen?
Click to expand...
Click to collapse
Yes it does.
Don't suppose you have a custom recovery do you?
Sent from my Nexus 5 using Tapatalk
My phone was rooted and I had latest TWRP with latest Paranoid Android,
dndwanted said:
My phone was rooted and I had latest TWRP with latest Paranoid Android,
Click to expand...
Click to collapse
Adb in recovery then. See the thread i previously told you about
Sent from my Nexus 5 using Tapatalk
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
dndwanted said:
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
Click to expand...
Click to collapse
You've not read my thread properly. Try again
Sent from my Nexus 5 using Tapatalk
I installed the adb in 15 seconds thing and then I followed this thread http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please tell me what have I done wrong because I can't seem to figure it out.
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
@rootSU
I get this: http://imgur.com/ccw4lJ6
:/
ChickenNugget said:
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
Click to expand...
Click to collapse
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately I get the same error.
dndwanted said:
Unfortunately I get the same error.
Click to expand...
Click to collapse
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
rootSU said:
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://imgur.com/KCoHxg8
dndwanted said:
http://imgur.com/KCoHxg8
Click to expand...
Click to collapse
Unless you can get recovery to show up, you're screwed.
I don't know anything about twrp so I can't help there.
Sent from my Nexus 5 using Tapatalk
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
dndwanted said:
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
Click to expand...
Click to collapse
Try manually option 2
Otherwise you can fastboot flash philz recovery - which is a recovery I know.
Sent from my Nexus 5 using Tapatalk
Doesn't work.
dndwanted said:
Doesn't work.
Click to expand...
Click to collapse
In more descriptive terms please
Sent from my Nexus 5 using Tapatalk
So I was going to reinstall Cataclysm ROM because it has been giving me problems the last few days, mainly it's been dropping my WiFi signal forcing me to switch it on and off just to use my phone, like once every minute
So I downloaded the file to my device, and went to flash it, but I wiped the dalvik and cache, and I pressed data I'm pretty sure, 100% by accident cuz I was so mad at my WiFi signal constantly dropping
Anyways now my phone says "No OS Installed, are you sure you want to reboot?"
I just did a few hours worth of research and... nothing seems to work
I've tried a few ADB sideload guides but I can't seem to follow what they're saying since my screen shows something completely different than what theirs shows
I checked a couple forums too and no one else was experiencing what I am
So I've come to you guys to help D:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Any other ideas?
I saw the USB OTG method works, should I just buy one of those and try it out?
It's just like an add on hard drive that I'll load the ROM onto right?
Do I have to flash the stock img or can I flash a new ROM, like Cataclysm again, or Carbon or something?
I'm going to go buy one of those USB OTG drives, a Kingston 32 or 64gb one from Canada Computers
#fingerscrossed it works guys!
If you have anything else for me to try let me know!
devchaube said:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Click to expand...
Click to collapse
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Back in business! Picked up a couple of USB 32GB OTGs for $15 each (WICKED)
Plugged them into my PC, transferred 3 ROMs over (Cataclysm, XtraSmooth, and Stock IMG)
Just tried Cataclysm now, and it's working, everything was successful, and no problems!
Damn I love USB OTG
devchaube said:
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
Click to expand...
Click to collapse
If it did not work there, it must have been a missing driver issue. Or your fastboot setup.
Sent from my Nexus 5 using Tapatalk
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
devchaube said:
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
Click to expand...
Click to collapse
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got it working last night, since I couldn't do it using TWRP or CMD
I just used Wugs Toolkit, selected the bricked / bootloop option, and flashed stock + unrooted it
Loaded the newest imgs available, so I'm good for now
I'll wait a bit, see if the WiFi thing comes back on stock, if not then it was probably something to do with Cataclysm, I didn't even save any logs to hard to see what it was
Thanks for all your help though!
It didn't work because you didn't install the drivers for adb/fastboot properly. Anyhow nice to see your device is working again!
Any help appreciated. I accidentally put the pixel elemental x kernal on my pixel xl and no I am stuck at the google screen with an unlocked bootloader. Can these batteries get pulled at all? Im just stuck here, and very nervous.
Solved
having the same problem, im interested in how you solved it
dablitzkrieg said:
Solved
Click to expand...
Click to collapse
hiw did you fix this i seem to be in same problem
Did you start in recovery and flash the files manually through usb on a computer?
Sent from my Nexus 7 using XDA-Developers mobile app
chrisinsocalif said:
Did you start in recovery and flash the files manually through usb on a computer?
Click to expand...
Click to collapse
i cant get into recovery i got red corrupt screen i did fastboot continue got it booted back up but had a emergancy and had to run out and forgot to plug back in battery died now i cant seem to get to get it booted back up again just seems to bootloop or get stuck with white screen with the dots when i do the fastboot continue
chrisinsocalif said:
Did you start in recovery and flash the files manually through usb on a computer?
Click to expand...
Click to collapse
thank you so much for your help.somehow i got it back up and running
Had the same happen to me. It didn't want to go into recovery gave a message it failed. With some patience I manged to get the button combo to work for fastboot then did a flash-all of the factory image. I think the trick was it had to be plugged in to get to download mode and I think you may hit the power button slightly before the volume down. It was a bit tedious. I tried to recover the boot.img and that trashed things up worse, got no google loading logo or something odd. Anyhow flashing the full factory image fixed things!
Glad you got it resolved, maybe this helps someone else in the same spot.