Tried this and rogue recovery, but I want to get up JB. So.. I used the easyoneclick and got rogue installed, then tried to flash the latest EOS4 at the time. That put me at the boot screen (4 color any boot animation) and never got any further.
So... I used the easy one click to restore stock, and that got me back to good for a few days, but still no JB.
So then I tried Goo manager and oddly enough it couldn't push the "recovery script" or what is actually twrp recovery. I was able to boot into recovery and push the GM downloaded twrp though.
So, now I have updated twrp (sort of through GM), and nightly EOS4 - but still stuck on boot animation - left it for 4 hours before I decided it wasnt' going to work. Any ideas? I was reading some about frameworks and I'm thinking that might be my problem, but I'm not finding any really good walkthroughs or advice. What can I try next? Any help greatly appreciated - Thanks!
Did you wipe the cache, Davlik, system and factory reset before flashing?
frederuco said:
Did you wipe the cache, Davlik, system and factory reset before flashing?
Click to expand...
Click to collapse
I did, but I can try again!
Bigscout79 said:
I did, but I can try again!
Click to expand...
Click to collapse
And... I'm very grateful! That seemed to work! I might not have been wiping the system.
Thanks!
Glad it is all sorted.
Related
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.
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.
please help!!!!!
hi am using a gionee e3. i changed my phone font last night using the "my font" app (not the first time), i was prompted to reboot my device, the device comes on displaying the gionee smartphone screen but doesn't boot any further than this.help needed
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Gilbert_vanguard said:
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Click to expand...
Click to collapse
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
mcgrabowski said:
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
Click to expand...
Click to collapse
yup that's one possible solution. but usually bootloop spells doom
thanks guys
thanks guys, apparently it was doom afterall, nothing worked. had to reinstall the os. lost everything
Ok I just got my brand new OnePlus One in the mail today. Opened the box, loved the design and build quality, etc... Powered it up for the first time all good, played around with it for a few minutes, liking everything. An update option popped up for 38r, I did the update, maybe I shouldn't have., but too late. I did the update, then phone rebooted, and everything good again
So then time to root this beast. I went through the typical steps, all good, got TWRP Recovery installed easily, then flashed SuperSU.zip in Recovery, it said successful, I pressed Reboot System, and here's the issue, the phone is just stuck on the boot animation screen. I see the Octagon CM animation spinning, but it just spins, and spins, and spins, not going any further.
So now what ?
What I'd do is to install a custom ROM but I'm pretty sure if you perform a factory reset it would boot back up. Also try wiping the cache. This is what I'd do but there might be alternative solutions out there.
Yuvin said:
What I'd do is to install a custom ROM but I'm pretty sure if you perform a factory reset it would boot back up. Also try wiping the cache. This is what I'd do but there might be alternative solutions out there.
Click to expand...
Click to collapse
I went into TWRP Recovery did a Factory Reset, then reboot system, and IT WORKED
No idea I had to do a factory reset in Recovery to make it work.
Zorachus said:
I went into TWRP Recovery did a Factory Reset, then reboot system, and IT WORKED
No idea I had to do a factory reset in Recovery to make it work.
Click to expand...
Click to collapse
That's great! Enjoy your rooted OPO!
Hi All,
I am at my wit's end with my Galaxy S3 at this point. I was running CM11 M12 snapshot, but I was getting reboots at least once per hour. I decided to try to dirty flash the latest nightly, but the boot loop started then. Here's what happens:
Cold start:
1. Samsung Logo flashes
2. Galaxy S3 Cyanogenmod Logo screen, 10-20s
3. CM11 Boot animation (spinning arrow gets stuck sometimes)
4. Reboot after arrow stops
I want to format /data to try a clean flash. However, CWM reboots during this process. I can format /cache and clear the dalvik cache. I can mount and unmount /data in CWM.
Is there another way to try to format /data? It seems something is seriously corrupted (probably why I was getting reboots when I could actually load CM). Any help would be greatly appreciated.
Side note: I made a nandroid backup before all of this, but CWM is giving me the classic MD5 mismatch error, so I need to fix that before restoring the backup (assuming it's not just corrupted...).
Thanks for your help.
EDIT: I followed this guide and this comment to flash back to stock.
I originally thought I had a bad emmc block, but after checking them manually (through adb shell dd in recovery) and through a CWM flashable scanning tool, I could not find a bad block. So I went back to rooted stock. Now I am deciding if I should just de-bloat stock 4.0.4 TouchWiz (it's very ugly) or try another custom ROM...
ScheissSchiesser said:
Hi All,
I am at my wit's end with my Galaxy S3 at this point. I was running CM11 M12 snapshot, but I was getting reboots at least once per hour. I decided to try to dirty flash the latest nightly, but the boot loop started then. Here's what happens:
Cold start:
1. Samsung Logo flashes
2. Galaxy S3 Cyanogenmod Logo screen, 10-20s
3. CM11 Boot animation (spinning arrow gets stuck sometimes)
4. Reboot after arrow stops
I want to format /data to try a clean flash. However, CWM reboots during this process. I can format /cache and clear the dalvik cache. I can mount and unmount /data in CWM.
Is there another way to try to format /data? It seems something is seriously corrupted (probably why I was getting reboots when I could actually load CM). Any help would be greatly appreciated.
Side note: I made a nandroid backup before all of this, but CWM is giving me the classic MD5 mismatch error, so I need to fix that before restoring the backup (assuming it's not just corrupted...).
Thanks for your help.
Click to expand...
Click to collapse
Can you get into recovery?
Sent from my Nexus 5
ShapesBlue said:
Can you get into recovery?
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can get into CWM recovery.
ScheissSchiesser said:
Thanks for the reply. Yes, I can get into CWM recovery.
Click to expand...
Click to collapse
Alright. Are on you on the latest version of cwm?
Sent from my Nexus 5
ShapesBlue said:
Alright. Are on you on the latest version of cwm?
Click to expand...
Click to collapse
Yes. ClockworkMod Recovery v6.0.4.5.
Thanks for the response. Anything I should try?
ScheissSchiesser said:
Thanks for the response. Anything I should try?
Click to expand...
Click to collapse
I'm not completely familiar with CWM, I've always ran either twrp or Philz. I'd maybe suggest switching to another recovery. It's personal preference but to each there own. You should be able to flash it via Odin
Sent from my Nexus 5
Thanks for looking into this. See my edit in the OP for my solution. I'm still not sure WHY it happened, but I have a working (Stock Rooted 4.0.4 TouchWiz) phone again.