I just used Unrevoked 3.2.1 and now installed Cyanogen 6.0.2. Now my phone just loops the Cyanogen boot screen over and over and over. Been doing this for about 15 minutes. What do?!?
install a different rom
kthx I already fixed it
How did you fix it, I am having the same issue and not sure what to do ..
i just had the same problem and fixed it by having to wipe all the data and cache, rebooted, at first it started blue looping but before i knew it, it went straight into the OS and worked.
derized said:
i just had the same problem and fixed it by having to wipe all the data and cache, rebooted, at first it started blue looping but before i knew it, it went straight into the OS and worked.
Click to expand...
Click to collapse
im having the same issue the only problem is when i went to clockwork restore back up i accidently clicked back up so it backed up the bad flash and now when i restore i get the splash screen loop over and over.... help
IamaNoobsickle said:
im having the same issue the only problem is when i went to clockwork restore back up i accidently clicked back up so it backed up the bad flash and now when i restore i get the splash screen loop over and over.... help
Click to expand...
Click to collapse
Boot back into recovery and use the old backup you intended on using initially. That should hopefully fix it.
Sent from my Droid Incredible running some random CM7 nightly.
Related
I'm pretty f**ked, I've just tried to install CM7 and it's gone onto bootloop. When I try and get back into recovery (I only wiped delvik cache or whatever ><) it shows a short Clockwork recovery loading screen, hops back to the htc loading screen, and back onto the CM7 bootloop.
How the hell do I fix any of this?
Edit: oh hell yeah, it's actually stopped bootlooping and it's loaded. God thank you. Thanks to everyone who also made tutorials that I have used - I've thanked your posts
Tuoni said:
I'm pretty f**ked, I've just tried to install CM7 and it's gone onto bootloop. When I try and get back into recovery (I only wiped delvik cache or whatever ><) it shows a short Clockwork recovery loading screen, hops back to the htc loading screen, and back onto the CM7 bootloop.
How the hell do I fix any of this?
Click to expand...
Click to collapse
congratulations, you are person no. 362935629375
do a full wipe after flashing cm7
theq86 said:
congratulations, you are person no. 362935629375
do a full wipe after flashing cm7
Click to expand...
Click to collapse
after or u mean before i always full wipe before flash only
then all work great after flash
do full wipe and clean all caches after flashing cm7.
I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Relax bootloops aint a major problem really, i suggest you go to cwm and wipe all, or try and testore a backup, if all else fails just go back to stock using a toolkit, re root and flash a rom
Sent from my Galaxy Nexus using xda premium
SomeGuyDude said:
I flashed the latest Axiom and everything was fine. Did a reboot and it just sat on the boot animation for a while. Like, 15 minutes. So I did a battery pull and tried to boot again. No go. Pulled the battery and went into CWM, wiped data/cache/dalvik and formatted /system then re-flashed the ROM. Stuck again. Went BACK into CWM, wiped/formatted, and installed Liquid (which worked before). STILL can't get past the boot animation. Tried to restore a Nandroid and got an error.
I'm in a bit of a panic mode here because I have no idea what to do.
Click to expand...
Click to collapse
Do this.
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
I ran across this problem when I was flashing a Jellybean version of Cyanogenmod. If you flashed it on a NON-TOUCH recovery it will most likely boot loop like mine did. I installed a touch recovery and flashed and BANG. I had had Cyanogenmod. Hope this helped
This was my fix...
dj923 said:
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
Click to expand...
Click to collapse
If it is the CM9 bootloop issue (where it hangs at the little blue dude) check out this page (sorry it won't let me insert a link because I'm a new user lol):
forum.cyanogenmod.com/topic/59357-cm9-boot-loop-issues-my-solution/
I couldn't get it to work until I followed this method, likely the use of Darkside Super Wipe and Darkside Cache Wipe was what fixed it. Hope this helps.
OOOhhh this happened to me when i first rooted my phone LOOOL......this is what u do....
if you are on cwm 5.0.2.7 or lower...u need to use darkside super wipe then flash the rom
i did the darkside wipe and it booted up fine. thanks a lot guys!
if cant be fixed flash stock. it happened to me once too. i think it was because i flashed the wrong radio
I flashed the ATT MIUI rom onto my tmobile note 2, all was working fine, than i tried to install rom manager, it installed and miui warned me about root so i enabled it in permission manager but it wouldnt work and it went into a force close loop "permission manager has stopped working" every 5 seconds. Restarted the phone and it went away, then i went into recovery, wiped cache, dalvik cache, and flashed GAPPS. They installed just fine, then i rebooted and was stuck on the MI logo for 5 minutes, i rebooted back into CWM and tried to wipe DATA/FACTORY RESET , this is where the problem is when i pressed "yes" it turns the phone off and reboots, it doesnt wipe the data , i tried going into mounts and storage and wiping system there, that works but when i tried to wipe data it reboots so im assuming the problem has to do with wiping the data. After wiping system,cache,dalvik cache i tried to go back to jedi x7 and it flashes but once it gets to the boot screen it turns off and restarts. now i just took the battery out and hoping someone can help me
EDIT - FIXED
Read the thread i posted updates of what I did to fix it
50 views / no help? come on anybody give your suggestions please :crying:
A shot in the dark here....
Get the flashable TWRP 2.3.2.3 and copy it on your external SD.
Go into recovery and flash it and then try to flash the Rom with TWRP.
I hope this helps you.
If twrp doesn't work.
I suggest you use odin to flash stock rom
Sent from my GT-S5360 using xda app-developers app
i used odin to flash to stock everything passes its on the boot screen right now on the samsung logo with the blue glow behind it
its been like 10 minutes since it was done flashing and rebooted into the samsung logo.. its still here
pulled the battery out at 2:20 and rebooted and its still on the samsung logo , it passes the tmobile logo and it gets stuck on the samsung logo after it and doesnt do anything it just sits there
haldi15 said:
pulled the battery out at 2:20 and rebooted and its still on the samsung logo , it passes the tmobile logo and it gets stuck on the samsung logo after it and doesnt do anything it just sits there
Click to expand...
Click to collapse
Where u from?
Sent from my SGH-T889 using xda premium
i fixed it, went into the stock recovery , wiped data and cache there and rebooted and it finally works , and im EST time zone
haldi15 said:
i fixed it, went into the stock recovery , wiped data and cache there and rebooted and it finally works , and im EST time zone
Click to expand...
Click to collapse
Gladr u fixed it!! :thumbup:
Sent from my SGH-T889 using xda premium
first thing you would always do in a situation like that is odin a stock image. glad you got it fixed.