This is the first time have i downloaded a rom and so i got cm10 and now it's just stuck at the boot animation. PLEASE HELP!!!
Make sure you did not skip factory reset before flashing the rom.
Might be redundant but you gotta do a battery pull to get out of boot loop.
Sent from my Nexus S using xda app-developers app
Is it stuck on the google logo with the unlocked padlock below? If so try pulling the battery and retrying. If it gets stuck after that then you have yourself a booting problem.
I have a similar one (with phone getting stuck on google logo at start up), and I get passed it by heating the phone using a blowdryer (battery out). I'm on Jellybean and rooted and it's an gt-i9020T model. If everything about your problem is like mine, you can try the same solution, maybe it'll help get passed the frozen screen? P.S this solution only helps you boot one time, if you reboot it'll get stuck again (at least it does for me).
Never heard that about the hair dryer. Sounds scary. Follow this http://forum.xda-developers.com/showthread.php?p=20629823
And hopefully you downloaded the correct rom 4 your phone. Then reflash rom in recovery
Sent from my Nexus S 4G using xda app-developers app
LOL what is this blow dryer method?! I see the same user posting about it on other threads.
Related
Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!
You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App
brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila
The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.
You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium
So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App
Again the exclamation mark IS the stock recovery.
well today I decided to flash some different roms to my infuse. Apparently my phone doesnt like being abused and flashed several times in one day (lol)
I can still boot into recovery and load a rom. The phone loads everything, but when I try to reboot it just shows "samsung" on the main screen. It doesnt boot loop, it just constantly shows samsung... I let it sit for about 10 minutes and the screen never changed. What is an easy fix for this? I am using the Atrix2 right now (terrible phone) and want to get my infuse up and running again...
http://forum.xda-developers.com/showthread.php?t=1336359
^can this be used? I am not really sure what to do... The phone isnt really "bricked" it just wont boot.
I appreciate any advice
j.aussie said:
well today I decided to flash some different roms to my infuse. Apparently my phone doesnt like being abused and flashed several times in one day (lol)
I can still boot into recovery and load a rom. The phone loads everything, but when I try to reboot it just shows "samsung" on the main screen. It doesnt boot loop, it just constantly shows samsung... I let it sit for about 10 minutes and the screen never changed. What is an easy fix for this? I am using the Atrix2 right now (terrible phone) and want to get my infuse up and running again...
http://forum.xda-developers.com/showthread.php?t=1336359
^can this be used? I am not really sure what to do... The phone isnt really "bricked" it just wont boot.
I appreciate any advice
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1331381
Try a battery pull, also wipe cache/dalvic, restore.... If that doesn't do it...ultimate unbrick
Sent from my SAMSUNG-SGH-I997 using XDA App
Get the Odin one click to stock
Sent from my SAMSUNG-SGH-I997 using XDA App
Not bricked. If the screen turns on you're not bricked.
Anybody know what causes this? And it's not the boot screen but the Motorola logo because the software starts to boot. I can reboot and usually it comes back to normal but it does this and sometimes I will sleep another 7+ hours and not have the phone on in case an emergency
Sent from my Nexus 7 using Tapatalk HD
radzer0 said:
Anybody know what causes this? And it's not the boot screen but the Motorola logo because the software starts to boot. I can reboot and usually it comes back to normal but it does this and sometimes I will sleep another 7+ hours and not have the phone on in case an emergency
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Are you using Custom ROM? Nearest bet is, it might be ROM or Kernel issue. Would be good if you reflash another ROM or go back to stock firmware to see if that's the case.
It did this before I unlocked the bootloader and all. Doesn't do it every time but based on times I see on it it happens around the same time as full charge would come around. Also I have changed rooms a few times since and it continues. Wouldn't the room try to boot and lock? Because it's not even getting to the boot logo it's hanging on Motorola.
Sent from my Nexus 7 using Tapatalk HD
radzer0 said:
It did this before I unlocked the bootloader and all. Doesn't do it every time but based on times I see on it it happens around the same time as full charge would come around. Also I have changed rooms a few times since and it continues. Wouldn't the room try to boot and lock? Because it's not even getting to the boot logo it's hanging on Motorola.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Which is your phone? Does it have a forum here in XDA? If it has a forum, it might be good to post this issue over there, as you would get more feedbacks from the users using this phone.
From the problem you explained, its getting stuck into bootloop after getting fully charged that's why no boot animation. It should be a software/ROM/Kernel related issue I guess, though not sure.
RAZR maxx hd.. I figured maybe they released a new main firmware that's non rom related and since I don't run stock I didn't get it..
Sent from my XT926 using Tapatalk 2
For about a month now my phone has been randomly restarting into qhsusb_dload.
I flashed the international ICJ, bricked my phone, sent it away for repairs. I sent it to mobiletechvideos, they repaired the brick and gave me s-off.
After the repairs it worked fine for ~1 month.
Now, the phone will almost always boot to qhsusb, though I can get it to boot into the rom/recovery/bootloader.
I've tried changing roms and even hboot versions but I'm too inexperienced to track down the problem.
I'm confused as to your problem... qhusb_dload is a complete brick, yet you say that you can fix it?
Sent from my evita
I'm just as confused as you.
My phone will spontaneously shut down, no lights or anything. When I plug it in and check device manager I see the qhsusb_dload.
But then after I give it some time and fondle the buttons just right it reboots and I'm back to my bootloader.
I can boot into a rom but it usually doesn't last very long (~1hour) before I get a reboot.
The phone isn't always completely bricked...just sometimes?
It is possible to enter that mode without bricking. Typically holding volume up instead of volume down which goes in to recovery, when booting.
How often does it happen?
Sent from my One X using xda app-developers app
It happens about half the time when at boot it and then frequently at rom startup. I've never had any trouble booting into recovery or the bootloader, and it does seem more frequent when the battery is under 40% (but that just may be me.)
I'd say it's down 75% of the time.
Is your phone s-off?
Sent from my One X using xda app-developers app
Yes, but I paid to have it done so I don't know how it was s-offed
So long as its soff in the boot loader that's all that matters. Its a pain in the ass but I would ruu and stay stock to see if it keeps happening.
Sent from my One X using xda app-developers app
Ran the RUU, now my phone won't boot to a rom. I can still get to the bootloader and the recovery though. All I get is a boot loop to the htc white screen if I let it do it's thing.
Ruu and stay stock for a while to see if it keeps happening while stock.
Sent from my One X using xda app-developers app
Hello, I have 10.1.3 CM on my phone right now. If I flash any other Roms like 10.2 CM, AT&T stock MF3, etc I'm having reboot problems. The initial first boot into the phone desktop is fine. However, I can never get into again. It always gets stuck on the Samsung boot screen. It's the image with Samsung and a unlocked lock. When I go into recovery, I have to wait a long time too. Sometimes I get the enter a password screen in TWRP. Once I get in, I have to format data and I can get to phone desktop again. However, when I reboot again, I get stuck and the cycle continues. The only thing that reboots for me with no issues is 10.1.3 CM.
I'm not sure why you're posting here, you're a long ways away from your forum lol. This is the HTC One XL forum.
Sent from my Evita
And another thing, this should be in the Samsung CM thread. Don't tick them off by putting it in general too
Sent from my HTC One XL using XDA Premium 4 mobile app
OK thanks sorry.