Related
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Start over
Nand recovery then root again. Find a stable rom. There are tons that float to the top of the forum. I'm on Damage Control 3.5, works great.
Tried to Nand, It error's out and won't restore.
Like I said, DC 3.5 is what gave me the trouble to begin with, at least thats when my troubles started.
My phones gone completely unstable..and at the moment, unusable.
Also, be patient. After a flash, it may take a while for it to load. You seem overly anxious, by your post. I've flashed 30x and probably only bootlooped twice and those were Fresh's 3rd to last rom.
I let it sit there for 10 minutes saying fresh 1000x over a couple times, pretty sure I'm not being impatient.
battery is now dead.
Full wipe
Are you wiping everything? Dalvik wipe, user data wipe, cache wipe? Can you get back to recovery? How did you root?
Yes I can get into recovery, yes I'm wiping everything.
I used Simpleroot to get Root.
Rerun
I would try to re-run the second button in simple root to unlock nand. It doesn't hurt to re-run. You really shouldn't have a problem recovering nand if that process worked the first time. If you can't get that to run, you might want to adb it, but since you simplerooted your phone, you might have to read up on that. Once you take care of nandroid, you are good to go.
Nand is giving me an error that backup cannot be found <even tho I most definitely did Nand backup my stable setup> so IDK what fixing nand would do even if it is broken if it cant find the restore files. erm..
End of the Road
I suggest you do a forum search for more opinions/solutions. You are not the only one on here that has been through this. I did a quick search and found a handful of threads with this exact same topic.
Alanmw86 said:
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Click to expand...
Click to collapse
How did you install a different recovery if your stuck in a boot loop? As for your problem, i had a bootloop before on freshz's older rom, and some of the solutions i had read werent working, i ended up booting into recovery, and rewiping without doing a reinstall of the rom, and it solved my problem, also have read that pulling the battery has gotten some people out of there loops. Hope this helps
I pulled the battery booted into recovery and wiped the rom, flash an alternate, booted up, changed to Amon and started over, was the one time I was able to get it to boot threw, after that same results.. I couldn't explain how it managed to boot up just one time either.
I am so confused! I recently started getting a sprint installer (Com.sprint.ce.updater) force close upon rebooting of the phone. It doesn't appear to be causing any adverse effects of the phone, but it is annoying. Any ideas?
Normally, I use clockworkmod as my recovery of choice, but I was using Amon Ra to wipe cache and dalvik cache and then flash SBC 4.2.2. Unfortunately, I accidentally wiped data instead of cache. Not a big deal, I have several clockworkmod backups.
Reflashed clockworkmod and attempted to restore data. Data restored, but started to get this Com.sprint.ce.updater force close. Tried other data restores, and still force close. Even attempted to do a complete data/system wipe. System wipe resolved issue until data restore occurred. Tried a complete restore using a clockworkmod backup that I know works. Still Com.sprint.ce.updater force close!
I really don't want to have to start all over again with a clean rom. Help?
Sent from my PC36100 using Tapatalk
something seems like its not compatible or was backed up wrong. thats why i dont use clockwork, but i may be wrong. Next time, post in Q&A. thaats the updater for OTA's i believe, and i'm guessing your running sense and not aosp. so possibly somethings corrupted.
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 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 recently got a replacement Evo from Sprint and was able to root and have been running MikG for a while. I haven't been getting the battery life that I'd like to see (I'm a fairly heavy user) so I want to go back to using Deck (which I had great success with in the past). However, when I flash Deck 1.3 I get stuck in a white screen boot loop. I wipe Cache, D-Cache and Data via AmonRa, but no look. I can get back to recovery just fine and restore a nandroid backup just fine.
Any thoughts?
Make sure to wipe everything except your sdcard and battery stats.
Wipe data factory rest, data,system, boot, cache,dalvik cache, android secure and sdext if your partitioned then flash ROM and gapps and see if that works for you.
Sent from my PC36100 using xda premium
Just tried wiping all of those partitions and reflashing with the same result. I even powered off after flashing just to be safe and I let it go through the boot loop about 10 times as well. No luck.
Just out of curiosity, what partition is the kernel stored on? I didn't know if there was anything special that I needed to do to wipe the kernel or not. My guess would be system but I'm not positive what wipes the kernel.
Try a format all zip. Are you partitioned for a2sd? Wipe SD ext.
You can find the format all in the link below
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702