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
Related
So i installed latest cm7 nightly 55 and it started normally waited about a minute on the cyanogen mod bootscreen then started looping. any ideas?? i have cwm recovery installed (non nvflash version) if i hold down vol up it goes into a S/W upgrade screen then goes black. holding Vol Up and Down doesn't do anything on a virtual windows 7 pc.
Couple of questions: Which rom were you using before you flashed the nightly? Are you sure it was looping? Sometimes the initial boot after a flash takes a minute or 2.
Needless to say you need to NVflash recovery. Do that for sure whether you're looping or not.
phburks said:
Couple of questions: Which rom were you using before you flashed the nightly? Are you sure it was looping? Sometimes the initial boot after a flash takes a minute or 2.
Needless to say you need to NVflash recovery. Do that for sure whether you're looping or not.
Click to expand...
Click to collapse
Ditto on the above - plus what did you wipe before you flashed? Alos, you might try pulling the battery and starting up again.
You amy not be able to do anything if that does not work until you flash a real recovery. Follow the one-click method on the dev thread - NVflash and recovery all in one package.
Thanks for the input guys, I tried using nvflash but it doesn't pick up the device when I try to install the apex drivers. I am using a virtual machine so I'll try on a regular one.
Sent from my HTC Sensation 4G using XDA App
Actually guys I got a sensation so ill sell the g2x if anyone is interested. I'm gonna include an 8gb sdcard.
Sent from my HTC Sensation 4G using XDA App
You needed to clear the cache and then reinstall the rom. That was my problem.
Sent from my LG-P999 using XDA App
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Let me guess. You flashed CWM via ROM manager?
Follow he guide here and let us know how it goes:
http://forum.xda-developers.com/showthread.php?t=1056847
Also, before you install the ROM use the wipe tool in my sig.
I appreciate the response but I did use that thread to flash it.
ae2012 said:
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Click to expand...
Click to collapse
When it get to the point where "the cyan colored horizontal loading bar" let go of the volume and power button and see if it boots into CWM.
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
ae2012 said:
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
Click to expand...
Click to collapse
Try rooting process all over again... just make sure battery have plenty of charge and make sure during any of the process there's no interruptions... let us know what happen after that...
Sent from my LG-P999 using xda premium
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
No need to unroot... as long as your computer still detect your phone... just flash everything again... I mean since you want to root... I would just do all the rooting process again... and reflash clock work... don't use rom manager to flash clockwork mod...
Or
And since you can't get into clockwork... you can just try flashing clockwork again... no rom manager
Sent from my LG-P999 using xda premium
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
ae2012 said:
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
Click to expand...
Click to collapse
Try flashing Google apps again. Cm7 doesn't include them in their builds.
Sent from my LG-P999
Worked like a charm. Thanks, yall are the best.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Rom Manager is not a safe alternative. Stay with Nvidia ClockworkMod.
Its should be a blue lg logo when you have to let go of the buttons.
Sent from my LG-P999 using xda premium
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Every time before you re- flash a rom I would recommend doing a data/factory reset within clockwork recovery. then Wipe your cache. And then even a wipe of the dalvic cache under advanced settings. Then flash the rom then gapps. Then reboot. Its called doing a clean install. It just makes everything smoother when re- flashing. And if your apps ever not update like that again just fix the permissions in clockworkmod then reboot. It usually fixes it. And i don't recommend flashing directly from the rom manager. Do it from recovery instead. Hope this helps.:thumbup:
Sent from my LG-P999 using XDA
[edit]
Sent from my G2X.
Rocking stock CM 7.2.0-RC1
Similar issue, totally different outcome...
Ladies and Gentlemen (and low-lifes),
I have found myself in a similar situation, after recently flashing a ROM, to where I am now unable to boot into CW Recovery. The ROM flashed is working fine but when I attempt to boot into recovery I get a black screen and it never progresses beyond that. I have attempted to reflash of course via NVFlasher and from all indications it's been a successful flash. That said, the results remain the same... black screen.
FYI: I have not yet attempted to flash back to Stock Recovery.
•Current Rom - Owain's Domination v77 (a great ROM by the way)
•Current kernel - Harsh's 3.0.32
•Used Nullifier to prep device for ROM install (as I have been doing for sometime now)
If anyone has any experience w/this issue or any advice going forward I would greatly appreciate it.
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
dark ma++er said:
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
Click to expand...
Click to collapse
Ok, I will bring my concerns to an end now. I forced CWM to remain in play by not letting go of the power and vol. down buttons then using my thumb to see if I could stroll through options in CWM. Once I accessed a few it remain stable. I nullified and re-flashed my ROM and all seems ok in my personal corner of the universe. I am now able to boot into CWM without issue.
I was on bb4 Rom, and tried to reboot into recovery to flash the official jelly bean, but now I get no output on the screen. I can use various combinations of the buttons, and it will vibrate, but won't boot. Can anyone help?
Sent from my LT26i using xda premium
ishamm said:
I was on bb4 Rom, and tried to reboot into recovery to flash the official jelly bean, but now I get no output on the screen. I can use various combinations of the buttons, and it will vibrate, but won't boot. Can anyone help?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
If you don't have fastboot or adb working there's not much to do for your device.... sorry mate. At least other two users had the same issue lately, i wonder what's causing it.
oh good...
what would be the combination to boot into fastboot? i wander if its possible to get into it, and just the screen is not working during boot?
ishamm said:
oh good...
what would be the combination to boot into fastboot? i wander if its possible to get into it, and just the screen is not working during boot?
Click to expand...
Click to collapse
To get in fastboot mode press Volume down + Power and release the buttons when the white text message, you have about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" which means boot in fastboot mode.
Thanks, couldn't remember which buttons or was, different from my phone XD
Unfortunately I get nothing but vibration from the tablet. Bricked?
Sent from my LT26i using xda premium
soft brick
I had .30 stock & flashed a copy of the JB OTA via TWRP.
I did a full wipe (everything except SD cards (so I thought)
Somehow my micro SD card was wiped, but not the Dock SD card.
Want to guess where my TWRP back up copies were?
I boot flashed TWRP again but it doesn't appear to work with JB yet.
(doesn't see any files on any sd cards).
Next thing I'm going to try to do is fastboot a copy of the .30 blob.
I'm checking out http://forum.xda-developers.com/showthread.php?t=1803343 but it appears that process is dated.
Any suggestions are greatly appreciated
I have tried various things to fix this, tried booting fastboot, adb etc, but to no success. Can anyone help? I've never seen a problem be too much for xda XD
update: so the device appears too have been on last night, as the battery was dead (no vibration when power button held), I plugged it in, got a vibration to say it's charging. Could it be the screen is actually broken, as in a hardware fault, just with coincidental timing that I was trying to get into recovery?
Thanks
Sent from my LT26i using xda premium
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
Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app
Listen like the kernel is the problem. So flash another one (easy way) or go back to stock.
If it's working fine then, it was the kernel which made this happens.
Much success
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ack-nak said:
Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?
abaaaabbbb63 said:
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?
Click to expand...
Click to collapse
Flashed with stock kernel and it's still doing the same thing. I also restore back to stock 4.4 with stock kernel and it's still doing the same. Do I need to unroot and root again then flash rom, kernel, and etc? Don't really want to do that if I don't have to but guess I have no choice? Thanks again.
Yep, do a factory reset and see if it's working fine again... I'm thinking so.
CHEERS
Sent from my ME301T using XDA Premium 4 mobile app
Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app
Ack-nak said:
Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
what do you mean unroot and root again?
biggiephat said:
what do you mean unroot and root again?
Click to expand...
Click to collapse
This means, going back on to the stock firmware. This will remove the root for sure.
After that starting with rooting again.
Hope this answers your question
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app