Develop Bugs

[HELP] Boot loop problems

First off sorry if this is answered in another post, lease kindly direct me to the post if it is =)
I just tried to install a second ROM from ROM Manager. I was running DCU and created a back-up in ClockworkMod before I started then installed the new Fresh ROM successfully. When I tried to go back to my first ROM via the restore point I set up it gets stuck in a boot loop. The 2nd restore point from the Fresh ROM loads up just fine.
Is there anyway to fix the older restore point and get back to DCU or should I just wipe everything and reinstall DCU...
Thanks in advanced!

do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.

Bielinsk said:
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Click to expand...
Click to collapse
thanks, i was able to wipe everything from the original android recovery mode and upload an old nandroid back up but from Clockwork it didnt seem to clear the dalvik cache, when i clicked clear it just went back to the last menu it never said anything in the log and when i loaded up the Clockwork backup it still didnt work :/

[Q] Tips for re-flashing Installed ROM?

I've got a general question that I haven't really found an answer for - although I know the information is there, I'm just not 100% sure how to piece it together. I'm hoping all you experts out there can help provide some guidance.
Using my EVO as an example, I currently have Fresh 3.5.0.1 flashed and have been very happy with it. But, I've been dinkin' around with Titanium Backup and uninstalled a few things (i.e. LiveWallpaper) and generally (probably) made a mess of things.
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
I have ROM Manager installed... is it as simple as creating a NANDROID backup, downloading the ROM again and flashing? Or, should I boot into recovery and clear caches, wipe data/factory reset? I'm not sure if a "wipe data/factory reset" from the CM recovery (3.0.0.5) is the right thing to do.
Guidance would be very helpful and much appreciated. Hopefully, others could use any information provided to do the same with their device if they're unsure how to do the same thing with other ROM's.

i usually like using amon ra recovery instead of clockwork recovery which is the one use by rom manager, if you want to try it rom manager has an option at the bottom that says flash different recovery and says amon ra, if you click it your recovery will become amon ra which i like better for wiping. but to answer your question, yes for a fresh start on a new rom you need to boot into recovery, then NANDROID BACKUP, then wipe 1.cache 2. dalvik cache 3. data and then flash your new rom and you are good to go

If you want to start fresh on the current 'Fresh' ROM then, yes, wipe fully and reflash.
sent from my

Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
Click to expand...
Click to collapse
Just do exactly what you did when you flashed it for the first time. Place zip on sd card, nandroid backup, wipe everything, flash rom.

[Q]How do i flash Whitehawkx's Deodexed ROM?

Well, i already have CWM on my phone and everything, but how do i flash this baby in without having to wipe everything?

13light said:
Well, i already have CWM on my phone and everything, but how do i flash this baby in without having to wipe everything?
Click to expand...
Click to collapse
You have to wipe or you will get stuck in endless bootloop.

Also, use titanium backup to backup and restore all your apps - the market will automatically restore everything for you either way, so you're not losing much other than some game saves or things that weren't on your sdcard...

Or..... backup your custom rom (if not cm7)in rom manager or cwm, then flash the update (after full wipage), boot up, let it sit 10 min. Get to recovery do advanced restore and restore the data only from your backup, reboot and you have all your data and the new update.
DARKSIDE

Nandroid Backup Failure

Allow me to preface this by stating my credentials. I've been rooted and have flashed most every ROM created since day one. I'm no stranger to the processes involved.
Just recently, this started happening. If I create a nandroid backup, then try to restore it, the boot animation just goes forever. It doesn't boot loop, it just keeps going.
This has happened with both CWM3 and CWM5, when trying to restore ICS backups. I've tried flashing the VR Superwipe with no luck either. I've also tried Fixing Permissions.
Has anyone had similar situations that could offer a solution?

Only ICS backups? Did you install a different hboot?

Well I've only tried it with ICS cause I've been running them since January.
I'm using Hboot .92

I personally haven't run into issues with restoring ICS backups using CWM 3.0.0.8. I've done the same process for GB and ICS restore, which is:
1) boot into recovery
2) backup rom
3) flash a new rom then realize I need to restore for some reason
4) boot into recovery then wipe data, format boot, & format system
5) restore and enjoy
I've done this on ICS roms AOKP and CM9 with no issues. I'm not sure how to find a fix if you have used CWM 3 and CWM 5 unsuccessfully.

If you've used the same hboot the whole time that can't be the problem. Try reflashing recovery with ROM Manager and use the "erase recovery before flashing" option.

[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.