In CWM, did the typical things
A Data/factory Reset, Format: System, Data And Cache, And Clear The Partition And Dalvik Caches, Do That To All Of Them 3 Times Each.
ran new radio zip.
Booted into download mode, and did odin thing as instructed following info here http://forum.xda-developers.com/showthread.php?t=1652398
used the md5 for latest stock ATT ICS.
This went thru fine and rebooted.
here I am, at ATT boot animation, just runs once and sits.
I can get into android system recovery....
What do I do next?
please point me if I missed the obvious thread......
factory reset in the recovery
xTRUEx said:
factory reset in the recovery
Click to expand...
Click to collapse
no dice!
any other ideas?
OK I tried flashing different things, went back to CWM, then did stock again.
works!
yuck I hate this bloat ware
one of my recommendations in that post you followed was try factory reset and/or flash the stock again if things are not right, especially coming from custom roms.
but i will edit the radio flashing to do it 2 times and add another warning to reflash stock again
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
dmccrack said:
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
Click to expand...
Click to collapse
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
SlimSnoopOS said:
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Click to expand...
Click to collapse
The ROM was downloaded via Goo.im app
dmccrack said:
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
Click to expand...
Click to collapse
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
dmccrack said:
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
Click to expand...
Click to collapse
dmccrack said:
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
Click to expand...
Click to collapse
No problem. As for your issue, its fairly simple actually. What you need to do is a clean flash which is either of the two steps I listed earlier. You're trying to go from TW to AOSP but what you did was only wipe the cache then flashed the rom. Wiping cache and dalvik cache is regarded as a dirty flash, something you only do when flashing a newer version of the rom you're on. You never fully removed the TW rom before flashing Liquid which is why it did not boot. Basically, when you want to flash a new rom, by a different developer, you need to do 1 or 2 in order to have a successful flash.
For AOSP roms, you should also be flashing the recommended GApps (Google Apps) as well so that you have your Play Store and a few other Google Apps. The latest "generic" gapps zip is listed here at the top, its "20120301" which is March 1st. Liquid may have their own, that's for you to find out via their thread. Google apps are included in TW roms so this is not necessary.
So I've been running Graviton 2.0 on my Nexus 5 for a few months and recently I've tried upgrading to 2.6. Problem is, when I install the updated rom, I get the "Unfortunately, com.android.provision has stopped" error message loop times infinity. I tried installing 2.6 by booting into recovery mode and installing the zip using CWM. I then wiped the cache and the Dalvik. I've also tried doing a factory reset prior to the previously mentioned steps and that hasn't worked either. Any help would be much appreciated thank you.
squishywtrmln said:
So I've been running Graviton 2.0 on my Nexus 5 for a few months and recently I've tried upgrading to 2.6. Problem is, when I install the updated rom, I get the "Unfortunately, com.android.provision has stopped" error message loop times infinity. I tried installing 2.6 by booting into recovery mode and installing the zip using CWM. I then wiped the cache and the Dalvik. I've also tried doing a factory reset prior to the previously mentioned steps and that hasn't worked either. Any help would be much appreciated thank you.
Click to expand...
Click to collapse
If it we`re me, i would flash the factory image in fastboot, reroot and start over. Or do you have a working stored recovery to flash back to?
gee2012 said:
If it we`re me, i would flash the factory image in fastboot, reroot and start over. Or do you have a working stored recovery to flash back to?
Click to expand...
Click to collapse
I've been able to recover back to Graviton 2.0 after each unsuccessful attempt through the restore function in CWM.
I installed cyanogenmod a few days ago and it was working fine. I installed a font changing app, and it needed to reboot to work. When it tried to reboot, it got stuck on the cyanogenmod boot screen. I booted to recovery and did a factory reset, wiped dalvin cache to no avail. I found a stock Rom for my phone, but Odin doesn't seem to see it when I go into downloading mode. Am I doing something wrong? What should I do next?
Just reflash CM.
hi,
Recently i've updated p5100 to omnirom kitkat and i have CWM touch recovery. And also my device is not rooted.
out of the blues, my tab started auto rebooting itself. so i decided to do a factory reset to it. But i noticed nothing changed. the tab looked exactly the same. so i decided to flash a new rom (slimkat) to it. and i did. i followed the typical flashing technique through the sdcard. I cleared data, cleared partition, dalvik cache. and also flashed the new rom. but when i boot it, it remained the same old omnirom kitkat.
I did it a few times and got my tab stuck on bootload (omnirom) . i just dont get why CWM is not factory reseting the device or accepting any new rom. i even tried flashing TWRP. but no luck! so as a conclusion, my p5100 cant accept any new rom or recovery image and it cant factory reset. stuck on boot animation! but i could flash in the AROMA filemanager to it... would seriously appreciate if anyone could help me with this problem.
Thanks in advance.