Nexus S storage corrupt - Nexus S Q&A, Help & Troubleshooting

Hi, I'm having a lot of issue with my Nexus S so I want to reflash with full 2.3.3 image... The thing is when I mount the phone and copy the file, after I reboot the Nexus S to go in recovery... The update.zip is not there. I tried to create a folder and put some files on it... When I unmount the phone and remount it ... everything is gone except "LOST.DIR | .android_secure | Android | DCIM. The rest is gone .... Looks like the phone memory is corrupt ...
Looks like everytime the phone use the memory everything begins to crash (force close of all application) and even the phone just freeze and I need to remove the battery.
Is there any way I can save my phone? Probably a bad flash or something cause this issue (I flashed to gingerbread 2.3.3 from the file found on this forum)
If anyone is able to help.... it will be appreciate.
Thanks.

Here's something to add:
Looks like the whole storage is read-only (at some point) I'm changing some settings and after a reboot it's not kept ... backgroung is default, google account is not configured .... Even tried to factory-default again and it gives me a unable to format /system or /data I don't remember the whole line ... I was kinda stuck in the custom recovery where you can flash from /sdcard/update.zip ... I look at the mount with "adb shell" and it looks OK.
I can provide adb logcat if needed ... But any help will be appreciate ...
Thanks!

Put the phone in download mode then reflash using Odin after it boots go into settings and wipe your SD and then do a hard reset. That should fix any problems.
Sent from my Nexus S

if you have CW recovery installed, you can use it to fix the permissions issues

Hi,
I tried the odin flash and no good... now I installed the CW recovery and tried the fix permissions... looks like it's hang... is this procedure long?? I'll leave the phone like this...
Tried to wipe to factory default and reflash... same issue has before, update.zip is not staying on the usb storage... Is there another way to fix this issue...
Thanks for your help, appreciate!
Sent from my Nexus One

Ok, fix permissions done, still not working... tried to factory default... No good.... Any ideas?
Sent from my Nexus One

SpOuK-3- said:
Here's something to add:
Looks like the whole storage is read-only (at some point) I'm changing some settings and after a reboot it's not kept ... backgroung is default, google account is not configured .... Even tried to factory-default again and it gives me a unable to format /system or /data I don't remember the whole line ... I was kinda stuck in the custom recovery where you can flash from /sdcard/update.zip ... I look at the mount with "adb shell" and it looks OK.
I can provide adb logcat if needed ... But any help will be appreciate ...
Thanks!
Click to expand...
Click to collapse
I have the exact same issue... were you able to fix it?

in the worse case scenario, in CWR advanced menu you can format the internal SD card

I'm very interested to hear how you get on with this, sounds like the infamous freezing problem that the Nexus S seems to suffer from.
Please let us know how you get on and if the suggestion above to format the internal SD with cwm works.

xspyda said:
I'm very interested to hear how you get on with this, sounds like the infamous freezing problem that the Nexus S seems to suffer from.
Please let us know how you get on and if the suggestion above to format the internal SD with cwm works.
Click to expand...
Click to collapse
Tried it... it doesn't work ... SpOuK-3- said he sent his phone to samsung

legojj said:
Tried it... it doesn't work ... SpOuK-3- said he sent his phone to samsung
Click to expand...
Click to collapse
Bugger! I was hoping there would be another way. Out of interest, had either of you recently performed an update either ota or manual?

try fastboot oem lock and then fastboot oem unlock.
unlocking the bootloader will wipe and format ur sd card

deeren said:
try fastboot oem lock and then fastboot oem unlock.
unlocking the bootloader will wipe and format ur sd card
Click to expand...
Click to collapse
Yea i have tried that, no success.
And yes I did a nightly update (build 39)

legojj - as above had you recently performed an update when you ran into this problem?

xspyda said:
legojj - as above had you recently performed an update when you ran into this problem?
Click to expand...
Click to collapse
Yes, i went from cyanogens nightly build 38 to nightly build 39.

legojj said:
Yes, i went from cyanogens nightly build 38 to nightly build 39.
Click to expand...
Click to collapse
I figured that would be the case (though not necessarily cyanogenmod related). This seems to be the common factor with all Nexus S phones suffering from the freezing issue - the problem always starts pretty soon after an update.

xspyda said:
I figured that would be the case (though not necessarily cyanogenmod related). This seems to be the common factor with all Nexus S phones suffering from the freezing issue - the problem always starts pretty soon after an update.
Click to expand...
Click to collapse
Do you know if there is any way of fixing it, cause I have even used odin and still nothing. Do you know what the re partition check box in odin does?

As far as I can tell there is no way to fix it, not for us users. Not even sure Samsung fix the issue, seems they just give replacements which is quite worrying.
I started a thread about the freezing issue to gather info and hopefully to find a pattern / solution to the problem. Apart from establishing that the problem seems to occur after an update in.every case, so far no dice.
I'd be delighted to hear of a fix as I feel like I'm waiting for a time bomb to go off with my Nexus S!

Ok... so after doing some reserch i decided to use adb shell to delete the sdcard partition and remake it inorder to hopefully find the error. Everytime i tried deleteing the partition, nothing happened. So i tried resizing it and then i got the error that saying
" /.../clockworkmod/backup/.../data.img is corrupt run scandisk or chkdisk. "
Two things that dont exisist or i dont know how to use on adb shell. Anyways, it seems the corrupt file was created by my clockworkmod before i updated to the new cyanogen.

That's interesting although from my own research I'm not convinced cwm is the cause of the freezing issue as there are many reports of people running into problems without having ever flashed a custom rom or recovery.
I'm glad you're trying to get to the bottom of this though, it wiuld be great for us to be able to find a solution.
I refuse to believe the only sulolution is to replace the phone - can't see this being anything but software related.
Please keep us posted.

Related

skyrocket keeps rebooting every 1 or 2 minutes

I have a strange issue with my samsung galaxy s2 skyrocket AT&T, it keeps on rebooting every one or two minutes, by itself.
I have been busy with this for two days without success, I tried the following:
- unstalling apps: not working, after any reboot (automatic or manual) the apps reappear again.
- using Odin to install another rom. Not working, even after a green success signal in Odin, the phone reboots and nothing has changed. All (many) apps that I installed still are present, the same settings etc, everything is the same. I tried to install different ROMS with Odin, without any effect.
- deleting all folders and files when the phone is plugged in the pc,...after phone reboot all folders and files re-appear again, nothing changed.
Assistance with this issue is very welcome.
Thank you
I've seen this issue before with it rebooting because of a stuck power button. Not sure if that would be the culprit in your situation or not. Especially with folders re-appearing and what not.
sounds like the same as this http://forum.xda-developers.com/showthread.php?t=1751338
possible fix Using loop devices to workaround corrupt eMMC partitions
Had the issue before. Never pinpointed the exact cause, but I moved all my pics/music/crap I wanted to keep to my external and went ape chyt on wiping. Formatted internal via the comp, then went into mounts & wiped everything! Fresh install & only reinstalled apps (no data) with titanium. Been smooth sailing since.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
suaver quarterly
vincom said:
sounds like the same as this http://forum.xda-developers.com/showthread.php?t=1751338
possible fix Using loop devices to workaround corrupt eMMC partitions
Click to expand...
Click to collapse
This ^^^^^ Is what fixed mine
Tsaxmafia said:
This ^^^^^ Is what fixed mine
Click to expand...
Click to collapse
The workaround in http://forum.xda-developers.com/showthread.php?t=1704646 is too complicated for me. I'm not a programmer, just a regular user that knows how to use Odin and install a custom ROM, but that's it. I guess I have to return it under warranty by AT&T
Although I would like to erase everything (i got a backup). At the moment all data, apps, email and phone numbers are visible when booting up (at least for 1 or two minutes before it reboots by itself) and I don't like them at ATT checking that out.
orfeo.one said:
The workaround in http://forum.xda-developers.com/showthread.php?t=1704646 is too complicated for me. I'm not a programmer, just a regular user that knows how to use Odin and install a custom ROM, but that's it. I guess I have to return it under warranty by AT&T
Although I would like to erase everything (i got a backup). At the moment all data, apps, email and phone numbers are visible when booting up (at least for 1 or two minutes before it reboots by itself) and I don't like them at ATT checking that out.
Click to expand...
Click to collapse
then try bricking it, use odin and check repartition and see what happens, also see if a factory reset will wipe your data
vincom said:
then try bricking it, use odin and check repartition and see what happens, also see if a factory reset will wipe your data
Click to expand...
Click to collapse
I tried to brick it without success yet.
Odin repartitioning gives this message:
"Can't open the specified file. (Line: 1876)"
and give a FAIL
Factory reset has not effect whatsoever, all stays the same. By the way, gives this message
Error mounting /sdcard/ .android_sercure!
Any other bricking methods/tips are welcome
Thanks
orfeo.one said:
I tried to brick it without success yet.
Odin repartitioning gives this message:
"Can't open the specified file. (Line: 1876)"
and give a FAIL
Factory reset has not effect whatsoever, all stays the same. By the way, gives this message
Error mounting /sdcard/ .android_sercure!
Any other bricking methods/tips are welcome
Thanks
Click to expand...
Click to collapse
try mount the sdcard, flash a tar file from another phone or a zip file from another phone like the i777, i know that it didnt write to the nand before but you never know. or learn how to use adb, maybe it can delete stuff, but i never used it so cant help u there.
u can also try to short out the usb port by touch wires inside the port as it may fry something up in the phone so it cant turn on
If you installed an app that seems chair than what it should be worth or from a random website, you could have a virus...first try uninstalling the culprit, if not, you may need to do a factory rest
Sent from my SGH-I727 using Tapatalk 2
raynan said:
If you installed an app that seems chair than what it should be worth or from a random website, you could have a virus...first try uninstalling the culprit, if not, you may need to do a factory rest
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've gone through all that, factory reset, uninstalling apps etc..nothing works since after the auto reboot all changes appear to have no effect. I.e. new pictures taken are not stored after the reboot. I'm stuck with all settings and files of one particular time a week ago, that keeps on reappearing. As far as I understand this is a corrupt partition issue. But thanks for replying anyway..this issue doesn't seem to happen very often.

Type password to decrypt storage?

I've had my Nexus S for a year now and it's been pretty problem free... When it had Gingerbread it had the odd reboot glitch but since ICS it's been solid. I have the bootloader unlocked and had root. I had tried out a couple of custom ROMs and had gone back to stock ICS in anticipation of JB rolling out in July. I got the OTA push of JB in mid July and after a factory refresh have had no problems with the phone until yesterday.
I was typing a text message and my phone rebooted in my hand. It never did complete booting and left me at a prompt that stated "Type password to decrypt storage" and nothing would make this phone boot! Also, since the JB update I no longer had root and Clockwork Recovery no longer worked because I didn't have root... which I wasn't worried about up until now. I had to tether the phone to my laptop reset Recovery using the SDK tools and then wipe everything and reset the phone and reinstall all my apps. Funny thing is I've not been able to find much about this from any of the forums I read frequently... seems there aren't many who have experienced this.
Just wondering if anyone else has run into it...
it's happend for me too. i had to wipe cache and fixed.
Same thing happened to my Nexus S. I have no idea how it came into this "type password to decrypt storage" damned state. I'm trying all passwords and PINs I know but none is working! I'm trying to avoid a factory reset.... Isn't there a way to log in and override this thing, something like forgotten password in emails???
still no solution for this? i've wiped data and cache and still no fix!
I'm facing the same issue: woke up this morning to find my phone asking for a password in order to decrypt storage. Very annoying, since I don't have a very recent backup.
Running CM10.1 nightly 0210 with stock CM kernel. I tried reinstalling CM and wiping cache, but that didn't help. I'll see if I can fix it and and will repost here if/how I fixed it.
gearjunkeez said:
still no solution for this? i've wiped data and cache and still no fix!
Click to expand...
Click to collapse
If you can boot into bootloader (fastboot), try to flash Google factory image.
untar (unrar/7-zip) the tar file and flash the update zip within. This should wipe everything including system.
Code:
fastboot -w update image-soju-jzo54k.zip
kooske said:
I'll see if I can fix it and and will repost here if/how I fixed it.
Click to expand...
Click to collapse
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
HELP!
I just had the same thing happen to my phone. Can you please dumb down what you just said for me? The only part I care about is how to recover my pictures. I haven't done the factory reset yet as I've been trying every password I can think of and now see that it is a bug and not something I have done. Anyway, I have 3 gigs of pictures of my 18 month old that I will cry if I lose so if you can help me recover them I would really appreciate it. I have tried hooking my phone up to my computer in it's encrypted state and it does not register. Please explain what you did in simplified terms for me as I have no idea what ROM or CWM means. Thanks!
kooske said:
It seems that there is no other solution for this other than a wipe data/factory reset. It's the solution offered in a googleGroups discussion as well. (Can't post links yet, not enough posts...)
Luckily after re-installing ROM and gapps all my apps were restored, and I was able to extract all my pictures and some backups on the sdcard using the mount USB option in CWM. So no big data loss for me.
It's a strange issue though, and should've been solved long ago. First occurrence I found was somewhere in February 2012, that's a year ago!
Click to expand...
Click to collapse

[Q] after installing 4.4.1 - no cellular + data - SOLVED

SOLVED! see solution in the first comment.
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
hbhc123 said:
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
Click to expand...
Click to collapse
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Synyster06Gates said:
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Click to expand...
Click to collapse
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
hbhc123 said:
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
Click to expand...
Click to collapse
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
chi_heng said:
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
Click to expand...
Click to collapse
Flash the newest version of TWRP. The issue is fixed.
Synyster06Gates said:
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
Click to expand...
Click to collapse
I have done what you said and it worked perfectly
many thanks!
hbhc123 said:
I have done what you said and it worked perfectly
many thanks!
Click to expand...
Click to collapse
No problem! Glad you got it taken care of.
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
any one else
benbailey84 said:
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
Click to expand...
Click to collapse
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
ddloco said:
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
Click to expand...
Click to collapse
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
benbailey84 said:
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
Click to expand...
Click to collapse
Well in our case I have my efs on my PC from weeks ago restoring it doesn't fix whatever the ROM changed lol

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.
Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(
Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged
Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?
help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
im also having this issue with my galaxy tab2 7".. help is badly needed
Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app
hope someone finds a solution for this.
No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?
sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
same problem please help me... :crying:
seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....
Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

[Q] Bricked xt925 - read-only eMMC ?

Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?
Why not flashing a stock firmware to go back to STOCK?
joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.
I agree with bwen diord...aint never see anyone recover from that, least not yet.
cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA

Categories

Resources