The Problem: No matter what custom rom I load...it boots into an apparently endless display of the colorful boot animation that comes stock on the Nexus. I have to battery pull to get out of it. I've got an Unlocked/Rooted phone w/clockwork recovery working. I can backup and successfully restore the OEM rom I backed up after each failed custom rom install attempt.
I've been working through issue after issue all evening and have continued to hit the same problem no matter what my approach.
I've got Rom Manager and can download and load ROMS via it's GUI - or by booting into clockwork recovery and doing it manually by choosing the zip I previously downloaded. I've renamed the oem recovery file in system etc... still no joy getting anything to boot successfully except the OEM image I backed up.
Could someone point me in the right direction?
nondem said:
The Problem: No matter what custom rom I load...it boots into an apparently endless display of the colorful boot animation that comes stock on the Nexus. I have to battery pull to get out of it. I've got an Unlocked/Rooted phone w/clockwork recovery working. I can backup and successfully restore the OEM rom I backed up after each failed custom rom install attempt.
I've been working through issue after issue all evening and have continued to hit the same problem no matter what my approach.
I've got Rom Manager and can download and load ROMS via it's GUI - or by booting into clockwork recovery and doing it manually by choosing the zip I previously downloaded. I've renamed the oem recovery file in system etc... still no joy getting anything to boot successfully except the OEM image I backed up.
Could someone point me in the right direction?
Click to expand...
Click to collapse
How long exactly are you waiting on the boot animation? when you first flash a new rom, it can often take a long time on this screen first boot up. be patient. dont pull the battery unless its been like 15 minutes
can you give us any info on what phone you are using, and which roms you tried?
When you flash a completely different ROM, you HAVE to do a full data wipe in CWM.
When you update the current ROM, you have to do a wipe cache and dalvik cache.
And like the guy above said, it can take a while on first boot.
Sent from Galaxy Nexus (GSM)
Progress
First - Thanks for the help. I did a full data/cache wipe right before attempting to flash a ROM and it worked. Didn't even take longer than usual to boot into the OS.
I had done that earlier but I think it must have been the order I had followed or something. Regardless - I got a ROM up and running and can repeat the process reliably
Of course - there is another hurdle that I don't find anything on so far...if I add the google apps to the ROM I get stuck in a crashing Verizon login wizard. "Touch here" results in a crash message and the wizard restarts.
I can access settings and use the phone - but "Home" is the wizard.
Related
Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?
i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me
Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help
I flashed the incredibly re-engineered v2.2 rom a week or so ago and it worked great till today it was giving me a force close on a bunch of apps, so i restared it and it still didn't help. Did a *228 and when it restated it just goes to the black screen that says htc incredible Loading then after several seconds it flashes blank for half a second then says same thing. I used rom manager to flash it. I've also used virtuous and skyraider 3.5. I'm good at computers but android is new to me as i've only had this fon 2 months. I have to do a battery pull to restart it. Any Ideas on how to fix this? I can boot into recovery but havn't been able to do anything... Never used it so not sure what to look for but like when i click recovery or factory reset, nothing happens. Oh, and i did a search but didn't come up with similiar problem.
htc incredible s-off
radio 2.15.00.07.28
Flash a different rom.
sent from my Dinc
How do I do that? When I boot in recovery mode I have option of fastboot, recovery, clear storage, simlock, and factory reset. When I select recovery it goes to bootloader, reboot, reboot bootloader, and power down, with reboot highlighted. Wen I select that it boots like normal than gets stuck on boot up screen.
Try fixing permissions through Rom Manager first, if not I would reinstall the rom. Be sure to do a full wipe, don't just flash over your previous rom.
If neither of those work, I would follow this thread
http://forum.xda-developers.com/showthread.php?t=786436
Flash back to stock 2.2 and see if your phone starts acting the same way. If so I would take it back to verizon. If everything seems ok, re-root and flash JUST the rom and apps that you want, no kernel, themes, anything extra yet. See if that fixes the problem.
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
I would re-download a different ROM (making sure you don't have a corrupt download), check the MD5 SUM's to verify integrity of your download, mount USB Storage in Recovery to transfer the file to your USB card (when phone is off, hold down the Power and Volume Down buttons at the same time), wipe all user data/factory reset and Dalvik, and then reflash the ROM of your choice.
mennotech said:
I made sure I did full wipe when I installed it so that shouldn't b problem. The issue Is i can eve get to rom manager because he Fon wont load past the boot image. And its out of warany so vzw prolly wuldnt be much help.
Click to expand...
Click to collapse
Go to that link in my post, download the PB31IMG from the 2.2 Stock OTA, put it on the root of your SD card, boot into the bootloader and let it update. You will go back to being completely stock and unrooted. Root it and then try installing the rom again.
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.
My friend's phone somehow got into a reboot cycle. It loads up, launcher starts, notifications start working. Then there is a nullpointer and a core service that is failing to start then it reboots.
So as a solution I thought try wiping data/cache. When booting the bootloader it was already unlocked - not sure if we did that a while ago or what. So going into recovery, trying the data wipe, it says success and then when I start the phone it is the same, no data is gone, apps are there, reboot problem continues.
So next step, try flashing the os. I downloaded the most recent yakju build, jwr66y. My bootloader version is PRIMELA03 and the build comes with MD04, so I try:
fastboot flash bootloader <bootloader_img>
And it reports success, everything looks fine. So I reboot the bootloader and it says BOOTLOADER VERSION - PRIMELA03.
Try fastboot oem lock, says locked. Reboot, UNLOCKED. Tried flashing the bootloader and the main img with and without restarting but always get the error:
Device version-bootloader is 'PRIMELA03'.
Update requires 'PRIMEMD04'.
when trying to flash the stock rom.
I also can't boot the stock image via 'fastboot boot'. It looks successful up until it says booting and goes to the Google screen with the padlock at the bottom and just hangs.
If I try using adb sideload to push the stock update, it says verifying, then aborts.
I also tried flashing the recovery with a cwm recovery but the same problem - it says writing, OKAY, no error message, everything looks fine, then boot recovery and it's the stock recovery.
What it looks like to me is that the bootloader and possibly the entire system is failing to write to the system flash but for some reason thinks it's succeeding. How is this possible? Is the flash dead? Am I missing something basic? I haven't rooted a phone in a couple years so it's quite possible I'm just missing a step.
Thanks in advance for any advice.
I just tried flashing an older stock (imm76i), starting by flashing the radio, but again the radio flash looks successful but the kernel won't flash because it complains about an out of date baseband and sure enough, the old one is still the one it's reporting, not the one just flashed.
tried fastboot erase system and fastboot erase recovery. Both report success but recovery boots as normal and system boots as normal (still in a reboot cycle).
I should also mention, that after the system boots, there is enough time to uninstall an app. It says successfully uninstalled, but after a reboot, the app is still there (this was the first attempt to stop the reboot cycle as a custom keyboard app was suspected). But again, the changes to flash seem to not be sticking.
Hi,
Have you resolved the problem? I'm in the same situation and I don't know what to do to stop the continuous reboot. I've already tried to flash a stock 4.3 factory image, erase the user data or only unlock the bootloader but nothing works. I'm running Android 4.3 stock without root and my bootloader is locked.
thank you in advance.
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403