Related
Hey guys I seem to have quite a problem with my skyrocket. My internal storage has become read-only. No amount of wiping, formatting, or flashing with ODIN changes anything.
As soon as anything on my phone tries to save data, the /data partition gets remounted as RO and every app begins to crash.
I tried a factory reset, which reported success until I booted up and everything was still there on the phone.
So I tried to reflash the phone with ODIN which also reported success, but when the phone rebooted it was still running the same ROM (CM10 nightly) and all my old data was still there. I've tried flashing both the rom and the recovery and neither can be written to.
Any ideas on what happened? Sadly the phone was a refurb and so it's 90 day warranty is up so I can't just send it in.
Edit: I should add that I didn't do anything to the phone when this happened. It happened during the evening while I was out. I woke up the next morning to my phone force closing and on reboot all the texts and pictures I had since about 12:30 AM were gone.
What did you flash with Odin?
Try flashing a completely stock build.
Remounting partition as RO happens when partition has errors. You might want to reflash stock with repartitioning, there is a PIT map in one of the threads on the main page of Q&A.
Jack_R1 said:
What did you flash with Odin?
Try flashing a completely stock build.
Remounting partition as RO happens when partition has errors. You might want to reflash stock with repartitioning, there is a PIT map in one of the threads on the main page of Q&A.
Click to expand...
Click to collapse
Originally I tried flashing a different CWM build and TWRP. Neither of which actually got written to the phone.
I just tried flashing stock ICS without repartitioning and it booted right back into CM10.
So next I tried flashing stock with re-partitioning checked and a PIT file vincom had posted in another thread. It still booted right back into CM10 after reporting success in ODIN.
Very strange, but if even download mode doesn't succeed in writing to the device - I don't think there's anything that can be done but HW repair.
That's what I thought as well. I've found a couple of other people with the same problem throughout the various GS2 variants. Unfortunately the only fix I've seen anyone find is to get a replacement from Samsung.
I may have to buy one off someone with a broken screen and swap out the circuit boards.
to clarify, do not check "repartitioning" in odin, it will cause a hardbrick for the skyrocket, in op's case he has a nand error so repartitioning wont cause a hardbrick because it wont repartition since it wont write anything because a failure in the nand(write failure). as far as i know its a hardware failure and there is no workaround for that failure. but u can read this post http://forum.xda-developers.com/showthread.php?t=1704646 and see if the steps there will help
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Odin?
EatonZ said:
Hello, I am in a bit of a jam and am trying to find the best way out.
My device is encrypted using the native Android feature. I have Lean Kernel and CleanROM on the device. So it is rooted/unlocked. I was trying to clean the device further by uninstalling some useless apps with Titanium Backup. Turns out I messed up on something..
When the phone boots to the encrypted device screen, the keyboard doesn't show up! I am not able to get into the phone to do anything!
I have the latest CWM recovery installed. I tried a factory reset and such, but it says it fails to mount the internal SD card. /:
Anyone know how I can fix this and flash a new CleanROM? Data wiping is not a problem for me, but CWM refuses to mount the SD card to do it..
Any advice? I am relatively new to the Android scene, so try not to make things too complicated.
Click to expand...
Click to collapse
This probably wouldn't work, but have you tried reflashing with Odin?
budzylikessoup said:
This probably wouldn't work, but have you tried reflashing with Odin?
Click to expand...
Click to collapse
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
flanks vidsguir
budzylikessoup said:
I'm not sure if it will work, as I don't encrypt my device. What it will do is wipe your system, data, etc. partitions, but it won't touch your internal SD. This will probably be fine; it will install a keyboard and you should be able to enter your password, that is, if it can flash the ROM properly.
Click to expand...
Click to collapse
I'm still trying to understand how Android storage works, so I may sound like a noob here haha..
All I have is an internal SD card. I don't have an external one or anything. Are system, data located on another internal flash chip or something? If they are on the internal SD, I would imagine everything would be formatted and reset once this is flashed.
Sorry, I read the linked post wrong...So this will wipe everything, system, data, and internal SD.
As for the difference, the system and data are different partitions than the internal SD.. so normally when you factory reset in CWM, it just wipes the data, not your internal SD or system. What this means is that it won't touch some files, like ones you download from the internet, but it will get rid of all of your apps and appdata, as you know, and these are stored in the data partition.
I got it sorted. Thanks for the help.
Glad I could help!
EatonZ said:
I am looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1984436
I am downloading the very first package. Since that seems to wipe everything, which is what I want at this point.
Will flashing that work?
Click to expand...
Click to collapse
Just wanna say this thread was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
EDIT:
I just got a response on twitter from a friend who ran into the same issue with clockwork. According to him, apparently TWRP doesn't have this flaw. My phone's working now and I don't want to monkey around with it anymore, but maybe a more experienced user out there could comment on/confirm this, and maybe add the info to the tutorials (if it's correct).
Thanks again!
SpoonlessCorey said:
Just wanna say this post was a lifesaver, and I'll just leave my experience here for fellow noobs, like myself, stumbling into this issue.
I CMod'd my S3 with Clockwork (following very detailed instructions) and tried out encryption (knowing ahead of time that a factory reset would be in order if I didn't like it). As you all know Clockwork has trouble mounting the encrypted /sdcard/ directory, and won't do the factory reset. I was afraid that since Clockwork couldn't deal with the encrypted data, so too might Odin, leading to the risk of bricking. This thread gave me enough courage to give it a go. Following the above linked instructions solved the problem. Odin had no problem wiping and writing over the encrypted data. after I was back to stock I ran through installing Clockwork and CMod again. And just like that, the problem's fixed.
Thanks a bunch everyone!
Click to expand...
Click to collapse
Yeah, I was worried I might have created a $200 paper-weight!
I'm glad that my question ended up helping you as well!:good:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...
shmusername said:
Hi, I've been meaning to write this since 2016 or 2017, I think, butI think I can still remember all the important details of this crisis...
So I had rooted this 'Galaxy Avant' phone originally so I could disable/remove the extra stuff of the systems' in the hopes of improving the phones' performance, but I didn't change the OS from whag metropcs gave me at that time. I also had a password and/or a pin lock on both the sd card, startup, and internal memory. Everything was okay until I ran into a wifi issue where it wasn't connecting to a semi-public wifi hotspot, so I thought if I cleared the wifi apps' cache the issue would go away. Trouble was I didn't know that the wifi cache wasfor some reasin the same as the system's cache, and a few seconds after clearing it, my phone crashed, and continued to restart itself. So I panicked and tried removing the password/pin locks for easier backup to recovery/resetting. Well the external sdcard managed to decrypt, but when I proceeded to attempt the same for the device, it decided to factory reset itself.
I lost nearly everything from that event. I did periodic backups to the sd card but not daily and since that phone was also responsible for my own memory retention, at least a month or two of my soul is still missing. Any new contact, commitment, itinerary, life decision, goal, deadline, or other important note from that time was wiped and can't be found anywhere else, and I still don't know who else is or was affected from this (especially if I had just made their acquaitance).
So all that to say I must get this device back to how it was before the cache-wiping incident. The phone hasn't been turned on since, except to dump the system image onto my linux desktop. With testdisk I can see what I assume are the deleted partitions from before the factory reset, but I don't know how to undelete+decrypt them and/or copy them back to the device. Please tell me honestly that there's a way to do this, and what that way is. My functioning really depends on it...
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Go to Sammobile .com or samsung-updates .com, enter your model number in their search feature to find your stock firmware. If you can find the firmware, you can use Odin to flash the firmware to restore the device to normal function.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...
shmusername said:
Thanks, but the device already functions normally; it reset itself to factory defaults, after all.
I just want to be able to restore the device to as it was before the accidental cache wipe—apps as they were, files, and all...
Click to expand...
Click to collapse
Oh, you mean you want to recover your lost data. All I can say is try some data recovery software on PC, there isn't any guarantee that it will work though. Data recovery on android is not very reliable.
Sent from my LGL84VL using Tapatalk