Ok, so let me tell you what I was doing. I'm running a custom ROM (NSCollab) and I bought the premium version of ROM Manager so that I could update the ROM. Well as soon as I went to update it, it rebooted and now is stuck on the Google screen. What in the world just happened. I did a battery pull and it still gets stuck at that spot.
Maybe a bug in the rom code.
Phone might not support that rom.
is it frozen on the boot screen? Leave it on boot for about 20 mins, if it still isn't working then just remove the rom.
Sent from my GT540
But I wonder why my phone gave me an update option if it wasn't supported.
Hmmm, the rom could be broken.
Sent from my GT540
So how do I go back or reboot into Recovery from here?
Can you get into your phone? If not then go into safe mode.
Sent from my GT540
Ok, I was able to reboot into Recovery and install the previous version of NSCollab. I wonder what the deal was?
Related
Its fixed. It seems that it was stuck and just needed that extra kick with another ROM. Not really sure what the hell happened but its working fine now.
Please delete post.
Yesterday I plugged the HOS into my laptop and it started to act a little weird. It wouldn't show the SDcard but it allowed me to open it. I copied a new ROM to it and installed it. Since I did this, the phone will not work. Once it boots, it just freezes and reboots when I try and do anything. The nand allows me to boot and scroll through the home screens, but if I try and do anything else it freezes and reboots. I can't install any other ROM that's not sense base like AOKP or MIUI as they just boot loop. I can get to recovery and the boot loader no problem.
Update: I can boot a stock nand and get into the app drawer. But, once I click on an app or pull down the notification bar it freezes.
Update 2: Was able to get the cyan alpha to install after a good 5 minutes of bootloops and it runs perfect. WTF is going on here?? haha
Can anyone give me any suggestions to try? Thanks for any help that you can provide me.
I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app
I flashed the Cyanogen mod 10.1 nightlies for 2013-01-05. The boot animation was running for an abornomally long time so I pulled the battery and booted up and now the boot animation will not stop running. I tried searching for help but with no avail I have not found it too fix this problem. Also I made a CWM backup.
jubjubcat said:
I flashed the Cyanogen mod 10.1 nightlies for 2013-01-05. The boot animation was running for an abornomally long time so I pulled the battery and booted up and now the boot animation will not stop running. I tried searching for help but with no avail I have not found it too fix this problem. Also I made a CWM backup.
Click to expand...
Click to collapse
Also after trying too restore it, I just get the error Couldn't find directory no files found.
jubjubcat said:
Also after trying too restore it, I just get the error Couldn't find directory no files found.
Click to expand...
Click to collapse
Nevermind fixed it.
How did you fix it? rh
How did u fix it? I am facing a similar problem.
and when i tried to upgrade from cm10 to cm10.1 i was stuck at "Android is upgrading - Starting apps" screen. and a fresh installation of cm10.1 was stuck at the boot animation.
I am using Siyah Kernel 1.8.7 and having cyanogenmod as my secondary rom.
Plz help somebody
utsav7r said:
How did u fix it? I am facing a similar problem.
and when i tried to upgrade from cm10 to cm10.1 i was stuck at "Android is upgrading - Starting apps" screen. and a fresh installation of cm10.1 was stuck at the boot animation.
I am using Siyah Kernel 1.8.7 and having cyanogenmod as my secondary rom.
Plz help somebody
Click to expand...
Click to collapse
SiyahKernel s3-v1.8.8
Posted on January 13, 2013
Changelog
rebased on i9300 update7 sources (sudden-death issue is supposedly fixed in this source drop)
reverted temporary fix for exynos-mem exploit as i9300-update7 sources already fix that
cm10.1 is now supported in dual-boot configurations
1.8.7->1.8.8: fixed cm10.1 not booting when installed as 2ndROM (a tiny typo in ramfs)
BUT,it doesn't work anyway (just trying now at it's stuck on the boot screen)
Just try it and report back! :good:
You do realize that the siyah kernel is for the international S3 which has different hardware then our s3? If you are using a kernel for a different phone then of course it wont boot....
R: [Q] Flashed cyanogen mod 10.1, stuck at boot animation
By "International", you mean the exynox version unlocked right?
Sent from my GT-I9300 using xda app-developers app
R: [Q] Flashed cyanogen mod 10.1, stuck at boot animation
Whatever, it's been released v1.8.9 and it's said to fix the CM10.1 issues
Sent from my GT-I9300 using xda app-developers app
Flash problems
I've had installs stick at the boot animation or shortly thereafter several times. Usually it's because of a dumb mistake. The only thing that's consistently worked for me is flashing back to stock VZ firmware via Odin and doing the whole process over from root through installation. It sucks but it always works.
Howdy.
I've just flashed CyanogenMod 10.1 - 20130315 to my droid 4 with Safestrap, and I haven't been able to boot into it; the cyanogenmod splash screen with the rotating wheel graphic shows up, but it spins for upwards of 40 minutes without doing anything.
I followed the guide on the cyanogenmod wiki for the droid 4 device. The forum won't let me post a link to it.
Before I installed I wiped / factory reset, and after install I wiped cache/dalvik; still no dice. I've tried doing the same process several times (even wiking the system before trying to reflash), but the same result has always occurred: ever unhelpful eternal wheel...
I'm a bit at my wits end; I haven't been able to find any other information about this that wasn't solved by wiping cache / dalvik, so I turn to y'all for help.
Same here
I installed Cyanogenmod 10.1 with CWM the link:[Recovery/Bootstrap][5-sep-2012] CWM Touch recovery v6.0.1.1 - xda-developers and i went ahead and installed the mod: cm-10.1-20130211 all went fine untill i noticed that my camera is not working (not a big deal) but then i noticed that my phone only saw 488MB out of my 32GB this was un acceptable after i found how to connect my phone to my pc so it showed up as a storage device do that i copied the same mob but a different version (cm-10.1-20130129_v2) so i went ahead and booted into Android system recovery <3e> and i did a factory reset and then i said oh f*** i need CWMR to install the thing so i just waited for it to do its thing and then reboted the device thinking after i boot up i will reinstall CWMR but i was never able to boot because im stuck on the boot animation. Been waiting for +20min or so and nothing please help me what can i do this is my only phone please help
help with CM10.1 ROM issue
Hi folks,
this is my first post on XDA. I have a Sprint htc EVO 4G LTE phone which was running on JB.
Thought of root and flash with CM. So, first I unlocked the bootloader using htc dev and installed TWRP custom recovery and then rooted.
Then I flashed the stable CM 10 then flashed gapps which is compatible for CM 10 version. so far so good. oh, btw I did nandroid backup before flash and also wiped to factory reset, cache and Delvic cache.
After the flash i clicked on reboot system and I see the Cyanogenmod boot, but its stuck at that stage and I waited for more than an hour. No luck.
Thank god I did back up before this, otherwise not sure what I'm gonna do.
But, could someone tell me why it gets stuck at this point. I know some of you guys had this problem. I searched everywhere but didn't get help. I thought of posting this in android development forum, but as a newbie I can't do that.
Please help me out.
P.S: when I'm on boot screen (power button + vol down button) I see unlocked at the top but I also have TAMPERED in red color on top of that. Was this normal? or do you think that is causing the problem? and what should I do now?
(First of all I am not an expert)
It happens sometimes about 1/10 of every flashes I did with cm10
It might because some files didn't get copied or got corrupted.
Just try this method
Format data
Format system
Format cache
Wipe dalvick cache and factory reset
Now flash the ROM
Hit thanks if I helped
Sent from my WT19i using xda app-developers app
---------- Post added at 11:35 PM ---------- Previous post was at 11:27 PM ----------
(First of all I am not an expert)
First wipe every thing(system,data,cache,dalvick,android secure....)
Now install ROM,
Wait don't install gapps
Now find an extended cm10.1 kernel or lupus kernel(or such kernels) for your device and flash it via pc
I prefer flashing kernel after installing the rom
Hit thanks if I helped
Sent from my WT19i using xda app-developers app
NEED HELP Cm9
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
neso97 said:
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
Ask in the Xperia X10 mini forums.
Three-finger salute
Ran into this situation today when I tried to restore a backup and I couldn't get past the CM10 logo on bootup. Holding down all three buttons, power, volume up and down, got me back to the Clockworkmod boot screen.
ETA: Sorry, posted in wrong forum. My situation pertained to a Samsung Galaxy 5 Media Player.
neso97 said:
OK so i have xperia x10 mini i have root long time so i decided since there is no update from 2.1 that am gona manualy put new software.I watched youtube video on how to do cyanogenmod 9 so i did everything(flash,bootloader....) and after all that the screen started and i got stuck on that blue screen i tried to turn phone off that didnt work i can only restart the phone and when i plug in it doesnt say anything i cant open sd card or anything its just stuck like that pls help.SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
Hi...i just happened to flash my x10 mini to cm9-robyn yesterday...same thing happpened to me...boot the animation until run of battery....i accidently booted it to recovery and just leave it...fortunately after sometime it booted by itself and run as normal. The cm9 run ok except the wifi is not working. Hope that will help. I am not an expert.
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
I just bought my wife a new phone (Razr hd ftw) because she was on the original razr and its pretty much no good anymore. I was giving her the luxury phone treatment. I rooted it, unlocked the bootloader, installed CWM, and installed cm11. Everything was going great but now for some reason when I try to get into the recovery...i get the moto logo, and its just shuts off. I flashed a new recovery twice, and it shows success on my cmd window, but its still shutting off when I try to get into recovery menu. Any suggestions?
**Update** I was able to get back into recovery after trying over and over again. I still have the issue where it shuts off, but its random. I wonder whats wrong :-/
Which version of CWM are you using and where did you get it?
This isn't the correct place to asking for help...