Related
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
aburn95 said:
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
Click to expand...
Click to collapse
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
stephen_w said:
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
Click to expand...
Click to collapse
So everything should run fine after trying the actual restore of my backup even though i couldn't format the system? I have a backup but don't want to restore over data that wasn't deleted or whatever. If that's possible.
How the hell do i know which modem to use anyways? There's like 10 to choose from
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
aburn95 said:
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
Click to expand...
Click to collapse
As for the modem, I'm using KI3 on mine. You already did a factory reset so you should be able to just re-flash Valhalla.
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
aburn95 said:
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
Click to expand...
Click to collapse
I'm not sure about that one. Definitely go check the original Valhalla post to make sure you don't have to set the mounts.
Guess you don't have too. I'm using it now. thanks for the help
aburn95 said:
Guess you don't have too. I'm using it now. thanks for the help
Click to expand...
Click to collapse
No worries. Good luck
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
aburn95 said:
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
Click to expand...
Click to collapse
Did you restore your previous apps are do fresh installs?
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
aburn95 said:
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
Click to expand...
Click to collapse
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which backup your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
stephen_w said:
No worries. Good luck
Click to expand...
Click to collapse
lumin30 said:
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which on your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
Click to expand...
Click to collapse
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
aburn95 said:
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
Click to expand...
Click to collapse
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
aburn95 said:
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
Click to expand...
Click to collapse
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
lumin30 said:
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
Click to expand...
Click to collapse
Ok cool. In another phones forum a system wipe is actually suggested a lot. I think... I did it every time on the G2x before installing any new roms or backups. I wasn't doing it at first but started after someone suggested it. But yeah I think the factoy reset is enough. Seems to be enough so far.
aburn95 said:
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
Click to expand...
Click to collapse
I am a noob too. No worries. Vahalla Black is solid. Backups are tricky. Fresh installs are the way to go.
Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance
What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.
As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium
thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again
No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847
Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium
Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks
okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again
reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol
jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.
Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?
thank you
that's what i ended up doing and it worked. thank you so much for all your help!
Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.
Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium
UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...
Hi. I was toolin' along doing real well on CleanRom 4.5 for several days. Starting yesterday, the phone would randomly reboot itself to the HTC screen. I figured I had a bad app or something. Today, I went to open an app (Draw Something) and the phone froze for a bit. Then it rebooted, and now I cant get it booted back up. I usually never make it past the HTC screen. Got into recovery once but it rebooted in the middle of clearing the cache.
Any advice?
Welp, just made it through cache and dalvik and rebooted in the middle of factory reset. I wonder if I'm doing more harm than good.
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
hcricket said:
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
Click to expand...
Click to collapse
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
omario8484 said:
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
Click to expand...
Click to collapse
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
hcricket said:
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
Click to expand...
Click to collapse
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
omario8484 said:
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
Click to expand...
Click to collapse
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
hcricket said:
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
Click to expand...
Click to collapse
What's your battery at?
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
hcricket said:
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
Click to expand...
Click to collapse
Keep that simmy in there..now what's your battery ....when does it reboot ...when trying to get into aroma installer?
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Worst case scenario you can relock the bootloader and run an RUU. But I think u can get out of this without having to do that
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
hcricket said:
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
Click to expand...
Click to collapse
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
omario8484 said:
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
Click to expand...
Click to collapse
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
hcricket said:
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
Click to expand...
Click to collapse
Hold down your power button until your screen turns black and than see if it's still rebooting
Still no go. Thank you for your help - I've got it to 98% battery, powered it down, and I'm going to the bar, hah hah.
try flashing CM10 instead of a Sense rom. Aroma can cause freezes and reboots on its own. I would also be scared to run the RUU also since your phone freezes randomly. whats was your stock version?
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
denversc said:
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
Click to expand...
Click to collapse
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
kleeman7 said:
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I told him to flash a rom that doesn't use aroma. He is getting freezes all the time. TWRP used to freeze up on me all the time after the 2.20 ruu until twrp 2.2.2.0 was released. Phone still has trouble getting into recovery from the bootloader though. He should install CM10 or codefirex without using a custom kernel. Maybe run "fastboot erase cache" in bootloader then wipe cache,dalvik,factory reset,system,external in recovery then flash CM10 or codefirex and gapps. keep it plain until you find issues you can attribute to the rom or to the phone. i have had very few issues with latest builds of jb aosp roms besides some battery stuff.
Well, although I had fully charged it and then powered down, now that I am ready to work on it this AM, it wont start at all. I'm thinking she's gone, captain.
Thank you everyone for the replies.
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.