Develop Bugs

[Q] What to do after rooting?

So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics

Become a flashaholic like the rest of us. BTW once start you can't stop.
Best advice I can give is to read, read, read and then read some more. Trust me the answers to your questions are in the 1000000s of pages.
Myn's ROM is very good. But I like Caulkins ROM the best with netarchy's 4.2.1 kernel. You don't want to use setCPU with 4.2.1 its not needed.
Just my 2 cents.
And then for some real fun start playing with the CM 6.1 RC1. That's were the fun really begins.
Sent from my PC36100 using XDA App

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
The first thing I did was to start flashing custom ROMS. In the early EVO days, there weren't many choices. Now, there are tons of good options out there, so get to flashin'! You'll also get lots of good ideas hanging out in the themes and mods forum. Stroll around in the "post your screens" thread and you'll be blown away by what some folks have accomplished.
Just my thoughts, of course, I suspect you'll get lots of other suggestions.

yea unfortunately lots of these terms are like a foreign langauge to me =\
after looking up the process of installing roms i see lots of people are saying do a nandroid back up and then copying the rom, radio/WIMAX/PRI/NV updates and kernel
the definitions/translations for that?

Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app

jacoballen22 said:
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
Using a custom ROM (or kernel) or boot animation is done through "flashing." Flashing is done via Recovery which can be accessed by the steps listed in a post above. I use the Amon Ra recovery and there are directions how to isntall this elsewhere on the site. I copy the ROM (or kernel or boot anim) to the root of my SD Card, boot into recovery, nandroid backup, wipe caches, wipe data, then I can specify an option to boot from zip on sdcard. (don't remember if it's high-level menu item or not) Anyway, find a Recovery you like (Clockwork or Amon Ra) and there will be specific directions on everything you can do on that Recovery's thread.
This is really a condensed version and there's way better and more thorough advice in Development and Q & A forums in stickies. I highly recommend reading those.

Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah

I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app

jacoballen22 said:
I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Hopefully you didn't "just" wipe battery stats - there's a process;
It should be done as follows (copied/summarized from the cyanogen wiki found here);
Battery recalibration
1. Charge the phone to full battery; let it keep charging until the battery says it is fully charged. Do not just wait until the light is green, it isn't always fully charged, causing a lot of inaccuracies. (You can check by going to: Settings -> About Phone -> Status -> Battery Level = Full.)
2. Wipe battery stats with Amon_Ra or ClockworkMod recoveries.
NOTE: To have the most accurate of battery stats, reboot the phone immediately after wiping the battery stats and wait for it to boot completely to the desktop. Once your entire boot is done and you have full access to the phone, go ahead and pull the charger and continue with this troubleshooter.
1. Do not charge the phone until after draining the battery completely, resulting in it automatically shutting off.
2. Recharge the phone completely and then use as you normally would.

I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector

6uPMAH said:
Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.
Click to expand...
Click to collapse
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?

Brutal-Force said:
I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector
Click to expand...
Click to collapse
good looks! the terms are IMO the most important thing to get a hold of

R1pTheJacka said:
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?
Click to expand...
Click to collapse
Is Nandroid back up the same that Titanium pro back up does?
fachadick said:
Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah
Click to expand...
Click to collapse
How do you do this?
fachadick said:
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Click to expand...
Click to collapse
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!

phillip623 said:
Is Nandroid back up the same that Titanium pro back up does?
How do you do this?
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!
Click to expand...
Click to collapse
Nandroid isn't the same thing as titanium, think of nandroid as an image, sort of like a disk image or a windows restore point. Once restored, it will take you back to exactly where you were at the time of the backup.
The numbers that you see in Rom Manager represent the recovery version. You currently have clockworkmod version 2.5.0.1 installed.
It's been spelled out above, and elsewhere through the forums, but I'm bored and I want to clean up this post anyway (I tried that new 8whatever keyboard again - still hate it. And before I cleaned it up, this post was three paragraphs of broken english), so here are some basic steps spelled out on what to do immediately after rooting, along with some terms.
The first thing you want to do once rooted is go into rom manager, and towards the bottom, hit the option that says "Flash Alternate Recovery". Once you do this, you'll notice at the top where it used to say Current Recovery: ClockworkMod 2.5.0.1 it will now say Current Recovery: Ra Recovery 1.8.0.
Now close out Rom Manager, and turn off the phone. Turn it back on while pressing down on the volume. The screen with the skateboarding Andy's will show up - this is the hboot screen. Among other things, this screen will tell you the version of hboot you're running, and whether you're S-ON or S-OFF. There may be a few different options listed here, but we're only interested in the one that says Recovery.
Select Recovery. The phone will reboot, and you should end up on a screen with green text. At the top it will say Android System Recovery, and all the way at the bottom, it will say Build : RA-evo-v1.8.0 From here select Backup/Restore. There are a few options, but note the two important ones - Nand backup, and Nand restore. Select Nand backup. It will ask if you're sure, so say yes. It will take awhile and the bottom of the screen will fill with dots. When it's done select Return then Reboot System Now. Congratulations, You just performed your first Nand Backup using Amon Ra recovery.
When you can, mount your phone as a drive, and go into folder inside the nandroid folder on your sdcard. You'll see a folder with today's date. Copy it somewhere safe on your computer. If you're interested, you can look in that folder and note the wimax.img file - this is where you're backing up the infamous RSA Keys (I'm not explaining what that is here, just know that you REALLY want to have this backed up, and kept somewhere safe). once the copying is done, unmount as a drive, and disconnect from your computer. Congratulations, now it's playtime.
Use either Titaniaum Backup or MyBackup Pro to back up all of your apps and data. Mybackup Pro will also backup call logs and text messages and things like that - I'm pretty sure Titanium does also, but I'm not sure. Your contacts should be backed up to google for easy restoration later.
Head over to the dev section and find a ROM that appeals to you. You can go with completely stock rooted if you want (which is essentially where you are now, but stock rooted would have the latest OTA updates when they come out), or stock with some tweaks to Sense, or non Sense at all (the most popular of these is CM, which rebuilds Froyo from the ground up.) Sense refers the stock launcher called Rosie, as well as some buried functionality in the phone - for example the mail, calendar, and dialer apps look and act different between Fresh and CM roms. Sense is a UI developed by HTC to go over what is commonly referred to as vanilla android/AOSP. AOSP stands for Android Open Source Project and is what google released on the n1, CM is an AOSP rom. Also, you're looking for a Deodexed rom (as opposed to odexed) so you can theme it later if you want.
Once you find a rom you like, download it to the root of your sd card (you may want to download it on your computer and move it to your sdcard). Refer to the above to get back into recovery, but this time instead of selecting Backup/Restore, select Wipe. Select Wipe data/factory Reset and let it do its things, then select Wipe cache, and let it do it's thing, then select Wipe Dalvic-cache, and let it do it's thing. What you've just done is erased all of the personal and superfluous data that was in the phone - you want to make sure that when you load the new rom, you're loading it on an empty slate, and that there's nothing of your old data left that could possibly corrupt something in the new rom. Some people say to wipe all of those options 2 or even 3 times each - I don't buy that though. Also, don't worry about the other wipe options you had there. Not needed now.
So once you've wiped, hit return, and select Flash zip from sdcard. It will pull up a list of .zip files found on the root of your sdcard. select the rom you just downloaded, and let it install. This may take a while. Don't freak. Once it's done, select Reboot system now. This will take a while too, maybe even a few minutes. Don't freak. Once it eventually boots up, restore all of your stuff with either Titanium or MyBackup Pro. Congratulations, You just flashed your first rom.
Now head over to the themes and apps section. Find a theme that interests you. Make sure its compatible with your rom (either sense or cm) and download it. Flash this the same way you flashed your rom, but you may or may not need to wipe first. Always refer to the op of those threads for specific instructions.
Finally and most importantly - head over to the thread in my sig and find a new font you like. All the cool kids are doing it. When you find one you like, copy it to your sdcard and flash it the same way you've been flashing everything else. You don't need to wipe anything for those though.
Tips;
1: never forget to wipe. As a rule, when flashing roms, you'll be wiping what people refer to as all three - that means wipe data/factory reset, wipe cache, and wipe dalvic cache. When flashing kernels or themes, you'll generally just be wiping cache and dalvic cache. Again though, always refer to the instructions in the op in which you found whatever it is your flashing.
2: if you'll be flashing both themes and roms, and possibly kernels, never flash in the same recovery session. So rom first, full reboot, then kernel, full reboot, then theme, full reboot. In that order, wiping and rewiping as needed.
3: give you're rom at least a few days before you give up on it, most need time to settle into your phone so to speak, and need a few battery cycles to get to peak performance, which brings up to
4: You should wipe your battery stats whenever you flash a new rom. Remember you saw that option under Wipe back in recovery? Well now you get to use it. I posed the link and process above in the thread.
5: At this point most people use Amon Ra instead of clockworkmod because there seems to be uncertainty as to weather or not clockworkmod correctly wipes. ONLY Amon Ra backs up the wimax.img, clockwork does not.
6: rom manager is a graphical front end for clockworkmod. A lot of people still use it to flash, becasue it's so easy to use, it can be used to download roms directly in the app, and doesn't require the zip file to be on the root of the sdcard - it van be anywhere on the card. Don't forget though, you can download the rom through the app if you want, but still switch to amon ra to flash it.
7: you cannot restore a nand backup you make with amon ra with clockwork, and you cannot restore a nand backup you make with clockwork with amonra.
8: on the off chance you need to change your hboot version for any reason, you can only restore nand backups with the same hboot version that they were backed up with. NOTE, were talking about hboot here, not recovery.
Damn, that was a lot of of text. Sorry about that.

i would recommend reading this thread: http://forum.xda-developers.com/showthread.php?t=790427
i have only been in the android world for about 3 months now, and was able to root and flash custom roms with ease within a few weeks of getting my evo. its really not hard at all once you understand the process.
as far as what rom to flash, that depends on the user. different rom have different features. if i were you, i would recommend reading the specs on each rom before flashing. some may have features missing, such as 4G, full camera support and such. And usually all that info is provided in the thread along with the rom. so, pay attention to that.
as for me, the goal for rooting was to do certain things that was only possible with root. such as, Nandroid backup, ShootMe, Wifi Tether and to disable some of the Sprint apps. so, i am using a stocked rooted rom. it is what it says. the same stock rom as the factory but rooted.
a lot of ppl use various custom roms to get better battery life. battery life on stock roms have improved quiet a bit lately. at least in the past 3 months, i have noticed a big improvement. hope this helps answer some questions.
and remember to always do a nandroid backup. i also use My Backup Pro to backup my Call Logs, SMS & MMS.

few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?

ok, so titanium pro will backup everything, even how your homescreen is set up.
the nandroid is for if there is a problem, or if you want to go back. ALWAYS HAVE AT LEAST ONE BACKUP MADE WITH AMON AT ALL TIMES OR YOU COULD PERMANENTLY LOSE 4G (FOREVER, NO FIX EVER)
rom manager can control clockwork recovery while booted up in a touch screen interface. it removes the need to use the annoying volume keys. doesnt work with amon.
i would highly reccomend amon to you. it is just that much better, but doesnt work with rom manager. volume keys arent that hard anyways. use amon.
ONCE AGAIN, ALWAYS HAVE AT LEAST ONE AMON BAKCUP AT ALL TIMES, AND ALWAYS BACKUP BEFORE DOING ANYTHING EVEN SLIGHTLY CONSIDERED MODDING. SERIOUSLY, TAKE 4 MINUTES OUT OF YOUR DAY TO WATCH DOTS APPEAR, AND SAVE YOURSELF 200 DOLLARS OR HOURS OF SETTING STUFF BACK UP. SERIOUSLY. DO IT.

Thanks for the detailed and informative post! This should be in the question and answer thread. I'm finally able to change my font and onto ROMS. I'll reply back once I'm on a normal keyboard.

R1pTheJacka said:
few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?
Click to expand...
Click to collapse
1. all your contacts are backup-ed on your google account. when you sign on to the google account after you flash a new rom, the contacts will be automatically downloaded to the phone. so, no further work needed to be done there. i use My Backup Pro to backup my SMS/MMS and Call logs. I think it is very similar to Titanium. Basically you use the program to backup the stuff you need onto your SD Card. Then, once you have flashed your new rom, you install Titanium or the My Backup Pro and use the Restore feature to restore what you need. As far as Apps go, I found that it was better to use App Brain, since that keeps a log of all the apps install on the phone, its usually a breeze to re-install all of them through that.
2. Amon RA & Clockwork perform the same function. you use either to flash custom roms, perform nandroid backups, etc. so, once you root your phone, you will need to install one of these.
3. ROM Manager.. does what the name says it does. you can change the rom on your phone using that utility app. But i think the Amon Ra/Clockwork Recovery method is the preferred way of changing out roms.

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

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] Working with a Used Phone

Hello all,
Introduction:
My name is Dev, and I have purchased a phone from Craigslist about a year ago. I used to use Windows Mobile phones. I had no problems with them. I have used the T-mobile MDA, Wing, and Touch Pro 2. They have been good phones for me, until recently. I have always wanted a faster phone and the Touch Pro 2 seemed to be quick enough for me. Nope. It slowed down just like the others. My brother is younger than me, and he has been attracted to the Android market since the T-mobile G1. I never got an opportunity to enter this operating system market. I am very tech savvy however, and it has merely been a case of me not wanting to "change." However, I am past that and I want to contribute to the Android community. My first Android phone is the T-mobile myTouch 3G Slide. (I like sliding phones in case you haven't noticed. I must have the physical keyboard. I text a lot.) I bought it used from Craigslist, and it seemed to work fine then. The previous owner was nice enough to clear all the data off of it, and give it to me fresh. I have been using it since.
Leading into my problem/question:
Lately, however, it has been slowing down too. I want to reset it to a clean slate. I know how to do it. It is in the menus. However, I do not like how this phone has been modified. Why would you modify a phone? I have never had to do this with my Windows phones. There has never been a need to flash any roms or anything. They had updates which were simple to use. Plug the USB into the computer and follow the simple steps. Make sure it doesn't shut off during flash. Simple. I've done this plenty of times with printers, motherboards, CD-ROMs, and all other flashable devices. I understand how big of a risk this is. If the flash doesn't complete (or is the wrong rom), then the device will not work again. Unless, you J-TAG the device and flash it again correctly. But, that requires a lot of work, and a wiring schematic to figure out where the J-TAG ports are. I have learned this information from back in the day when I used to do dish testing. You would flash roms to satellite TV boxes and experiment with new encryption technologies for satellite TV. That being said, I am terrified of flashing phones, because I would have no idea where to look for J-TAG ports for phones, if I mess something up. So, in conclusion, my experience in flashing has been for testing purposes only.
Problem/Question:
How do I figure out what the status of my phone is? It says Cyanogen Mod on start up. My brother tells me this is a very good rom. Who decided that though? Is it a bad idea to go back to stock T-mobile rom? I've always had this thought nagging me to try it and see why people go through all this headache of S-OFF and rooting phones. However, if I go back to the stock rom, will I be able to gain access to the phone's internal memory again? I don't like the idea of losing the S-OFF and rooting privileges the previous owner worked so hard to do. I would like to flash the latest T-mobile rom to the device, but how do I know if it will mess up everything and clash with some code leftover from the modified rom of Cyanogen Mod? Also, how do I backup all my stuff? I want to keep all my setting for the programs I have downloaded from the Google Market. I want to keep my contacts and notes. I want to keep my text messages and MMS messages. I am one of those idiots who keeps all his text messages and MMS messages archived. I go back through the messages from time to time for retrieval of important information I may have spoken about with someone in the past. I know this is a loaded post. I am sorry. If anyone is willing or able to help me, then please pick any point in this post and we'll go from there. This was just an outline of everything so you guys can help me find a starting point.
What I Know About the Phone:
T-Mobile myTouch 3G Slide
Android 2.3.3
Baseband 47.63.35.21U_7.15.35.16
Kernel 2.6.32.17-cyanogenmod-g501281a [email protected] #1
CPU ARMv6-compatible process rev 5 (c6l)
Mod CyanogenMod-7.0.0-Slide
Build GRI40
I believe it is S-OFF and it is rooted. I would like a procedure to verify though. Please.
Memory Card:
Memory card has a lot of folders and stuff on it from which I have no idea. Some of it says nervous stuff like ".android_secure" "clockworkmod" "2111.zip" "signed_Froyo_Slide_Radio.zip" "gapps-gb-20110120-signed.zip" "update.zip" "update-cm-7.0.0-Slide-signed" and "Android" I like it when my memory card is clean with nothing but a few folders like "Pictures" "Videos" "Movies" "Data" "Programs" "Software" "Music" and other general stuff like that. I like this so I can use the memory card elsewhere and know where everything is. Basically, I want to know if I can delete everything without shooting myself in the foot. How do I find out what each .apk is for? Will a stock T-mobile rom come with all the stock backgrounds, contact pictures, and all the other stock goodies? I feel like some of those were on the SD card too.
Things I like:
Speed. I like things to be fast. Utilitarian. I don't want any fancy effects, typically. I like everything simple. For example, my desktops are all using the Classic Windows Theme, and all fade in / fade out have been disabled. I want my phone to be the same way. Nothing I don't need. Minimalistic. I don't like to keep many programs running at once. This was something I liked about the Windows phones. I could click in the upper right hand corner and it would present a list of running programs. I could close specific ones that I did not want to run in the background. Android doesn't seem to have a feature like this, but it does seem like they close if they are not being displayed on the screen.
WIFI
How do I fix the WIFI in this phone? It seems like the radio drivers are wrong are outdated. It keeps dropping the connection immediately after the phone connects to a wireless network. I noticed a thread, but I cannot post to it. I wanted to ask how I would apply this patch to my phone without having a rom or anything. I thought maybe I could boot the phone into the recovery mode, and install the radio drivers maybe? I don't know what I am doing though, and want some guidance.
http://forum.xda-developers.com/showthread.php?t=1177650
And, why does the GPS take so long to get a fix?
Moderators/Thanks
I am very sorry to anyone and everyone whom I may offend in this post. If all my questions are answered somewhere else, please direct me to the correct area. I have been searching and researching for so long and I don't seem to be getting anywhere. I gave up about two months ago, and now I am back again trying to fix this phone. Please do not be mad at me for pestering you guys with annoying questions from new users like me. I know you guys are tired of answering these questions over and over again. Please. Just give me a little guidance. Thank you so much for any and all help. I really truly appreciate this. Android seems to be a very good operating system, and I am looking forward to all your posts.
P.S.
Sorry about the length of this post. It is my first time.

Test
Testing to see if I get notification of replies.

Well, for starters, welcome to the myTouch 3G Slide fora, second, yes, your brother is right, you are running the best ROM available at the moment, but your running an older version of itif you like, i can link you to an updated version of the ROM or i can point you to the "Android Development" section of the forum for the myTouch Slide and you can pick one your self, if you need any help with your device, feel free to PM me or reply to this thread at any time, seeing as how iI am one of the last people who actually still support this device for ROMs, i would reccomend my "TeamFreedom LeWaOS" ROM, but im still working out some kinks in it, for now, i will give you the opportunity to update to the latest version of "CyanogenMOD 7.2":
Download the ROM (has fix for WiFi i believe): http://download.cyanogenmod.com/get/RC/update-cm-7.2.0-RC2-espresso-signed.zip
Download for the latest 2.3.3 GAPPS: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Also, here is how to FLASH these ROMs:
Pre-requsite: PLACE "update-cm-7.2.0-RC2-espresso-signed.zip" and "gapps-gb-20110828-signed.zip" on the root of your sdcard
1: Hold the power button on your phone
2: Tap "Reboot"
3: Tap "Recovery"
4: when in "Recovery" use the Volume +/- keys to move and the trackpad to select "Wipe data/factory reset" then select "yes" if necessary
4a: select "Install zip from sdcard"
5: then select "choose zip from sdcard"
6: select "update-cm-7.2.0-RC2-espresso-signed.zip"
7: When finished select "reboot system now"
8: again, reboot into recovery
9: flash "gapps-gb-20110828-signed.zip"
10: reboot system, and enjoy your updated phone, this process overall is the same for all android phones, and for all ROMs

Thank You
Thanks. I will try the new CyanogenMod rom.

Dealing with the performance of your phone, how many SMS/MMS msgs do you have currently? I noticed you said you dont like deleting them. Thing is, if you have a lot of msgs it can significantly impact your phones performance. Obviously it impacts the messaging app but in my experience it can affect the whole system. This may not be the case on CM ROMS but i have noticed it on stock. (i dont use CM much, prefer Sense).
Also u can try overclocking. I like NoFrills app from market. Its free and allows u to select your i/o scheduler and governor.
For backups, hands down Titanium Backup is the best if u ask me (and many others).
Hope this helps a little.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Update on CM7
Hey, guys.
So, I've updated to CM 7.2.0. Since then, I've been having problems with the touch screen and the phone app. If I use the directional pad, I can highlight the phone app, but when I click on it, it crashes. Also, the touch screen is unresponsive all the time. Sometimes, I will get lucky and when I reboot it, I will get access to the touch screen again. I am wondering if maybe I didn't update the drivers for the touch screen or the phone radio or something. I have a hunch that the phone app is crashing and lagging the whole system, so the touch screen isn't working because of that. When the touch screen does work, the phone app is also working. I am thinking of just flashing the phone with HTC's stock rom and then rooting and s-off it all over again, because I think the previous owner didn't do something right. I want to know if I can just flash the stock rom without any consequences. And, also will I be able to get it rooted and s-offed again? I'm hoping that by flashing the stock rom, I can test my touch screen and phone app with confidence. Maybe the phone app is sending commands for a newer firmware revision, and mine isn't updated to that version yet. Not sure how this works really. Anyways, any help would be greatly appreciated. Thanks in advance.

Suggestion. Re-flash the rom, but in recovery go into advanced, wipe dalvik cache. Hit back, now in mounts and storage. Wipe the following, boot, system, hit back wipe/factory reset, wipe cache. Flash rom, then gapps. Reboot. You should be good to go. Hope this helps.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Oh and to check for S-off reboot to bootloader when holding power, or while phone is off power on while holding vol down. Should say alfarev s-off or unlocked.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

Ran into a wall
Alright, guys.
So, I ran into a wall. It is now completely unresponsive to the touch screen. I had recently flashed it, and I am trying to do what you had suggested, Dvarl. The problem is that I cannot touch the android logo so I can continue onto the Rom Manager where I can flash and reboot into recovery. If I try to go into the recovery by holding the down arrow and power button, then clicking on "Recovery," I get the red triangle logo. It has always been this way. Lastly, my phone is not s-offed. Thanks for helping me out with that. lol Any ideas on how to flash without the Rom Manager recovery flash?
Edit: I think I have found the problem. I think my digitizer is going out. I am going to maybe purchase a new one and see if it fixes the touching problem. I'll keep you guys posted. Thanks for all your help thus far!

[Q] Unusual problem installing Jellytime R16

I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?

I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?

Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.

I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).

foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.

Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."

bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?

Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.

Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.

if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?

Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.

Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.

Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app