4.4 and 4.3 Sticky Roll-Up Thead
Do not use EZ-Unlock! You will instantly hard brick your phone and you will have to go through a painstaking hardbrick repair or get a JTAG repair.
Thread Purpose
The official 4.3 touchwiz update brought significant changes to the Verizon Galaxy S3. Once you took the update, the phone is completely stuck on the 4.3 or 4.4 base and any attempt to change the rom (unless using safestrap) will brick the device. Previous rooting and unlocking methods will no longer work on the update and will cause bricks if used. However, there are great threads going around regarding the update but are fragmented all over the device sections. We need a place to have all the information available on the new update. The old sticky roll-up thread should be used for anyone who still has an unlocked bootloader, meaning you did not take the 4.3 or 4.4 OTA update or your phone did not come with it pre-installed.
If you have 4.4 NE1 baseband you are unable to go back to any version of the 4.3 updates. Running any kind of 4.3 rom in safestrap will not work, and installing a stock 4.3 rom will brick your phone. You are limited to using a modified safestrap located in this thread, with no current modified custom roms.
This thread should strictly be for reference only, meaning posts should only be made if you believe a specific thread should be linked in the OP. If you want to discuss any aspects of this update that you're confused about, please use the 4.3 discussion thread (first linked sticky) or post your question in the Q&A forum. Keeping post counts low will make it easier for new members to access the information they need, so please post appropriately.
How can I tell if I have the official 4.3 or 4.4 update if I bricked my device?
It's important to know what base you're on so you can fix a brick. In any circumstance except a hard brick, once you boot into download mode you will see one of three possibilities:
If you're on a 4.3 or 4.4, you're in the right place:
4.3
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit:0
Bootloader RP Swrev: 0
4.4
Product Name: SCH-I535
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Bootloader RP Swrev: 0
If you're on the 4.1 baseband, you're in the wrong place and you should head here: Stickied Threads [9.2.13]
The information displayed in download mode will look like this:
4.1
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Stuck Threads
https://towelroot.com
Only tool available that will root 4.4 NE1 and 4.3 NC1 basebands. Will also root 4.3 ML1.
Touchwiz 4.3 (VRUCML1 and NC1) update discussion thread
Great resource with plenty of helpful people roaming the thread constantly. Use this thread to discuss any aspect of the 4.3 update you want.
[ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
A tool that will root the 4.3 VRUCML1 base. Will not work on NC1 or NE1 basebands.
[RECOVERY LOCKED] Safestrap Recovery v3.71 [2014-01-10 Alpha]
Only custom recovery that will work on the 4.3 VRUCML1. Do not try to use any other custom recovery, you will brick your phone. Right now you can only install custom Touchwiz 4.3 roms, so follow the directions in the thread. Will not work on the VRUCNC1 baseband, lacks kernel modules for WIFI connectivity. Will not work at all on the NE1 baseband.
[RECOVERY LOCKED/NE1] Unofficial Safestrap Recovery v3.75 [2014-06-27 KK B01]
Only recovery that will work on the NE1 baseband.
[HOWTO]Comprehensive IMEI/EFS Backup
Old thread, but a good one. This should be done immediately after you root, steps A and B (if still possible).
[INDEX] TW 4.3 Download List (5-24-14)
Everything you can install on 4.3 basebands NC1 and ML1.
[INDEX] TW 4.4 Download List (7-10-14)
Everything you can install on 4.4 baseband NE1.
[GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
Use this if you bricked your device, and you're still able to access download mode. You can also use this guide to return completely to stock if you need to. For NE1 you need to use an appropriate NE1 stock rom, not the 4.3 rom listed.
[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
Use this if you bricked your device and can't enter download mode. Computer will recognize device as QHSUSB-DLOAD, but other than that you have no other sign of life. You can also fix this problem with a JTAG repair if you can't get this method to work.
Useful Information
If you have 4.3 VRUCNC1 baseband, since wifi modules aren't available it is recommend to Odin flash the Stock 4.3 VRUCML1 rom then root and install safestrap. That way you will have working wifi after rom installations.
[FAQ] KNOX and you
Very useful information on KNOX that everyone should understand. However, we have a locked bootloader and the sprint device doesn't, so don't listen to what he's telling you about flashing AOSP roms. If you do it you'll brick the phone, just understand what he's saying about what knox is.
[FIRMWARE] (MODEM/RPM/TZ/SBL) Verizon SGS3 (SCH-I535)
Good information on the locked bootloader and why it can't be downgraded to a previous modem. Do not flash any files from this thread if you're on the 4.3 base.
I think that's all I can think of, hope this helps everyone who needs it!
I am unfortunately stuck on 4.3 stock that came with a warranty replacement phone. I somehow hard bricked it BUT the hard brick link above worked perfectly.
Thank you for this thread
Sent from my SCH-I535 using Tapatalk
Very good post. Thank you for your trouble and time. Wish more people would visit and read before they start rooting and flashing. Thanks again.
Sent from my SCH-I535 using xda app-developers app
Thanks for grouping everything. helped a lot
Not sure if this is the right thread to ask, but can I use safestrap to flash a custom kernel on the stock ROM?
Sent from my SCH-I535 using Tapatalk
root
The root method send me to the S4 forum. Is this the correct fourm for rooting my s3 4.3 using safestrap?
jl2222 said:
The root method send me to the S4 forum. Is this the correct fourm for rooting my s3 4.3 using safestrap?
Click to expand...
Click to collapse
Worked for me.
tyler.frost92 said:
Not sure if this is the right thread to ask, but can I use safestrap to flash a custom kernel on the stock ROM?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Actually, the safestrap thread would have been the best place to ask a question about safestrap. And no, you cannot flash a custom kernel on safestrap.
Sent from the Shark Tank using XDA Premium 4 mobile app
Thread updated with new information about the VRUCNC1 baseband.
Let me know if I missed something.
BadUsername said:
Thread updated with new information about the VRUCNC1 baseband.
Let me know if I missed something.
Click to expand...
Click to collapse
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
EVoorhees said:
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
Click to expand...
Click to collapse
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
EVoorhees said:
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
Click to expand...
Click to collapse
BadUsername said:
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
SlimSnoopOS said:
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
Click to expand...
Click to collapse
That makes sense, thanks for posting that.
Sent from my HTC6525LVW using Tapatalk
SlimSnoopOS said:
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
Click to expand...
Click to collapse
That's what I was planning on doing since I didn't see a module for NC1.
Thanks for the heads up, though.
Anyone know how I can add the ability to change songs using the volume buttons like in Cyanogenmod? I've been doing a little research and haven't found anything yet. Its not hugely important but would be one of the major things I need, besides the reseting volume and constant WiFi nag, that I need until I get time to get safestrap recovery and install a custom stock ROM. I'm pretty damn angry that the replacement phone I got from Asurion has the ML1 update. I personally can't stand TW. I wish there was a Boot loader unlock tool like HTC phones as I don't need a warranty anymore.
Any help would be appreciated. I'll update this if I can find anything, perhaps in a Xposed module. I'm sure what I'm looking g for is right in front of me and that I'm just oblivious of it.
Edit: Wanam Xposed seems to have one or more of the features I require. I haven't had the opportunity to teat it yet but that seems to be my solution.
Edit 2: had some issues where the phone was restarting. Defaulted everything back to normal and have only had 1 or two since. I didn't use many of the features of Wanam so I'm not sure exactly what it was.
Edit 3: It continued happening even after I flashed a stock .tar file in Odin and I eventually narrowed it down to the battery that asurion had sent me. Seems Wanam was not the culprit!
Sent from my SCH-I535 using Tapatalk
I will note that my phone has the line BOOTLOADER RP SWREV: 1 in the Download mode, which is different than what is up there. I have 4.3, ML1 update. Is there a difference? What does this line indicate, if anything?
Help! I have a Samsung S3 I535 for Verizon with the very latest baseband version ...NC1. At this point I can do nothing with the phone as far as root, recovery or a custom ROM! My Sprint version of the S3 is much easier to work with! I surmise that my phone has the Knox boot loader and can not be unlocked? However, I thought that the phone (I535) could be rooted and have a custom recovery. Is this correct and I just can't seem to find the proper thread or am I stuck with STOCK for the rest of this phones (probably short if I can't set it up to my liking) life?
len207 said:
Help! I have a Samsung S3 I535 for Verizon with the very latest baseband version ...NC1. At this point I can do nothing with the phone as far as root, recovery or a custom ROM! My Sprint version of the S3 is much easier to work with! I surmise that my phone has the Knox boot loader and can not be unlocked? However, I thought that the phone (I535) could be rooted and have a custom recovery. Is this correct and I just can't seem to find the proper thread or am I stuck with STOCK for the rest of this phones (probably short if I can't set it up to my liking) life?
Click to expand...
Click to collapse
Read the OP of this thread.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Towelroot works with NC1 and is an APK.
5ft24 said:
Towelroot works with NC1 and is an APK.
Click to expand...
Click to collapse
Ya I read that a couple days ago, I'll add it to the OP when I get a chance.
Sent from my HTC6525LVW using Tapatalk
Related
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
(wasnt really expecting to get the update at all with a rooted phone)
also i cannot get into supersu cause my phone is still recongnized as 4.3 instead of 4.1.2
...not really sure what to do
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
KabuTheFox said:
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
Click to expand...
Click to collapse
Nah, you'll have a hardbricked phone with seemingly no way to fix it if you attempt to downgrade. If/when VRUCML1 stock tar file is posted then you could flash that in Odin. What you'll need is something specifically for TW 4.3 whether that's root, root/unlock, or Odin. Nothing older is compatible.
KabuTheFox said:
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
Click to expand...
Click to collapse
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Thanks Slim !!
:good::good:
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
SafeRoot was a success and I now have a rooted device. I just purchased this used and it did an automatic update when i turned it on. Pretty bummed about now being able to switch out the ROM, but at least I've got root now! saferoot is awesome!
aarontsuru said:
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Click to expand...
Click to collapse
the update database doesnt recongize my phone tho, and thats why it couldnt complete the update.
but according to my phone im still on 4.3 technically
it has been some time, there might already be something out for all i know by now
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!
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
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps
aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Trevon75 said:
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Click to expand...
Click to collapse
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
SlimSnoopOS said:
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
Click to expand...
Click to collapse
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Trevon75 said:
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Click to expand...
Click to collapse
Unsure why it won't flash any other roms try this thread it's a good starting point
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
JacobManning17 said:
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Click to expand...
Click to collapse
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
landshark68 said:
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Muleguy said:
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Click to expand...
Click to collapse
You might be referring to this post in the general section. I am still unsure how they managed to do this if they downloaded the 20 MB VRUCML1 modem from our S3 forum. There is only one person whom I know to have extracted it and that is Invisiblek. Not a single other person before this user has mentioned having their bootloader locked from installing the VRUCML1 modem in CWM or TWRP. I really did not understand what they were trying to say so I just kept the convo moving in a different direction.
landshark68 said:
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
lexluthor said:
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
Click to expand...
Click to collapse
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by open1your1eyes0 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in open1your1eyes0's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
landshark68 said:
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by openyoureyes1 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in openyoureyes1's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
That is correct. Towelroot works just fine with NE1
Sent from my SCH-I535 using XDA Premium 4 mobile app
landshark68 said:
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
Click to expand...
Click to collapse
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
---------- Post added at 09:17 PM ---------- Previous post was at 08:25 PM ----------
lexluthor said:
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
Click to expand...
Click to collapse
All went great. It took a good half hour after the upgrade for the CPU to stop being pegged at 100% and have the phone be responsive again.
Very easy, it kept all of my applications and settings and I didn't really need to do much other than towelroot and re-install xposed.
I'm due for an upgrade soon anyhow, so I didn't really want to go through a lot of work getting to Kitkat.
Towel root not working any longer. Keep getting unsupported device with NE1 .. Ugh ..
My brother gave me his Bell locked Galaxy S4 today, so I've spent the day trying to unlock it to use on Rogers. After much reading of posts here, I managed to get it unlocked as follows:
I am no expert, though I am experienced with rooting and such. The following steps describe what I did to unlock my phone. I am not sure if all of these steps are necessary but they did work. Since I am not an expert, there is no point asking me questions if you have any problems, since I will not be able to help. Of course, some of these steps can void warranty, and could brick your phone if done improperly. I am not responsible for anything bad that happens.
1) Download and flash stock Columbia 4.2.2 rom with Odin (i used 3.09)
2) Root with CF-Auto Root
3) Flash Clockwork Mod (I use Caboomi's img2tar for this)
4) Get rid of KNOX by "installing" DE-KNOX zip in CWM (DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V2.0)
5) Download Chainfire's RegionLock Away, install and run
6) Restart and success!
7) Finally, I flashed the current (4.4.2) firmware of the provider I switched to (Rogers), as I was having problems with the phone and some other things. This seems to be operating properly now.
Note: I was able to install 4.2.2 rom even though I was unable to downgrade to 4.3. (Fail to flash aboot like many people get) I assume this is because the 4.2.2 rom does not modify aboot. Also, Chainfire states the RegionLock Away only works for the Note 3, however many people have used it successfully on the S4 as well. It did not work for me on 4.4.2, so I'm guessing either installing 4.2.2, or removing KNOX, or both got it to work.
I hope this helps some people. If it does, thank the developers who made everything above!
What firmware where you on when u began? 4.4.2? Or earlier?
Sent from my SGH-I337M using XDA Free mobile app
I don't think KNOX affects the sim locking and unlocking. I know for sure that RegionLockAway works in 4.2.2 because I downgraded my phone to that rom and unlocked it...without doing any of the KNOX related stuff.
I think this method you are using trips the KNOX fuse when you downgrade from KitKat.
OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
I downgraded to 4.2.2 by simply using ODIN. This process will trip the fuse. The trick in getting it to work is to clear all of the leftover files from 4.4.2 after the flash. You can't boot directly into the system after the flash. You have to go into recovery mode and do a factory reset. If you don't do this, the system wouldn't boot as what everyone is finding.
So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib
Sent from my SGH-I337M using XDA Free mobile app
Psykologikal said:
So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
Just a simple factory reset should do.
So nothing for 4.4.2 directly? We have to downgrade? Thanks