I have a nexus 5 16gb model with an unlocked boot loader but I am NOT rooted. I was happily using it when I put it to sleep and the next time I went to use it it would not turn on. I plugged it in and put it on charge where all it does is boot loops. When it isn't plugged in it is useless. I can't access recovery because when I do it turns off again and starts to reboot. It is in a 3 second or so boot loop no matter what I do. I have a lot of files on there I need and I don't know what to do. The only thing I could think of doing was use the WugFresh nexus root toolkit and the flash stock when boot looping option but it wouldn't work because it couldn't find my devices fast boot ADB thing :/ My friend unlocked my bootlader and rooted for me but I unrooted because I didn't like it. I really need help even If i can just somehow lock the bootlader so my warranty isn't voided . Please anyone that knows anything about this give me any advice!
You should be able to get into fastboot, flash a custom recovery, and then go into that custom recovery and use adb to pull the SD card files.
Ask this question also in the nexus 5 q and a section for more help.
Sent from my Nexus 4 using XDA Free mobile app
Related
Hi
I got somehow a big problem.
I tried to update my Nexus S by mistake with the I9020A 2.3.6 Rom. It failed. At least somehow it said so.
Now i cannot load my phone normally. Sometimes I have to battery pull several times before the Nexus S boots up again. The other times it stays with a nasty "Google" on screen.
Even more strange. I cannot access the recovery submenu. It does stay at the same nasty "Google" on screen. It does no longer show up the triangle where you the can load an update.zip
What can I do?
Nexus S: GT-I9020
I9020XXXKB1
EUR
Thanks for help
Cheers
Martin
Since you said you can't access the recovery console and it gives you a google logo, I'm going to have to ask: Do you have access to the fastboot bootloader?
If so, are you rooted? If no, you have the option to take it in to get fixed or to root your phone.
If you decided to root/are already rooted, connect your phone to your computer while in fastboot, make sure all drivers are installed and use a command prompt to use the fastboot tools. The Unlockr's Nexus S rooting guide will be a huge help in guiding you where to be.
Does "fastboot devices" return anything on your computer, or is it empty?
(Sorry if you know most of this crap, but number of posts + lack of information in the OP + you saying you don't have a custom recovery = assuming you need a bot more in depth instruction.)
Thanks god I have been able to push the fastboot recovery console!
I did manage to access backup & restore and then load the stock 2.3.3 rom. I am back in business
Thanks for help. I think it is solved.
Cheers
Martin
Now make sure to make a backup.... helps save your a$$
Sent from my Nexus S using xda premium
Hello All
I flashed my Nexus S i9023 with 9020 by accident. I was not watching. Phone is completly dead. I presume there are no ways to restore it? Wrong bootloader was flashed.
What's more important is the data on the phone, including pictures. I had done a backup but forgot the Nexus S SDCard is only a partition...%$%$#$#
Do I have any hope? Anyway to rip the phone apart and extract the data from the memory chip?
funkyblue04 said:
Do I have any hope? Anyway to rip the phone apart and extract the data from the memory chip?
Click to expand...
Click to collapse
If you know how to do board level chip removal without applying too much heat and then you have the equipment to read the memory the answer is a conservative yes. Otherwise for the normal person, the answer is no. The data is gone.
I have yet to see a hard bricked nexus s. Pull the battery and put it back in. Hold power....do you feel the vibration like it does when you first turn it on? If so you are not seeing anything on the screen because you have SAMOLED drivers when you have an slcd. If you are at this point, you should be able to again pull the battery, put it back in and boot into the bootloader by pressing and holding volume up and power. You should now have access to fastboot and can flash the individual partitions with the correct 9023 software.
If you can't get fastboot working the next option would be to try to restore via Odin by putting your phone in download mode. Lastly you could send in your phone for jtag recovery. Unfortunately there will probably be no way to recovery data off the SD unless option 1 works.
Sent from my Nexus S 4G using xda premium
I tried everything. It was dead. No download mode at all. No active USB and a USB JIG did not put the phone in download mode. (Some suggested the screen won't work due to SAMOLED vs SLCD, but that was not the case either!)
Lesson learnt! I returned the phone and it was EOA'd and got a new one.
Rem3Dy said:
I have yet to see a hard bricked nexus s. Pull the battery and put it back in. Hold power....do you feel the vibration like it does when you first turn it on? If so you are not seeing anything on the screen because you have SAMOLED drivers when you have an slcd. If you are at this point, you should be able to again pull the battery, put it back in and boot into the bootloader by pressing and holding volume up and power. You should now have access to fastboot and can flash the individual partitions with the correct 9023 software.
If you can't get fastboot working the next option would be to try to restore via Odin by putting your phone in download mode. Lastly you could send in your phone for jtag recovery. Unfortunately there will probably be no way to recovery data off the SD unless option 1 works.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
There might not be bricked ones but there are unusable ones. I was trying to help a guy who's Nexus S got borked by the 2.3.6 OTA. The bootloader won't unlock and Odin won't flash any files due to the bootloader being locked. Download mode is a screen that says to unlock the bootloader. If he had unlocked the bootloader before this happened it would have been an easy fix. But because the bootloader cannot be unlocked now, although the phone is not a technical brick, it is effectively one.
jboxer said:
There might not be bricked ones but there are unusable ones. I was trying to help a guy who's Nexus S got borked by the 2.3.6 OTA. The bootloader won't unlock and Odin won't flash any files due to the bootloader being locked. Download mode is a screen that says to unlock the bootloader. If he had unlocked the bootloader before this happened it would have been an easy fix. But because the bootloader cannot be unlocked now, although the phone is not a technical brick, it is effectively one.
Click to expand...
Click to collapse
Download mode should just be a blank screen. Odin is samsungs factory tool to recover phones to a stock setting. It could care less about the bootloader state. Since you can get to the bootloader you need to flash the rom through fastboot. That would recover the phone you described.
glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
Sent from my Nexus S 4G using xda premium
A few issues, Phone will not actually unlock bootloader even though both windroid and all in one says the token flash was successful. I even tried doing it though fastboot. I've re submitted keys three times through the dev site so can't imagine it's not right.
I do suspect that the firmware is corrupt as it won't boot into android and none of the bootloader options work. If i select recover or factory reset or whichever it just vibrates and goe back to fastboot screen.
I have a stock rom that it loads up but fails all but one file when updating. Didn't think bootloader needed to be unlocked to use a stock rom so don't know why that is happening. Phone did boot up once the other day after constantly trying to load up a diff rom but only stayed on for 15-20 min before it locked up and restarted back in fastboot screen. Wtf is wrong with this thing? I should mention it did this randomly from the start.
guess everyone here is just as noob as me
Wipe cache
Factory rest
Again flash stock ROM
Sent from my Q600 using XDA Free mobile app
Sounds like a bad emmc/memory chip. A good test is to unlock the bootloader and reboot back to fastboot, and if it is locked again, than you have bad emmc, which is a hardware issue and you will need to get another device.
Sent from my Nexus 4 using XDA Free mobile app
Hello to you all, I am new to XDA and it is because of this problem I am having.
The other day, my N5 shut down unexpectedly and kept that virtual power button pressed (I've seen this happen to a lot of people). The next day, it stopped doing that, but the next big issue started: The phone was stuck on boot animation. Since then, I am not able to boot the phone, so I entered the bootloader (which is still functional) and tried to unlock the bootloader (I blame myself for not doing this since the beginning) from my PC but every time it reboots the phone to keep the changes, the bootloader locks itself again, preventing me to fastboot an image to my device
This is the main issue here, I can't start up my phone, the bootloader won't unlock and somehow, I can't ADB because my PC won't recognize the device. In other words, it seems my Nexus is bricked (may be the first Nexus in the history to be bricked).
I believe there must be a solution for this problem, can anyone help me please!?!?!
Thank you all!
this is how I fix mine.
Can you boot into recovery?
hongkongking said:
this is how I fix mine.
Can you boot into recovery?
Click to expand...
Click to collapse
Hey, thanks for this help, I'll let you know how that goes. And yes, I can boot into recovery.
My device isnt recognized on ADB, and everytime I try to unlock the bootloader, when the device restarts, immeditaly locks the bootloader again.
did u factory reset and wipe dalvik / cache? did u install a correct PC driver? did you ever using adb to connect to your phone?
I remember someone said sometimes you need to unlock the bootloader several times to get it unlocked.
from this and this, your nand flash seems has problem.
Try using LG Flash Tool to flash facory image, it doesn't need to unlock bootloader, but i think it's better not to write anything to nand flash as you don't know if it has problem or not, do so might make your phone completely bricked.
I, my nexus won´t boot, after click to turn on, is stuck on logo of google.
I can not access to recovery mode, neither to download mode, anything..
I've tried reinstalling the rom via LG mobile support tool, but the software does not even detect the nexus, but in device manager is identified and the driver installed correctly .. I do not know what to do ..
Can someone help me?
Note: the nexus is all in stock.
Thanks for the help
Try getting into bootloader mode, turn the device off, hold the VOL- and press POWER, u should get a screen with text displaying the bootloader version, whether or not it's locked and what version it is, LG Mobile Support Tool will not work with Nexus, u need WUGZ Nexus Root Toolkit, it will do it all for u, but u need to be able to get into bootloader, or at the very least u need to have developer options enabled in the phone, if not then idk man, u need to get to bootloader and I can walk u thru the fix
Sent from my Nexus 6 using Tapatalk
I have the same issue. took phone to 4.4 and then started doing the updates and eventually it will get to freezing at the Google screen and stay there. tried to reboot and stops there. I can use the Nexus Root Toolkit and and will let it me do almost anything with it but getting the phone to boot to working order and staying there is not happening. Any help or suggestions would be appreciated,