Ok so most likely I did something wrong, and not Clockwork but I really have no clue how this happened.
Started the day out on my daily driver, CM7 (#39 atm) but got the urge to flash so I figured I'd check out Evervolv. Pretty neat btw, nice work. Anyway, made a nandroid then flashed Evervolv and did some apps, setup etc, flashed an Ubuntu font pack I found in a WarmZ thread which worked fined then decided to go back to CM7 for the time being.
Restored my nandroid and I'm back in CM7, decide I miss the Ubuntu font so I flash that and get bootloops. No problem, restore my nandroid and all is well. Knowing just enough to get myself in trouble I decide to extract the fonts from the Ubuntu font pack, delete CM7 fonts located in /system/fonts, then copy the extracted Ubuntu ones to that location. Had to reboot for some reason and I'm getting bootloops again.
Here's the fun part...restored the same nandroid of #39 as before but now I'm getting bootloops on that. Tried yesterdays #39 nandroid, bootloops. Tried the Evervolv nandroid, bootloops. Every backup I had bootlooped. Btw before these restores I was formatting cache, dalvik, wipe data/factory reset, then went into mounts and wiped boot, system, data, cache. I'm paranoid I guess.
Thinking maybe the sd card was bad I ran a clean install of #39 from another sdcard without issue. Then I got the idea to put my normal sdcard back in and restore my once-was-but-now isn't working nandroid of #39 then flash #39 zip on top of it, and it worked. No more bootloop. Not only that, but now all my other backups are fine again.
So anyone have a clue what happened and how I can avoid it? My guess is I borked something messing with the system/fonts and for some reason the wipes weren't clearing it but like I said I know just enough to be dangerous. Is my wiping ritual wrong? Did I miss something? Any thoughts or ideas?
What version of clockwork were you using out of curiosity?
Sent from my ADR6300 using XDA App
3.0.0.8
HTC Incredible - CM7 - Incredikernel 2.6.37.4 (testA)
I know one of the 3.0 recoveries is known for not wiping completely. That's the only thing I can think of?
Sent from my ADR6300 using XDA App
3.0.0.8 is good far as I know. I suppose it couldn't hurt to downgrade and reflash to be sure (erase recovery checked of course)
HTC Incredible AMOLED - CM7 #39 - Incredikernel 2.6.37.6 (testA)
I think 3.0.0.7 was the one with the problem, I can't remember though. I personally use 2.5.1.2. Not really sure what else would cause that problem though, that's weird.
I was having troubles with 3.0.0.8 and was advised to switch to 3.0.0.7 and have had no problems wiping. I would try that if you think wiping might be the problem.
Related
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
aheavyguy said:
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
Click to expand...
Click to collapse
If this ONLY happens to you when using cyanogenmod roms, then you are not alone. The exact same issue happens to me also ONLY when using CM 6.1 and CM 6.1.1. I have never had this issue with any other rom, both aosp or sense-based, except with CM 6.x roms.
Sent from my HTC EVO running Myn's Warm TwoPointTwo RLS 4 loaded with all the goodies
Yea for some reason these last 2 releases just wont work right on my phone. Which def sucks because I love Cyanogenmod roms. Anyone have any suggestions as to why this might be happening?
Try the following:
Wipe data+cache twice
Flash sense ROM
boot
wipe data+cache twice
verify MD5's
flash CM
flash gapps
U recommend clockwork or ra
What? This title for a thread and no poop jokes? The Internet makes me sad.
Seriously, though...
I'm partial to Clockwork now because I use ROM Manager Pro. AmonRa was the one I always used on my Hero. Both are good. It's yet another "personal preference" thing.
CM6 Issues
I too have had trouble with CM 6.0 and 6.1. I flashed CM6.0 Stable, and could not get apps to install or uninstall after flashing. I tried restoring an earlier Nandroid backup of my previously working HTC Sense ROM, and still could not install/uninstall any apps. I tried clearing Market cache, fixing permissions, wiping cache, Dalvik cache, numerous reboots, and flashing earlier ND backups with no luck. I finally bit the bullet, flashed Stock RUU, and had to reroot to get phone working properly again.
Think I would have learned from above, but being flashaholic that I am, I flashed CM 6.1 when it came out. Exact same probs, and again had to reflash stock RUU and reroot.
No more Cyanogen mod for me. Nothing against CM, and it may work great on some people's EVOs, but its only caused me headaches.
Good news is I'm getting pretty damn proficient rooting phone using old-school manual adb shell/rageagainstthecage/chmod exploit method, having done it three times now (although I hope I don't find myself in this situation again).
YMMV
Me too. Tried with both clockwork and ra...no dice. Problem is, when I went back to warm, it left pieces and now even warm doesn't run correct. I tried wiping twice and clearing the dalvik too. I know it wasn't erasing everything because there would be apps that were already installed. Like it was installing to a partition, though I have never set that up.
...
I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App
shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).
Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.
Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App
Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.
At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App
What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.
I currently have:
Fresh Evo 3.4.0.1
netarchy-toastmod-4.1.9.1 kernel
I would like to go to:
Fresh Evo 3.5.0.1
netarchy-toastmod-4.3.1 (unsure on bfs/cfs and havs/nohavs)
Looking to:
Save battery (Am using superpower and underclocking while unplugged)
OC/UC
Wifi Tether
The only reason i am paranoid is that I am still slightly new to flashing and like asking questions. (it took me a long time to work up the courage and flash what i have.) Also when i updated clockwork (to 2.5.1.2) i saw people having problems flashing new roms etc. so i didnt update anymore.
Backing up is not a problem (plan on using astro and sms backup)
Also should i use clockwork (version?) for fresh evo and RA for toast?
Again just looking for a smooth install. My phone is my baby and only source for internet..
Thank you for taking the time to read, even more if you reply and help.
Surrattster said:
I currently have:
Fresh Evo 3.4.0.1
netarchy-toastmod-4.1.9.1 kernel
I would like to go to:
Fresh Evo 3.5.0.1
netarchy-toastmod-4.3.1 (unsure on bfs/cfs and havs/nohavs)
Looking to:
Save battery (Am using superpower and underclocking while unplugged)
OC/UC
Wifi Tether
The only reason i am paranoid is that I am still slightly new to flashing and like asking questions. (it took me a long time to work up the courage and flash what i have.) Also when i updated clockwork (to 2.5.1.2) i saw people having problems flashing new roms etc. so i didnt update anymore.
Backing up is not a problem (plan on using astro and sms backup)
Also should i use clockwork (version?) for fresh evo and RA for toast?
Again just looking for a smooth install. My phone is my baby and only source for internet..
Thank you for taking the time to read, even more if you reply and help.
Click to expand...
Click to collapse
I never have problems with clockwork but, I always flash from recovery and wipe catche partition and dalvik cache. You also need to upgrade to the current version of clockwork. You current version does not save you wimax keys.
Sent from my PC36100 using XDA App
So youre saying if i update to 2.6.0.1 and ill be fine. Just wipe the cache and all that?
Any suggestion on which kernel version?
Nandroid what you have first. I also have never had problems with clockwork, RA on the other hand on 2 separate occasion caused issue I could not fix!
I forgot to mention nandroid.
I am updateing clockwork now.
I am going to try tonight and hopefully post back if all goes well. Im going with 4.3.1 bfs havs.
***EDIT***
All is well.
I guess i just wanted to hear good feedback.
And i tried clearing the cache, i waited 30-40 minutes. Still was at the White Boot screen.
Restored from nandroid and installed 3.5.0.1 w/o wiping cache. worked within 5 minutes.
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Coreyfuncrusher said:
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Click to expand...
Click to collapse
I think i know what ur doing wrong first flash the rom then reboot then go back to amon ra wipe cache and then flash gapps and if it still doesnt work then do the exact same things but with clockwordmod (which u can both flash from rom manager).
Sent from my PC36100 using XDA Premium App
Followup Question:
Can I restore a Clockwork Backup using Amon RA? Amon wants to check the nandroid folder for backups..and I don't have any nandroid backups (not sure how I didnt do one). can I move a existing clockwork backup from the clockwork folder to the nandroid folder on my SD's root and use that?
Or does anyone have any suggestions on how to flash to clockwork? Now when flashing to CM7 or Fresh I'm getting stuck on the loading screen.. Thanks
So, it looks like the issue is with gapps. When I flash CM7 it works great..once I reboot into recovery, flash gapps, I get the freezing error. I am using version:
gapps-hdpi-20101113-signed.zip
Is this what I should be using?
No there's a newer version you can use let me see if I can find it and get you a link...
Edit: I found the one on my SD card its not the newest but it should work
http://db.tt/YuaCnd9
Sent from my nightly EVO
I am currently running andybonestock ROM as my "stock" ROM. I've wanted to try out the newer Sense ROMs but I keep running into a problem. Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over. Now let's specify what I do every time I try to flash one, and maybe I'm doing something wrong.
My first step is always to backup in recovery. The next thing I do is run the super wipe script, followed by wiping cache, dalvik, and then running super wipe again. Then I choose the update file and update. I reboot my system and let it fully load. I run and complete the setup where it asks you for email and wifi etc. Finally I install and run Titanium. Now maybe this is my problem but I've read many times this is how to do it but correct me if I'm wrong. I selected batch restore and let it restore missing apps with data.
I'd really like to run a ROm I liked but can't deal with the rebooting. Any help would be greatly appreciated. And I've tried searching to no avail.
Thanks
Sent from my Droid Inc2 using Tapatalk
Try to restore apps, but not their data. You're going from sense to sense rom, so it seems like that shouldn't be an issue, but I think you should give it a shot.
but then what's the point of Titanium? if I'm losing the data, it's no different then restoring it via Google
Its either the data or the super wipe scipt seems they cause more problems than they help.
What recovery are you using? I've been running ext4 and the format all except SD and it never gave me any problems. What's with everyone wanting super wipes when you should be able to do everything in whatever recovery your using?
I'm using clockwork and I figured superwipe is more efficient
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Linch89 said:
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Click to expand...
Click to collapse
I appreciate the help but I doubt it's that but ill try it. Anything else
Sent from my Droid Inc2 using Tapatalk
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
nitsuj17 said:
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
Click to expand...
Click to collapse
Yup, I have made that mistake myself.
I've flashed many different sense roms and AOSP roms. I recommend getting 4ext recovery because it has a format partition option that's really easy to do. I format all partitons (except sdcard) and then i wipe data/factory reset. I've never had any issues with flashing roms sense or AOSP. Titanium Backup I only restore data for games, but going from AOSP you must just restore apps.
hakoreh said:
Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over.
Click to expand...
Click to collapse
I have the exact same problem (only with Sense 3.5 ROMs, though), and it happens even when not restoring apps/data.
It's kind of sad, as I was enjoying trying out different ROMs, but no amount of wiping with different recoveries or superwipe have helped.
I half wonder if many of the roms are OCed, and my phone can't handle that, but I've tried flashing different kernels right after the rom, and it still happens.
I must say i don't re-flash to AOSP, but i restore my nandroid backup. However, I do format my partitons and wipe data/reset before restoring. I can try flashing MIUI 1.12.9 and then flashing sense 3.5 rom again. I'll be able to do it tomorrow. I'll let you know.
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
hakoreh said:
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
so I tried a Sense 3.0 ROM and even a Sense 2.1 ROM and still no dice. While the ROM did last a whole day without restarting, it did not hold and went into its usual boot loop again.
I'm really annoyed but want to try something new. I have 4EXT recovery now.
Does anyone know anything else I can try???
TY
OK I've had it. I even tried it without restoring anything from scratch and still eventually get restart errors
Sent from my Droid Inc2 (ICS wanted) with Tapatalk