My phone is rooted and I have had many custom roms on my phone, but now when my phone boots, it gets to the lock screen, and reboots automatically... I can get in to the recovery mode, and I flashed couple of different roms, but it ends up the same way - the moment it boots, it starts restarting itself... Any help??
If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.
another thing it could be is the wifi, on CM7 for example i'd get bootloops if i enabled the wifi on the 1st boot, dunno if the current nightly still does it coz i dont enable my wifi until i done one complete reboot after flashing a new ROM.
Or flash http://forum.xda-developers.com/showthread.php?t=868720
Full wipe 1.3 for ext3 and 1.5 for Ext4 roms , then re flash the Rom ur having problems with.
hmohammed43 said:
If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.
Click to expand...
Click to collapse
I tried all of this... still no luck... It's the same - boots up, the lock screen shows it self, and then it keeps rebooting...
Any new ideas?
Hmmmmm
What rom are you on at the moment?
It doesn't matter. I've changed couple of them. It started on ARHD, but it's the same when i flash cyanogen... Maybe I should try flashing radio? Because, when it boot's up, just before restarting, i see that it's not connected to the mobile network... And it first started happening when I landed in Turkey... Can it have something to do with their network??
I wouldn't think it's anything to do with the network....but i would flash the reccomended radio (the one from the 4th of january)
http://forum.xda-developers.com/showthread.php?t=877295
Also, wipe every partition manually (except /sdcard !) from the advanced menu in clockworkmod recovery, then use the wipe/factory reset option in the main menu, then flash the rom. If that doesn't work, the only thing i could suggest is using a WWE RUU from here:
http://forum.xda-developers.com/showthread.php?t=824357
Make sure you flash one for either 1.32.405.3 or 1.32.405.6 (those are the only rootable firmwares, and the unbranded ones don't like being downgraded, so you'll need a goldcard if you flash higher). When the RUU finishes, it'll bring you back to stock, then you can root the phone again
As I thought, flashing radio helped!! Thank you very much!!
Related
HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???
It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.
i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?
Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App
thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?
That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.
thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...
i also faced same problem CM7 .. i tried CM6 and it went on fine..
heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.
i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...
hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..
im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...
I have always had random reboots with the phone, however they were mostly infrequent.
Fastforward to yesterday, I was running the latest stable version of CM7 (7.0.3.1 or something to that effect). Everything was working out okay, and so I decided to flash the latest WiMAX and Radio updates. First I did the WiMAX, everything went fine and the phone rebooted and I used it without issue for a couple hours. At this point I flashed the latest radio from Caulkin's thread. After rebooting, the phone makes it through the splash screen, and into the rom splash screen, then once actually booting the rom it boot loops. If I get lucky, and manage to turn the phone into Airplane mode before the boot loop, I can prevent it from occurring.
So I have tried to re-download and reflash this version and the last version of the radio many times, without success in stopping the boot loops. I have reflashed the ROM as well as gone back into old Sense nandroid backups and the problem persists. I have flashed the FORMAT_ALL.zip file and the problem still persists! I have tried to update PRL and Profile, and the problem still persists!
Any help would be greatly appreciated.
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
dougjamal said:
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Very interesting, indeed. Good catch, by the way......Since you are using CM7, you may have to apply a GPS fix of some sort. Does the smell thing occur with other AOSP roms like Salvage-Mod? What about Sense-based roms?
posting & replying via the XDA Premium app.
/bin/bash said:
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
Click to expand...
Click to collapse
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
teh roxxorz said:
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
Click to expand...
Click to collapse
I haven't put CM back on the device, as directed above I put on a stock rooted rom to "bug track", so gapps is installed, yes, but by default in Sense / HTC.
From the last two hours or so it still reboots after location settings are off, but less frequently than if they are on. Perhaps this is a heat issue? The more radios and things on the quicker it overheats into bootloop?
Also, stressing the phone in any way, such as running linpack, triggers a reboot.
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
flash twrp recovery via fastboot
simms22 said:
flash twrp recovery via fastboot
Click to expand...
Click to collapse
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Runge2970 said:
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Click to expand...
Click to collapse
are you wiping data(factory reset) or are you just wiping your dalvik and cache?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
OK do what simms22 has explained. That should work.
But from what I am interpreting is that you are doing cache not wipe. So you go to "wipe data/factory reset" menu and hit/press yes. It should wipe it and done. BTW it might have been in a boot loop because you might of dirty flashed or you didn't wipe cache and dalvik cache. That is very important to remember. Never dirty flash and also wipe cache and dalvik cache.
Also did you play with tweaks and such before this was happening. Like voltage or over clock because that could be the problem too.
Dalvik cache and cache are hash signed by the last rom that was flashed. New rom, new hash sign. No need to wipe caches, just data.
Sent from my i9250
Cwm is notorious for failed wipes.
Definitely upgrade to twrp, and if your phone is so messed up twrp can't wipe it, use the android revolution wipe script.
Sent from my Galaxy Nexus using xda premium
If you're backed up and don't mind losing EVERYTHING, yes, EVERYTHING in /data, then boot into fastboot mode and run
Code:
fastboot erase userdata
from your computer. (Might need root privileges if running on Linux)
Hi guys. I got it to work finally. I didt some tweaking whit the DPI. Maybe that was the cause of the crash ??
But i went to use the Galaxy Nexus toolkit, first of all to flash the other recovery program. But since it dint work either i flashed it whit sock rom, from the same toolkit at started all over. That did work, but hell of a way to go
Hello!
After some fiddling around I have finally succeeded into installing the MIUI custom rom. (had a heck of a work around to perform because I forgot to put the custom ROM on my SD card first.)
Right now, I've got Clockwork Recovery 5.8.4.0 installed with the latest miui. Fastboot is also installed and working, and my phone is unlocked. The correct boot.img has also been installed.
It even boots. BUT. After it has showed the MIUI logo and goes to my home screen, it starts loading for like 4-5 seconds where everything still works, and it then stops. Crash. The screen freezes and my phone reboots. It seemed like a SIM card problem to me, but even removing the SIM card and booting my phone wont solve this issue. Does anyone have any clue what I can do?
Summary of installed software:
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
Latest MIUI for One X (downloaded this afternoon)
Latest ADB Development Kit. (Not used though)
Latest Flashboot.
Factory Reset performed (Whole phone is empty except for above mentioned programs.
Thanks in Advance!
P
Erase Cache
While in Fastboot Mode .Perform This command
Fastboot erase cache
Should do the job for u!
I would suggest flash the boot.img again and then erase cache again.Will work
Tried it, but..
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
^^ for ARHD 16 u need hboot 1.33 , 1.36 depending on your CID
for miui did you do full wipe?
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache? I think ARHD does that anyway, but might be worth doing the superwipe.
Oh, and if you're restoring system data or system apps with Titanium backup, stop it.
HBOOT!
I am afraid ur not on the right CID version for installing JB roms.
Please update ur Hboot
@ali3nfr3ak: Yes, I did a full wipe before MIUI. After every flash I do a Dalvik Cache Wipe, Factory Reset Wipe and Cache Wipe. Even the fastboot receive a cache wipe after every flash.
How do I update my HBOOT? The rest seemed pretty straight forward, but there are tons of versions out there, and I do not know which one I should be taking. And what is CID? I've also been having troubles porting a Super Wipe toward my mobile phone. Can a Super Wipe be performed within fastboot/recovery?
Haha and no, I'm not using Titanium Backup
Right, I've succesfully restored my phone to it's old state. Flashing MIUI again provided the same error. Could it be that my hBoot is out of date here? My One X still has the 4.0.4 android version, whilst MIUI is based on 4.1, right?
Change the rom, miui isn't good.
Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!