Help with CM7 boot looping - EVO 4G Q&A, Help & Troubleshooting

H'okay. So. I had Myn's 2.2 and I wanted to try out something different so I decided on CM7 RC2.
I do a nandroid backup (ofcourse) and then proceed to wipe my cache/factory reset. I then flash CM7 and then do a partial restore of my data for my apps/contacts.
I then proceed to the boot screen and it just loops, over and over again. Without loading my data, CM7 boots just fine... so what in my data is preventing me from being able to boot into CM7?
Thanks in advance!

Boot into recovery, wipe dalvik cache, reboot system.

Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.

r916 said:
Boot into recovery, wipe dalvik cache, reboot system.
Click to expand...
Click to collapse
I have tried this.
totalanonymity said:
Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.
Click to expand...
Click to collapse
What am I supposed to restore to get apps/contacts back then? :3

What you should do is backup your apps with titanium, backup your rom, then wipe factory/data, cache, dalvik cache, flash the rom. on the first boot, it may take an extra couple of minutes. After you sign in, blah blah, open titanium backup, then restore apps with data, NOT system settings.

What you have to do is flash Calkulin's Format All zip. This will delete everything except for the SD card. While still in recovery reflash CM7 and then while STILL in recovery flash the proper Gaaps. You follow these tlstwps I guarantee it will work without a problem. FYI, in terms of restoring your apps with data more than likely it wont work. I have always had trouble restoring AP data when going from Sense to AOSP (CM) Hope this helped.

Related

CM7 Stuck in Bootloop

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

[Q] Camera flash not working with Synergy RC1

I'm sorry if this has been asked before but I tried searching multiple times and couldn't find anything about this. I just recently flashed my phone following the directions from the developer and the only major issue that I know of is the camera flash will not work when taking a picture in low light. I also tried the "flashlight" app and that also won't turn on the light either. Before I try re-flashing the ROM, is there anything I can try before? Thanks for the help...
I can assure you that it is NOT the rom, unless, of course, you have a corrupt download. My camera flashes like it is suppose to and my flashlight turns on and i am currently using the Synergy RC-1 rom. You can try rebooting into recovery, wipe cache & dalvik and then re-flash Synergy atop your current install.
posting & replying via my EVO 4G
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
mexag05 said:
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
Click to expand...
Click to collapse
If you're going to reflash the same Synergy rom then go into recovery, wipe cache & dalvik and then make a nandroid backup of only your data as well as android.secure & sdext partitions. (If you do not have any apps saved on the android.secure [usually paid apps] and/or the sdext partition then disregard including them in the backup). Afterwards, flash the Synergy rom, boot to your homescreen, and then clear all of the default widgets from your homescreens. When you're finished, reboot into recovery, wipe cache & dalvik then restore the backup that you made of your data, android.secure & sdext, if applicable. Whe the restore it complete, boot to your homescreen. You will find them as they were in the previous installation of the rom.

[Q] Problem flashing GingerTiny

Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
prinzmetal6 said:
Just did a clean install of Anthem v2.1 and everything booted up fine. I went into recovery, wiped data, dalvik, and cache, and installed the latest gingertiny kernel. When I reboot from recovery, I get bootloop. What's wrong?
Click to expand...
Click to collapse
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Thank you!
cmlusco said:
Thats because you wiped data. You should only wipe dalvik-cache and the cache partition.
Click to expand...
Click to collapse
Just to add to this. NEVER wipe data after flashing a Sense 3 or Sense 3.5 ROM. Actually even some Sense 2.1 ROMs that is a bad idea.
This is because the way these ROMS are built as the storage in /system cannot hold the whole ROM so they have to build part of it in /data. So wiping data will clear the ROM components as well as the user data. If you have to wipe data, plan to reflash the ROM again. So I say don't wipe data AFTER flashing the ROM unless you plan on reflashing the ROM. You can and will probably need to wipe data before flashing the ROM though.
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
prinzmetal6 said:
Is there a reason why Titanium Backup isn't working? When I try to restore the progress bar just doesn't do anything...I had this problem with my Galaxy Tab and I had to change the app processing mode but is there a different issue?
Click to expand...
Click to collapse
Make sure USB debuggging is on. If it is, I don't know.
I think the problem is that I ran out of internal memory, I have a huge sd card so I think I can solve this problem. Thank you for replying though. I would've posted something on the actual rom page but I don't have enough thumbs up

Having a huge problem with my phone not wiping.

Okay, I was on AOKP M4 and I wanted to upgrade to M5.
So I backup everything and make a backup of my ROM. I wipe the phone and caches and flash M5 with the GAPPS, with the latest CWM touch recovery. When my phone reboots I notice I have the same wallpaper as before and when I unlock my phone my pin is still requested and all of my apps and settings stayed exactly the same. I was never asked to sign into my Google account and the start up/set up screen never came up. I checked to see if I even updated and yes I was on M5. Now the ROM isn't very fast or smooth and I get a lot of force closes and things not working properly.
I tried the whole process again with the CWM non-touch recovery, and again my phone did not fully wipe and all my apps and setting remained exactly the same.
I tried it again with the TWRP touch recovery, and again my phone did not fully wipe and everything was the same and my phone remains kind of slow and I'm getting a lot of force closes.
Why is my phone not fully wiping? What can I do to fix this?
I would really appreciate some help!
you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.
zephiK said:
you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.
Click to expand...
Click to collapse
Yes, that is what I'm doing. I'm wiping factory/data and I'm still having the same problem
Like with the TWRP recovery, I went to wipe, I hit factory reset, then cache, then dalvik cache and then flashed the ROM and GAPPS and all my apps and settings stayed the same. It was like if I had dirty flashed it. I don't understand what's going on.
zephiK said:
you need to wipe factory / data.
wiping cache and dalvik doesn't wipe "/system/etc etc etc"
1. Wipe Factory
2. Wipe Data
3. Wipe Dalvik
***FORMAT /SYSTEM*** (under mount in CWM I believe)
4. Flash ROM
5. Flash Gapps.
6. Flash Kernel
for full wipe.
Click to expand...
Click to collapse
Try that additional step too. May or may not help
Sent from my Galaxy Nexus using XDA
killyouridols said:
Try that additional step too. May or may not help
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
What does that do exactly? Would I have to worry about my media and sd card being wiped?
SubyWill said:
What does that do exactly? Would I have to worry about my media and sd card being wiped?
Click to expand...
Click to collapse
No, all music, pictures ect will still be in place.
Sent from my Galaxy Nexus using XDA
Okay thank you, I guess this time in TWRP I'll do factory reset, cache, dalvik cache, and system and see if it works out
Okay, so I did factory reset, cache, dalvik cache, and format system.
I flashed M5 and GAPPS, rebooted and everything was still the same. My phone did not fully wipe.
I don't understand what's going. I'm so frustrated right now
SubyWill said:
Okay, so I did factory reset, cache, dalvik cache, and format system.
I flashed M5 and GAPPS, rebooted and everything was still the same. My phone did not fully wipe.
I don't understand what's going. I'm so frustrated right now
Click to expand...
Click to collapse
I would do a factory reset, if that doesn`t help flash a stock rom and root your phone again. BTW don`t you have a nandroid backup to revert to
gee2012 said:
I would do a factory reset, if that doesn`t help flash a stock rom and root your phone again. BTW don`t you have a nandroid backup to revert to
Click to expand...
Click to collapse
I have a nandroid backup, but that doesn't solve the problem of my phone not wiping.
I guess I'll unroot my phone and lock the bootloader and re-do everything to see. I don't understand why my phone isn't wiping correctly.
sometimes cwm just doesnt work with factory wipe. i've used it a few times now and sometimes it works and sometimes it doesnt. i have no idea why. you can try doing a factory wipe from the phone settings>backup and reset. ive only done that twice but it worked both times. if that still doesnt work just go with a fresh flash of google images using fastboot.
SubyWill said:
I have a nandroid backup, but that doesn't solve the problem of my phone not wiping.
I guess I'll unroot my phone and lock the bootloader and re-do everything to see. I don't understand why my phone isn't wiping correctly.
Click to expand...
Click to collapse
Init.d folders can only be wiped with a factory reset afaik, or manualy off course. By locking and unlocking the phone you perform a factory reset anyway, so i would flash a stock rom and start fresh. No chance on left files or scripts. You can do it with GNex Toolkit, option 8. Put the downloaded and not extracted .tgz file here C:\Galaxy Nexus ToolKit\put_google_factory_image_here and flash.
Thanks guys, I'll try that!

[Q] How to upgrade rom without data wipe

Hello,
I have an Amazon Kindle Fire with gedeROM v1.7. I love the updates because it makes my device better and better.
But can i update my device without data wipe so i don't have to reinstall and reconfigure the entire device every time. And if I can can someone please tell me how.
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device. But all the data and apps go with the wipe so any help would be awesome!
Thnx for all the help!!
Moaely said:
My usual procedure is download file, data wipe, clear davlik and cache, flash, wipe cache restart and wonderfull a better device.
Click to expand...
Click to collapse
If you're not switching to a different ROM (ie, from CM7 to CM9, or from hashcode to energy...) then you can optionally skip the data wipe (factory reset), which will retain your data and applications...
Alternatively, you may want to take a look at Titanium Backup.
Thnx for the info.
I have been hearing a lot about Titanium Backup, can you give more info about the program.
With TB you can back up any apps on your device. Then when you update a rom just download TB again and then you can restore your apps that you backed up. I love TB and use it on every device that I have rooted. It is a lifesaver!! Ok maybe a time saver anyway!! LOL!!!!
I had a REALLY bad experience from not wiping everything completely. I'd definitely do a backup, like Titanium or MyBackupPro, and wipe it all just to be safe. To many goofy things can happen if you don't.
It really depends on what ROM your flashing. There are rare occasions you can cross flash without issue. Not recommended. Just updating the same ROM so wipe is necessary, unless mentioned by the dev.
If you do wipe than BUYING titanium backup is the way to go. The free version doesn't auto install apps, each needs confirmation.
I can get any ROM on the kf or my gnex but up and running in less than 15 minutes.
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
chris_m128 said:
this is what I have been doing and I am not sure if it's bad to do or not. I make a backup of just my data using twrp, then I wipe the caches and do a factory reset. Then I install the rom, and then restore my data using twrp
Click to expand...
Click to collapse
Restoring your backed up data is akin to not having done "factory reset" in the first place.
You shouldn't encounter any major issues so long as you're flashing newer versions of the same ROM and there hasn't been a large change (for example, switching to linaro).

Categories

Resources