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
Hello, so it looks like i screwed up here and got ripped of on ebay. I bought a nexus i9020t for a friend at work to bring back to india.
The seller said it had a rom install badly on it, but it could still get into the bootloader. He claimed with some effort it was likely fixable..which me and 33 other bidders agreed (*dumb move*)
Unfortunately with some further research I think this phone is having the eemc problem where it can't read its internal memory. It is stuck on the google boot screen, but bootload is accessible. When i go to look in the sdcard from recovery, it can't mount it.
"Fastboot oem unlock" won't work and from what i read, its because its trying to wipe the internal memory..but it can't access it, it freezes and when i boot back into bootloader its still locked. Also the phone boots into android every once in a blue moon, like after 20 battery pulls it will boot into 2.3.4. I've tried Wugs tool to try unlock to no avail, driver setup checks out according to the UI.
I need to unlock the bootloader to do anything, i even need to unlock bootloader to put on clockwork mod. Anyone know of a .zip package that will install clockworkmod, so i don't have to do "fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img" because that requires unlock.
Also i'm having trouble seeing the point to all this because even if I get the bootloader unlocked thats not going to help a hardward problem.
The fact it boots into 2.3.4 on ocassion indicates to me that its freezing at boot because the internal memory..i mean if there was no rom on there it would never load jack.
So other than my clockworkmod .zip install question, anyone know if the internal sd card can be replaced? I mean ill go in there if its an actual sd card and not attached to the board or something. Need some guidence here, I see the problem around, but is there reall a solution so this?
Have you tried flashing with odin ? Mabey tick the repartition option.
Sent from my Nexus S using xda app-developers app
Yea I will do that this afternoon, also I will try using the PA drivers and Wugs tool on another machine.
I'm not sure but you could try to root the phone with the gingerbreak exploit over an adb shell. After doing this you could install ROM manager and flash cwm. The ROM manager app doesn't need an unlocked boot loader. It just needs root permissions.
After doing this you should be able to boot into cwm.. BUT I don't how it could help you with your hardware problems.
Sent from my Nexus S using xda premium
I'd get a refund. If it boots once in a blue moon, something isn't right hardware wise. It either boots or never boots, not "when it feels like it".
Yea idk i hoped the guy had just super effed up the software.
Now where i'm at is i got the bootloader unlocked using the fastboot command, i had to try serveral times, but it worked eventually.
Now i need to load something or do something that will alow me to repartition system.
Basically once bootloader was unlocked i used wugs tool to "flash stock + unroot" from "can't boot" status. It worked on recovery, bootloader ect..alle the way up until it tried to write the system, and gave an error "write failed (unable to remote write)" or something like that.
So now i'm basically tyring to get the "sabra root toolkit.zip" on the device so that i can use clockwork to partion the /system. Or some other way of partiioning /system.
But i'm having difficulty pushing files to the device because wugs tool is expecting you to be booted with usb developing on, and i can't boot.
I've tried "pushing files", and "installing .zip packages from my machine" under wugs tool, and it fails every time because adb device not found, and i think its because i'm not fully booted.
Still recommending a refund. This isn't easy to fix, it's actually not fixable by commoners.
Okiedoke here's the update, I got this puppy working. Just as I did with the "fastboot eom unlock" command, I just kept trying the wugfresh "flash stock + unroot" with the "can't boot" option checked. Several times it failed when trying to write to /system, eventually I tried and it worked. Now I havnt had a boot go bad since the fix (knock on wood) and its running jelly bean.
As for the troubles couple things I noticed
1. I don't think ABD works unless you're fully booted and you have USB debugging on.
As a result not much of wugfresh's options work, only the fastboot ones do.
So the "can't boot" option only uses fastboot so it works while in bootloader.
While the unlock option won't work, because it's trying to use ABD in the beginning.
In fact the only option that doesn't use ABD that I can think of is the cant boot.
So if youre locked like I was, you need to use the command line.
2. I think the problem was the rom the guy had on before had a full blown bad flash.
The /system and I think the bootloader was messed up as well.
Luckily sometimes the device could communicate with its storage, but most of the time it couldn't.
3. Getting the drivers right is a total pain, sometimes one set of driver will work for one thing, and fail for others.
I used two laptops and switched back and forth messing with the 3 available driver settings in wugfresh.
For my problem the pnet drivers are not an option...because you have to be booted to install them, so I just switched between signed and raw. Also the USB ports you use deffidently matter so switch between those as well, if using a desktop use only the back ports.
Here are the steps I took, unfortunately they weren't precise so I can't really say what did it.
1. Download wugfresh, do the raw driver install (if you can use another machine and do the signed driver install).
2. Download the adroid sdk.zip, and extract it.
3. Use command line and go to the tools folder in the adroid sdk folder (I forget exact path, but it's the tools folder somewhere in the extracted folder).
4. Now type "fastboot oem unlock".
5. If fastboot is working right you should get the unlock screen, choose yes.
6. Mine froze here and I had to try several times until it worked..switch back and forth between the 2 comps if you have that option.
7. Once unlocked do the wugfresh "flash stock + unroot" with the "can't boot" option checked.
8. It may fail, but again switch back and forth between machines, and USB ports, if it works then you should be good to go.
One thing I noticed is that recovery showed it couldn't mount my sdcard, but after option 7, and it failed to write the /system, my bootloader changed to a more up to date version (android laying down) and it was able to see the sdcard (which shows me the recovery/bootloader where kinda screwed up in the first place). After I tried again after that maybe 1 or 2 times writing system was successful.
Thanks for all your help I'll click thanks on all you guys.
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
. The phone was running great for weeks, it had the USB fast charge hack, and the setup in my sig, when suddenly I woke up to a bootloop after going to bed with a perfectly good phone. Stupidly, I had no backup in recovery to flash. Trying to put an update.zip onto the internal memory is when I discovered that USB mount in recovery doesn't work. In CWM or TWRP I get nothing if I try. I also couldn't mount anything from /sdcard, /data, or /system, I would get "Error mounting /system!" if I tried. It also won't flash a zip from sideload in CWM, although it seems to push it over just fine as it takes a while and reads the file size of the zip. It seems as if anything I try to do to /system, /sdcard, or /data just won't take.
. I can get it to listen to fastboot commands, it will even list as one in Wug's toolkit, but it is not recognized as an ADB device in Wug's. Fastboot seems to work by itself, and in Wug's. In both cases, it seems to flash the radio, bootloader, and recovery just fine. When I (or the script in Wug's) gets to flashing the /system, /sdcard, and /data portion however, then it returns an error after seemingly writing everything. I've tried flashing with manual command line, Wug's Toolkit, and a batch file from someone here on XDA, none of it works.
ODIN hangs indefinitely within a few seconds of trying to flash. I can only get the COM:3 box in ODIN to go yellow, never green like I remember when I unlocked the bootloader. How can I get ODIN working? I feel like if I can get it going I should be able to fix this.
I'm at my wits end here. At this point I've tried fastboot, ODIN, and Wugs Toolkit. Nothing works I can flash recoveries. I have download mode. I have fastboot working. What can I do to get this damn thing working? Can this be a simple USB driver issue after all the drivers I've tried?
Anyone who helps me fix this will get thanked by me every time I see them for quite awhile, I've put too many hours into this already! Yes, I've moved on to a GS4, but I LOVED this phone and would like to get it going again. I'll still use it as a GrooveIP phone at home, or give it to my kid. Or even to have it as a backup would be great. Thanks for all the help guys!
http://forum.xda-developers.com/showthread.php?t=2500397
Have you tried going trough the same steps?
Oh yes, several times, with a GB, ICS, and the latest JB AOSP ROM, for the correct phone (sph-d720). I always use crespo4g images. It never works. It acts as if it writes, but has an error that says "can not automatically format" when it tries to flash the zip. When I reboot the phone there is no change. I can flash recoveries just fine.
Sent from my SPH-L720 using xda app-developers app
Nobody? I would love to get back on this phone... My favorite device of all time to this day
DizturbedOne said:
Nobody? I would love to get back on this phone... My favorite device of all time to this day
Click to expand...
Click to collapse
I have a hunch that your internal memory has gone bad. Any luck so Far by any other method?
Sent from my Nexus S using Tapatalk
No go from anything I've tried. It seems like it just won't be recognized as an ADB device. Pretty disappointed at this point.
Tapatalkin' from my SGS4
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