Related
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2
i brought the phone at launch, its a T-Mobile version Super AMOLED I9020, im in india though, using indian sim.
the phone was previously rooted, then unrooted, then rooted, then unrooted again. then filnally i was using unrooted nexus s, but with unlocked bootloader and stock recovery.
4-5 months after this, the phone started stucking on google logo.
it used to stuck at google logo at times but a quick battery pull would fix it, one day it didnt. since then it always stuck at the google logo on boot and never turned on, except some 1 out of 1 million times after connecting to computer.
i tired to format the whole phone using stock recovery, it was successful and the phone turned on, but next time when it switched off, same problem again but this time even formatting wont work, the formatting from stock recovery would just display an error that it failed to find a file and formatting aborted.
i tried everything, hundreds of stuff from google and XDA but nothing seems to be working.
today i managed to flash CWR to it. i tired to then erase sdcard but it says failed to mount /sdcard . i also tried other things like update from sd card(i have a ICS update.zip file in the memory) but still it said failed to mount sdcard, tried to wipe-> 'error mounting sdcard'
and now i dont know what ive done but when i boot the phone(normally) it doesnt even display the google logo, it enters bootloader by itself and says 'fastboot mode - no boot or recovery img'
bootloader is still unlocked, CWR is still there and accessible.
i took it to samsung service centre too, they said they will have to replace the motherboard(quoting me 400$ for it lol)
this is my last try really, ive been trying to fix this thing from ages!
is there anything that can be done?
going to sell it if i still cant fix it
I'm in about the same spot. If you have a Linux box available, you might try Adam Outler's "Unbrickable Resurrector." (http://forum.xda-developers.com/showthread.php?t=1397393) It's supposed to be a last gasp kind of thing before you give up. However... I ran it and it crashes -- not the phone, the software itself. Sigh.
I got here by making a backup, then unintentionally erasing everything on the phone, including the backup, the boot image, and the recovery image (the backup, presumably). That's what the message "no boot or recovery img" seems to be saying. Fastboot doesn't work either.
So here's my last gasp before I take it in for repair: apparently you can buy or build a micro-USB connector called a "USB jig" -- it's just a connector with a resistor connecting a pin that's usually not connected. This is supposed to put the phone into download mode, where you can copy a recovery image to the phone. Then you can use CWM to install a new image.
-Rod
It sounds like your mem is shot.
Sent from my Nexus S
I've had a similar problem to this and to solve it I just locked the boot loader and then unlocked it again and everything was back to normal for me. You could try that and see if it works
Sent from my Nexus S using Tapatalk
sell faulty nexus phone
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit
amity_coolin said:
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit
Click to expand...
Click to collapse
R u still interested in a faulty Nexus S?
Hi.
My solution may sound a bit strange but me too have the same problem.
Just heat the phone a bit and see if it boots.
Heat it from a hot air source such as laptop heatsink area.
Just get the cell phone warm and it may boit up.
I know it may sound strange but it has worked for me everytime.
Regards
Sent from my xperia TX via xda premium
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Fox5.56 said:
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Click to expand...
Click to collapse
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
graphdarnell said:
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
Click to expand...
Click to collapse
I copied anything I wanted saved, but I did not do a legitimate backup of software files.
I have pressed the wipe data icon on the boot screen under the confusment of the many different posts. What step does that leave me at?
EDIT:
So crazy Buster99 fastboot flash did it. Sucks because I tried that before but I guess I may have missed one line of the reflashing script. Well thanks, after three days I've finally been put in the right direction.
Seems like that pesky /misc partition is causing problems. Glad you got it sorted out though.
Sent from my SGH-T889 using xda app-developers app
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.