Database Info

What's the best way to restore after wipe?

I've got JF 1.41 and the apps/caches on my SD card, and would like to apply the update. I have JF Auto Updater, and it found and downloaded - but I got the continuous loop after the update.
When I moved to 1.41, I had the same issue, and basically wiped the phone. I then reinstalled all of the apps one-by-one, which was somewhat painful since I have so many. I did back up my SMS prior to the wipe, but just for archival purposes (not that I needed most of them, but it'd have been nice to restore after the wipe).
For those who wipe their phone before an update - are you doing any backing up/restoring after the update? I know there's a couple of apps that do the backups, but I'm not sure how well they work with the apps on SD, or how well they can be applied after a wipe.
Sorry if this is the wrong forum - I posted here instead of apps because I figured people who find themselves wiping their phones more often would probably be here more than in the app forum.

giantcrazy said:
I've got JF 1.41 and the apps/caches on my SD card, and would like to apply the update. I have JF Auto Updater, and it found and downloaded - but I got the continuous loop after the update.
When I moved to 1.41, I had the same issue, and basically wiped the phone. I then reinstalled all of the apps one-by-one, which was somewhat painful since I have so many. I did back up my SMS prior to the wipe, but just for archival purposes (not that I needed most of them, but it'd have been nice to restore after the wipe).
For those who wipe their phone before an update - are you doing any backing up/restoring after the update? I know there's a couple of apps that do the backups, but I'm not sure how well they work with the apps on SD, or how well they can be applied after a wipe.
Sorry if this is the wrong forum - I posted here instead of apps because I figured people who find themselves wiping their phones more often would probably be here more than in the app forum.
Click to expand...
Click to collapse
the reason is that JFs update negates the link you created to your apps .. therefore your apps are essentially missing
http://forum.xda-developers.com/showthread.php?t=480582
using the modified update to v1.42 you maintain the link and no more flashing android laughing at you .. if you stay on the RC29-RC30-RC33 path you should not need to wipe your phone .. at all

Thanks LR! Didn't realize that - going to give it a quick backup using Nandroid and then follow the instructions on your link!
Edit - worked like a charm! Even better, being able to just slap on an upgrade and run a couple of scripts. Thanks again LR!

IF you do need to restore here is a post that might be able to help you. It might look complicated at first but if you can do LR steps then you should have no trouble following this. It's actually really easy however it'll only help you if you already have a backup of your apps.

Updating JF releases and restoring settings with NAND

So I'm rooted, with a NAND backup on my windows machine of data.img, boot.img and system.img.
I'm currently on JF's RC33 release
baseband ver 62.33.20.08H_1.22.12.29
kernel 2.6.25-01843-gfea26b0
build kila-user 1.1 PLAT-RC33 126986
JF Updater from the Market is telling me that JF RC33 v1.42 is available, so I downloaded it. Here's my questions.
If I update to 1.42, then can I flash those backups to the phone and get my settings and apps back, or will flashing it return me to the previous version?
Can I flash just one of those, like data.img, and get my apps and settings back, or do I have to download everything again?

You shouldn't have to perform a wipe, so your apps and settings will remain intact.

Ok, I just wanted to clarify. I'm not too certain how Android handles itself as an OS on the device, and how integrated the apks are into the framework of the OS.
I must say though, after rooting it was like opening my eyes for the first time. I've learned SO much since I rooted.
Putting the update on now. If it does cause any problems, I guess I can wipe and restore.

if it hangs, or for any reason you have to wipe.. try removing the link of the app folder before you wipe.. when the phone is on the flashing android screen you are still able to perform commands using adb... try to remove the link so the apps would be in your ext2 partition and just link again when u re-flash it.

[Info] Upgraded from JF RC33 to JF 1.51 without wipe! Apps on SD.

Hey all, wanted to report for others who may be looking in the future for this info. I was on JF RC33, I had used Lucids script to help make my apps and cache run off the SD. (Fat32/EXT2)
I went to the market, downloaded JF Rom upgrader. I upgraded to the cupcake radio 1st. (So installed the radio 1st)
After that I went here
http://forum.xda-developers.com/showthread.php?t=480582
Downloaded the US 1.51 JF update.zip (Be sure you delete the radio update.zip 1st after you installed the radio) and put that in the root of my SD card. Then I did the Camera, Home button to turn the G1 into the recovery mode and I applied the update.
After that I booted up, all my apps were STILL linked and working on my G1. The ONLY thing that was glitching was any app trying to use root and the SU Request screen always was blank.
Thanks to pychobj2001 who suggested to turn on "USB Debugging" which did the trick surprisingly. The SU Request screen came up normally as it should and now ALL my apps work correctly. (Providing they have cupcake support)
So in a nutshell, I did not have to wipe anything, kept all my apps, everything is still linked to the SD working perfectly. =D Just wanted to post this info since I know when I was looking over threads after threads, most were talking about wiping 1st and reinstalling 1 by one again.. Im glad I dont have to.
My next task, using Ubuntu to move my 2GB to my 4GB SD card. Should go smooth I hope. =)
Hope this helps someone else too. =)

Thats not surprising since installing the OTA Cupcake update wasn't intended to wipe your data. Upgrading from JF ROM to JF ROM (especially the 1.51 version) shouldn't require a wipe at all.

i think his point is upgrading from JF RC33 to JF 1.51 without wipe while the app2sd is all function well!
this sound great as me too looking this info for so long it kept me from upgrading from my current 1.51 to any other roms...

tbgreen said:
i think his point is upgrading from JF RC33 to JF 1.51 without wipe while the app2sd is all function well!
this sound great as me too looking this info for so long it kept me from upgrading from my current 1.51 to any other roms...
Click to expand...
Click to collapse
Yea, thats about right, for those who were scared like I was to upgrade, thats why this info is here. I did learn alot tho. Basically long as your apps and apps-private is on the SD, If you lose the cache but you have your apps linked. Your apps will be installed, you just need to resetup their configs and so. Clean start but without having to hunt your apps down.
Also I dont know about going from rom to other roms, this was for JF to JF. But long as your apps are on the SD, you should be ok, but you may need to lose your cache and just run the apps again to set things up the way you had them.

12/18/2009 [UNOFFICIAL] v1.3a - CDMA MoDaCo ROM 1.3

THIS ROM HAS NOW BEEN SUPERCEEDED BY MODACO ROM 2.0. I WILL NO LONGER BE PROVIDING UPDATES/SUPPORT FOR THIS ROM.
12/18/09 Update
Here is my most recent version of the updated MoDaCo rom. I have fixed the version display info.
This rom should be safe to upgrade from stock or MoDaCo 1.1 roms.
If you experience force closures the issue is with your dalvik-cache or your boot-cache.
You can clear your dalvik cache from the recovery mode. Do not do a factory wipe. Choose the dalvik-cache wipe/clear.
You can clear your boot-cache from adb as a temporary fix by typing:
rm -r /data/boot-cache
reboot
Changelog:
1.3a:
-rebuilt properties file
-shuffled some apk's around
1.3:
-no longer requires wipe to install/upgrade
-fixed ssh password in about screen
-fixed version info to show correctly
-all market apps should show correctly
-updated to busybox without color codes (this is for the windows users using adb shell)
-upgraded to latest relase of wifi tether
-minor performance tweaks and optimizations
-minor interface tweaks (new lockscreen animations)
1.2c:
fixed issue with protected apps not showing up in market
reverted displayed version # in phone settings (sprint update is still there though)
1.2b:
fixed builld/version info
fixed force close issues for people who upgrade from MoDaCo 1.1
1.2a:
manually patched Sprint Maintenance Release to MoDaCo 1.1 rom.
Get 1.3 here.
Install from the recovery console. No wipe should be necessary!
Please post here if you have problems.

Just flashed from 1.1, getting a bunch of force close messages on boot can't use internet, software version 1.29 so no update, don't know if I should've flashed from stock but thought id try from 1.1.

I'll look into it later right now I need sleep. FYI I updated from a stock patched Rom freshly rooted. You may need to do a wipe for it to work properly. Also i hand copied the individual patched files into the modaco 1.1 to make this work. I am new to this so I do not know how to update the version # by hand editing yet.

getting a bunch of force close messages also,plus it lags pretty much
dunno why but i tried it,thx anyway..time to flash again .

Is the bluetooth audio streaming working?

works great nice job man

i would also like to know if you can play media via bluetooth speakers on this ROM...all ROMs w/ the MR update don't seem to be able to do it, but the Sprint MR update w/ no custom ROM installed can

I got a bunch of force closes when it booted up. I also noticed the browser and some google apps will no longer open and just force close.

mine works perfect

Works fine for me. I did revert back to stock before doing the update and reset my data to be sure.
The build number in the "about" screen is the old number, but things do seem to be updated to the new stuff anyway. To change the build number, I think you need to edit the /system/build.prop file.
Great work!

My force closures have healed themselves! Well, except for the "market" app but I bet I can uninstall/reinstall it.
Obelisk, hopefully this description of my steps helps in finding some answers...
Last night, before I saw obelisk's first few posts regarding his experiment, I had decided to bite the bullet and flash back to the stock Sprint RUU.
First I copied all of my app and app-private folders to my SD card. Then, I did a nandroid backup and then flashed the RUU. I let Sprint download and install the MR. Then I rooted and flashed the recovery image. This is when I found obelisk's posts and decided to try it out. After I flashed his "unofficial" update I booted up and then rebooted (it stated "reboot required" in the menu\settings\about phone\build number after "MoDaCo Custom ROM"). At that point everything was working fine. No force closures, phone was sleeping correctly, I had mute and speaker phone buttons in the call screen, etc...
I decided to copy my apps back, restore my nandroid backup (even though I knew this would undo everything I had just done) and then reflash obelisk's updated modaco again. After doing that I rebooted and got a ton of force close errors. I just closed them all and went to bed!
HERE"S THE WEIRD PART! I woke up this morning and the only force close I'm getting now is with the market app (and ONLY if I try to open it). All my other restored apps are working fine. I am about to go to work but I will play around with this some more. I'm keeping it for now!

I just rebooted and all of the force close errors came back. I guess I'm going to go back to my original pre-MR nandroid backup.

i think the problem is related to the software version number which i haven't figured out how to update yet, so a lot of the apps, and yes there were about 20, that were patched in the maintenance release don't get updated properly until i increment the rom version somehow. i'll mess with it tonight when i get home from work.

did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy

johnsongrantr said:
did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy
Click to expand...
Click to collapse
How do you go about doing a fresh ruu?

I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.

obelisk79 said:
I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.
Click to expand...
Click to collapse
im getting an error 107. the ruu nor htc sync connects to my phone anymore

ABNinja said:
im getting an error 107. the ruu nor htc sync connects to my phone anymore
Click to expand...
Click to collapse
Is your battery fully (or at least mostly) charged?
EDIT: Sorry, I just noticed that's a different error.

Great Rom
I came from a rooted stock Rom wither the Mr update...wiped, flashed...apps2sd, then reboot. Worked flawlessly! I also added the extras from another Rom and everything is running fine. Great work on this..

are you getting error code 107 or 170? google provides no help for error code 107...

Questions from a NOOOOB

I have a bunch of questions, but here is where I'm at.
I had 2.2 stock OTA. I then used bootstrapper to place dr154's Deodex OTA 2.2 onto my phone: http://forum.xda-developers.com/showthread.php?t=794007
Next, I again used bootstrapper to put NexTheme on my phone: http://forum.xda-developers.com/showthread.php?t=749692
Question 1: Are both the deodex OTA and NexTheme now on my phone, or did NexTheme replace the deodex OTA? If I were to load another Theme on, would all 3 coexist or would the other(s) be replaced?
Question 2: If I were to factory reset my phone, what would it revert to? Stock? dr154's deodex? Etc.
Question 3: If vzw released a system update, do I have to do anything to my phone before I receive it?
Now more questions regarding SYSTEM APPS.
Problem 1: MotoTorch was preloaded as a system app, as a part of either Deodex or NexTheme, assuming these coexist. When a new version came out in the market, I could not update to it, because it was a system app. Superuser, same thing, a newer version came out, couldnt get it, "installation unsuccessful".
Problem 2: Additionally, lots of the system apps aren't even recognized as installed by the market. So sometimes you won't even know if an update is available. This was the case with MotoTorch.
So I used the common solution that everyone uses and that I found with a little searching, I loaded adb and mounted /system/app as rw, then removed the apks. Then reinstalled them from the market. Then remounted /system/app as ro.
My question regarding system apps is this:
Question 4: What is the advantage of having an app be a system app?
Question 5: The stock system apps such as Amazon Mp3, or City ID - can I safely remove these? Which ones CANNOT be removed? When I did ls /system/app, there were a huge number.
Lastly, I am new, so I'm sorry if I missed it or could have search it or whatever, but I'm wondering....
Question 6: What is tranquility exactly? I see a lot of themes say they're based of tranquility? If I wanted it, where could i find the newest version? If I install a theme based off tranquility, and then a new version of tranquility comes out, can I reinstall tranquility on my phone, then reinstall the theme and will then the theme be using the newest tranquility?
Question 7: What are the advantages of being blur-less?
Question 8: Is xda the best place to find new themes? Or is there another more centralized site?
Thank you very much for any answers!!

just about everyone of your questions are answered somewhere on the web, but ill give it a shot anyways.
1. Themes only replace certain apks, (this is usually stated in the themers OP) so at times you are most likely going to have a merge of themes, sometimes you will notice it sometimes you wont.
for example, you load a new rom which has apks 1-20. Now you load a theme that has apks 1-6. next you decide to load theme 2 that has apks 1-4. then you load theme 3 with apks 1-2. so even though your main theme is is theme 3, you still have parts of 1 and 2.
2. I would avoid a factory reset, just keep a backup and a copy of the rom your on. And if need be boot to recovery and restore one of those.
3. Yes you would need to revert back to bone stock, best done with an sbf. Google it, that subject is beaten to death.
your using the term system app wrong.
1-2. if the apps were loaded and pushed to system/app they usually wont update. the apks should be in data/app.
when you did the mount/uninstall/install this loaded the apk to the proper data/app location.
4. again wrong terminology. consider system app an app that is either neccesary for phone to run or an apk that MUST be in system/app
5. google "remove droid x bloatware"
6. would take way to long to fully explain that. newest can be found on rom manager or TBH.
7. personal preference, plus less &%$# running in the background.
8. no centralized site, you can find different stuff on different sites. mydroidworld, droid-life, droidforums, droidxforums, etc.

thanks for your answers, but when i ls /system/app i see a lot of useless junk that I am pretty sure aren't required for the system...
the theme gave me mototorch to /system not /data

Here's the BIG question. Did you make your own nandroid back-up before you started this whole process? In other words- did you go into bootstrap recovery and create a back up of your phone first? and then do all this other stuff? Bc that is the easiest and number one way to return your phone to its factory settings. In fact- at this point it may be the only way. With 2.1 we had an SBF file which was essentially the original "rom image" (i come from windows mobile so forgive me). So if you were tinkering around or flashing roms and something happened - you could restore using the SBF to the factory state.
On 2.2 there is no complete SBF. Team Black Hat released a partial SBF they are calling a "system SBF" that can help people that have fubared their phone installing themes and what not. But i don't think it returns the phone to factory settings- I could be wrong since I am a complete newb to android.
So to make a long story even longer- that is why I asked if your remembered to make your own nandroid back up of your phone b4 you did all this stuff- so you have a way to return your phone to its original factory state. If you did not- then don't let it bother you. I have read many posts from seasoned android users that simply got excited and forgot to do it. Eventually - the SBF has to be leaked and we all can sleep a little easier.

I didn't make a nandroid backup. Thanks for letting me know about this, now I know not to try to revert until a true sbf comes out, you might have just saved me from bricking. I guess if an OTA comes out, and we still don't have an SBF, I'll just have to wait for a customized version of that OTA to be released.

Turns out the full SBF was released yesterday by the way:
http://forum.xda-developers.com/showthread.php?t=807903

DroidXChat said:
I didn't make a nandroid backup. Thanks for letting me know about this, now I know not to try to revert until a true sbf comes out, you might have just saved me from bricking. I guess if an OTA comes out, and we still don't have an SBF, I'll just have to wait for a customized version of that OTA to be released.
Click to expand...
Click to collapse
DroidXChat said:
Turns out the full SBF was released yesterday by the way:
http://forum.xda-developers.com/showthread.php?t=807903
Click to expand...
Click to collapse
Yes- this is confirmed lagitamate. So you are good to go. You can now restore to factory by downloading this sbf and using RSDlite (RSDLight? - can't remember).
So- didn't have to wait to long