Develop Bugs

[Q] New ROM without wiping data & cache

I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!

elziko said:
I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!
Click to expand...
Click to collapse
hm, did you do nandroid backup + titanium backup all data etc?

kmetek said:
hm, did you do nandroid backup + titanium backup all data etc?
Click to expand...
Click to collapse
yes I have a full nandroid backup of my original ROM should anything go wrong. I didn't do a titanium backup though because I thought that not wiping the data & cache would be easier.
If it doesn't work out then I can revert to my nandroid backup and start again, this time WITH a titanium backup.
I'm wondering what sort of problems I should expect?

elziko said:
I'm wondering what sort of problems I should expect?
Click to expand...
Click to collapse
The problem issue of not wiping data is kinda random... Sometimes when you flash a different ROM despite not wiping data it would work and sometimes it wouldnt.
When upgrade your ROM and flash the same ROM but with different version, you can do it without wiping. The impact should be minimum.
When you flash a different ROM that the currently using, there is a chance that not wiping might result in a boot-loop or the ROM not working as it should be.
The main guideline should be to flash any ROM and do a full wipe if you get a boot-loop or find any issue with the ROM. Doing a full wipe when flashing different ROMs is also recomended.

OK, thanks. Since I have all the backups to go back if needs be I think I'll carry on and see if I have any issues.

elziko said:
I have upgraded from my rooted 2.1 to the rooted official HTC 2.2. However to avoid having to reinstall things and setup my phone I did not wipe the data & cache before flashing the ROM.
Is this a particularly bad idea for some reason? Everything seems to work OK... so far!
Click to expand...
Click to collapse
Personally, I think it's a risky.
However, wait until you get problems, then do a full wipe, including Davlik cache and do NOT restore apps from a backup after.

Flashing a Sense ROM after flashing CM6.1.1

I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!

danootz said:
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
Click to expand...
Click to collapse
No sometimes recovery doesn't wipe everything correctly... downlload caulks format all and then flash sense rom. Should fix your problem!!
Sent from my PC36100 using XDA App

!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.

danootz said:
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
Click to expand...
Click to collapse
radios have nothing to do with it. they base roms off new ota so that you can get the benefits of the changes not the radios. You can flash the original radio that came with the evo and it would not affect the rom. The radio controls your signal strength and wimax strength. which is why there is a thread with all the different radios because each phone reacts different to each radio.....

[Q] ROM Flashing crash issue

Hello, first i would like to say i have spent over 10 hours trying to flash a custom ROM on my incredible all of which include searching through endless forums for people with similar issues. current specs are:
hboot: .92
radio: 2.15.00.07.28
clockworkmod: 2.5.1.2
I used unrEVOked 3 to root.
I have tried to flash redemption 2.3, cyanogenmod 6, skyraider 3.5, and the stock incredible 2.2 image which i saw in another thread here. What happens is the roms install fine and boot up. At some point, usually within the first couple minutes they are booted up, the phone restarts and will not boot back into rom. Any help would be appreciated.

Are you doing a complete wipe before installing the rom?
If so try installing the rom from recovery (don't install from Rom Manager), and flash a different kernel. Then reboot and see if the problem still persists.

Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED

baboonsRus said:
Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED
Click to expand...
Click to collapse
Not sure that 3 times is necessary, but I like the analogy.

baboonsRus said:
Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED
Click to expand...
Click to collapse
LOL love that last bit.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.

Thanks guys, i already did wipe dalvik cache, wipe cache, and do a factory wipe each time before installing the various ROMS. none of this fixed the issue. i found a back to stock image, and i took it into verizon and they are sending me a refurb. than its back to root again!

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] Why didn't I have to go through setup again after flashing custom ROM?

So I just flashed Juggernaut 3.69 to my GS2 and after it was all done I was very surprised to see many of the T-Mobile apps still on the phone. I was even more surprised to see that I didn't have to go through the setup process again. It even remembered my Google account info. Have I missed something here? Every other device I have ever flashed completely overrode the stock ROM with the custom ROM, why has that not happened here? I want that T-Mobile crap gone!

It should cone with an app called "bloater" you can remove those apps from there. And did you wipe data/factory reset? If not that is probably why your gmail is still there
There is enough hate in the world. Why can't we all get along here ...?

unlvmike said:
It should cone with an app called "bloater" you can remove those apps from there. And did you wipe data/factory reset? If not that is probably why your gmail is still there
There is enough hate in the world. Why can't we all get along here ...?
Click to expand...
Click to collapse
I followed the instructions to a "t" and they didn't say to wipe data/factory reset. I did see bloater after I posted this. I'll do the factory reset and see what happens. I just don't see how a custom ROM can flash over a stock ROM and the device still retain previous settings. If the stock ROM was truly erased I would expect a clean slate when the custom ROM has finished installing.

Wiping data is a choice, you can if you want, but it's not frowned apron if you don't lol
Sent from my SGH-I727 using xda premium

typoknig said:
I followed the instructions to a "t" and they didn't say to wipe data/factory reset. I did see bloater after I posted this. I'll do the factory reset and see what happens. I just don't see how a custom ROM can flash over a stock ROM and the device still retain previous settings. If the stock ROM was truly erased I would expect a clean slate when the custom ROM has finished installing.
Click to expand...
Click to collapse
Oh, no you don't NEED to factory reset, I'm just saying that is why your account was still there.
There is enough hate in the world. Why can't we all get along here ...?

i don't know about you guys
but every time i upgrade Juggernaut from version to version, i need to do a full wipe, else it just constant FC or reboots
that's the great benefit of Ti, just hit restore all, come back in a few minutes, done!

AllGamer said:
i don't know about you guys
but every time i upgrade Juggernaut from version to version, i need to do a full wipe, else it just constant FC or reboots
that's the great benefit of Ti, just hit restore all, come back in a few minutes, done!
Click to expand...
Click to collapse
The only time I've wiped my phone was when I test a different ROM on my phone. I use juggernaut as my daily and I don't wipe when updating... No FC or reboots here
Sent from my SGH-T989

If I don't wipe, I feel my battery drains faster than it normally would if I did wipe. So, I always wipe just in case