Related
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
So i've tried flashing Wyrms nightlies (multiple versions) and now skyraider 4.0 and every time i flash the rom, and reboot it gets stuck in a bootloop. I'm not sure what i'm doing wrong, but i can get back to my backedup roms. Any suggestions?
Are you wiping before flashing the new ROM?
What clockwork recovery version are you using? I've never had an issue with roms causing bootloops, this is my process though it might be a little overkill. Clockwork 2.5.1.2, put rom on SD card, boot into recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, format system, format data, format cache, then flash the rom. I say its possibly overkill because I think most roms install scripts do some of those wipes for you but I've never run into bootloops after rom installation.
Sent from my ADR6300 using XDA App
so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App
I flashed CM7.1 and I'm stuck in a boot loop. I tried wipe cache partition, wipe date/factory reset, wiping dalvik cache and reflashing a different rom but still keep getting the boot loop. What else should I try doing to slove this ?
Could be kernel related, are you using an aosp and hopefully not a sense kernel? Need more info, what kernel, recovery are you using?
I'm using ClockworkMod recovery I'm not sure what kernel I using
Easy fix, recommend starting from new. wipe the entire phone in recovery at least 3 times, sd card also, backup sd card to computer if you need to via USb toggle, flash Cm 7.1, flash tiamat kernel, found in development section, reboot, good to go, nandroid once up and running, happy flashing
Thanks, okay I'm glad you said easy fix I'm not as worried now. I'm gonna follow your advice. Whats a roamer kernel ?
sorry swype acting weird, use tiamat kernel 4.1 something in development section
The FIRST Thing you should do is get rid of Clockwork Mod, and get Amon Ra, so you can wipe everything.
Just wiping Data/Cache/Dalvik when flashing a new ROM isn't enough.
Hey thanks again ! ! I followed your advice and got everything working again
I'm running amon ra, haus mod rev .a
i've partitioned my sd card with 32 swap, 1024 ext2, then to ext3
I've wipes all data/factory reset, then cache, dalvik cash, and data
I then have tried flashing 2 different ROM's and boot leave me stuck in a boot loop after flashing.
I'm not sure what to troubleshoot next.
Thank you in advance for your gracious help.
Chris
TurbineTester said:
I'm running amon ra, haus mod rev .a
i've partitioned my sd card with 32 swap, 1024 ext2, then to ext3
I've wipes all data/factory reset, then cache, dalvik cash, and data
I then have tried flashing 2 different ROM's and boot leave me stuck in a boot loop after flashing.
I'm not sure what to troubleshoot next.
Thank you in advance for your gracious help.
Chris
Click to expand...
Click to collapse
First off,what roms did you try flashing and Then you need to wipe everything,from data/factory reset,cache,data,android_secure,SD ext.,system,dalvik-cache,never the SD card.Now understand that sense 3.5 roms take alot of space,so the boots and such take longer and boot more times.
Diablo67 said:
First off,what roms did you try flashing and Then you need to wipe everything,from data/factory reset,cache,data,android_secure,SD ext.,system,dalvik-cache,never the SD card.Now understand that sense 3.5 roms take alot of space,so the boots and such take longer and boot more times.
Click to expand...
Click to collapse
I tried Nitrous and Express.
This is the first time i have seen instructions to wipe SD ext and system.
So here is what i did per your instructions.
I went right down the wipe list in amonra haus mod rev .a and performed the following wipe operations:
Wipe ALL userdata/factory reset
Wipe CACHE
Wipe DALVIK-CACHE
WIPE DATA
Wipe SDCARD:.android-secure
Wipe SYSTEM
Wipe SDEXT
Wipe DATA:battery stats
I did not wipe the following:
Wipe BOOT
Wipe SDCARD
Wipe DATA:rotate settings
I then flashed this ROM
http://forum.xda-developers.com/showthread.php?t=1542036
I had heard to give everything lots of time to complete, so i have let my phone sit in the boot loop and reboot about 30 consecutive times. I think that's enough time to do something different. I then took the battery out to stop the boot loop, replaced battery and powered on the phone. It continued to boot loop, and i let it sit again for another 5 or so mintues boot looping away. I pulled the battery again and powered it back on and it continued to boot loop. It reboots every 25 seconds and the only thing i see on the screen is a black background with
"htc EVO 4G"
In white letters across the middle.
I Wiped everything again and this time i also did
Wipe DATA:battery stats
I then partitioned the sdcard again, with
SWAP: 32
ext2:1024
then under the partition menu in amonra, i selected
SD:ext2 to ext3
that process complete
Then i go to the main recovery menu and select
USB-MS toggle
and copy over the ROM from my pc to the sd card. this was the only thing i copied over and the sd card is totally empty accept for the 269MB ROM zip file. (in past attempts i have copied over the ENTIRE contents of the sd card that i backed up)
I then flash the zip and wait for it to complete.
It finishes and then goes into the boot loop again. and i've let it continue to try and do anything other than what i have described above. It does not. I pull the battery and it boot loops again.
Is there something else in the partitioning process that i need to do? Do i need to format the sd card first or after?
What you really need to wipe is: boot, system, data, cache, dalvik, and sd ext [if partitiooned], and you're good to go. Wipe the boot, and then try again.
teh roxxorz said:
What you really need to wipe is: boot, system, data, cache, dalvik, and sd ext [if partitiooned], and you're good to go. Wipe the boot, and then try again.
Click to expand...
Click to collapse
Thanks for the help!
edit: I wiped everything you said and nothing else and i still get boot loops. It reboots once every 30 seconds or so and i let it keep rebooting for about 8 minutes. Then i popped the battery and let it try to boot again but i got the same boot loop.
Again, i really do appreciate the help, what should i try next?
After flashing the rom wipe cache and dalvik again before reboot if it loops more than 3 full loops pull battery and reboot to recovery wipe cache and dalvik then under.advanced menu fix permissions(uid mismatches) and the wipe cache and dalvik again and reboot when wiping before flashing wipe each option a few times in a row until they complete the wipe rather quickly that will ensure they are wiped properly. U can also try reflashing your recovery or changing recoveries to amon RA 2.3 or amon RA style supersonic recovery v3.11 depending on what recovery you are using currently
Sent from my SPH-D710 using xda premium
TurbineTester said:
Thanks for the help!
edit: I wiped everything you said and nothing else and i still get boot loops. It reboots once every 30 seconds or so and i let it keep rebooting for about 8 minutes. Then i popped the battery and let it try to boot again but i got the same boot loop.
Again, i really do appreciate the help, what should i try next?
Click to expand...
Click to collapse
Are you sure your downloads aren't corrupt somehow?
Sent from the original Swagged Out EVO via Tapatalk 2
-EViL-KoNCEPTz- said:
After flashing the rom wipe cache and dalvik again before reboot
Click to expand...
Click to collapse
Thanks for your help!
The ROM flash goes directly to a reboot so i never get the chance to wipe anything after it installs.
if it loops more than 3 full loops pull battery and reboot to recovery wipe cache and dalvik then under.advanced menu fix permissions(uid mismatches) and the wipe cache and dalvik again and reboot
Click to expand...
Click to collapse
It boot looped again I followed your instructions and i still get the same boot loops.
when wiping before flashing wipe each option a few times in a row until they complete the wipe rather quickly that will ensure they are wiped properly. U can also try reflashing your recovery or changing recoveries to amon RA 2.3 or amon RA style supersonic recovery v3.11 depending on what recovery you are using currently
Click to expand...
Click to collapse
The last time i wiped everything about 4 times in rapid succession and then let the phone sit for about 5 minutes before flashing the ROM. Still got boot loops
For the ROM in question the OD posted a specific version of amon ra recovery, Haus Mod, and said it worked. I downloaded that reovery from
http://forum.xda-developers.com/showthread.php?t=1542036
What can i try next?
swagstr said:
Are you sure your downloads aren't corrupt somehow?
Sent from the original Swagged Out EVO via Tapatalk 2
Click to expand...
Click to collapse
someone else suggested that as well. I did md5 checksums on the file i downloaded and on the file as it sat on the card, and both were identical.
This also happens when i try to flash another newer ROM that requires partitioning the sd card.
What should i try to do next?
TurbineTester said:
someone else suggested that as well. I did md5 checksums on the file i downloaded and on the file as it sat on the card, and both were identical.
This also happens when i try to flash another newer ROM that requires partitioning the sd card.
What should i try to do next?
Click to expand...
Click to collapse
Are you flashing Apps2SD with the ROM?
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
swagstr said:
Are you flashing Apps2SD with the ROM?
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
Click to expand...
Click to collapse
No I'm not. Do i need to?
And how would i do that?
THe thread for the ROM is was trying to flash doesn't mention anything about flashings apps2SD. Is that something that is required for all the newer ROM that require the partitioned SD card?
HTC EVO 4G reboot
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
lordway said:
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
Click to expand...
Click to collapse
All products... And I mean all products will have defects. You got the one in a million. And that sucks, it really does. But you need to realize one defective product does not mean ALL HTC phones are terrible. If I were you, I would talk to Sprint and HTC, it may be a long shot. But if this wasn't your fault, one of them should try to help you fix it.
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
lordway said:
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
Click to expand...
Click to collapse
Same here. But i have had my evo 3D for nearly a year and have had no issues. I only decided to root because all the bloatware that gets added with every system update was killing me, then i found out u can flash ROMs and such. I have a headache from this bootloop issue as well and i was wondering, after you gain S_OFF, HBOOT returns to *** LOCKED *** and i was wondering if that had to be unlocked before flashing, but i havent heard anyone say to do this.
Flashing a ROM and getting stuck on boot is an issue with the ROM usually, flashing a ROM and getting stuck at a black screen that may or may not reboot is usually kernel base mismatch. Flashing a ROM that just plain reboots usually means something is wrong with system boot or one of the caches. Between different ROMs and or ROM bases (stock, modified stock, custom aosp) you need to perform a full system wipe before flashing new rom. I have a guide for the new evo lte but all the relevant knowledge is the same. And sorry for crashing the thread I'm very tired and I thought I was in the lte forums