Hello!
Apparently I broke my latest rom, MIUI ICS alpha 2.5 with recovering applications and system data from Titanum Backup. After suggested reboot, there was a loading screen going on forever, so i wanted to wipe & install or go back to previous rom. I removed the battery, as it was only way to shut down the phone.
Booted up to CWM with "+" key, and after a few seconds it's just turning off. I can select some options but it keeps turning off.
It did it during "format data", which wasnt finished, it did also shut down just after finishing formatting cache. About the same amont of time.
CWM version: 5.0.2.7
I have my backup rom and also new one, but cannot install any of them 'cause it keeps shutting down. And yes, the phone is connected to the charger, so it's not a problem of low battery.
Any ideas, please?
[EDIT] [SOLVED] Just rebooted with adb. It's ok now
Well for 1 don't restore system data. 2 pls explain what you mean by turning off as you mentioned you can access certain things. Is it powering off as in completely off? Are you pressing the power button on clockwork recovery? If so that makes screen blank not power off
Sent from my HTC Vision using xda premium
no, it just turned off my phone completely even if i was just switching options, suddenly "poof"
Run superwipe and reflash rom. If that fixes it flash the backup uf whatever you like fhat you didn't restore "system data" for.
Sent from my HTC Vision using xda premium
Related
Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.
Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
No good man I hope you got insurance
Sent from my PC36100 using XDA App
Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App
same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...
xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.
Edit: Found the solution to my problem (in comments below).
I installed the latest version of CM7 last night, and everything was running smoothly until I downloaded Launcher Pro. At that point, every time I tried to do something, I got an error message along the lines of "android.media process has stopped unexpectedly", or something extremely similar.
So this morning I decided to reboot my phone and when booting, even after removing the SD card and putting it back in, it got stuck in the CM animation (the Android riding the skateboard).
So I held volume down and power and went into that menu and choose backup/restore, where it then took me to ROM Manager's little menu. After trying to hit backup and restore again, it looks like it's trying to load something from ROM Manager, but it just gets stuck with a black screen with the hat and arrow (ROM Manager's logo).
Is there anything I can do to fix my phone without having to do a complete reset?
In clockworkmod recovery, use the optical joystick instead of the power button (as a selector). Took me forever to figure that out Lmao. Your phone is not bricked, don't worry.... I mean you did do a nandroid right?
Sent from my ADR6300 using XDA App
That did it, I had been using the power button by mistake.
Thanks for the input! I had done a Nandroid and I use Titanium Backup, so after reverting back to the stock Sense UI, I downloaded 7.02 instead of the latest CM7.
Glad that worked for you!
Sent from my ADR6300 using XDA App
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?
Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
if you can get into cwm then try fastboot and flash the factory images from the boot screen
_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.
id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it
I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.
My HTC desire with the official ginger bread update on is now looping the "quietly brilliant" startup screen - my battery run out and when I started charging it and switched it on, this happened, completely random
I have tried recovery mode etc, however this doesn't work
Does anyone know if there is anything I can do?
Does it go to
- bootloader mode vol- and power
- fastboot mode back and power
I had the same problem, after doing some research I came to the conclusion that the issue was with the partition type of my memory card.
Try this, remove the memory card insert the battery and then restart [do not insert the memory card]. If it works now then you have the same problem I was facing. If not then this could be something different.
Reply, if the same i will provide the solution.
try deleting (wipe) user data and dalvik cache if you don't have something important.
Sent from my HTC Desire using xda app-developers app
Key phrase here is "with official gingerbread update".
via xda app
yes it has the official gingerbread update on it from the htc dev site - ie I have never rooted it or put a custom made rom on it
recovery or fast boot, ie switching on with volume buttons doesnt work
I have tried without the memory card and without the sim card still loops
I just cant seem to stop it looping this screen!
*edit*
oh wait, I just tried fast boot, back and power and that worked!
what can I do now? reinstall rom?
The only option you have right now would probably be to run the official gingerbread RUU again. Unless you wanna root it from this point forward.
You'll probably lose all your data which is probably lost at this point anyway.
My concern is that it just went crazy and you are on stock so I feel something else might be broken.
via xda app
Get the 2. 3. 3 RUU from htcdev only and run it from pc.
Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy
Nerdmom3 said:
Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy
Click to expand...
Click to collapse
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you!
I wiped the internal SD. That enabled me to format the phone then install the Liquid Smooth ROM. So far so good. It's been 48 hours with no problems.
Thanks again for your help!