Ok. I just flashed CM10 stable on my SGS2 Skyrocket, and LOVE it, so I wanted to give it a shot on my Xoom (MZ604). I was having problems getting into CWM, due to the recovery image being overwritten (I was running stock, unrooted 4.1.2 until tonight).
I got that all sorted by flashing the stock, rooted ROM found here, and that was humming away fine. Rebooted into the bootloader, and flashed the CWM linked here. Rebooted into that version of CWM, only to find that I can't access my external SD card where I have the CM10 image stored.
Flashed back to the original CWM I had when first rooting, and flashed CM10. Flash went well, rebooted, and now I'm stuck at the CM load screen. The one with the circle going around and around.
I thought maybe something was wrong with my tablet, so I rebooted into CWM again, and reflashed the stock, rooted version, and it was fine. Flashed back over to CM10, and the same thing. Stuck at the load screen,. It has been there for at least 30 minutes.
I did wipe the cache and Dalvik before every flash of both ROMs.
Any ideas anyone? TIA
EDIT: Is it possible to put the CM10 image on internal SD card and flash it from there? I had assumed that wouldn't work because of formatting and the like, but if it's on /sdcard and not /system...
Edit 2: Just did a factory reset(can't believe I forgot this!!), and all is well now. Mods, please lock this thread. Thank you
Related
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Handalaan said:
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Click to expand...
Click to collapse
Let me guess, you didn't convert back to RFS before flashing??
Try Factory reset. And don't use the backup you have for Cognition, Flash a fresh full ROM. Your backup could be messed up.
EDIT: Studa beat me to it.. Grrrr
studacris said:
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Click to expand...
Click to collapse
This is exactly what I needed to do. Apparently, (after finding a link I somehow overlooked before posting this) it had something to do with the format of the partition so upgrading the Stock to Cognition forced the RFS to EXT3 change allowing -all- of my backups to work. Thanks guys for getting me in the right direction.
Perhaps Im a little Slow
So Im suffering the same issue. Running Serendipity 7 update 2
I looked down at my phone one day and it was in clockwork recovery v2.5.1.2
I figured I had loaded it by an errant button press. So I selected reboot system now. It goes back into Clockwork right after the serendipity 7 splash screen.
Tried Factory Reset
Tried doing a restore
Tried doing a serendipity 7 re install Original and update.
I can install zips from sd card including the external one.
Any Recommendations ?
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.
When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:
All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)
ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
try formatting system after the data wipe, then flash rc7.
dmalikyar said:
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
Click to expand...
Click to collapse
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
droidstyle said:
try formatting system after the data wipe, then flash rc7.
Click to expand...
Click to collapse
Tried that and it made no difference.
dmalikyar said:
Tried that and it made no difference.
Click to expand...
Click to collapse
try using odin......just remember after you odin back to the root66 image, you have to reinstall CWM and doesn't hurt to make sure ur bootloader is unlocked using the 1.2 version of the ez unlock then flash again
digitalsynner85 said:
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
Click to expand...
Click to collapse
I'll try the Odin route. I'll go back to root66 and try it from there.
dmalikyar said:
I'll try the Odin route. I'll go back to root66 and try it from there.
Click to expand...
Click to collapse
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
digitalsynner85 said:
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
Click to expand...
Click to collapse
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
imklaho your
droidstyle said:
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
Click to expand...
Click to collapse
I Odin'd root66 and installed the ez unlocker as well as clockworkmod via rom manager. I went into recovery and wiped data/factory reset/wiped cache/wiped dalvik cache. I then installed LS RC7. It went through the installation and indicated that it completed. After I reboot, I briefly see the Samsung logo, then the screen is completely black. No boot animation. I let it set for over 20 mins. and nothing happens. This is absolutely bizarre. I've tried 3 different downloads. I'm at a loss. Is there a way to convert the zip to an img and odin it on?
KT747-Kernel-AOSP-JB-VZW-10-31-2012.zip
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
dmalikyar said:
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
Click to expand...
Click to collapse
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
dmalikyar said:
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
Click to expand...
Click to collapse
Have you tried TWRP recovery as opposed to CWM?
shangrila500 said:
Have you tried TWRP recovery as opposed to CWM?
Click to expand...
Click to collapse
I installed twrp and I really like the interface but it didn't resolve the issue of flashing RC7. I've installed paranoid android and can install aokp and cm10 with no problems. I can't install RC7 or slim beans.
Cannot install Liquid Smooth
Yah the guy at Liquid Smooth is kind of a butt wipe. I understand the desire to have a screen capture and a logcat but if the user can't even install the flash how is a screen capture going to help. Maybe a logcat could. But either way why be an A hole about it.
I am having the same issue, I even formatted my system and still LiquidSmooth says it flashed but it just refuses to boot. I have used Odin to install the stock JB 4.1.1 from Poland but I still get the same problem. I do believe it has something to do with having tried CaponMod4NSS_3.0 the day before. Still I would think formatting the system would resolve that.
Any ideas? I will try to install the Samsung 4.1 ROM with Odin to see if that helps.
Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!