Hi there xda people,
Since all you cool people seem to be doing amazing things with your Galaxy phones, I bet this is an easy question for you.
Quick question: Since I have upgraded my SCH-I535 to Android 4.4.2 am I good to use heimdall to flash (if that is even the right word) ClockworkMod recovery on there. And then use ClockworkMod recovery to install CyanogenMod?
Ok here are the details:
I am trying to put CyanogenMod on my Samsung Galaxy SIII (Verizon) Model SCH-I535. Never done this before but I am not afraid of the command line and I am running Ubuntu on my desktop.
I have been diligently reading through the instructions on the CyanogenMod site because I cannot afford to brick my phone and I am a little confused. Please set me straight.
A few versions back CM unified all Galaxy S III variants into one (d2lte). Instructions for 2dlte say
"Warning: The d2vzw variant cannot follow these installation instructions. For this variant, reference the device-specific installation instructions"
But when I go to the instructions for d2vzw it says:
"you must be a 4.2.2 or older build or this will not work"
According to the specs in "About Phone" I am on 4.4.2
So do you all use heimdall to put a custom recovery on the SCH-I535? If so will ClockworkMod do the trick?
If so what variant of CyanogenMod do I install? d2vzw or d2lte?
And finally, which version number of CM should I use to make sure all the bells and whistles work? CM10, CM11?
There is a similar question to this one on the CyanogenMod forums and no one has answered it.
Thanks to anyone that can give me some reliable advice!
ijustwannanewphone said:
Hi there xda people,
Since all you cool people seem to be doing amazing things with your Galaxy phones, I bet this is an easy question for you.
Quick question: Since I have upgraded my SCH-I535 to Android 4.4.2 am I good to use heimdall to flash (if that is even the right word) ClockworkMod recovery on there. And then use ClockworkMod recovery to install CyanogenMod?
Ok here are the details:
I am trying to put CyanogenMod on my Samsung Galaxy SIII (Verizon) Model SCH-I535. Never done this before but I am not afraid of the command line and I am running Ubuntu on my desktop.
I have been diligently reading through the instructions on the CyanogenMod site because I cannot afford to brick my phone and I am a little confused. Please set me straight.
A few versions back CM unified all Galaxy S III variants into one (d2lte). Instructions for 2dlte say
"Warning: The d2vzw variant cannot follow these installation instructions. For this variant, reference the device-specific installation instructions"
But when I go to the instructions for d2vzw it says:
"you must be a 4.2.2 or older build or this will not work"
According to the specs in "About Phone" I am on 4.4.2
So do you all use heimdall to put a custom recovery on the SCH-I535? If so will ClockworkMod do the trick?
If so what variant of CyanogenMod do I install? d2vzw or d2lte?
And finally, which version number of CM should I use to make sure all the bells and whistles work? CM10, CM11?
There is a similar question to this one on the CyanogenMod forums and no one has answered it.
Thanks to anyone that can give me some reliable advice!
Click to expand...
Click to collapse
Your on a locked bootloader. You cannot run any custom roms. Reverting back to a previous version of Android is no longer an option. The only choice or even chance you have at this point is installing safestrap and running one of the few locked bootloader roms that are available
Sent from my Cataclysm Nexus 5
Thanks!
Hey thanks for the heads up! I would have totally bricked my phone. As I have been searching more I pieced together the fact that for the SCH-i535 if you took the android 4.3 update you got the locked boot loader. Ah well, I guess I will have to spring for a phone that isn't so locked down.
ijustwannanewphone said:
Hey thanks for the heads up! I would have totally bricked my phone. As I have been searching more I pieced together the fact that for the SCH-i535 if you took the android 4.3 update you got the locked boot loader. Ah well, I guess I will have to spring for a phone that isn't so locked down.
Click to expand...
Click to collapse
Keep your eye on Craigslist for an S3 that isn't locked down. Or stick with what you have and pop on Superlite. It's stock, but at least it's debloated. Good luck!
Related
Hey all,
After looking over some of the ROM's available and other information regarding the S3, I'm a little confused on the rooting process. I've rooted my motorola droids and xoom, but this one seems different, no doubt due to 4.1.2, which my S3 is running. I understand that there are 2 sets of ROMs in here, with one set being specifically for Verizon S3 Android Development. Does it matter which I use? I'm liking hyperspeed rom, from what I see it looks good, but most of the root guides/walkthroughs I've seen are from last year. So my question is, what do I need for my unrooted Verizon S3 running stock 4.1.2 to root and install Hyperspeed or other JB Roms. One guide was very detailed but links to Odin and other files didn't work or was an old ICS guide. Need some pointers, been a while since I've done this.
Thanks in advance...
I recall using an app called "EZ Unlock" to root the phone, it was super easy. Once rooted and unlocked I think the next step was installing ClockworkMod or similar recovery. Then do a full nandroid backup. You should probably read the thread on backing up your IMEI as well, I don't know if its still an issue but you should do it just in case.
Now you can start thinking about the two sets of available ROMS.. Basically you have numerous flavors of TouchWiz and AOSP roms. The TouchWiz roms behave more like the stock os on the device and still have the Samsung camera, etc while the AOSP roms are more "Nexus" like. Personally I prefer the AOSP side of things and have settled on CM10.1.
bullitt6996 said:
Hey all,
After looking over some of the ROM's available and other information regarding the S3, I'm a little confused on the rooting process. I've rooted my motorola droids and xoom, but this one seems different, no doubt due to 4.1.2, which my S3 is running. I understand that there are 2 sets of ROMs in here, with one set being specifically for Verizon S3 Android Development. Does it matter which I use? I'm liking hyperspeed rom, from what I see it looks good, but most of the root guides/walkthroughs I've seen are from last year. So my question is, what do I need for my unrooted Verizon S3 running stock 4.1.2 to root and install Hyperspeed or other JB Roms. One guide was very detailed but links to Odin and other files didn't work or was an old ICS guide. Need some pointers, been a while since I've done this.
Thanks in advance...
Click to expand...
Click to collapse
Follow this guide or flash a rooted stock rom using odin.
http://forum.xda-developers.com/showthread.php?t=2046439
CrustyMcLovin said:
I recall using an app called "EZ Unlock" to root the phone, it was super easy. Once rooted and unlocked I think the next step was installing ClockworkMod or similar recovery. Then do a full nandroid backup. You should probably read the thread on backing up your IMEI as well, I don't know if its still an issue but you should do it just in case.
Now you can start thinking about the two sets of available ROMS.. Basically you have numerous flavors of TouchWiz and AOSP roms. The TouchWiz roms behave more like the stock os on the device and still have the Samsung camera, etc while the AOSP roms are more "Nexus" like. Personally I prefer the AOSP side of things and have settled on CM10.1.
Click to expand...
Click to collapse
EZ Unlock is for unlocking the boot loader not for rooting your phone. The IMEI issue normally happens when flashing AOSP ROMs but it has happened when flashing TouchWiz ROMs.
Okay, so my Android 4.3 AT&T Galaxy S4 is rooted (through Kingo) and the only reason I did it in the first place was to flash CyanogenMod or some stock Android variant. Now I'm being told I can't install a custom recovery on my phone for two reasons. 1) AT&T locked the bootloader 2) I'm running Android 4.3.
Now, I'm considering unrooting my phone but even that's unclear and confusing, and it's hard to find people on these forums who are willing to help with these relatively simple (to the non-newbs, of course) things.
Can I flash a custom recovery? Can I run CyanogenMod or any good ROM? If no, will I be able to, ever? If no, how do I unroot? Would it be wise to just wait for the next update from Samsung or AT&T and install it so I automatically unroot?
Much appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
drooskiii said:
Okay, so my Android 4.3 AT&T Galaxy S4 is rooted (through Kingo) and the only reason I did it in the first place was to flash CyanogenMod or some stock Android variant. Now I'm being told I can't install a custom recovery on my phone for two reasons. 1) AT&T locked the bootloader 2) I'm running Android 4.3.
Now, I'm considering unrooting my phone but even that's unclear and confusing, and it's hard to find people on these forums who are willing to help with these relatively simple (to the non-newbs, of course) things.
Can I flash a custom recovery? Can I run CyanogenMod or any good ROM? If no, will I be able to, ever? If no, how do I unroot? Would it be wise to just wait for the next update from Samsung or AT&T and install it so I automatically unroot?
Much appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
im not confirm with it but i read theres a tool called "loki" with it you can unlock your bootloader and run custom firmware. but the rom must provisioned with loki.
search for it and read you in.
hope i could help you a little.
http://www.xda-developers.com/wp-content/uploads/2013/12/Screenshot_2013-12-18-16-20-14-576x1024.png
Hello, I have a Samsung Galaxy S3 I535 (Verizon) and have been done with flashing custom roms for a while now. I figured I would just wait until my contract is up in May go to At&t and get the Nexus 5 (straight off Google's site). I actually got in the mood to put Cyanogenmod on my phone until my contract is finally up. I hear all of this talk about Knox and once you upgrade to 4.3 I535VRUCML1 there is no turning back.
Can someone with plenty of experience confirm that there is absolutely no possible way to get Cyanogenmod on my phone at this point without bricking it. I have been searching all over the web and just can't figure it out. Some people are coming up with guides to flash a hacked version of the VRUCML1 update and then install CWM and Cyanogenmod from there.
So the main question is...
Is it possible at all to ever get CWM / Cyanogenmod back on my S3 that currently has the latest (4.3 I535VRUCML1). I am willing to attempt anything since I am getting rid of the phone in 2 months. Also not selling it afterwards since screen is cracked.
There is no way yet, but maybe soon. A post looked promising a few days ago.
I'll post here if I find something.
Sent from my HTC6525LVW using Tapatalk
I also am very interested in this topic, same build phone and also want to use Cynogenmod
Hi,
Apologies if this has been asked countless times but I've done a quick search and found nothing relating to recovery with the NG8 build.
I have rooted the device but cannot access the stock recovery. The blue writing comes up when I boot but then the device powers down.
I'm in the UK on T-Mobile with the GT-I9505 version, Android 4.4.2, build NG8.
Is there a fix for this? I am contemplating putting a custom recovery on but want to make sure that's not going to brick the device on this particular build.
I've seen a lot of posts about the MF3 version having a locked bootloader but not the NG8 so just want some clarification please.
Many thanks.
Chris
Bud, i think you meant to post this in the Galaxy S 4 forum, this is galaxy s 4g (sgh-t959v)
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
arikinthecity said:
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
Click to expand...
Click to collapse
No it currently cannot run CM13 or any version of CM. Only via safestrap with the 3 options stock, Paul pizz and Superlite
Sent from my Nexus 6
arikinthecity said:
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
Click to expand...
Click to collapse
Hey!
As @ShapesBlue says, if you took the OTA to 4.2.2 then you are locked. HOWEVER, there is a method developed by the typical enterprising XDA member that "Downgrades" the firmware by flashing part of the boot loader/firmware but leaves the crucial bit intact that doesn't brick the phone. Sort of a hybrid firmware flash. I believe it's supposed to open the phone up to flashing TWRP and non-stock custom ROMs. I know someone who used it and it worked on CM12.1 last year, but he also had some trouble after awhile (don't know if that was related to this procedure or not) and made an error later that bricked his phone, permanently it seems.
What isn't mentioned in that OP, at least the last time I looked, was that after doing this procedure, if you flash the firmware recommended in the CM12 and CM13 thread OP's, you will overwrite the partition that is spared in his zip file. Then you will be dead! He does explain exactly what partitions are flashed by telling you how to make the zip file. The updater-script I expect is not touched. Looking at it or in the other files you'll need to do this process will show you what's written where, but they have the partitions names. You can go into the CM12.1 thread OP on XDA for our phone and by clicking on the "d2vzw ROM Extras" link you can find all kinds of stuff, plus a few different partition tables that tell you how your phone is setup. There is other info in the OP itself about this and other topics related to flashing CM as well. (I'm the OP )
WARNING! Don't go into this haphazardly though. I would read through that thread thoroughly and see what if any success people are reporting, and ask questions. You don't want to ruin your phone!
It's in the "Android Development" forum in the root forum for our phone.
Report back on what you end up doing.:good: