Database Info

Odd behavior when upgrading to cm10.0.0 on HTC one s

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

[Q] Phone won't boot into ROM or recovery--Possible hardware issue?

I've been having a bit of a hard time with a friend's Skyrocket tonight. I flashed CM9 for her before, and it seems to work well. In the past two to three weeks, though, she tells me that her phone's been randomly turning off. Tonight, I finally decided to install CM10 on the Skyrocket, thinking that this would fix the issue. I installed it through CWM like normal (I've flashed many a ROM, so I couldn't have messed up this process).
With everything installed, I reboot through CWM. The issue is, the phone just goes black. After pulling the battery and trying to boot again, I see the Samsung logo, followed by a black screen. The phone sort of pulsates for a bit at this point, giving me a short vibration here and there, before finally stopping. Attempting to get into recovery doesn't work either. I also, due to me not being used to the download mode feature (I personally have a Galaxy Nexus), accidentally tried to start it by holding the power and volume buttons (rather than holding volume and plugging the phone in, not touching power). The yellow triangle would show up very briefly, and then the phone shuts off.
When getting into download mode the proper way, I was able to get into Odin and flash CWM again. At this point, I should definitely be able to get into Recovery. But alas, I cannot... Same issues as before. At this point, it's revealed to me that, after the random shutoffs that my friend had been experiencing, she would sometimes also have trouble turning the phone back on. Noticing a trend?
I'd like to know what you guys think: Is this a software issue, or is it a hardware issue? For the former, what do you guys recommend so the phone could boot normally again? And for the latter, well... I don't suppose there are any easy hardware fixes I could try?

If you pull the battery and reinsert does the phone start on its own with no button pushes? If so... Stuck power button.
Sent from my SAMSUNG-SGH-I727 using xda premium

stoopendis said:
If you pull the battery and reinsert does the phone start on its own with no button pushes? If so... Stuck power button.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Nope, not at all. I need to press the power button for it to start.

It'd flash back to stock with Odin and then go from there.
Sent from my SGH-I727 using xda app-developers app

jd1639 said:
It'd flash back to stock with Odin and then go from there.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I'm embarrassed to say that I didn't try flashing to stock because I figured it would work, but somehow, it did. I still feel that there's something wrong with the power button, and I'll be doing some more testing, but for now, everything's okay. Thanks for your help.

I bet you can reflash cm10 and it'll work fine. Just do a factory reset and the wipes and you'll be fine.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Wipe ALL the things, then Odin back to stock and reinstall. I'd bet that solves it
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

[Q] Stuck in boot loop, tried everything but still stuck.

Hello,
I had a rooted verizon galaxy s3 (CM10) and I recently got stuck in a boot loop. So I connected to Odin and flashed both MD5 files and the root66.tar file, booted into recovery and tried to do a factory reset.
The problem is my power button won't work in recovery mode, so I can not select anything in the menu. The volume buttons work I just cant select anything.
I've searched all over for 2 days now and I can't find anything about my problem, am I screwed or is there something I haven't thought of yet?
Thanks preemptively for the help.

bump please help

Maybe possible to send commands to phone via adb?
Sent from my SCH-I535 using xda app-developers app

Which recovery you are using? Try twrp which recognises touch so no need of power button to select any option. I think class cwm also has touch based recovery.
Thanks doesn't hurt....

Thanks for the replies, I tried to run adb but just runs a lot of code then closes out. I tried to re-download and the same thing happened.
I was using the stock.vzw.root66.tar and BOOTLOADER_I535VRALF2.... I flashed them many times and nothing has changed it still just gets stuck on the 4G LTE screen. Where would I go about finding the recovery files you mentioned? I'm willing to try anything at this point.
Thanks again for the replies.

TotallyAGG said:
Thanks for the replies, I tried to run adb but just runs a lot of code then closes out. I tried to re-download and the same thing happened.
I was using the stock.vzw.root66.tar and BOOTLOADER_I535VRALF2.... I flashed them many times and nothing has changed it still just gets stuck on the 4G LTE screen. Where would I go about finding the recovery files you mentioned? I'm willing to try anything at this point.
Thanks again for the replies.
Click to expand...
Click to collapse
If it's stuck at the LTE logo, boot into recovery and factory reset.
Edit: to Odin flash CWM or TWRP, you can find both files in Open1your1eyes0's root thread in the dev section. Use either once you're rooted.
Sent from my SCH-I535 using xda app-developers app

If you just want this to be fixed quickly, you could always flash a Full-wipe rom that contains the bootloader, etc. Then after your back in the stock rom you could always re-unlock the bootloader, install custom recovery , re-root and flash whatever rom you wanted.
Surge1223

Thanks for the replies, I've searched the internet for a full-wipe rom and I cannot seem to find one, can you point me in the right direction?
Also sorry for the delayed response, I actually graduated college yesterday.
EDIT: Now I can't get the phone to boot into download mode or recovery mode, the Samsung logo comes up and the screen goes black. I'm pretty sure my phone is ****ed.

What was the last change you made? Also are you using the oem cable? Also, heres the link scroll down to section 5. http://forum.xda-developers.com/showthread.php?t=1762709
Surge1223

[Q&A] [CM 10.2]

This is the Q&A for the unofficial CM 10.2 for the SGS4G.
Sent from my SGH-T959V using xda premium

Is it just me or is fix permission missing from CWM.

So, apart from GPS not working, as far as you know everything basic is working well?
sent from me

getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
Yeo, it is. I didn't touch anything related to the recovery except the recovery fstab that I must update to b compatible w the new JB so idk if I have to do anything else to have that feature back or it was CWM by default then, I will find out bout it soon.
itzik2sh said:
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
Click to expand...
Click to collapse
You can say so
Sent from my SGH-T959V using Tapatalk 2

Damn... I thought there was a chance GPS would somehow be possible I'm starting to think its wishful thinking... Come on samsung
Sent from my SGH-T959V using Tapatalk 2

getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
I believe koush decided to throw away the fix permissions button in CWM because he said it was largely placebo effect and had no real purpose anymore.
Sent from my Nexus 4 using xda app-developers app

Thanks for all the solutions and answers that I have collected from users around here, I have been able to update the OP for the FAQ (post 3) in the main thread. So either a question is answered here or not, please also have a look over the FAQ @ post 3 in the dev thread to track down the answered common questions, thanks .
Sent from my SGH-T959V using Tapatalk 2

so do you know if external mics work on this Rom?

Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?

http://www.android.com/about/jelly-bean/

Vismis said:
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
Click to expand...
Click to collapse
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium

1234west said:
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?

Vismis said:
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Click to expand...
Click to collapse
Battery Pull. Hold Vol Up + Vol Down + Power. Whenever The Samsung Galaxy S 4G Splash Screen Comes On, Let Go Of The Power Button And Keep The Volume Buttons Held Down. Should Take You To Recovery
Sent from my SGH-T959V using xda premium

OMG YES!!! I have no idea what i did but i pressed the combo when i plugged it into my computer and it looped the battery screen twice then went straight into CWM recovery did not go through the splash screen like a normal CWM recovery start but whatever i got to remove the rom and flash the new Slim Rom . Anyone have any idea what could have caused this just so i know what to or what not to do in the future ?

Try using adb
Sent from my SGH-T999 using xda app-developers app

To get to CWM recovery on this ROM, simply download 'Quick Boot' application and use it to get to recovery. It works.
Apex launcher crashes as well. I think issue is ROM related. Also, ROM is very heavy, I couldn't find why.
Edit: ROM is snappier after using CM performance features and letting cache do its work.
sent from me

jeffreylin_ said:
That's not very helpful if you can't get past the CyanogenMod splash though.
Click to expand...
Click to collapse
I got through the splash screen on 1st try.
You should check if you worked according to ROM instructions.
I usually always format system as well as wipe everything twice before flashing any new ROM.
I was referring to :
1. the lack of recovery button on power menu.
2. The inability to use hardware keys to get to recovery after flashing this ROM.
Heimdall One-click (in download mode) and try again.

You're right - I missed that option in developer features - it's called 'advanced reboot options'.
I'd suggest you get to download mode - one click heimdall and reflash this ROM after dowble wiping dalvik, cache, and format system.

I've flashed numerous ROMS to my phone before but have never ran into a problem like this.
-I went back to stock
-flashed CM7, as recommended from the OP
-downloaded and flashed CM10.2 but it gets stuck around 75%
I've been on this thread, and the rom thread as well as waiting a bit, hoping to find a solution or it figures itself out. Nothing! Is it unsafe to pull my battery when its at 'Installing update' (75%) for an extended period of time?
Also, i am on CWM 5.0.2.8
Thanks

I flashed it from ICS (Ultragen) and had no problem.
You can try that as well.

Power Button Broken, no more custom roms?

So my power button has been broken for a couple months now and I've been using the same custom rom since. (BTW it's not the outside button, but the actual switch that's broken)
Is there any way to install a custom rom using ODIN? Or is odin only capable of installing stock roms because of the file type?
My phone wont allow me to get into the custom recovery, but I can get into Download mode.
Please help!

xkookooman said:
So my power button has been broken for a couple months now and I've been using the same custom rom since. (BTW it's not the outside button, but the actual switch that's broken)
Is there any way to install a custom rom using ODIN? Or is odin only capable of installing stock roms because of the file type?
My phone wont allow me to get into the custom recovery, but I can get into Download mode.
Please help!
Click to expand...
Click to collapse
Idk about using Odin for custom tars, but I imagine it would take someone more effort than its worth to compile one just for this purpose. When you try booting into download mode, how are you doing this? And how are you booting into recovery? What happens once it gets there?

You could also just get the power button fixed. Then all your problems are solved.
Mobile tech videos will do it.
Sent from my SCH-I535 using Tapatalk 2

Doesn't ROM manager or something do reboots into recovery?
This post was made by Vanlandi.

adb reboot recovery
Actually if you didn't want to bother with setting up adb I'd imagine you could just type 'su' press enter, type'reboot recovery' and press enter into of the many terminal emulators in the play store.
Sent from my SCH-I535 using Tapatalk

bobloblaw1 said:
adb reboot recovery
Actually if you didn't want to bother with setting up adb I'd imagine you could just type 'su' press enter, type'reboot recovery' and press enter into of the many terminal emulators in the play store.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I knew there was a way to do it!
This post was made by Vanlandi.

Casper34 said:
I knew there was a way to do it!
This post was made by Vanlandi.
Click to expand...
Click to collapse
ADB always has your back!
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
ADB always has your back!
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I meant by terminal. That's easier. LOL.
This post was made by Vanlandi.

Get "quickboot" from the store
Sent from my SCH-I535 using xda app-developers app

Casper34 said:
I meant by terminal. That's easier. LOL.
This post was made by Vanlandi.
Click to expand...
Click to collapse
Oh, well yea terminal is great as well. You can do the same for download mode as well or even try using it to attempt to delete pesky files that just won't delete with a file manager.
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
Oh, well yea terminal is great as well. You can do the same for download mode as well or even try using it to attempt to delete pesky files that just won't delete with a file manager.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Ya! I forgot about terminal. You can do everything from there if you know the commands.
Kinda off topic here, but is there a thread with the common commands for terminal? Like to reboot, delete files, move files, and such.
This post was made by Vanlandi.

Not sure how you get into download but not recovery since the procedure is same except use volume up instead of volume down. Also the Quickboot app/widget is much easier than terminal emulator if just need to get to reboot/recovery or download modes. Enables the extended power menu same as the power button.

Mobile tech videos Did a great job repairing my broken power switch. Pretty quick turn around.
Sent from my SCH-I535 using Tapatalk 2

I have a similar problem, but when I use the terminal commands or any app to reboot into recovery, the phone vibrates and turns off but then stays off until I pull the battery and replace it. Also, when I try to go into download mode, it comes up for about 5 seconds then turns off (similar to SDS). Any thoughts? I originally planned to try to switch roms and see if that would fix the power button issue, but if it's hardware, I'll try to unroot and take it too Verizon as a last ditch attempt.
Also, when I take the back case off and put it back on, the power on/off screen pops up.
Thanks!

I have the same exact problem as the guy above buy my power button is just completely borked.
I thought I could get into download mode but that doesn't work either.
I'm going to try and resolder the replacement power button I purchased that didn't work.

odin mobile

Mobile Odin did not work either. Gets stuck at logo screen when it first boots then stays black.

xkookooman said:
Mobile Odin did not working either. Gets stuck at logo screen when it first boots then stays black.
Click to expand...
Click to collapse
I think the rom your trying to flash is bad …
Phone starting but getting stuck at boot screen means it's soft bricked, try flashing a different rom …
And once you manage to get your phone running use ''recovery tools'' from play store to flash a custom recovery, it flashes a touch recovery so that will eliminate your button problems …

No my phone operates fine. When I attempt to get into recovery, it restarts, a brief screen appears where it says "rebooting recovery" on the top left, and then it stays black. TO get out of this I go into Download Mode, and press Cancel to Restart.
I'm currently using CyanogenMOD 10.1.2.
At this point I'm thinking of just going to a mobile phone repair store...

xkookooman said:
No my phone operates fine. When I attempt to get into recovery, it restarts, a brief screen appears where it says "rebooting recovery" on the top left, and then it stays black. TO get out of this I go into Download Mode, and press Cancel to Restart.
I'm currently using CyanogenMOD 10.1.2.
At this point I'm thinking of just going to a mobile phone repair store...
Click to expand...
Click to collapse
Mobiletechvideos did a great job fixing my power switch... It was doing the same thing your describing. Been perfect ever since.
Sent from my SCH-I535 using Tapatalk 2