Hello Friends
My friend has had his Nexus S for a few months now and just this week it decided to brick itself.
Strange part was that he was not rooted or had bootloader unlocked, which is a pain because he cannot access download mode without it (bootloader) unlocked.
The only prior symptoms were that earlier in the week he had to factory reset a few times due to non-responsiveness and freezing.
Now I know the correct steps would be abd->unlock bootloader->Download mode->Odin but I am stuck at the first step.
Without being able to boot, I am unable to check USB debugging.
So I ask you, brilliant XDA community, how can I get into adb given this scenario?
I thank you in advance for your help
Oh and by the way I have done factory resets, wiped cache etc.
and I can access (locked) bootloader, the volume up and power menu, and recovery.
C
If you can get into bootloader and recovery, you're not bricked.
ADB is used when Android is booted up.
Fastboot is used in bootloader.
Get Fastboot working (proper drivers etc)
Go into bootloader on your phone.
run 'fastboot devices' if your phone and serial number shows up, fastboot is working.
run 'Fastboot oem unlock'
then flash clockworkmod recovery 'fastboot flash recovery filenameofrecovery.img'
boot into recovery.
mount the internal sd. search for a stock nandroid backup in the forums, copy it over to the internal sd.
umount, go back to main menu of cwm recovery and restore that nandroid backup.
reboot. if it boots up and stuff, shut down phone, go back to bootloader and 'fastboot oem lock' to relock bootloader and you should be at stock.
Thanks so much for your help!
I'll try it out tonight!
okay so I am able to get to the point where it asks if I want to unlock the bootloader and I choose yes on the phone, but it just hangs.
Any ideas?
I offer my apologies good XDA-ers, shameless self bump!1
Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
I had the avatar custom ROM on my phone.
wanted to sell it, so went into CModRecovery and tried to restore my phone to a previous restore point i had, thinking that would be with the Tmobile stock.
Anyways, right after that, my phone was soft bricked, constantly restarting. At the beginning i was able to go into recovery, and i tried to restore it to the previous point again, but it didnt work, tried clearing cashe and stuff, but still didnt work, and then I dont know what happened, but all i can access now is bootloader, cant even acced CModRecovery anymore.
I know my phone is soft bricked, and I've found the original RUU Tmobile for my HTC one S, and im using the Hasoon all in one toolkit to try and factory reset it, but the problem is, I dont have USB Debugging enabled, and my phone is soft bricked, so I dont know how to enable it now, and I cant follow any of these tutorials for fixing the soft brick, without it enabled.
So now my question is, how can I enable USB Debugging with my phone in the state that it is (ie, only thing that acccessible is bootloader)
Thanks for taking the time to read this, and I really appreciate any help.
I dont think you even need ADB at that point. From the bootloader you can enable fastboot (by selecting fastboot with volume keys and pressing power button to activate it). Then reflash the recovery from your PC by running fastboot flash recovery your-recovery-img.img Then you'd be able to access recovery again.
And when you restore a nandroid of another rom and are on a hboot version 1.09 or higher (and S-on) you also need to flash the boot part of the backup. So first you need to get the boot image to your PC from the phone. At least TWRP recovery has an option to mount storage as a USB drive, probably CWM has this also... Finally flash the boot image to your phone by booting the phone into bootloader, selecting fastboot mode as before, and then flashing the boot from your PC by running fastboot flash boot boot.img.
Hope this helps. I'm just writing what I would try in your situation .
Sent from my One S. Please hit thanks if I helped.
So this is what I did:
1. In bootloader, selected fastboot with the power button. Now im at the screen where it has 4 diff options: bootloader, reboot, reboot bootloader, and power down. Also on this screen, since I have the phone connected to the computer, it says FASTBOOT USB
2. So now I open up cmd and write what you said, fastboot flash recovery recovery.img (the cyanogen mod renamed to recovery)
3. And it says it failed.
4. So I cant proceed with the rest of what you said. I'm not sure why it failed, but does it have to do with the fact that my USB Debugging is maybe disabled, and thats why its not able to find the phone?
5. Because even when I was trying to get the Hasoon all in 1 toolkit to work, the reason I couldnt was because everytime I'd try something, it would say "device not found" in the cmd prompt window.
As I'm sure you can tell, I'm pretty confused :S
masoodi said:
So this is what I did:
1. In bootloader, selected fastboot with the power button. Now im at the screen where it has 4 diff options: bootloader, reboot, reboot bootloader, and power down. Also on this screen, since I have the phone connected to the computer, it says FASTBOOT USB
2. So now I open up cmd and write what you said, fastboot flash recovery recovery.img (the cyanogen mod renamed to recovery)
3. And it says it failed.
4. So I cant proceed with the rest of what you said. I'm not sure why it failed, but does it have to do with the fact that my USB Debugging is maybe disabled, and thats why its not able to find the phone?
5. Because even when I was trying to get the Hasoon all in 1 toolkit to work, the reason I couldnt was because everytime I'd try something, it would say "device not found" in the cmd prompt window.
As I'm sure you can tell, I'm pretty confused :S
Click to expand...
Click to collapse
Did you relock the bootloader? Does it say *** RELOCKED *** or *** UNLOCKED *** in the top of the bootloader?
If it is *** RELOCKED *** then you need to unlock the bootloader again (here are nice guides for doing it. I don't remember the exact fastboot commands right now). If it says *** UNLOCKED *** then I'm unfortunately out of ideas. I did however do some googling and found this: http://www.askabouthugo.com/general...on-fastboot-with-remote-signature-verify-fail
And are you sure you are trying to flash an S4 version of the recovery and not an S3?
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
then go back into volume up + power (fastboot mode)..... fastboot flash recovery <recovery-name>.img while the recovery file is in the fastboot.exe folder. then boot into recovery.
zephiK said:
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
Click to expand...
Click to collapse
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
lemonspeakers said:
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
Click to expand...
Click to collapse
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
zephiK said:
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
Click to expand...
Click to collapse
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
tkdsl said:
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
Click to expand...
Click to collapse
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
teh roxxorz said:
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
Click to expand...
Click to collapse
I've already tried this on 3 different computers.
I don't see how having dev mode would affect bootloader if I never boot into the OS.
Someone had the same issue and had found a fix. I will give this tampering fix a try:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735
lemonspeakers said:
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Click to expand...
Click to collapse
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Dr.Linde said:
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Click to expand...
Click to collapse
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
lemonspeakers said:
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
Click to expand...
Click to collapse
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Dr.Linde said:
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Click to expand...
Click to collapse
That is sooo SCHWEET! I can't wait to try it on my phone when I get home! Woot!
I unlocked and flashed custom recovery CWM 5.0.2.7. on my mytouch 4g slide. I needed to exchange my phone because of hardware defects; so I wanted everything back to stock. I downloaded PG59IMG.zip. I went ahead and relocked the phone and instead of flashing stock ROM (PG59IMG.zip) which was what I was suppose to do I made a big mistake and went ahead and restored everything using CMW while being in re-lock. After everything loaded; I wasn't able to get into recovery mode. It would just loop back to the bootloader screen. I tried reset to factory settings and It would just load for a little bit and then it would go into bootloader; nothing happened. I tried to unlock the phone again but in the command prompt after I type in code fastboot flash unlocktoken unlock_code.bin It would just freeze on the next line "waiting for device" I couldn't find any answers on any forums about this specific problem. Please help! I am very new at this. Thanks in advance!
[email protected] said:
I unlocked and flashed custom recovery CWM 5.0.2.7. on my mytouch 4g slide. I needed to exchange my phone because of hardware defects; so I wanted everything back to stock. I downloaded PG59IMG.zip. I went ahead and relocked the phone and instead of flashing stock ROM (PG59IMG.zip) which was what I was suppose to do I made a big mistake and went ahead and restored everything using CMW while being in re-lock. After everything loaded; I wasn't able to get into recovery mode. It would just loop back to the bootloader screen. I tried reset to factory settings and It would just load for a little bit and then it would go into bootloader; nothing happened. I tried to unlock the phone again but in the command prompt after I type in code fastboot flash unlocktoken unlock_code.bin It would just freeze on the next line "waiting for device" I couldn't find any answers on any forums about this specific problem. Please help! I am very new at this. Thanks in advance!
Click to expand...
Click to collapse
Because the PG59IMG.zip is handled by the bootloader (not recovery), I am not seeing a big issue here. Just need to place the file on your MicroSD and bring up the bootloader. Assuming your are still relocked, and you have the right back-to-stock image version, the bootloader will pick up the file and things should flash smoothly.
Hi! I'm kind of new to this so please forgive me (done once before with a few problems).
Basically, I was looking to root my new HomTom HT16 with SuperSU by downloading a custom recovery (TWRP). I rebooted into bootloader with USB Debugging enabled and OEM Unlocking enabled too.
I selected Fastboot mode from the menu in the bootloader and plugged my phone into my computer. I had no problems recognising the device. I followed the bootloader unlocking steps with:
{fastboot oem unlock}
The instructions that I was originally followed told me that I had to use the Fastboot command (with the recovery.img being TWRP):
{fastboot flash recovery recovery.img}
I was told nowhere that I had to clear any cache partitions (still not sure if I had too). Everything I did seemed successful until I was told to take the battery out, put it back in and turn the device on. It brought up the "HOMTOM" text for the boot screen but instead of booting, it repeatedly turned off and on. Because none of this actually worked, it didn't actually flash the recovery, and so I couldn't boot to it. It just got stuck in a boot loop.
I searched up how to fix a bootloop and I could find anywhere a solid solution unless I just wasn't looking properly. I have all the factory ROM files, I just don't know how to use them to replace anything that could be corrupted. I flashed back the original recovery.img but it still will not turn on, it just says on the "HOMTOM" text screen for a very long time. The recovery also doesn't work, it's just an image of broken android with its internals showing.
Does anyone know what to do now?
adamshaw said:
Hi! I'm kind of new to this so please forgive me (done once before with a few problems).
Basically, I was looking to root my new HomTom HT16 with SuperSU by downloading a custom recovery (TWRP). I rebooted into bootloader with USB Debugging enabled and OEM Unlocking enabled too.
I selected Fastboot mode from the menu in the bootloader and plugged my phone into my computer. I had no problems recognising the device. I followed the bootloader unlocking steps with:
{fastboot oem unlock}
The instructions that I was originally followed told me that I had to use the Fastboot command (with the recovery.img being TWRP):
{fastboot flash recovery recovery.img}
I was told nowhere that I had to clear any cache partitions (still not sure if I had too). Everything I did seemed successful until I was told to take the battery out, put it back in and turn the device on. It brought up the "HOMTOM" text for the boot screen but instead of booting, it repeatedly turned off and on. Because none of this actually worked, it didn't actually flash the recovery, and so I couldn't boot to it. It just got stuck in a boot loop.
I searched up how to fix a bootloop and I could find anywhere a solid solution unless I just wasn't looking properly. I have all the factory ROM files, I just don't know how to use them to replace anything that could be corrupted. I flashed back the original recovery.img but it still will not turn on, it just says on the "HOMTOM" text screen for a very long time. The recovery also doesn't work, it's just an image of broken android with its internals showing.
Does anyone know what to do now?
Click to expand...
Click to collapse
Do you say you have the original files if yes, then if your device is a Mediatek device use SP Flash Tool to flash the rom. If you still need help contact me here or on [email protected]