[Q] jpy to jvp and back to jpy again - Galaxy S I9000 General

Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!

CalabiYau said:
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
Click to expand...
Click to collapse
You have to do a clean install. With Odin, pit 512, Re-partition and the 3 files. I advise to wipe data and factory reset before flashing.
You should restore the backup titanium applications, but only the applications carefully restored, not the data. JPY to return to the same but now flashing the JPY. If you have any lagfix enabled is recommended to disable it before doing anything. In Spain we say "better safe than sorry."

But then if i go to jvp I'll loose the chance to go back easily to JPY??
I mean that installing cleanly JPY again.,.......

Hello,
went through this today (from JVP back to CWM backup of JSD, never used repartition, flashing tool = heimdall), ran in some problems as I thought that the Gingerbread bootloaders work for Froyo,too (I think I read that somwhere here at XDA).
1) Tried flashing Froyo kernel (speedmod) only and restored CWM-Backup of JSD after factory reset/cleared cache and dalvik cache -> did not work, booting stopped at SGS logo without progress for a really long time (longer than recreating dalvik cache used to last).
2) Flashed a complete self-made JSD-ROM including bootloaders and then installed CWM backup of last running JSD system (again, after factory reset, dalvik & cache clearing) -> worked fine, no problem for hours now.
Maybe I did something wrong at first try, maybe needed the correct bootloaders - don't know.
Hope this helps you a little bit - recreating running system from CWM *full* backup including apps and settings finally worked for me, data on sdcard and external_sd will not be touched (unless you format internal sdcard which is /sdcard directory).
Edit: Be sure to have a copy of your full CWM backup on your harddisk so in case something goes totally wrong you can restore the backup to your SGS recovery, the backups are saved in /sdcard/clockworkmod/backups/)

Yes, I guess this should work. A clean JPY installation, then CWM and then restore...
By the way, we did you go back to JSD??? JVP was faulty??

No, believe me or not, I somehow "feel better" with JSD, JVP made absolutely no problems here, it felt very fast, stable, without (for me) noticable errors, no battery drain.
Maybe I'll try 2.3.4 again in some weeks as I like experimenting with Linux/Android in general but for now JSD is my choice. Only real advantage (again, for me, maybe you don't need this) of Froyo/JSD is that I can reenable logcat using speedmod recovery tweaks.

I use this as a reliable root back to Froyo from custom roms or gingerbread. Not failed me yet. I keep plenty of backups so touch wood, no fowl ups yet.
http://forum.xda-developers.com/showthread.php?t=1100906

are you using the Stock ROM ?

Related

[Q] Upgrading From EB01 Superclean 2.2 to 2.3 Voodoo Version

So I have been messing around with EB01 for the last few days and I am a newbie. So far everything has gone great. I first flashed SuperClean 2.1 Non-voodoo and the upgraded to Superclean 2.2 non-voodoo. Finally, I got some advice and added voodoo by flashing just the EB01 Voodoo Kernel from jt1134. Everything has worked awesome. Voodoo definitely working, confirmed w/ Quadrant Score of about 1500.
I see that Superclean 2.3 is out for EB01 and I want to try it out. Since I already have voodoo installed w/ Superclean 2.2, what steps do I need to do to safely upgrade? I have done everything right so far and don't want to mess this up.
Here is my best assumption: Download EB01 Superclean 2.3 voodoo version and flash without wiping or diabling lagfix.
My main questions are:
1. Which Superclean version do I flash since I want to stay with voodoo (in other words do you have to flash the voodoo version or is that just being redundant since I already have voodoo intalled?)
2. If I am staying with a similar ROM, do you need to disable lagfix?
3. Can you give me scenarios when I should disable lagfix?
4. I upgraded from SC 2.1 to 2.2 without doing a wipe and it worked great. Is a wipe necessary from 2.2 to 2.3, or did I just get lucky before?
If you are running voodoo you don't want to flash anything but voodoo over it. You do not need to disable lagfix. I would recommend wiping cache to keep wierd little remnants from hanging around. The only time you would need to disable lagfix is if you were going to flash a non-voodoo kernel. Hope that helps.
I think that helps. So it sounds like I should keep flashing the superclean voodoo versions when a new one comes out if I want to upgrade. I should select "wipe data and cache" in ROM Manager before upgrading. I use Titanium Backup to backup my apps. Is there any other way to get back your apps and settings other than using Titanium Backup and running a restore?
Also, I am running the Superdark ROM over the top of Superclean 2.2 voodoo. Would my best option be: flash SuperClean 2.3 while wiping all data and cache. Flash Superdark again. Reinstall all apps and settings.
If you want to stay with voodoo, yes. I don't ever get into Rom Manager anymore. With all of the new themes out with reboot options built in it's just easier to boot straight into recovery and take care of business there. I install my rom/kernel (since thats how Adry's packaging them at this point) then install my theme since the rom over-writes your theme changes, then I wipe the cache partition a couple of times and the dalvik cache a couple of times. Then reboot.
Edit: Sorry I forgot to mention that if you don't do a data wipe then all of you apps and settings usually stay intact. But backups are still a good idea should something go wrong.
I'm watching this thread too.
I had 2.2 and was having issues with it - looking to go up to 2.3 now that the screenshot app is back.
I have just flashed 2.3 voodoo over 2.2 voodoo without wipe, all is working fine.
No issues encountered.
Have you restarted your phone yet? That's when I got all my issues.
brettdacosta said:
Have you restarted your phone yet? That's when I got all my issues.
Click to expand...
Click to collapse
Yes, multiple times, been flashing mods.
I have just flashed 2.2v-2.3v and have not run in to any issues. I don't wipe anything and still have not run into anything weird. On 2.2v I did notice my pics from my camera weren't in my gallery, but 2.3v seemed to fix it.
Same here, I did an upgrade from 2.2 to 2.3 and no issues encountered. i did wipe the cache/dalvik cache but was willing to try it sans full wipe
I backed up just in case although
Mikes30000 said:
I think that helps. So it sounds like I should keep flashing the superclean voodoo versions when a new one comes out if I want to upgrade. I should select "wipe data and cache" in ROM Manager before upgrading. I use Titanium Backup to backup my apps. Is there any other way to get back your apps and settings other than using Titanium Backup and running a restore?
Also, I am running the Superdark ROM over the top of Superclean 2.2 voodoo. Would my best option be: flash SuperClean 2.3 while wiping all data and cache. Flash Superdark again. Reinstall all apps and settings.
Click to expand...
Click to collapse
Whoa now, don't use ROM Manager to flash ROMs in voodoo! Use the red voodoo recovery. You shouldn't have to wipe data to go from 2.2 to 2.3. Just wipe cache and dalvik cache to be safe. I'd just do a nandroid beforehand to ensure you can go backwards if something runs funny.
I was able to go from 2.2 to 2.3. I did however backup and then wipe data, cache, and dalvik. I got rid of a few small issues that I was having in 2.2. Namely, I could connect to certain wifi hotspots and not others. As soon as I installed 2.3, I locked on immediately.
Thanks for the ROM Manager advice. I did all my work through the red cwm. I am going to try a 2.3 to 2.4 update now with just wiping caches.
Do you guys have any advice w/ Titanium Backup? Once I clean installed 2.3, I, like a lot of people noticed that the new market redownloaded almost everything that I had downloaded in the past. Pain in the ass, because I had to uninstall a lot of crap. I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
how do i know if i have voodoo or non voodoo? im on a stock deoxed EB01. do i need to install voodoo kernel before i install a voodoo superclean?
sorry new to this fascinate.
Mikes30000 said:
I was able to go from 2.2 to 2.3. I did however backup and then wipe data, cache, and dalvik. I got rid of a few small issues that I was having in 2.2. Namely, I could connect to certain wifi hotspots and not others. As soon as I installed 2.3, I locked on immediately.
Thanks for the ROM Manager advice. I did all my work through the red cwm. I am going to try a 2.3 to 2.4 update now with just wiping caches.
Do you guys have any advice w/ Titanium Backup? Once I clean installed 2.3, I, like a lot of people noticed that the new market redownloaded almost everything that I had downloaded in the past. Pain in the ass, because I had to uninstall a lot of crap. I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
Click to expand...
Click to collapse
The reason it tries to download everything is the automatic restore function inside settings > privacy. It should be unchecked, and youwon't have to worry with it. Keep back up checked though at least I did. Good luck.
Mikes30000 said:
I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
Click to expand...
Click to collapse
The only thing from system data that I've restored is calendar data and calendar data storage. That has successfully restored my appointments, etc. that were in the stock calendar. I wouldn't load back any system apps, especially when going from eclair to froyo because you'd likely be overwriting newer apps with older ones.
dadsterflip said:
how do i know if i have voodoo or non voodoo? im on a stock deoxed EB01. do i need to install voodoo kernel before i install a voodoo superclean?
Click to expand...
Click to collapse
stock is non-voodoo. the voodoo superclean installs the kernel with it. however I caution you to do your homework about voodoo and how to use it properly before making the jump. You can hose up your phone pretty good if you don't use it right.

[Q] CM-6.1.0-RC1 ----> CM-7.0.0-RC1 ~ Upgrade Steps

Hi all,
This is probably a pretty basic question for you, so please bear with me, and if it is basic, hopefully there is a straightforward answer .
Having settled on the awesome CM-6.1.0-RC1, I haven't looked to change ROM.
However, with CM-7.0.0-RC1 being released, its time to upgrade .
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
I appreciate there is a lot of info in ali ba's dev thread [ [ROM] CyanogenMod experimental builds] however, there is approx 235 pages there, and the OP is a little lite.
Would it be possible to have guide here, as I presume many people will be wanting to follow the same upgrade path.
I am wondering how we can 'save' apps, [i.e. Angry Birds status, web browser installation, general settings/config,] during the upgrade... because I am guessing a full wipe is required and therefore a Nandroid backup won't really help...or will it?
Anyone that can help?
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
c_man said:
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
Click to expand...
Click to collapse
First question should be:
Do we need to wipe when upgrading from CM6.1?
If we need wipe, I suggest you to:
- do a nandroid backup
- backup all apps with titanium backup
- wipe + flash 7.0 RC1
- download and install gapps
- restore apps with titanium backup
If no wipe required:
- do a nandroid backup
- flash 7.0 RC1
Question: does UOT kitchen (for circle mod battery) works with 7.0?
gilliu00_ said:
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/15838-cyanogenmod-7-for-legend-v700-rc1-2152011/
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full ourput.
Please use Pastebin when possible
Skardy said:
First question should be:
Do we need to wipe when upgrading from CM6.1?
Click to expand...
Click to collapse
Yep, true.
Anyone?
Upgrading from earlier version of CyanogenMod 7?
* Perform a NANDroid backup of your current ROM.
* Flash CyanogenMod (your Google Apps will be backed up & restored automatically)
Click to expand...
Click to collapse
So no, you do not need to wipe before upgrading,
The backup is just for security reasons. You never know what could go wrong, so it's good to have a backup in place.
Just flash the new CM 7 and you should be good to go.
^ Mastacheata - thats if you're upgrading from earlier version of CyanogenMod 7
That question we are asking here is what if you're upgrading from CM6.1.
Oh I'm sorry, I misread that the whole time.
Gonna try it now and report back in a few minutes.
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
I'm thinking I may just do a full on Titanium backup, full wipe, then go for CM7.0RC1.
easyonthev said:
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
Click to expand...
Click to collapse
GPS not working in CM7.0 RC1 ??
Do we even have a list of things not working in CM7.0RC1? Again, the OP in the dev thread is a little lite with respect to 'known issue' and similar.
My test was unsuccessful.
I was neither able to install directly over 6.1 nor with prior wipe.
My phone would always end up in a boot loop.
Logcat did tell some Exceptions for unknown permissions.
Detailed explanation will follow in the developer thread.
i accidentally flashed cm7 build 0 over cm6.1 stable before. was able to boot but my phone was laggy & some features were broken, as far as i can remember. so i guess the best path is:
TI backup
complete wipe
flash cm7
TI restore
cliche by now, i know. but it never fails...
As we start the RC phase of CM7, many of you are now taking the leap from CM6 stable to the new RC's.
Some of you may be able to get away with doing this without a wipe; however, most of you will not be that lucky.
Differences in the rom, files system, and even Google Addons will likely throw most of you into boot loops.
Therefore, here is my recommended upgrade path:
1) Nandroid backup your current rom
2) Update your recovery to the latest available (CWR is my choice)
3) Format system via recovery
4) Wipe/Factory reset
5) Flash CM7 then Google addon 1/20
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM and/or Market.
Click to expand...
Click to collapse
Here is what CM Team recommends
Skardy said:
Here is what CM Team recommends
Click to expand...
Click to collapse
Perfect, I shoud've found that myself .
Now its just a question as to whether to go to CM7.0RC2 - lots of people still reporting bugs...

Newbie needs help/info

I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...

[Q] has it happened to u? g2 with CM7

Hello I recently downgraded from stock 2.3.4 and rooted the phone. Now I'm in cm7 but I have noticed a severe problem with the laggn in the system. Clock speeds where tryied at 700mhz made it slow and when is around 1500mhz clockd it gets laggier. I don't no wut to do about this issue would be a shame to go back to stock roms since cm7 got some good goodies but if I cannot find a resolution for this issue I would have to revert back to gingerbread.. comments appreciated
Did you use flash superwipe and wipe data/cache/dalvik cache in recovery before you installed CM7? Any chance you restored data+apps using titanium backup? That can cause problems sometimes.
Also i find 1500mhz for the cpu can be slow/unstable for me, try 1000-1200mhz and see if that helps at all. CM7 is probably the quickest rom i've ever used so you shouldn't be experiencing these problems.
+1 for a wipe and try again. I run at stock speed, not even the base CM slight overclocking, and it is faster than my old stock ROM.
Sent from my Desire Z running CM7.
Ok perhaps on the installation I've done something wrong, in the rom manager there is 3 options telling something about wiping and also backups, can ya tell me a quick safer way to flash the rom clean?
COA4178 said:
Ok perhaps on the installation I've done something wrong, in the rom manager there is 3 options telling something about wiping and also backups, can ya tell me a quick safer way to flash the rom clean?
Click to expand...
Click to collapse
safest way...
PS: don't EVER use ROM manager
1) reboot into recovery
2) go to backup and restore, and backup (you'll have to wait till this is done)
3) wipe data/factory reset
4) go to advanced and wipe dalvik cache
5) go to install from sd card, then go to choose zip from sdcard, and choose the ROM (.zip file) you want to flash, select it, then select yes (you'll have to wait till flashing is done)
6) choose reboot system now (the first button)
thats the safest way... ROM manager just messes things up...
—————
|RIROZIZO|
—————

[Q] Different backups, superusers, and flashing kernels

Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !
Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good:

Categories

Resources