Develop Bugs

Cannot boot my phone

My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.

blakerboy777 said:
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
Click to expand...
Click to collapse
what recovery are you using?
in clock work, try wiping to factory, wipe cache partition, wipe datavik then flash from zip to whatever rom.
in RA do the same but make sure your rom is on the root of your sd.
i had the same issue and did that and it worked fine.

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] [ROM] wajkiui stuck in boot loop.

i ran a titanium backup on my motorola defy whilst running CM7 2.3.7.
the backup was a user apps, systems apps and user data (for those firmiliar with titanium backup)
i then booted into recovery.
> wiped data/factory reset,
> install zip file from sd card
> chose and then flashed WajkIUI 1.10.8
it then booted up and then i then put the phone back into recovery mode and then flashed the google apps 2.3.5 package and that was too successful.
i then booted the phone up and once again it booted up fine.
i then installed titanium backup from the market, then restored all that i'd backed up previously. This once again was successful. I then continued my using my phone as usual. Then i thought too reboot because i was having problems with the theme manager allowing me to change lockscreens, so i rebooted.
It then went into a continuos boot loop and it allows me to go into CWM still and the stock android recovery whilst also allowing me to go into the stock Bootloader.
but i really like the rom but this constant loop annoys me,
how can i fix this without loosing data?...

I think the problem was restoring system apps from a rom to anoter, think you'll have to install your rom again and only restore apps (not sure if restoring data would or not be a problem)

oh, so you suggest i just do a user apps+data back up instead of doing a system backup using CM7,
okay i'll try this out and get back to you thanks .
Sent from my MB525 running CM7.1 2.3.7

wait, but wouldnt i lose all my contacts, text messages, email syncs, wifi settings etc.?
Sent from my MB525 using XDA App

no, this stuff you mentioned is user data, that will come along on a data restore, just try to restore only apps and data, leave system apps off.

WajkIUI doesn't require gapps to be flashed from recovery, so you can skip this step next time, maybe that was the problem (i am not sure, never flashed gapps for WajkIUI)

oh, okay i'll try this method then i'll get back with the results
Sent from my MB525 using XDA App

[Q] Include 'Preload' in Nandroid of Stock 4.1.2?

I noticed in TWRP 2.5 that there is the option to backup/restore 'Preload'. I have also read that the ROMs based on TMo 4.1.2 need preload working properly to boot, unlike previous ROMs. Should that option to include it be checked when backing up and restoring the stock 4.1.2-based ROMs?
I've also noticed that the the Preload size is 0 when backing up other roms in TWRP, so I haven't concerned myself with it. Before TWRP 2.5, I knew nothing of preload (I guess I still don't really know anything). Any thoughts?

Well, I guess I'll find out what to do by trial (and error?). I backed up JMT JB3 (including preload) to flash the Koodo update and run it for a while. I'll restore it later on and see how it boots.

I'm not sure how it works. I'm on JMT3 myself right now. I used ODIN to update to the official release when it came out, and it was doing fine, but I wanted to try some of the custom ROMs out there that are based on it. I was rooted with CWM, and did the usual backup that has worked since I can remember. I don't remember what ROM I tried next, but I didn't like it much, so I restored my back up. It restored correctly, or so I thought. After some use I started getting FC here and there. I couldn't fix it, so I did a factory reset from within the phones settings, not through recovery. As soon as it tried to reboot I kept getting a boot loop. I never was able to get it booted. I was able to boot to recovery, flash cache and wipe scripts that were recommended, and flashed JMT3. All is good now. I know trying a cache wipe or factory reset through CWM won't work since I tried it before, so I didn't even try it for this one.
So long story short I don't know how CWM (or any recovery) handles the preload. All I know is the scripts work to flash clean, or wipe cache/dalvik/fix perms, but I haven't gotten them to work after restoring a back up. My thinking is to be careful until someone figures it out because I don't think backing up will help if I ever need to. I'll have to start fresh each time I want to flash anything.
Here are the scripts I'm talking about: http://forum.xda-developers.com/showthread.php?t=2235141

Thanks for sharing your experience. I have those same scripts handy - had to use them when I flashed JMT3.
If or when I restore, I figure I'll wipe my current preload and restore the preload in my JMT backup, then flash the Infamous cache wipe script (or equivalent function in recovery if TWRP develops something similar). I'll post again to share my results when the time comes.

I ended up wanting to restore old stock 4.0.4 in TWRP 2.5.0.0 recovery. Part of me wanted to do it just so I could test the backup/restore of the preload.
I first backed up my current rom (stock Koodo/Telus 4.1.2) with the cache and preload included. I then wiped data, system, caches and preload, and ran the restore of my old backup. The 4.0.4 booted just fine. Once I was done checking for the info that I wanted, I went back to recovery and wiped all the same stuff (everything except internal and external SD) under advanced wipe options. I then restored my stock Koodo/Telus 4.1.2 backup. It seems to be running fine now although I haven't experimented much to test for any FCs. It didn't seem to have any issues booting at least.
I may have been doing some excessive wiping - I assume restoring a partition also formats it before overwriting it. I'm not even sure I needed to wipe anything to restore 4.0.4, but I didn't want a preload (110 mb) causing issues in a rom that doesn't need it at all. In any case, I know what can be done to avoid issues restoring stock 4.1.2, although I'm still not sure what needs to be done to avoid issues.

You did it exactly right. When using a 4.1.2 Samsung rom, be it custom or stock, and backing up or restoring; the preload folder is just as important as data or system. Basically the point of the preload patition is to get the system partition to fit. By symlinking the apps from preload to system Samsung has saved room and allowed a bigger rom to work on our hardware.
As an example, I am on TWRP 2.4.? and cannot backup preload. When I tried a different rom, then went back to my backup I had FCs like crazy. Because I had used the Infamous wipe script it had wiped the preload folder but there was nothing to restore to it from my backup. I had to reflash the rom I was using (really I just wanted the preload folder installed) and then restore my backup to get it working.
I hope all this makes sense. I'm going to Twrp 2.5 so I can backup my preload folder (when I stop being lazy).
Thanks guys.

[Q] Backup not working with new custom ROM

Hello
last night I tried installing the carbon rom for my Note 2 N7100. (v1.8 Release stable build)
Everything wen't fine but I used titanium backup to backup my files and I also have a backup with CWM. I cleared all data/factory reset and wipe cache plus I installed the 4.2.2 gapps. The OS worked completely fine but when I used titanium backup to restore all apps and system data, It asks to restart which I did and when I restarted my phone the startup time took 25 minutes+ so I knew something wen't wrong. I rebooted into recovery and wiped cache and data reset again but I'm still having issues. I forgot to mention I tried using titanium backup and just restoring system data and not the apps.
I decided to do a restore completely using the CWM backup then I flashed 4.3 gapps to get it back up to date. However, when I tried to startup my phone, gapps isn't working properly and keeps popping up com.process.gapps or something like that has stopped. Usually this means the wrong version of gapps is installed but I've tried reflashing it incase I had a bad flash but that didn't work either.
I'm now using carbon rom without any of my previous system data or apps.
What can I do?
Thanks