[Q] Flashing first ROM... is this normal? - Verizon Samsung Galaxy S III

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.

Related

[Q] I am Bricked....i think

Ok, So i rooted my T-mobile G2x 2.3.3 and there were difficulties when i flashed the Cyanogen 7mod. The Rom worked but the only default was i didnt get data. Like i couldnt even get Edge. The only way to use internet and stuff was through wifi. SO then i reflashed it thinking it was a bad flash. But when i reflash through rom manager it gives me the option to downoad with google apps. so i clicked that option. It downloaded fine but on the reboot it stayed stuck on the 2nd LG screen. Am i bricked or if anyone can help id appreciate it alot.
U can't do it via rom manager. U have to flash recovery using nv flash, then u can try to flash custom rom. Remeber to wipe data and format system before flashing any rom.
U r not bricked yet
Check here to nv flash the cwm
http://forum.xda-developers.com/showthread.php?p=13330067
Sent from my LG-P999 using xda premium
Did you flash CWM via NV Flash. If not, do that. Then boot into recovery by holding down the power + volume down keys until you get the second boot logo. Then wipe the dalvik cache and the regular cache. That is usually why a phone refuses to boot.
Also, if your phone turns on it is not bricked. Bricked means when you press the power button nothing happens at all. You can be soft-bricked like you are, but it can be easily fixed. Nothing to panic about.
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
iSpooNz said:
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
Click to expand...
Click to collapse
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
Ok so from CWM do i wipe everything?
jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
@OP, this is is correct. Use tga gunmann's nvflash tool from the development section. The process is super easy. Just make sure to follow his instructions closely. Just fyi, most people get errors during the nvflash process because they don't install the apx drivers appropriately, so take your time and read the instructions carefully.
iSpooNz said:
Ok so from CWM do i wipe everything?
Click to expand...
Click to collapse
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
phburks said:
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
Click to expand...
Click to collapse
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
phburks said:
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
Click to expand...
Click to collapse
Ok ill try that.
jboxer said:
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
Click to expand...
Click to collapse
Yea i wiped Dalvik cahce and the same result came up. So i factory resetted and same result. So im going to try what phburks said and see what happens.
Im still stuck in the second LG screen :/
iSpooNz said:
Im still stuck in the second LG screen :/
Click to expand...
Click to collapse
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
phburks said:
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
Click to expand...
Click to collapse
download the rom right?
iSpooNz said:
download the rom right?
Click to expand...
Click to collapse
Yea the rom. Is it cm7 that you're wanting to flash?
phburks said:
Yea the rom. Is it cm7 that you're wanting to flash?
Click to expand...
Click to collapse
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
phburks said:
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
Click to expand...
Click to collapse
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
iSpooNz said:
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
Click to expand...
Click to collapse
Not sure. I'd just play it safe, re-download both, wipe data, and reflash both. Sometimes its hard to determine which step went wrong and its best and quicker to just start with a clean slate and redo everything.
I wont be able to post for a while so good luck.

Went from ICS-SUPERLITE 5.0 to Stock ATT ICS, stuck at boot animation

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

CM9 boot animation loop

I have clockworkmod recovery installed and rooted. It's been a few months since I rooted, and can't remember exactly what I did, but OTA updates stopped working. Hence, I am still on gingerbread.
Trying to flash a custom rom now, CM9. I tried the rom manager method several times, found out that wasn't recommended, and then tried the recovery method.
The same thing happens either way: it boots into CM9, but the boot animation keeps playing.
With the rom manager method, I tried wiping nothing, then tried wiping dalvik only, then tried... whatever the other option was, wipe cache and data?
With CMW recovery I downloaded CM9 zip and the appropriate GAPPS, moved onto the internal SD card, booted into recovery mode Wipe data/factory reset, then Wipe cache partition, then install both.
I'm able to restore from backup each time, but this is annoying.
Thank you
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
UZ7 said:
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
Click to expand...
Click to collapse
So "UCLF6" appears to be rom that is similar to stock, I'm guessing the idea here is that I'm resetting the phone but retaining root, the idea being that something on my phone is messed up and preventing CM9 from booting but doesn't prevent the current rom from booting?
Two other questions
1. Won't format/system wipe out all my backups in addition to my data?
2. Have you had or seen this problem before? I'm hesitant to commit myself to something, especially with no backups, if it's just a theoretical fix. I do appreciate it either way.
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I had a similar boot animation loop when I went from stock GB to stock ICS. What seemed to fix it was updating my CWM from 5.0.2.6 (non-touch) to 5.5.0.4 (touch). (BTW, I couldn't find an advantage of stock ICS over stock GB. I have since put on CM9 which I'm liking).
UZ7 said:
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Still got the boot loop.
When I did the "Wipe data/factory reset" I did get an error message during one of the processes"
"Error mounting sdcard/.android_secure!
Skipping format"
I had a boot loop problem when I first tried to flash JB. I went from GB to ICS with a custom rom a few months back, but I couldn't get any of the new JB roms to work. I ended up having to upgrade my CWM to the touch version in order to get JB flash to work. Also, a tip-- the boot animation will take a minute or two even when it is working. Don't assume it is still a problem if you see it more than once.

[Q] Phone stuck "Optimizing apps" after upgrading rom

Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
CaffeinatedGuy said:
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
Click to expand...
Click to collapse
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
CaffeinatedGuy said:
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
Click to expand...
Click to collapse
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
His bootloader is not locked, he never upgraded to the official 4.3 ota.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Click to expand...
Click to collapse
I wanted to try something else before formatting the card and having to deal with that, so I downloaded the zipped rom here http://forum.xda-developers.com/showthread.php?t=2591895
From CWM I wiped cache (again), wiped dalvik (again), and installed rom. On reboot, went through app optimization without any problems.
I'm not sure what the problem was, but I fixed it by using a different rom.
Thank you for the help.

[Completed] [Q] Stuck in recovery loop after using Rashr Flash Tool

Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
CartoonmanPDC said:
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
So I was in the process of manually installing CWM Touch via Rashr Flash Tool, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, whatever that app wrote into the androids system, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS. Even when I explicitly chose "reboot to bootloader" in CWM, it would still reboot to recovery. I've even went to a totally stock restore, and it still kept happening. Cleared cache, data, davik cache, same result. What can I do?
I currently have 2 restores. One of cyanogen, where i used Rashr's tool, and the other a V6 stock restore.
Click to expand...
Click to collapse
Yes, restoring the last working nandroid backup would be an option.
Alternatively you may have to flash another recovery.
I found this guide to flash CWM recovery on a similar device: How to flash cwm recovery on the lg spectrum 2.
But I am not sure if it wil work for your device too.
So better ask in the General discussion > Questions and Answers forum.
Thread closed and thank you.

Categories

Resources