Related
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.
Hello,
I'm trying to Restore one of my backups from recovery and after reboot, the phone stuck on the white HTC screen, It happen to all the backups I have.
It's the first time this is happen, I managed to do that before without problems.
My recovery version is 3.0.1.5 and always has been (I didn't upgrade/downgrade) it ever.
I'm able to install a new fresh ROM, but I'm not able to Recover and this is very important for me.
I read other threads about it but neither are solving my issue.
Please advice.
Thanks!!!
(The backups are Coredroid and RCMixHD both Gingerbread).
I had the same problem and solved it by first flashing the old, clean ROM (in my case RCMix) and after the first successful boot restoring only data and system (in CWM "backup and restore" -> "advanced restore"). And I suppose if you restore system, the backup should be the same ROM as the one you have installed.
After that everything worked fine again...something must be wrong with CWM, seriously...
frosty_ice said:
I had the same problem and solved it by first flashing the old, clean ROM (in my case RCMix) and after the first successful boot restoring only data and system (in CWM "backup and restore" -> "advanced restore"). And I suppose if you restore system, the backup should be the same ROM as the one you have installed.
After that everything worked fine again...something must be wrong with CWM, seriously...
Click to expand...
Click to collapse
yes, but from then, are you able to do Restore as regular, like you did before without any problems ?
Or that only your system is working but your'e still unable to do restores ?
Well I am unable to do a complete restore, but it works when I first install the ROM and afterwards manually restore system and data. So I have got everything set up as if I did a normal restore.
It's almost the same as a regular restore any way, you won't notice any difference.
I will take a look into the CWM backups, maybe I'll find the reason for this bug.
thanks, that's nice, it's not so comfortable, but if I wont have a choice I will do that.
In the meanwhile I prefer fixing this issue, anything can do to fix it ?
(Strange, but my problem has been started since I'm using RCMix, may something in this ROM conflicts with CWM?!)
Quite the same here, I'm using RCMix too. But it might just be a random correlation, unless more people have this problem.
Until it is fixed I will just use my workaround, it is not too much trouble luckily
Oh yeah and I took a look in my backups. On the surface everything seems to be in order....
frosty_ice said:
Quite the same here, I'm using RCMix too. But it might just be a random correlation, unless more people have this problem.
Until it is fixed I will just use my workaround, it is not too much trouble luckily
Oh yeah and I took a look in my backups. On the surface everything seems to be in order....
Click to expand...
Click to collapse
I'm using CM7 and have no problem restoring my Nandroid backup, so IMHO it may be a specific issue with RCMix
Ok guys, problem has been solved by installing the latest recovery version from Rom Manager app. Then restart, wipe and... Restore successfully.
I still suspect the RCMixHD, because the problem has been started since I have installed it, maybe it changed something in the CWM, I'm afraid to reinstall it now , I'm sticking with Coredroid 5.3
I'm making this thread to try and solve issues and problems with cm7 for problems that you can probably solve instead of posting 10 times and making a repeated question in the official thread of cm7 development thread
If you have any issues we can help each other, to start with I got the blue then green light on my first restart, but after wiping data and cache AGAIN (I already did it before installing from zip) it worked!
I had problems with the notification widgets, but after a few restarts it didn't dissapeared. So that problem solved by itself
I currently have the flash notification widget not working (and it works on camera but not on video recording) I don't know if it is a common problem from the beta 3 version (If someone knows I would be thankfull***) but meanwhile you can get the flash to work with this widget https://market.android.com/details?id=com.advback.ledflashlight&feature=search_result
The Wifi is working OK but it seems like the refreshing time of signal is too low (I get close to the wifi router and maybe there are 1min. until the small widget at the top fills up) and viceversa I get away from signal and it is remained full until 1 min or so.
edit:
For Gps small fix you can find in the page 123 this from AkkiandDefy:
1.Search FasterFix in the market and install!
2.Open it and choose your region the
3.Now theprogramm will install the right Config
4.And then install GpsFix and let him search
Don't be afraid..let him search longer(till he tell the right adress). Once fixed he will find it always faster.
Admin or mods if there is any problem with my thread let me know, I'm just trying to help
good Idea
just trying to help hehe my idea is to get the important information in the first post just done the flashing of the test2 for gps going to try right now
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
EDIT: OK, so I tried another data/cache wipe and installing CM7 again as update.zip, but have to use the default bootloader now and it says "signature verification failed". :S
did you instal the nordic version? 3.4.3 11 (the last one) flash this, then install superuser (with superoneclick) afterwards instal the clockwork (I used the same one as you) then wipe data, cache install beta 3, gapps and gps test 2 and reboot it should work
Viridis said:
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
I had the same error - i reflashed the 3.4.3.11 sbf with rsd lite
after that, rooted , instaled clockworkrecovery and booted into recovery mode to instal CM7
After installing CM7, i allowed to boot itself (2init is set on automatic) then just reboot and enter into custom recovery via pressing vol down right after blue notification light appears - frome here you can acces custom recovery and install addons like gapps and gps fix.
Warning - entering from Clockwork recovery after CM7 installed will get you in bootloop and need to reflash the main sbf again.
Click to expand...
Click to collapse
really? I think I did it and it didn't happen that, but anyway my recomendation for those we don't know so much is to install from clockwork the beta, gapps and any fixes (gps etc) at the same time without rebooting so we don't have to use it anymore (in this logical order, 'cause maybe it doesn't mind but maybe it can prevent us from getting any error)
Thanks for the replies everyone.
Right now I've flashed 3.4.3.11 on with RSD Lite, that went fine. I've rooted with Superoneclick and installed the custom recovery app from before, and I can get into Clockwork recovery with that.
Now though when I try to do a wipe it says "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!". I took out my SD card and formatted and partitioned it with 500mb ext, 50mb linux swap and around 1.5GB FAT to see if that would help, but it hasn't. I did this with my PC, however I did use the one on the recovery before that, which was probably a bad idea. I didn't think to much of it since it should have only affected the SD card.
I think now I need to use ADB or something to fix this, I've also unrooted and rooted again. I also tried installing cyanogenmod before the mount errors when only an "app2sd" error was coming up on the wipe, but it didn't actually do anything, it just started up with the stock 2.2 froyo again.
EDIT: I tried just wiping and installing cyanogenmod.zip and gapps.zip anyway, but it just comes reboots with stock blur/froyo. I don't have any "update.zip"s or anything.
try wipe from stock. do: vol down + power and then when the ! appears with the android guy press vol down + vol up
afterwards you will get stuck in the moto logo. get out the battery, put it again and flash the nordic version 3.4.3 11 then enable adb and with superoneclick install root
IMPORTANT: NOW GET OUT ADB AND REBOOT
after reboot install clockwork and get the beta 4 and gapps into the sdcard,
then wipe data and wipe cache
install from zip first beta then gapps (if an error of line X appears and says installation aborted just try again it will work, happened to me several times) and reboot!
Hey, thanks for the thread.
I have a problem with FasterFix. Mine asks for root permission but it just won't load. Remains in black screen and does nothing. GPSFix opens, but don't sync.
Any ideas?
@Quarx
Thank you for the CM7 mod, I'm loving it.
Will post it to the original forum post once I'm able to.
And will buy you a beer
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
mariosanoguera said:
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
Click to expand...
Click to collapse
I hope someone post this on the main thread.
I just applied the *.zip(s) and the am loading in for setup, it seems to be working so far. The boot screen is AWESOME as always... setup seems a bit twitchy but hopefully I'll get it to work here soon. *crossed fingers*
I think Im starting to have the earphone piece problem
Quarx posted another version to the main thread. Downloading now. Seems like it doesn't need to wipe. Lets see...
It seems a little buggy for those who have green lens. I'm waiting with 4.0.
Can I delete this post?
Problems to edit the contacts
Hello.
I've had problems to edit the contacts, in my phone book.
I syncronized my contacs with the Facebook contacts. Have all of then in my contact list, but when i need to add a phone number to the contact, it says that i can't edit Facebook contacts in that device. I need to create a new contact and put the phone number in that new one, and that pisses me cause i will need to have 2 contact from 1 person, duplicating my entire contact list. And all my contat that are in my SIM card don't show in the MOD. I have downgraded and all the contacts now have reapered.
Please, if someone knows how to help, since i was using the Blur, and had all my contacts from Facebook before, editing and merging then when they are duplicated.
It seems like the camera is not THAT working. When I zoom in too much it crashes and I lose access to the camera.
Is Quarx even knowing about this thread?
Edit: I was listening to a song in PowerAmp, opened an YouTube video and all sounds gone, some process forced close and no sound was played until restarted.
Edit2: it seems like that DSPmanager forced close when YouTube opened. Disabled for now.
I've updated to beta4 and the only issue I have is with GPS. Just tested camera, video and flash and all working.
Edit: also issue with video playback... it jumps.
Sent from my MB525 using XDA App
I can't play any videos at all. Guess I'll be back to froyo till this is fixed.
Sent from my MB525 using XDA App
Hi, can anyone help?
I am running the most recent inc-deck ROM, with incredikernel. Yesterday I updated google maps from the market, and today, for the first time in months of using inc-deck, for the first time ever since having rooted my phone months ago, I am having force closes of most apps I try to open.
ROM manager force closes also, so I can't restore the nandroid I have on my SD card from there. I try to boot into Clockworkmod recovery, but all I can get into is the stock "white screen" recovery, not the black and orange clockwork recovery screen.
Is there a way I can flash a nandroid manually, without having to go through clockworkmod? Or does anyone have any other idea of how I can get my phone functional again?
Thank you in advance-
Try getting 4Ext recovery from the market if it is available for your phone. Flash it to recovery and restore your nandroid.
Sent from my T-mobile G2 using xda premium
ahadzi said:
Hi, can anyone help?
I am running the most recent inc-deck ROM, with incredikernel. Yesterday I updated google maps from the market, and today, for the first time in months of using inc-deck, for the first time ever since having rooted my phone months ago, I am having force closes of most apps I try to open.
ROM manager force closes also, so I can't restore the nandroid I have on my SD card from there. I try to boot into Clockworkmod recovery, but all I can get into is the stock "white screen" recovery, not the black and orange clockwork recovery screen.
Is there a way I can flash a nandroid manually, without having to go through clockworkmod? Or does anyone have any other idea of how I can get my phone functional again?
Thank you in advance-
Click to expand...
Click to collapse
Reflash cw recovery thru hboot and then see if it works. My only other thought would be messed up or bad sdcard. Try reformating it fat32, or try a different sd.
so it's fixed now, and in case this helps anyone:
i was trying to install cwm recovery directly on the root of my sdcard by attaching the phone via usb to my computer, and while i was looking around my folders i noticed that "whatsapp" was suddenly working on my phone, whereas when it was malfunctioning i kept getting notifications that whatsapp could not access old messages. so this made me wonder whether rom manager was working. i opened it, and indeed it was working. from there i fixed permissions, and this seems to have fixed the problem.
i don't know why attaching the phone to the computer would have let things work enough for me to get into rom manager, but i'm just grateful to have my phone back.
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