Develop Bugs

Some good old noob questions

I was looking to flash to Bakedsnack 1.8 with ROM manager, has anyone done this successfully? Or would you recommend doing it a different way. I ran the backup current ROM for the standard one that came with phone just rooted... but does that save EVERYTHING??

Yes, a nand backup saves EVERYTHING. Think of it like having a clone of your hard drive on your computer. If something goes wrong with your new ROM you restore a nand backup and everything is there.
Backing up through ROM Manager is fine. Make sure you do a complete data wipe and cache clear before flashing your new ROM of choice. If you don't do the data wipe and cache clearing you will likely end up going into a boot loop after flashing the new ROM. If that happens it isn't a big deal. You'll simply have to reflash the ROM, this time remembering to do the data wipe and cache clear.

[Q] How to ensure a clean ROM install

After playing around with several ROM / kernel combinations I am looking to return to the latest stock Rom. I have the PC36IMG file on my SDcard and will be installing via ClockworkMod recovery. What is the proper procedure to ensure the cleanest possible installation? Im a bit scared of all the options in recovery such as all the format options in the partitions menu. Do I need to format everything? Will any files be carried over? I know I will need to re install Clockwork and SU app just want to make sure everything is as clean as possible. Thanks in advance.

cleanest possible? Flash this in recover. It wipes 100% of every every time.
Courtesy of Calk.
If you are just changing kernels, choose wipe catch and delv catch.
Changing to a different rom you need to wipe everything.

Thanks for the tip. I am running a custom kernel so I'd be looking to wipe all of those files as well as the ROM. The ROM I am using is just a re packaged RUU, does the RUU completely wipe all data or will I still need to manually wipe?

You should always manually wipe. I never count on something else to do it for me. When I am changing roms I always wipe data/factory reset, cache and davlick, plus I use calkulin's format all tool that the other responder to your question attached to his post. That way you know nothing will be left over. Before you do all that, remember to make a backup of your current configuration just in case something goes wrong. I have been bailed out by nandroid backup a few times.
Also one more thing, there is a Rom on here that is the latest stock already rooted which would make it much easier on you. You could just wipe and flash and still have SU and all other benefits of having root. Just a suggestion.
I found the stock rom thread. It has both odexed and deodexed version. Odexed will probably boot faster, but deodexed can be themed and/or modded. Heres the link: Stock 3.70 EVO Rooted

I reccommend clearing the cache, and then wiping the dalvik to ensure a clean rom. After that, just flash your rom. As always if you are unsure, you can backup your SD card.

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] Custom Rom Question

Alright so i installed my first ROM on my evo last night. seems like it worked fine everything still works and the ROM is awesome.
http://forum.xda-developers.com/showthread.php?t=1012918
One questions i did have is, if i want to install another one how would i go about that?
Do i just install it like i did the first or do i need to remove the current one and install the new one?
Im sure this is posted somewhere but i wasent able to find the answer im looking for.
Thanks for any input

The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Furthermore, if going to an AOSP ROM, be sure to flash GApps right after you flash your ROM.
As far as kernels go, some people say to do it after you flash your ROM, some day to reboot and then go back into Recovery and do it, some say either way.

Load the new rom zip on your sd card from your pc. Boot to Recovery, make a nandroid backup of your current rom. Then factory reset the phone in Recovery and wipe data, cache and dalvik cache. Wiping them each 2-3x for optimal results.
Then flash the zip for your new rom. Reboot and there it is. If your gonna change kernels or task bars etc, I recommend booting between each zip flashed. Just seems I have less problems this way.
Also get a sms backup app if they are important to you. I use sms backup+. It's free and works great, backs up msgs to gmail. Then u can restore with the app when the new rom is loaded.
Sent from my Warm Z EVO

totalanonymity said:
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Click to expand...
Click to collapse
Awesome thank you very much. Sounds pretty much just like how you install one.
Thanks again

yes do that ^^ nandroid and you can leave the rom on your card if you have enough space and in case you want to reinstall it clean again.

one more question
im thinking about installing another rom and it has multiple downloads some are themes and some widgets and the main ROM. Do I install them 1 at a time or can i do them one after another.

Honestly, preference, with those, I think. As stated before, some people's phones are fine with flashing tons of things at once and some people's phones like to take it nice and slow and have a reboot in between.
Also, make sure the themes you are installing are in flashable zips. There are some out there that aren't and require manually placing them in the SD card or using adb.

http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about

dahlinc said:
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
Click to expand...
Click to collapse
ROMs are flashed in recovery just the same as any other ROM.
All add-ons in his first post are flashable via Recovery, as well.
Get into a habit of wiping cache and Dalvik cache before every flash of anything. (Data/factory when flashing between ROMs, though.)
Also, a nandroid backup before you flash anything would be wise. I stopped doing them as often because they take up quite a bit of memory when you start flashing things left and right! But, it is wise to do so before flashing anything. If anything goes wrong flashing a particular item, you can always restore a backup and start again from a very recent point (i.e. not losing much of what you did) from when there were no issues.
I personally also copy my files to my computer for safekeeping, should something occur with the SD card.

Thats all i need know thank you again!!!!

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?

i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App

KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.

If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed

snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?

Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk

Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.

eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.

Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?

teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.

Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!

I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.

Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.

SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?

when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu

Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk