So I must admit I am new to this. I am on a Samsung Galaxy Nexus (CDMA). I was running stock 4.0.2. Unlocked bootloader, rooted, and clockwork mod recovery.
I decided to flash my first custom ROM. I choose Android Open Kang Project - toro Milestone 3. I made a nandroid backup. I wiped data. First I did "wipe data/factory reset", then I did "wipe cache partition", and then finally I did "wipe dalvik cache". After that I pushed the aokp_toro_milestone-3.zip to the /sdcard/. After that I entered clockwork mod recovery and installed from zip. Installed successfully, then in recovery I was going to flash the aokp_gapps-ics-403-011312.zip and accidentally rebooted the system.
Well, it has been doing the team kang unicorn boot animation for about 40 minutes now. Is this normal? I read that it takes a long time for the first boot, but this seems excessive. Could it be because I accidentally skipped flashing the gapps? Should I reboot(adb reboot bootloader)? If I do that should I start from scratch(wipe data, re-flash ROM, flash gapps, flash kernel?, and then reboot device)? Or do I wait.
I would appreciate any advice/help!
I spoke with a friend, he said it was alright to reboot to the bootloader and start over. That is what I did. This time it booted up.
This thread can be deleted.
On past Androids I have owned I have seen dif ROMs that actually say you need to pull battery, flash twice, etc.. Not trying to say that's normal procedure, just saying it happens from time to time. You did good to wait and see though! First start can take a while sometimes, you don't want to do a premature bat pull. Glad you got it working.
Related
Greetings!
I've had my S2 for a few months now, and have been running PA 2.11 since the begging of September. So I've decided to upgrade to the latest and greatest, and everything I flash a new rom, I get stuck in a boot loop. I've tried the latest PA, PAC, LiquidSmooth, All-Star and slim bean. Each time, boot loop. I'm using the latest CMR. Current kernel is Cyanogen 3.0.42. My process is essentially factory wipe, system wipe, clear caches, flash rom, clear caches, reboot, wait 10-20min, reboot, wait an additional 10 min, reboot again. I go back and forth between factory wipe and Darkside Super Wipe, seeing if anything makes a difference, and so far, regardless of my process, I keep getting boot loops. I always follow the flashing instructions the first couple times, then try other options, but keep getting these damn boot loops. Thoughts? Your assistance is much appreciated..
dr_destructo said:
Greetings!
I've had my S2 for a few months now, and have been running PA 2.11 since the begging of September. So I've decided to upgrade to the latest and greatest, and everything I flash a new rom, I get stuck in a boot loop. I've tried the latest PA, PAC, LiquidSmooth, All-Star and slim bean. Each time, boot loop. I'm using the latest CMR. Current kernel is Cyanogen 3.0.42. My process is essentially factory wipe, system wipe, clear caches, flash rom, clear caches, reboot, wait 10-20min, reboot, wait an additional 10 min, reboot again. I go back and forth between factory wipe and Darkside Super Wipe, seeing if anything makes a difference, and so far, regardless of my process, I keep getting boot loops. I always follow the flashing instructions the first couple times, then try other options, but keep getting these damn boot loops. Thoughts? Your assistance is much appreciated..
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
suaverc118 said:
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I was using 5.x, but after quite a few boot loop flashes, I upgraded to the latest and greatest with no effect on the outcome.
You're doing way too much. Here:
http://forum.xda-developers.com/showthread.php?p=32532260
That's my thread on how to properly wipe before ROM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
So, don't know what the initial issue was with flashing the new ROM, but I took CWR 6.X off and put on 5.0.26 and got All-Stars up and running in no time. Thank you for your help!
Hi All,
Seem to have a slight problem with flashing Custom Roms onto my GNex at the moment. Not too sure what's causing it to freeze when booting up. All I get is the X logo and will stay there until the battery dies.
I'm able to revert back to a Google rom and regain use of my phone. Just can't seem to flash any custom roms at all. It's happened with CM10.1, CM10, XenonHD Stable-2.0, Minoco.
I've attempted to flash with CWM and TWRP. Both get the same results. Prior to flashing I've whiped both the Cache and Davlik.
I have previously used CM9 and older versions of Minoco on this device. So seems odd that this is happening now.
Any advise or ideas towards what I should look at would be appreciated.
Thanks,
Drav
you have wipe data before flashing different roms... dirty flashing(only wipe cahce and dalvik) is only if you are updating the same rom.. this is how i normally flash ALL roms
1. wipe data/factory reset
2. wipe system
3. wipe cache
4. wipe dalvik cache
5. flash rom
6. flash gapps
7. reboot
8. wait 10 mins then do another reboot
9. enjoy
PS- the 10 min wait and reboot is soemthing i do that IMO lets the new rom settle
Thanks k786,
It's booted up in a custom rom now after following those step by step. Much appreciated! :good:
Cheers,
Drav
Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!
I have a ATT Samsung Galaxy S3, running Android 4.2.2. I was putting Clockwork on and when I got done and rebooted system, nothing. It vibrates once and the words Samsung comes up then total black screen. Bootloader and downloader still work fine. I formatted, put a rom back on but the same thing happens. It just seems like there is a missing file that is stopping it from continuing to start up. Can someone give me some guidance. I jailbroke my phone 2 years ago so I am very rusty. Thanks for the help.
Clear data, dalvik, and cache in recovery, then reboot.
WARNING: doing this will wipe your data off the phone.
audit13 said:
Clear data, dalvik, and cache in recovery, then reboot.
WARNING: doing this will wipe your data off the phone.
Click to expand...
Click to collapse
cleared both, then even formatted. Like I said before, when I turn it on it vibrates, then the Samsung (in white) comes up then it goes to the black screen and stays there. Like its getting hung up. All happened after rebooting system in clockwork.
What ROM was on your phone. You mentioned 4.2.2 but I don't think ATT released a 4.2.2 ROM.
audit13 said:
What ROM was on your phone. You mentioned 4.2.2 but I don't think ATT released a 4.2.2 ROM.
Click to expand...
Click to collapse
I had a cyanogen mod on couldn't tell you which one exactly. My android version was the 4.2.2
what do you think of turning it back to stock, not that I want too?
You need to know which bootloader was on your phone before trying to restore to stock. The bootloader will determine how to restore the stock ROM.
First of all, boot into download mode and tell me what it says on the screen.
actually I had both twrp and clockwork both on there. Here is what is says on a start up downloader screen: A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise, press the volume down key to cancel.
if you have terminal emulator on your phone , type in
getprop ro.bootloader (you need the space) and press enter. this will tell you your bootloader version.
err on the side of kindness
Either do what Mrrocketdog suggested or go past the warning message to the download mode.
oooopps! forgot about going past warning message. been a very long long time since been there. :thumbup:
err on the side of kindness
I never put emulator on my phone. Here is what I just did, I followed the Cyanogen d2lte to the T. Rebooted and now it is stuck on the Samsung GalaxySlll screen with the little blue android. I flashed both files thru my recovery. Again, everything started after I rebooted my system for the first time after installing the clockwork mod
I have no idea, but jst a though. Would it help to go to advanced, mounts and storage, in clockwork and format everything except my sd card?
bootloader is clockwork v6.0.4.7
CWM is the recovery, not the bootloader.
Boot to recovery. Format system, cache, data, flash cm11, reboot
thanks for being patient with me. i will try and let you know
. this site would be nothing without people like you.
here is what i did,(1) wipe dalvik and cache. (2) reboot(3)apply cynaogen bootloader update. (4) in this step it tried rebooting to recovery and not before applying cm11. when i reboot the system it gets stuck on the samsung galaxyiii with the blue android guy, the screen gets stuck right before it would boot to the cynagogen screen. again all my problems started when i added clockwork mod and rebooted. at that time i already had twrp. what would i have to do to remove clockwork mod or just help me just start from the begining drawing board. thanks.
tepeee said:
here is what i did,(1) wipe dalvik and cache. (2) reboot(3)apply cynaogen bootloader update. (4) in this step it tried rebooting to recovery and not before applying cm11. when i reboot the system it gets stuck on the samsung galaxyiii with the blue android guy, the screen gets stuck right before it would boot to the cynagogen screen. again all my problems started when i added clockwork mod and rebooted. at that time i already had twrp. what would i have to do to remove clockwork mod or just help me just start from the begining drawing board. thanks.
Click to expand...
Click to collapse
You need to wipe data, cache, dalvik, mount system, format system, install CM11, reboot.
audit, i did exactly what you said and nothing the same results. stuck on the samsung blue android screen.
I'm trying to restore a backup, and every time I try TWRP successfully restores it, I reboot system, and then about 3 seconds into the boot animation the phone reboots into recovery and asks for my security pattern. When I unlock it, it says "running openrecovery script" and wipes /data/, then says "/cache/twrp/openrecoveryscript not found" and reboots to system. When Android boots, I have the setup screen and can't get out of it.
I arrived in this situation by trying to update to the july security updates, and finding that I flashed the wrong build of a ROM, then trying to go back to my previous state. After the first restore attempt, I wiped cache & dalvik, which I now assume was bad.
Is there something I can do to prevent TWRP from running that script? Can I edit it? Or should I just accept my fate and spend hours reinstalling everything
Running Dirty Unicorns 11.4, TWRP RC2.
Thanks.
Holy smokes, I am having the same issue..
I went ahead and wiped.. yay.. time to start again.
Same happened to me. Had to start over from factory reset status ?
Sent from my Pixel XL using XDA-Developers Legacy app
I recall reading on some thread (too many to remember which) that RC1 was more reliable for backups and RC2 for flashing zips.
I found this to be true. I never could successfully restore a backup with RC2, so I went back to RC1.
This is a well known issue with RC2. You can keep RC2 installed, but fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img for backups and restores.