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.
Related
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.
Try TWRP...it will be better
Sent whit HTC ONE S
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app
boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app
jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209
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.
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
Sorry everyone for this annoying post but I have done research enough to think that I may be out of luck so you guys are my last hope here.
Here is the senario;
I have been running Cyanogenmod 12 (courtesy of Sultan). Once the ROM was discontinued I decided to give Paranoid 5.1 a shot. I downloaded the new rom, suggested SuperSU and Gapps and booted to the most up to date TWRP. I flashed the rom, then supersu, and finally Gapps and then rebooted my phone. The phone stayed in the boot screen for about 45 minutes (maybe even an hour) so I powered off the phone, pulled the battery, and attempted to boot back into recovery using the power and volume buttons but nothing was working. The phone would just keep vibrating (pulsing) until i let the buttons go and then jump right back into the booting screen until I turned the phone off again. Hopefully I am doing something wrong and there is an easy fix but Im afraid that I now havae a brick on my hands.
Please help,
SuperNewb
[Update]
Now the phone will hold the boot screen for a couple minutes then the screen just goes black. Not sure what that means.
Also, just so you guys dont think im too ignorant, I will say that I I have flashed at least 10 different ROMs before this so I would like to think that I have a decent understanding of how this all should work.
Odin to stock and start over. See vincom's stickies.
Sent from my Nexus 5 using XDA Free mobile app