Database Info

[Q] Nexus S (wind mobile) can't factory reset! (jellybean)

Hi, first post here.
So I bought a Nexus S that was rooted and updated to Jellybean. It's an unlocked phone originally locked to Wind Mobile.
So it's been having issues with getting stuck on the google logo after reboot, so I decided to sell it. Problem is when I go to factory reset the phone it shows the reset bar but then that turns into a big triangle with an exclamation mark on it with a little android guy next to it. The phone gets stuck there. All I can do from there is remove the battery.
From there I tried going on bootloader using power and volume up (says unlocked btw), and from there I load recovery. On recovery there is an option to factory reset and I click on there, however it doesn't do it. This is what I says:
"--wiping data...
formatting /data...
E:format_volume: make_extf4fs failed on /dev/blo/ck/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."
So I think the error might be accociated to the sd card because the Nexus S doesn't come with an sd card, it has built in memory? Also on recory when choose "mount sd card" it says"Error mounting /sdcard!".
So how do I go about fixing my problematic phone? I have a dude that wants to buy it but I can't even reset the damn thing, let alone fix the freezing at start up issue. I am also totally new to this.
Extra info: When the phone freezes at the google logo at start up I get passed that by using a blow dryer on the phone. That's the only way I start up the phone after the battery comes out. This is the gt-i9020t model.

Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!

gunner49 said:
Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!
Click to expand...
Click to collapse
I don't know if it's a custom recovery because the previous owner installed everything/rooted.
When I press power and vol. up, It looks identical to the uploaded picture's bootloader/recovery.

Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.

gunner49 said:
Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.
Click to expand...
Click to collapse
In advanced there is no option that worked.

*Solution*
Ok so for those having this problem this is what I dug up:
Internal SD card error causes the boot freeze/factory reset error. When you try mounting SD card it fails, this is also what makes me think it's a fault with the phone's internal SD card.
I do not know how to "fix" this fault, however I'll tell you what I did to get passed this issue.
1) Heating up the phone helps bypass the frozen screen. On Boot it goes to the google logo and freezes, but you can get passed this by heating up the phone (using a blow dryer) before hand and it's relatively successful.
2) I believe that before factory resetting the phone (whether using recovery or the actual reset option on settings), if you heat up the phone, it might work the same way it works when booting up.
I did not try 2) because I managed to "reset" my phone manually by uninstalling all apps, deleting all files/cache/photo's/accounts, and by clearing all app data. This works just as fine if you ask me.
Overall this solution has not been "fixed", I encourage people to find a real fix, but for now using the blow dryer and manually resetting is one way around the problem.

Am I going to have to send it in to Samsung for reflash?

I hadn't touched my tab for a couple weeks since I only really use it in my car as a GPS and Entertainment center but when I grabbed it to charge it up, it was completed drained. No problem here since this has happened before and I'd just charge it up. So I boot it after the full recharge and it's stuck on the Samsung Galaxy Tab logo. After a little while I check it again and I'm like, "Crap, it's bricked. I'll need to reset it with Odin."
I proceed with Odin and nothing. It's still bricked. I do a factory reset and this is where I notice my big problem. When I do a factory reset or reboot I get
E:Can't open /data/log/recovery.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernel_log.txt
I tried reflashing the kernel, pit and firmware and I'm getting nowhere. What gives?

try removing the SD card and see if it boots up.

DigitalMD said:
try removing the SD card and see if it boots up.
Click to expand...
Click to collapse
Still no go but this did give me an idea. I just tried a simple reboot from recovery WITHOUT the SD card and got the error:
E:Failed to mount /sdcard
E: is the SDcard so I will create the directory with the files I mentioned above. I found the files on a different thread regarding a Samsung Galaxy phone. This may work.
I'm also going to try another flash without the SD installed to see if I have any luck there.
Thanks.

Issue is fixed
I decided to reflash while the SD card was removed and it got passed the initial splash screen. It was stuck at some wierd lock screen asking for a password. I went into recovery to do a wipe and factory reset and that brought the tablet back to life on reboot.
All is good again.

Incorrect Internal Memory Showing

My phone has 128GB internal memory, I've just flashed new firmware on it as I couldn't update my software.
Now my internal memory is only 16GB instead of the 128GB, is there anyway to fix this?

Tried flashing the stock ROM again, now I'm just getting the black screen with the white Samsung logo at the start.

Managed to fix it, this thread can be deleted now.

hey man, i have the same problem. I have the 32gb version and after flashing android 7.0 with odin it only recognize 16gb. How have you fixed it? thanks!

geto_llb said:
hey man, i have the same problem. I have the 32gb version and after flashing android 7.0 with odin it only recognize 16gb. How have you fixed it? thanks!
Click to expand...
Click to collapse
I remained persistent, I put it in recovery mode, wiped the cache and did a factory restore and reflashed android 7.0 and it worked after that, if it looks like the phone won't boot and it's stuck on the Samsung screen, leave it for a bit as it may start, I was impatient at first and thought it wouldn't boot and kept messing with it unnecessarily.

sharvey3878 said:
I remained persistent, I put it in recovery mode, wiped the cache and did a factory restore and reflashed android 7.0 and it worked after that, if it looks like the phone won't boot and it's stuck on the Samsung screen, leave it for a bit as it may start, I was impatient at first and thought it wouldn't boot and kept messing with it unnecessarily.
Click to expand...
Click to collapse
Recovery mode, Vol up + Home + Power keys. Vol keys to move up/down and power key to select.

Thanks! I finally tried making a factory reset and a partition wipe in the recovery mode and it just restart fine with all memory being recognized

sharvey3878 said:
Managed to fix it, this thread can be deleted now.
Click to expand...
Click to collapse
plz tell how you did it ?

Help needed diagnosing possible nand memory problem - Samsung Note 8.0 n5110

So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.

oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516

Help Get My P5110 Working Again!

Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
# MANUAL MODE #
-- Appling Multi-CSC ...
Applied the CSC-code : BTU
did not match sized '/system/csc/common/system/csc/others.xml (No Data Available)"
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.

PFMC84 said:
Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.
Click to expand...
Click to collapse
See the best way to get out of this is to install the stock Samsung firmware using the ODIN tool.
Then if you ever wish to install a custom rom again you can do as you like. Hope this helps. If you are require assistance, feel free to reply to this conversation.

I have tried a few times to flash the stock firmware with ODIN but it would either install the whole thing but it actually didn't work, or the install would crash part way through.
Unless there is some error with the stock firmware I've found online, is there a link to the proper one that I can download from somewhere? Or a specific version of ODIN that is needed for it to work?