[Q] Phone is partially bricked...? - Nexus S Q&A, Help & Troubleshooting

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).

Related

Huge problem,SD card wont mount

I just got a sidekick 4g off craigslist and whenever I put my SD card in the phone it will recognize its there but wont mount. Im not sure whats wrong,I tried formatting it(In Fat32,NTFS and FAT) but it didnt work. I tried using Astro and that was a fail as well. I even tried doing a hard boot. When I go inside the SD card setting it doesnt show the total space or avalible space and formatting it does nothing. When I click on mount,it attempts to mount but after awhile it just times out and gives me the error "activity sd card and phone storage (in process settings) is not responding" and I have the option to wait and force close. clicking wait doesnt change anything. Also my laptop reads the card perfectly,its just the phone that seems to reject my SD cards. BTW I tried 2 cards using the methods mentioned and the phone just refuses to mount the card. Any help would be greatly appreciated!
It fails to mount either of the cards you've tried? That's a concern. Did you do a factory reset of the phone after you bought it?
yea I did,im so confused.
I would try rooting the phone and either odin it or flash a new rom and see if that works either that or maybe that's why the kid was selling it on craigslist
Sent from my SGH-T839 using XDA App
Is there a way to do that without a SD card because it seems like a SD card is a requirement to flash anything.
You can both root and odin without an SD card.
Alright,i rooted and unrooted my phone multiple times. Its currently rooted so im going to try ODIN now.
Once you Odin , try to see if the /SDCARD mount's if it dosen't it could be a /SDCARD faulty .
STravers said:
Alright,i rooted and unrooted my phone multiple times. Its currently rooted so im going to try ODIN now.
Click to expand...
Click to collapse
I used odin and i think i bricked my phone . It said in the first box of the application failed in red and on my phone it was a status line in blue that seemed to be not moving. So what i did was rebooted the phone and it hangs on the samsung splash screen. It is able to go back into downloading mode but theres nothing i can do because it always fails to complete the process.
STravers said:
I used odin and i think i bricked my phone . It said in the first box of the application failed in red and on my phone it was a status line in blue that seemed to be not moving. So what i did was rebooted the phone and it hangs on the samsung splash screen. It is able to go back into downloading mode but theres nothing i can do because it always fails to complete the process.
Click to expand...
Click to collapse
what boxes do you check?
I got odin to work but the memory cards still fail to mount.
Do you have another phone/sdcard slot in your computer that you could use to try mounting them? they could just be dead SDcards.
EDIT: read the OP, jk about another computer.
If known good cards won't mount in your phone, it's most likely a hardware defect. Send it back home to Samsung

[Q] Need help repairing my Nexus s I9020?

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

Lost SD card access and can't mount USB

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 .

Stuck at Google screen, Can't mount E [I9020A]

So, as the topic states, I'm having major problems as of late.
Nexus S, GT-I9020A
ROM: CM9
Over the past few months, my phones been acting up. My phone when rebooted stalls at the Google Lock Screen. I am unable to mount the E drive in CWM as well,
Going into CWM,
1) wipe data/factory reset gives me problems, results below
--Wiping Data...
Formatting /data...
E: Format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
2) wipe cache partition
--Wiping cache...
Formatting /cache...
Cache wipe complete.
3) Mounts and Storage
Error mounting /sdcard!
Error mounting /system!
Error mounting /data!
format /sdcard ...
Error mounting /sdcard!
Skipping format...
Done
4) Apply update from .zip file on SD card
E: can't mount /sdcard/
.... That's about all the options that I would go through to fix a rom. I don't know what else to do, last time this happened the E drive magically mounted and I was able to turn my phone back on, this time I've not been so lucky.
Reading around, I haven't been able to get any information on where to go next, most topics seem to be successful with the things I've done. I'm afraid that the phone is bricked, is there anything else I could try before I throw in the towel?
What version of CWM recovery are you using?
polobunny said:
What version of CWM recovery are you using?
Click to expand...
Click to collapse
I knew I forgot something,
v5.0.2.0
Bump to the top,
Is there any insight on the way forward? I've heard of Odin as something that may help, but from what I've read, Odin is only Samsung, Fastboot for Google.
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
DizturbedOne said:
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
Click to expand...
Click to collapse
Ah, seemingly so eh? The phone is probably not even worth sending it in as it would probably cost just as much to buy a new one.
I don't have CWM Touch (assuming that's CWM with touch function), just CWM that requires the vol rockers. It's an old version.
Hmm, it's been a while, but how would I be able to change the recovery if I can't access the E drive? I presume ADB? Then hope it works?
Anyways, thanks for your help, it's been quite frustrating seeing nothing turn up.
Another bump in hopes anyone with a fix reads this.

[Q] Help - Can't mount internal storage?!? Brick?

I was running TWRP 2.7 and told it to wipe the drive. An hour later, it looked like it hadn't moved. I powered down. Then the system bootlooped and TWRP stopped working, not loading past the splash screen.
Using Fastboot I was able to reinstall TWRP 2.7 but it can no longer access the internal drive. I am told it is a size zero. I can't wipe the drive it fails for errors. I can't seem to find a solution.
I downloaded the stock firmware from Asus and tried to install that. No luck, it fails out immediately. I only tried to install the zip file inside of the zip file from Asus using TWRP. No matter what I can't delete or remove the partitions. If I run TWRP 2.6.3 it asks for a password I don't have, as if the drive is encrypted. I also tried Philz CWM and normal CWM and nothing can touch the partitions.
I am starting to get really worried now. I can't seem to find a simple process to restore to stock. I am TEMPTED to use the WIPE DATA function of the Asus Bootloader. But without the Asus recovery on there, I have no idea what will happen.
Can anyone recommend a course of action to restore this to stock? At least to get the Asus Recovery on there? I am running bootloader 10.6.1.14.10.
Thanks to everyone that can help!!!
In TWRP, format (not only wipe) data, but this time be patient until it is finished.
_that said:
In TWRP, format (not only wipe) data, but this time be patient until it is finished.
Click to expand...
Click to collapse
I am totally beside myself. I did exactly as you mentioned about 15 times last night. All that would happen is TWRP would restart after I typed YES.
Today, I did it, and BAM it started working. I will let everyone know how it went in a few hours. I am not touching it again.
Maybe I was just way overtired at that point.
Thank you for the help!!
BigKenW said:
I am totally beside myself. I did exactly as you mentioned about 15 times last night. All that would happen is TWRP would restart after I typed YES.
Today, I did it, and BAM it started working. I will let everyone know how it went in a few hours. I am not touching it again.
Maybe I was just way overtired at that point.
Thank you for the help!!
Click to expand...
Click to collapse
That did it! I was able to install CROMBi-KK and am moving forward!!!
I'm in basically the same boat (I think I got there the same way), except when I try to format now, I get:
Code:
Updating partition details...
E: Unable to mount '/system'
Full SELinux support is present.
Formatting Data using make_ext4fs function.
This is where it sits for an indefinite period of time. In my troubleshooting attemps I've had it display similar messages elsewhere about being unable to mount the /system folder. I tried going into Mounts even and it won't let me check that box.
For now, I'm going to just leave this sit here at this screen for a few hours while I "work" and see what happens, but if anyone has any brilliant ideas, I'm all ears!
SgtMac02 said:
I'm in basically the same boat (I think I got there the same way), except when I try to format now, I get:
Code:
Updating partition details...
E: Unable to mount '/system'
Full SELinux support is present.
Formatting Data using make_ext4fs function.
This is where it sits for an indefinite period of time. In my troubleshooting attemps I've had it display similar messages elsewhere about being unable to mount the /system folder. I tried going into Mounts even and it won't let me check that box.
For now, I'm going to just leave this sit here at this screen for a few hours while I "work" and see what happens, but if anyone has any brilliant ideas, I'm all ears!
Click to expand...
Click to collapse
You should let it finishes the formatting on your /data partition and ignore the /system for now. One user had a very similar issue and reported that it took almost 4.5 hours on his/her device for formatting on his /data partition. It was up running after that so be patient and plug the AC in for your device until it is finished the job, good luck....:fingers-crossed:
LetMeKnow said:
You should let it finishes the formatting on your /data partition and ignore the /system for now. One user had a very similar issue and reported that it took almost 4.5 hours on his/her device for formatting on his /data partition. It was up running after that so be patient and plug the AC in for your device until it is finished the job, good luck....:fingers-crossed:
Click to expand...
Click to collapse
Dude. I don't know how long it actually took. I had waited before for more than an hour and assumed it wasn't going to work since there was ZERO indication of progress. I started it this morning and checked it after I came back from lunch about 4+ hours later and it did indeed work out. I was able to successfully reflash a new ROM again after that and all is well! I'm so glad I finally stumbled across this thread or I don't think I would have ever though to just leave it to do anything for more than an hour. I still can't believe it would take that long...but I guess it does!
I had the same problem (twrp showed internal as 0gb). Is a twrp 2.7 thing or a kitkat thing. Thanks to know I wasnt the only one who f uped. Now I'm back and running. Thanks for the help.
Sent from my UNLOCKED SM900V.
I hope it's not "Another brick in the Wall"
The format was interrupted and now I'm getting the can't mount internal memory. I started the format again and plugged it in and I'm going to leave it alone over night. I hope it works.

Categories

Resources