Develop Bugs

[Q] Evo 4G Doesn't Like to Boot in New ROMs

Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.

When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app

So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!

Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.

totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app

I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.

Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?

RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.

Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).

Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...

Wiping the cache and dalvik most likely isn't necessary but it can never hurt.

RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.

Bootloops on every restart using CM 7.2

Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions

Hpi said:
Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions
Click to expand...
Click to collapse
a no
use titanium backup,
then flash the rom with clockworkmod
flash gapps
wipe data cache
reboot
restore titaniumbackup you made
done
thats all
sent from my Samsung Galaxy Gio using XDA premium

Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.

Hpi said:
Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.
Click to expand...
Click to collapse
You can make a full backup if you want in CWM
Sent from my GT-S5660 using xda premium

Maybe your download was corrupt or whatever... try re-downloading the latest CM7.2.

I doubt that the download was corrupt. I have had this problem for various versions now (CM7.1RC + subsequent patches, CM7.2 + patch). But just to make sure, are the md5 sums of the original files anywhere?
Is there a way I could turn off the boot animation and get debug output on the screen so I can see what's going on when it bootloops?

correct procedure for nandroid restore with data2sd?

hello, just wondering if there is actually an easy way to restore a nandroid backup including ext4 and data2sd?
basically, i am at the moment testing out a whole load of roms to see which one i like best.
but after doing fresh install, and having to reinstall all my user data and all my apps again every time....it takes a while.
is there actually a good practise procedure for completely restoring from a nandroid backup so that the phone will boot up and be exactly the same as it was when the backup was taken?
i ask because when i've tried this before, i always end up with either missing apps, or corrupt apps that result in loads of errors and fc's?
i have tried wiping and then using restore in cwm.
i have also then tried re-flashing data2sd....
always end up with errors.
if not, no big deal, i'm used to re-doing everything from scratch with this phone anyways, just thought that it might make it easier to switch between roms while i;m testing things out :s

Gloris said:
hello, just wondering if there is actually an easy way to restore a nandroid backup including ext4 and data2sd?
basically, i am at the moment testing out a whole load of roms to see which one i like best.
but after doing fresh install, and having to reinstall all my user data and all my apps again every time....it takes a while.
is there actually a good practise procedure for completely restoring from a nandroid backup so that the phone will boot up and be exactly the same as it was when the backup was taken?
i ask because when i've tried this before, i always end up with either missing apps, or corrupt apps that result in loads of errors and fc's?
i have tried wiping and then using restore in cwm.
i have also then tried re-flashing data2sd....
always end up with errors.
if not, no big deal, i'm used to re-doing everything from scratch with this phone anyways, just thought that it might make it easier to switch between roms while i;m testing things out :s
Click to expand...
Click to collapse
Nandroid should backup and restore sd-ext. Try reinstalling your data2sd script straight after the restore.

yes, that's what i mean...it does says it's restores ext4, but when i boot the phone, my apps are not there.
if i resinstall data2sd, they are still missing :s

if you avoid wiping sd-ext(which usually doesn't happen),you wont need to restore your apps again and again......try wiping stuff separately....
Another way is using TWRP touch recovery........it doesn't wipe sd-ext at all,even if you. goose to wipe it(a bug)

yeah, but what happens for me then is that the apps are all visible under my apps list on the phone, but as soon as i go to launch any of them, it brings up an error telling me "this app is not installed on your phone", or similar.
actually given up on the whole 2nd partition thing at the moment.
have been using the latest lewaos since last week, it's amazingly fast, pretty stable compared to most rom's i've used, but as soon as i have to update (which they release weekly updates for this rom), if i have data2sd or link2sd or any of that jazz, i get the same problems as if i had installed the rom fresh (i.e. missing apps, or "appas not installed" problem.
so for now i have no 2nd partition, and i'm just installing as many apps as possible to the sd card, and use some options in titanium backup to move dalvik into rom etc etc.
will see how it works out on friday when the new update is released, i don't hold out much hope though.
new job end of the month, so once i get paid properly i'm getting an iphone4s, 16gb storage, runs fast and smooth, no more messing about, i'll finally have a phone that works as it's supposed to
really genuinely can not wait!

[Q] I Made a Classic Boo Boo... Now I Need Help

I had been unhappy with the way my phone was acting the last couple of weeks, so I decided it was time to flash back to a previous nandroid backup I made a few weeks ago. I stupidly didn't make another backup before flashing back (I thought 'why should I? I don't like the way my phone is setup now, and I want it back the way it was when I made a backup before).
Now I'm stuck with 95% of my apps giving me Unfortunately, (app) Has Stopped. I can't get Ti backup, rom manager, Franco.kernel to work, all Google apps except Play Store don't work. I've wiped everything and tried the recovery again with the same results.
What should I do now?

Fix permissions from CWM recovery

Herman76 said:
Fix permissions from CWM recovery
Click to expand...
Click to collapse
Thank you sooooooo much!!!!

Roms not booting/booting straight into recovery after reboot

As the title suggests my phone refuses to boot properly after a reboot. I flash a new rom and everything works fine but when it comes to powering it off/rebooting it will either hang on the boot animation (the animation will play but nothing else- In the case of Sandvolds ROM) or it will boot, screen will go blank, vibrate and boot again only to go straight into recovery (when using this ROM)
I'm stuck on Sandvold's 0.12 rom (since I did a Nandroid backup of it, that's the only ROM which works. Anything new and it refuses to reboot).
Using 4EXT recovery, format all partitions (except SD card), using SuperWipe script, CM7 hBoot, S-Off.
Any fixes? I've tried a lot of potential fixes (reflashing the rom etc) but every time the same thing happens- the reboot never works. I can leave it for an hour (which I have twice) and it will always just stay on the animation making me have to restore the backup.

i have the similar problem.look: http://forum.xda-developers.com/showthread.php?t=2012808

siavash2death said:
i have the similar problem.look: http://forum.xda-developers.com/showthread.php?t=2012808
Click to expand...
Click to collapse
I was reading that earlier. It seems to be something with ICS and JB. Also reading the latter pages of Sandvold's thread, seems the latest version of the Playstore is creating bootloops and there's means to temporarily fix it using adb but that's all I got.
Don't know if this will help however but I suppose it's worth a shot- http://forum.xda-developers.com/showpost.php?p=34429350&postcount=16767

i don't want to use playstore.because i can't access to that for sanction! can removing the playstore with something like titanium backup solves the problem?

siavash2death said:
i don't want to use playstore.because i can't access to that for sanction! can removing the playstore with something like titanium backup solves the problem?
Click to expand...
Click to collapse
I don't know myself but it may work. Apps may not work however since they call back on the store to see if you've purchased it (or for your phone to re-download the apps after you login with your google account).