Database Info

CyanogenMOD 10 back up question.

Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!

LeonKnight12 said:
Hi,
I have followed everything in this thread http://forum.xda-developers.com/showthread.php?t=1837863
I have backups nandroid ready and wasn't too sure, if I dont like this build then i could restore back to stock using CWM? or Odin.
I felt that I need to wait for reply to comfirm before flashing this cyanogenMOD 10.
Thanks!
Click to expand...
Click to collapse
IF my memory serves me right, with an unlocked bootloader, you can recover to a TW rom but I think its needs to either have the kernel built into it OR you need to somehow flash to a TW kernel. I say this because I think that if your kernel is still an AOSP one, then the device will not boot up.
some roms already come with a kernel for their rom so I think in most cases, with CWM 6.0.1.x, you could restore a TW nandroid.

If you want to restore a backup of a TouchWiz rom you have then just use the EZ Recovery app to flash the hybrid (CWM/Kexec) recovery...reboot to recovery and restore your nandroid. Simple process!
Once the Dev's building TW roms start using the non-kexec flashing method then you will be able to restore using the normal CWM recovery. Just like you said, you can also use ODIN to restore to stock but it's a pain because you have to root all over again. Just know you have a few options.

Ok thanks everyone!

So good

Fwiw... I've been switching back and forth between Synergy and CM for a couple days now (flashing multiple times) and cwm touch works for synergy but u need new cwm for CM10.
Hope this helps.

[Q] Can't Boot pre-rooted Stock ROM

Hi all,
I got a verizon samsung galaxy s3 about a week ago and immediately flashed the pre-rooted stock ROM and then unlocked bootloader and flashed CM10 with success. I have been using it and enjoy the ROM but want to experiment with the stock (rooted) touchwiz ROM because some of the features seemed nice.
I downloaded the pre-rooted ROM which comes up if you search that term and verizon galaxy s3. I flashed it to my phone using Odin as instructed and it says "pass!" But the phone will not boot past the "Samasung Galaxy S3" splash screen. I tried clearing user data/factory reset from recovery but still does not boot. I was able to restore my previous CM10 backup using recovery, thank god, but still I'm unable to flash the original stock-prerooted ROM and boot. I tried it about 4 times with two different downloads and two different versions of Odin.
Is there a version which I can flash from CWM rather than going through Odin? Any help would be appreciated.
Thanks

There's plenty of stock roms, such as cleanrom, synergy, bean's, which will all give you the stock experience plus some. Did you make a backup after you rooted? That should always be the FIRST thing you do after you root.

iamjackspost said:
There's plenty of stock roms, such as cleanrom, synergy, bean's, which will all give you the stock experience plus some. Did you make a backup after you rooted? That should always be the FIRST thing you do after you root.
Click to expand...
Click to collapse
No I did not unfortunately. Which of those ROMs you mentioned would you recommend? I liked the contact groups, Swype contact to call or text, but not the bloatware.

Why not try CleanROM??

jmorton10 said:
Why not try CleanROM??
Click to expand...
Click to collapse
Thanks y'all. Just downloaded and flashed CleanROM. What a fancy installer.
I made a GOBackup of my apps and messages/calls prior to flashing the new ROM. I can restore that to this different ROM, right?
Thanks again

Flashing TW from 4.2 JB

Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium

nativesmiley said:
Can I flash back to TW from the 2.3.3.0 recovery or would I need to revert back to the previous TWRP.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You come back to TW at your own risk. This where most bricks happen. Best practice is to Odin back to stock and then come back to TW. Luckily you survived CM so far but flashing back to TW could cause a problem. If you don't want to Odin first wipe all partitions till raw and give it a shot.

ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks

Rudy_Ruettiger said:
ok just to clarify....Say I was on Synergy then flashed CM 10.1 now I decided I wanted to come back to Synergy. I would need to Odin back to stock, then flash Synergy? I just couldn't flash Synergy from Cm 10.1? Is this true for CM10 as well? What about flashing my nandroid backup instead of Odin back to stock?
Thanks
Click to expand...
Click to collapse
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:

goldsmitht said:
you do take the risk anytime you flash anything. HOWEVER, i have SYNERGY, MIUI, and CM10.1 along with Liquid (4.2) on my phone. YOU will have problems with finding your files, as 4.2 will create the 0 folder, and it may look like you have lost files. TWRP 2.3.3 does an excellent job of finding back-ups, or just scroll to find the TWRP folder to find your backups.
Gallery also has been known to "lose" pictures. IMO, they are still there, just have to find them. i've actually opened gallery and had it be empty, but a quick close, and then re-open and they show up. Sort of like it has to find them.
YMMV, make backups of everything, and flash away! just know what chances you are setting yourself up for, and be prepared.
edit: AND... i'm not responsible for anything YOU do to your phone... yada yada yada...
just thought i had to throw that out as well...
:cyclops:
Click to expand...
Click to collapse
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.

nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
Stay on TWRP 2.3.3. I've been using TWRP 2.3.3 just fine while flashing multiple Beans JB TW builds. Not sure what issues others had but it works fine for me. Also, if you intend to install 4.2 AOSP in the future then you'll have to update TWRP again anyway if you downgraded it.

nativesmiley said:
so i can use 2.3.3 to flash between TW and CM right? the last time i went back to TW was when i was on 2.3.2.3 and they were say i had to revert back to the recovery before 2.3.2.3. and with that i never had problems flashing between both ROMs. i just want to know if i can flash between TW and CM with 2.3.3 and not revert back to old recoveries.
Click to expand...
Click to collapse
yes, you can use TWRP 2.3.3 to flash old backups made with any version TWRP. with no problems.
however, you can NOT flash old backups made with CWM. different system and will definitely NOT work.
:cyclops:

thank you very much guys! appreciate the input!

what is the proper way to flash between TW and CM (10.1) so I dont get stuck in roaming mode again?

Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app

Nopi45 said:
Yea I am about to do this to correct me if I am wrong please but we are suppose to Odin back to 4.0.4 stock coming from 10.1 then up grade to stock JB from there
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
know that if you go the ODIN route, you will have to re-root and re-unlock your bootloader.
if you have the MOST up to date recover (CWM OR TWRP - I prefer TWRP 2.3.3) and you have a backup made of a TW ROM, and are on 10.1 currently, then just clear dalvic, cache, and restore your TW ROM.
however, if you do not have one, then would suggest factory reset and then clean install of TW.
there are always "chances" of issues, mainly the 0 folder, but i've been flashing back and forth between MIUI bV, Synergy, and CM10.1 and only problem i had was when my mobile network got switched, and i had to go back in and change to RUIM/SIM. and that was the only thing.
just know what you are doing and know where to go to get answers to help fix things that may go wrong.
and, "insert legal comments here"... no one is responsible for what YOU do to YOUR phone, except YOU.
:cyclops:

The only bad experiences I've had going from 4.2 to TW is when I only briefly installed 4.2 but didn't get data working. That left me with no data in TW. So I had to odin back to stock then re-root, unlock bootloader and flash.

will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?

Rudy_Ruettiger said:
will i be able to go from CM 10.1 to AOKP 4.2.1 without any issue?
Click to expand...
Click to collapse
I haven't had a problem going from one 4.2 AOSP rom to another. YMMV tho. Just flash a nandroid before you do it just in case.

Quick question about going from 4.1 to 4.4 (Been gone for a while)

So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol

aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck

dandydon414 said:
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
Click to expand...
Click to collapse
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar

aholeinthewor1d said:
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
Click to expand...
Click to collapse
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.

dandydon414 said:
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
Click to expand...
Click to collapse
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you

aholeinthewor1d said:
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
Click to expand...
Click to collapse
that recovery is fine. i've only used cwm and twrp.. had some problems with philz recovery so I ditched it. basically they're all the same. twrp lets you name your back where as cwm just uses some default name which of course you can change with a file manager. twrp also wipes all 3 (system, cache and dalvik) with one swipe where as cwm requires 3 separate operations. I really haven't done much in recovery other than wiping and flashing. I'm actually on the latest twrp and have had no problems flashing kk roms. keep in mind that you can't backup in cwm and restore it using twrp and vice versa. it's really more a personal preference as far as I'm concerned.

[Q] help upgrading from 4.1 to 4.3/4

ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.

Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app

Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.

yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.

resolved. thanks guys.

Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.

CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.

jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.

CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.

The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.