Can i flash from stock vzw, to ics rom, to jb rom, just like nexus? - Verizon Samsung Galaxy S III

hey guys, can i go back and fourth on the s3, with ics and jb and just like flash the rom, like on the nexus? or, wasnt sure how it worked. Looking for best battery life, that maybe be s3 stock, not sure, i know ics nexus stock was best.
Thanks, let me know!

It'll work pretty much exactly the same.. Need to have your bootloader unlocked of course

Well yes and no, there have been some strong debate threads on exact methods of going from ICS to jb. Some devs are calling for a full format of the system (not just data wipe) when flashing certain jb rom's. Which is fine, but a lot of issues arising when trying to restore previous nandroids. Apparently bootlooping has been occurring.
No expert on the issue, I'm comfortable with my synergy rom at this time, but the talk is out there.
Recommend some research into all that's been happening.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

I've done several flashes..um, too many probably, back and forth. I always do it clean, but I've had nothing more than the normal issues everyone else has with certain ROMS. I did lose my IMEI once, I simply flashed a Synergy backup and was back in business.

went from stock, to synergy build r60, to paranoid android without any issues at all.
stock, synergy and paranoid android all ran flawlessly on my phone. I havent had a reboot, or any issue with any of them.
hope youre experience is similiar.
READ READ READ

I always do system wipe and devlik wipe anyway before flashing ROMs. So should be good? There weren't a lot of vzw ROMs but downloaded 3 and will try them. Was hoping to have jb however might try ICS and see which has best bayyeru
Sent from my Galaxy Nexus using Tapatalk 2

guthrien said:
I've done several flashes..um, too many probably, back and forth. I always do it clean, but I've had nothing more than the normal issues everyone else has with certain ROMS. I did lose my IMEI once, I simply flashed a Synergy backup and was back in business.
Click to expand...
Click to collapse
Your imei was saved as part of the regular backup process or you did something else in addition?

bigdad1963 said:
Your imei was saved as part of the regular backup process or you did something else in addition?
Click to expand...
Click to collapse
If you flash the Synergy ROM it will create a backup automatically but the standalone tool is available too, just check the backup threads. Easy as reflashing in recovery.

So just root my phone. Then use what is the best app to unlock? Ezunlock?
Sent from my Galaxy Nexus using Tapatalk 2

thrgk said:
So just root my phone. Then use what is the best app to unlock? Ezunlock?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, Ezunlock work great and very easy

EZ unlock's current updated version is not working correctly. Search the forums for alternatives. Just a heads up
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

Related

Refurbished G2X and Flashing ROMS

I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
jboxer said:
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
Click to expand...
Click to collapse
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
TeldenW said:
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
Click to expand...
Click to collapse
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
jboxer said:
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
Click to expand...
Click to collapse
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
monte666 said:
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm using the NVFlash method.
Best ROM I found with the least problems
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernels...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
adeptustech said:
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
Click to expand...
Click to collapse
Second that but i'm on the GB til video can work good
Sent from my LG-P999 using xda premium
My original g2x could handle oc and UV big time, anything the devs put out . My replacement can only handle kernels with stock voltage and oc is unstable anything past 1.1ghz. So to answer your question, may be a coincidence or may just be bad luck on our part. Remember, not every processor is created equal despite being the same phone. I get tempted to get an additional replacement every once in a while but laziness tells me otherwise.
Sent from my LG-P999 using xda premium
TeldenW said:
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Click to expand...
Click to collapse
Possibly cleaning and wiping everything soo good that you clean the new rom right off your sd card?? lol. just a thought. ive done that when i 1st started flashing roms. or possibly flashing gapps on roms that dont require you to?
edit: i just realized how old this post is. lol
the reason refurbs night have worse luck is because of all the people who send their phones back because of that, they make up a reason to tell Tmobile and get a nice shiny new one. The old one is reset and passes all the "official" stability tests and gets sent out again.
Sent from my LG-P999 using Tapatalk 2

[Q] Rewinding sound while speaking.

Hi, I recently started messing around with my sgs4g and installed a custom rom using the GB Stater Pack and flash the KJ6 AOSP, everything is working flawlessly except that everytime I'm talking to someone I suddenly hear a rewinding-kind of sound and the other person can hear it too, it happened to me using octane rom, stock GB update and AudiophileFTW edition, can someone please help me get rid of that sound it's getting really annoying, I would really appreciate any help given. Thanks in advance
dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.
airfluip1 said:
dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.
Click to expand...
Click to collapse
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted
ajtorres14 said:
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted
Click to expand...
Click to collapse
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?
stephen_w said:
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?
Click to expand...
Click to collapse
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..
ajtorres14 said:
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..
Click to expand...
Click to collapse
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?
If you have the same issues on 2 different devices, you should redownload the roms(cwm and odin), maybe its a download issue i.e. mds5 error
Tell me if that works
Sent from my SGH-T959V using XDA App
As of today I have rooted my phone with different methods, re-downloaded everything, used different versions of Odin, went back to stock, install official GB, it's still doing it, also with the stock Gingerbread leak I noticed that besides the rewinding nose every 4-5 minutes, also the call log doesn't work and while I was watching a movie at work the phone light stayed lit during the whole film... I don't know what to do, is either go back to stock and recharge my phone every 4 hours or go back to kj6 aosp and deal with that annoying sound ..
stephen_w said:
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?
Click to expand...
Click to collapse
Kernel is stock no under nor overclocked, btw what's the modem's role on the galaxy s 4g can this be the issue, I have never changed it but what if I do, can it help in any way, thank for all the help...
The modem is the radio for your phone to communicate with the cellular service. People change the modem file to see if they get better speeds in their area. Check the dev section, there's a whole thread containing just the modem files to flash.
I don't know if it will makea difference but it certainly couldn't hurt to try.
Sent from my SGH-T959V using XDA App

Back to stock..

My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
I think a lot of people recommend the root66 stock..... But I'd try noSympathy's image
Sent from my SCH-I535 using Tapatalk 2
I'm rooting immediately after so whatever is a proven version will make me happy
SGS3 production
They're both rooted so no need to do after. Both are tried and true, noSympathy's is based off the last OTA but some people like to start from scratch so that would be root66.
Sent from my SCH-I535 using Tapatalk 2
I want to get back to unrooted stock.
I can't seem to locate the route66 stock image
SGS3 production
http://forum.xda-developers.com/showthread.php?t=1762204
It's up to you but it's just more work to go unrooted then root yourself. Check the development threat there maybe an un rooted image there
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:36 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1755386
Thought there would be a newer one but here's unrooted...
Sent from my SCH-I535 using Tapatalk 2
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
FormeriPhoney said:
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
Click to expand...
Click to collapse
Flash back to stock then root. Click link in sig.
i tried this......still having the same issue, switched from CM10 back to stock and had issues with my GPS being way off, like by 3300 meters off haha.....so flashed back to stock, still had the issue, so i used the rooted stock image and flashed that and i'm still off by about over 2k meters.....don't use my navigation or maps all that much but when i do need it i'll have a bit of an issue lol
I had issues with my gps for a few days. If was real flaky but got better with synergy 1.5. I have since move to 1.6 with a fresh install and am still okay. Check out a app called gps status. See if you can see any gps satellites. Maybe in that app clear your agps state in tools. Then if that doesn't work try to download gps assistance with the same app in the same settings. Make sure your out side for this stuff with your gps. It's probably not gonna hit ya sitting on the couch.
Sent from my SCH-I535 using Tapatalk 2
FormeriPhoney said:
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
Click to expand...
Click to collapse
I used the stock image from here:
http://samsung-updates.com/device/?id=SCH-I535
and used this method for rooting:
http://forum.xda-developers.com/showthread.php?t=1792342
my gps doesnt work at all
After Odin back to stock, non rooted image my GPS is fixed.
Now on CM10, loving it. Not sure if I'll ever try synergy again bc of that nightmare situation.
I use my gps pretty much all day. I needz it
SGS3 production
New AOKP JB issue with radio
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
douglasf01 said:
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
Click to expand...
Click to collapse
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
still had IMEI
toy028 said:
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
Click to expand...
Click to collapse
Well it turns out I still had my imei present on my phone and even after a factory reset like I did wit kies it still didnt work. Initially I wasnt able to get past the activation screen on the root66 rom, but I was able to with the stock factory image from kies in which case this allowed me to follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1838791
Once I did that my phone rebooted and everything came back as it was never gone, well except for all of my data on the internal sd card, but that is to be expected.
After 2 hours of going through numerous steps I finally found a fix, mind you not the most simple of fixes, but a fix none the less.
I think I am just going to stay stock for awhile like I mentioned and wait for the OTA that comes out in 2014 lol, unless in review of AOSP roms the issues present now are gone after sometime.
Tks
Nice. Tks
Gps works like a champ on beans!
Gps seems to work substantially better on cm10 than on stock....ran the GPS test and i locked onto 14/19 satellites.
Beamed via NFC through the local store to the internet from my SGS3.

[Q] Why does this happen? NFC Related

Ok, so I've discovered something interesting. Being the crack flasher I am, I often flip flop between AOSP, the occasional AOKP and TW roms. Seeing as I have a little 7 year old brother, my mother finds it nice to be able to instantly transfer stuff back and forth when dealing with him thru NFC and WiFi direct, so NFC is a big factor for me, in addition to being able to use Google Wallet. I notice that as long as I stick to AOKP/AOSP, my NFC is fine, but the minute I flash a TW rom and go back to AOKP/AOSP, it instantly breaks NFC functionality completely, regardless of me doing anything else.
For instance:
1) Odin back to stock ICS
2) Flash CM10 or any other AOSP/AOKP rom and check NFC functionality and its able to be toggled
3) Flash TW
4) Immediately flash back to CM10 and NFC will be grayed out and unable to be toggled
The same could be said for doing it this way:
1) Odin back to stock ICS
2) Flash TW
3) Immediately flash CM10/AOKP/AOSP rom and check NFC and it's grayed out and unable to be toggled.
What can be going on in TW that completely snaps NFC functionality so that you can't use it in CM10? All the MD5 checksums are valid and none of them have issues when being flashed, so I know it's not in part to doing anything wrong. Also, the only way to fix this is to flash back to a TW rom OR Odin back to stock if you want it to work in CM10 and stick to strictly that styling of ROM.
Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app
I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.
Bern612 said:
I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.
Click to expand...
Click to collapse
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited
Bern612 said:
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited
Click to expand...
Click to collapse
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No never thought of calling them. I actually thought i could only use verizon. I thinking about just giving it to my son, and getting the note II. My phone is on a business plan and his is on a plan with my wife, so i was going to do it that way.
And sorry digitalsynner85 for stealing your thread
SlimSnoopOS said:
Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.
ddurandSGS3 said:
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.
Click to expand...
Click to collapse
This is the answer, works great.. Thank the man!
Did you know there is a NFC fix zip in the CM10 nightlies discussion? Flash this in recovery after you flash back to CM10 and it should fix NFC.
Props to the person who made this zip (dont have time to look right now, sorry)
Lol I know about odin'ing back to stock and all that, I was being curious as to the technical reasons as to why flashing a touchwiz rom then going back to cm10, even through a restored backup would cause the nfc capabilities to break, that was the purpose of the thread thanks for everyone's input so far
Beamed via NFC through the local store to the internet from my SGS3.
annoyingduck said:
This is the answer, works great.. Thank the man!
Click to expand...
Click to collapse
It doesn't work 4 me. not at all.
my steps
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.Restore my CM10 nandroid
5.try out NFC. Nothing to do. greyed flag.
Tried also those steps:
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.NEW installation CM10
5.try out NFC. Nothing to do. greyed flag.
Any ideas?
Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.
annoyingduck said:
Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.
Click to expand...
Click to collapse
ok. I'm trying not to wipe anything. do u think wiping could be the problem?
Seams to be. Others reporting the same thing

[Q] Noob to flashing needs advice

I've flashed a few roms on my old phone - a moto droid x, and so far have not had any problems, and am currently toying with putting Liquid Smooth on my VZW GS3. I've read a lot of posts, old and new, and I could use some advice. Is there still a need to backup the imeid (?) before flashing a new rom? I am currently running the latest vzw firmware, am rooted and unlocked bootloader. Is this just a matter of flashing from CWM after wiping data/cache/dalvik? Ultimately, I'm fine with my phone the way it is, it works, but I'm a bit bored with it, and would love to be able to play with 4.2.2 instead of being stuck at 4.1.2 until vzw decides to update. At the same time though, I want to make sure to take any and all precautions so as to not hard brick it as I paid nearly full price for it so I could keep my unlimited. Thoughts? Suggestions?
Thanks
backing up imei is just a precaution you can do it or not thats really your choice. I would.
make sure you nandroid
clear data
clear cache
clear dalvik
flash rom
flash gapps
steps i run when flasing AOSP.
good luck.
ddurandSGS3 said:
backing up imei is just a precaution you can do it or not thats really your choice. I would.
make sure you nandroid
clear data
clear cache
clear dalvik
flash rom
flash gapps
steps i run when flasing AOSP.
good luck.
Click to expand...
Click to collapse
Thanks for the reply. Have you by chance used this rom? I'm looking for good battery life - prior to vzw's recent 2 updates, I was getting nearly 2 days on a full charge, but now am lucky to get 15 hours. If I do a nandroid, is there a need to backup the imei, or is that also backed up with the nandroid?
Thanks again
ddog511 said:
Thanks for the reply. Have you by chance used this rom? I'm looking for good battery life - prior to vzw's recent 2 updates, I was getting nearly 2 days on a full charge, but now am lucky to get 15 hours. If I do a nandroid, is there a need to backup the imei, or is that also backed up with the nandroid?
Thanks again
Click to expand...
Click to collapse
i got better battery on touchwiz roms.
beans rom is themed like AOSP and was great. a few otehrs have this theme but i have never tried them.
i liked the options in AOSP roms better so ive stuck with it.
i regularly get 4hrs screen on time. i got 7hrs screen on time with beans build once.
i also use ktoonz kernel everytime wth every rom.
i stick with AOSP for the customization and other options though. just personal preference. best bet is to try a bunch of roms and see what you need out of a rom with options.
i dont know if imei is backed up in nandroids. ive read that synergy rom backs up your imei when flashing but i dont know for sure.
Imei is not backed up in a nandroid.
You should definitely back it up. This phone has a potential to completely drop your imei on a custom rom even without flashing or modding anything, especially AOSP roms. It's very simple to do and saves you a huge headache if you do lose it.
Sent from my SCH-I535 using Tapatalk 2

Categories

Resources