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
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
So I wanted to do a fresh, clean reset of my device. I have been visiting XDA since the day the HTC EVO 4G came out, which is like three years now. Never needed to make a post until now because the search function has always served me well.
So anyways, I was on CleanRom 1.3 with CWM-based Recovery v5.5.0.4. I tried to upgrade to CleanRom 3.0.3. I did the usual - wipe data, davlik, etc, then did the full install using the suggested settings (stock kernel, 160DPI, etc). Yet, I can't get past the "The Device is Unlocked" screen with the ASUS logo.
Earlier, I messed around with the MOUNTS AND STORAGE MENU accidentally.
as of right now, it shows me:
-mount /system
-unmount /cache
-mount /staging
-mount /data
then the rest of the format options for system/cache/staging/data.
I am wondering if I got the mount and storage stuff messed up. I also wanted to put on a new recovery (TWRP), but I am unable to do that unless I can get past that screen.
I've did a clean wipe three times and it never gets past that window. Any help??? I feel like I made a dumb mistake that I might have overlooked.
Thanks!!!
Note: I *can* still access recovery. however, this version of CWM doesn't do external SD so I am stuck with this rom since i have no way of putting stuff on the internal storage
NOTE: I just heard/learned about fastboot... trying this process again and seeing where it gets me. Hopefully I can flash TWRP and start over with CleanRom 3.0 from there
Note: Now I have *no* recovery... i guess i did it wrong following a guide
note: i guess i bricked it... now i cant get the flashboot menu, even with a paperclip in the reset button. after wiping data from there (in order to try installing twrp), it just says it will try to get into ota recovery (which there isnt) and NOW it only reboots into the device is unlocked... then reboots into the device is unlocked screen. and no, i didnt make a backup like i should have. i accidently did the wipe data during the "wipe data/usb/android" 3 option menu... so am i screwed?
note: going to contact asus tech support... hopefully somehow its a cheap replacement and/or fix. however.....
ASUS LiveChat Support
One of our representatives will be with you shortly. You are number 68 in the queue. Your wait time will be approximately 160 minute(s). Thank you for your patience.
LONGGGGGGGGGGGGG WAIT!!!!!!!!!!!!!!!!!!
Ugh, after all this time, getting down to #12... the chat is closed!!!
Ah, well just got off the phone with ASUS tech support. All I have to do is:
1) Go to best buy and get a copy of the reciept with proof of purchase, which isnt an issue because i purchased it on june 20th with my best buy card.
2) e-mail them the copy of a reciept
3) pay for the shipping to them
4) get it serviced since its under warranty.
wahooo! it won't be a $300 paperweight. however, i am curious if there is actually a solution to this problem, so maybe someone else can use this thread better than it helped me.
What can I do?
I took the phone outside, and after some hours of snowball fighting I came home and noticed that the phone wont boot.
The bootloader works, and I can enter in the recovery, but if I try to Format System it wont work, or if I try to install a new one it says:
E: Can't mount /storage/sdcard0
I have an unlocked, rooted
- Nexus S running a
- CM11 Rom, with
- CWM Recovery v6.0.4.3.
Duff X said:
What can I do?
I took the phone outside, and after some hours of snowball fighting I came home and noticed that the phone wont boot.
The bootloader works, and I can enter in the recovery, but if I try to Format System it wont work, or if I try to install a new one it says:
E: Can't mount /storage/sdcard0
I have an unlocked, rooted
- Nexus S running a
- CM11 Rom, with
- CWM Recovery v6.0.4.3.
Click to expand...
Click to collapse
Reseat the sd card?
If you don't have a warranty then take it apart and inspect it then put it together again.
Duff X said:
What can I do?
I took the phone outside, and after some hours of snowball fighting I came home and noticed that the phone wont boot.
The bootloader works, and I can enter in the recovery, but if I try to Format System it wont work, or if I try to install a new one it says:
E: Can't mount /storage/sdcard0
I have an unlocked, rooted
- Nexus S running a
- CM11 Rom, with
- CWM Recovery v6.0.4.3.
Click to expand...
Click to collapse
Try take out the SD card or you might have water damage or something after the snowball fight
Well, I did a partial disassembly and used a hair dryer on it..
By partial disassembly, I mean this stage:
i.imgur.com/A87sg0y.png
Didn't go further.
About the SD card, as far as I know this phone doesn't have an SD card slot..
Just internal memory.
So i was using my phone 5 days ago like normal and sudendly it decided to reboot itself, after that it got stuck on the 4 balls android logo and doesnt boot into the system anymore.
what iv tried so far:
-Full Wipe
-Download and flash a full factory image, then full wipe
-Download and flash TWRP with SlimRom + Gapps then full wipe
Nothing works, it always get stuck in bootlogo, it just sits there dancing like its booting normally but it never does, im runing out of options here, what can i do guys?
Note: i have access to bootloader, all button works, also have access to recovery without any issues.
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
Let me download a kitkat image and see what happens, ill report back as soon as i do it
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
mediavieja said:
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
Click to expand...
Click to collapse
Aight so i flahshed twrp and slimrom again but im once again stuck on bootloop what do u suggest?
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
audit13 said:
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
Click to expand...
Click to collapse
Nope, tried stock MM (latest stock) and didnt work
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
audit13 said:
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
Click to expand...
Click to collapse
Must be then, cause i tried LP and didnt worked
I think it has something to do with differences in partition layouts between kk and LP/mm.
audit13 said:
I think it has something to do with differences in partition layouts between kk and LP/mm.
Click to expand...
Click to collapse
Do u know if theres anyway to fix it?
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
audit13 said:
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
Click to expand...
Click to collapse
Awww well thanks anyway for all ur help men, i really apreciate it
You are very welcome. We are all here to help and learn from each other.
The cheapest solution may be to buy a used nexus with a busted screen but working motherboard and perform a bit of phone surgery. I've done this a few times over the years with great results.
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
HSF3232 said:
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
Click to expand...
Click to collapse
Well i followed the procedure to fix persist, i was getting Unable to mount "/persist" (Invalid argument) so bu running command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist i was able to mount it, after that i rebooted the phone to bootloader and i was able to flash and run the latest software update so i have to say thank you very much sir im gonna try to put slimrom now on this bad boy and change the post title to fixed