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
Related
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
jordanjackthomas said:
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
Click to expand...
Click to collapse
I hate to be the one to tell you this.. sounds like you got bit by the nand flash failure that all of us nexus s owners fear. Warrenty repair is the only recourse in that case.
Sad to say but sounds like you got bit .
"So here's the problem. Just got my One S the other day and I attempted to install trickDroid on it. I got it rooted and unlocked and tried installing. Something went wrong somewhere along there and it wont boot up, only past the first screen and its all black after, i do hear the start up sound after a while but it stays black screen. So i tried to revert it back to stock and during the process I though I had to erase/reset data, so i did that. Only then did i realize that everything was on internal memory and it did not have an external sd card. So I cant install anything without transfering the files from my PC. I tried different versions of clockwork by fastbooting it because i heard it connect to pc automatically. But i end up with an I drive I cant access(insert disk in to I) or on the phone its says something about "unable to open ums lunfile htc one s" I also tried the all in one tool and the latest version doesnt have stock recovery. So the main problem is I can't transfer files on to the phone to reinstall any ROMs and I cant revert back to stock. I am thankful for any help anyone can provide me." sorry for the double post
I was running CM10 on a rooted TFT101. I was having some WiFI connectivity issues so I decided I would try out a new rom. I used Titamium Backup and backed up all my needed files to my Mico SD card. Once backed up, I rebooted into CWM v6.0.1.3. I went to do a factory reset prior to flashing the new rom. The tablet just froze. I rebooted the tablet back into CWM. I tried to again do a factory reset and again the tablet just froze. I tried to boot back into CM10 and I just sits and spins and never actually boots into the OS. I decided that I would just go ahead and just flash the new rom and do a factory reset after the fact. I placed the new rom on the micro sd card and booted back into CWM. I attempted to install zip from SD card and now I get e:can't mount /sdcard/. I have tried 3 different micro sd cards and nothing. I have formatted each to fat32 and not one of them is recognized. All 3 are recognized by windows.
Since I can't boot into the OS...and I can't load a new rom....I am dead in the water. Any help would be greatly appreciated.
Thank you in advance.
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Lethe6 said:
If you can get it to that endless boot logo and connect it through USB, ADB (info - download) should be able to access whatever's left on your device assuming it gets far enough in the boot process. If it does, you can adb pull the backups to your computer to save them.
That being said, Easy Flasher will help you get back to 100% unrooted stock and "unbrick" your device with a few clicks. Then you can start over with a new recovery and rom. But it will wipe your entire device clean, hence why I suggest you first check if you still have backups and if you do, pull them on your computer using adb.
I can't help with the CWM problem, I haven't used it in a long time.
Click to expand...
Click to collapse
Thank you Lethe6. I saw that option and wondered if that might help me. I will try it out today.
One quick question. If I flash back to stock I am guessing I will just need to reroot once I am able to boot it back up?
Thank you again for your assistance.
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Lethe6 said:
Yes exactly. Easy Flasher has a root option as well so it's fairly easy to get going with customizations after restoring to stock!
Click to expand...
Click to collapse
Go figure. I went to fix the issue last night per your instructions and I was sitting at the Google login screen for the the new rom I loaded. What ever issue I was having corrected itself. That never happens. I guess I shouldn't complain =)
Thank you again for your assistance Lethe6!
Hello,
I have a Nexus S that was encrypted because one of the Exchange servers I connect to requires it.
The unit has since failed to boot into CM9. It enters into the "Google" start screen, flashes once, and stays at the "Google" start screen with the soft buttons activated. I assume this is what is called "soft bricked". Recovery still works, and so does Download mode.
Mounting from recovery has failed. I've tried CWM and TWRP, but neither can mount, nor can they format the SD card. I've attempted load stock rom through flashboot, but of course that fails because it doesn't have access to the SDcard.
Attempting to mount Internal SDCard and Data through TWRP as hinted in Cyanogen forums have failed as well.
I can't seem to find Odin files for Nexus S either. I may be wrong, but there might not be Odin files for the vanilla non-4G Nexus S.
Can someone offer advice on what to try next?
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
amadaeus said:
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
Click to expand...
Click to collapse
I have the same problem. Can't do anything with my phone since it can't mount the internal sd... I'm currently searching for the files to restore the phone, so if I find anything, I'll post it here.
. 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