[Q] Stock NE1 keeping unlocked bootloader possible? - Verizon Samsung Galaxy S III

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 ..

Related

Rooting

Hi,
I've had my GSIII for a couple of months now. It's completely stock and unrooted. I was wondering if there was any benefit to rooting it, but not unlocking the bootloader and installing the custom recovery. I know that I won't be able to install custom roms or kernels. But is there anything else that I'd be losing out on?
Thanks
Please post questions in Q&A
Thread moved
Thanks
FNM
usmaak said:
Hi,
I've had my GSIII for a couple of months now. It's completely stock and unrooted. I was wondering if there was any benefit to rooting it, but not unlocking the bootloader and installing the custom recovery. I know that I won't be able to install custom roms or kernels. But is there anything else that I'd be losing out on?
Thanks
Click to expand...
Click to collapse
The only reason to unlock the bootloader would be to allow you to flash custom ROMs such as Cyanogenmod10, SlimRom, etc. You can do this by downloading EZ-Unlock from the play store. You will need root to run the program.
You will need root access to do anything a "superuser" needs to do, i.e. run programs such as Titanium backup, triangle away, ROM manager, Ez-Unlock, Root access using file explorer programs, and other programs that require root to function. You can flash Custom Recover without root, using ODIN and an ODIN CWM tar with a boot chain. You can then flash superuser/root using custom recovery.
If you don't need CWM Recovery, then you can just root using the PC USB method.
zenboy444 said:
The only reason to unlock the bootloader would be to allow you to flash custom ROMs such as Cyanogenmod10, SlimRom, etc. You can do this by downloading EZ-Unlock from the play store. You will need root to run the program.
You will need root access to do anything a "superuser" needs to do, i.e. run programs such as Titanium backup, triangle away, ROM manager, Ez-Unlock, Root access using file explorer programs, and other programs that require root to function. You can flash Custom Recover without root, using ODIN and an ODIN CWM tar with a boot chain. You can then flash superuser/root using custom recovery.
If you don't need CWM Recovery, then you can just root using the PC USB method.
Click to expand...
Click to collapse
A couple of months ago, I had an Evo that was fully unlocked, with a custom ROM and kernel. For now, I just want to root it, so that I can run things that require root, like Titanium, and some of the other apps that I bought when on the Evo. I rooted and unlocked the Evo because I was tired of it being sluggish. I actually really like the current setup on my GIII. I'm sure that down the road some ways (when I get bored), I'll fully unlock it, to take advantage of other ROMs.
I am still on 4.04. If I just root, will I be able to update to JB with the OTA?
Similar question...
I am stock 4.0.4, but want to root now that JB is out (don't know why I waited guess I just like the idea of doing it before probably the last major OTA). So I plan to root and unlock. Just wondering do I do it now before loading the JB OTA or afterwards? Are there advantages of one over the other? Thanks!
Sent from my SCH-I535 using xda app-developers app
usmaak said:
A couple of months ago, I had an Evo that was fully unlocked, with a custom ROM and kernel. For now, I just want to root it, so that I can run things that require root, like Titanium, and some of the other apps that I bought when on the Evo. I rooted and unlocked the Evo because I was tired of it being sluggish. I actually really like the current setup on my GIII. I'm sure that down the road some ways (when I get bored), I'll fully unlock it, to take advantage of other ROMs.
I am still on 4.04. If I just root, will I be able to update to JB with the OTA?
Click to expand...
Click to collapse
You should be able to receive the OTA update for JB if you check for updates in settings; if not you will receive it soon. Rooting will not speed up that process at all, and since you'll likely be on JB soon there's really no point in rooting right now. OTA will remove root anyway, but there is a rooting method for JB already available.
If you do eventually decide to root, the main advantage is you can unlock bootloader and flash a custom recovery to install one of the many ROMs available for this phone. If you dislike TouchWiz, you can flash an AOSP rom like CM10 which is more of a stock Android experience. If you don't mind TouchWiz, you can install a ROM like CleanROM which gets rid of Verizon's bloat with a few extra perks.
If you're not into installing custom ROMs, you could still take advantage of rooting by freezing unwanted apps which hinder battery life and run other root-only apps like AdFree which block ads. Also, you can avoid waiting for Verizon to push out updates and install the leaks early.
The big reason I rooted was to uninstall all the bloatware and the ability to back everything up. That right there should be enough for anyone. As far as the ota, you should be able to, just expect to lose root as I've seen in other cases.
OnceAMatrixMan said:
Similar question...
I am stock 4.0.4, but want to root now that JB is out (don't know why I waited guess I just like the idea of doing it before probably the last major OTA). So I plan to root and unlock. Just wondering do I do it now before loading the JB OTA or afterwards? Are there advantages of one over the other? Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No point in doing that now because you will likely receive the OTA update within days, which removes root. You could technically install the leaked OTA manually right now (check the dev section), but since you're running stock you'll just receive it automatically. I wouldn't bother.
Quacker said:
You should be able to receive the OTA update for JB if you check for updates in settings; if not you will receive it soon. Rooting will not speed up that process at all, and since you'll likely be on JB soon there's really no point in rooting right now. OTA will remove root anyway, but there is a rooting method for JB already available.
If you do eventually decide to root, the main advantage is you can unlock bootloader and flash a custom recovery to install one of the many ROMs available for this phone. If you dislike TouchWiz, you can flash an AOSP rom like CM10 which is more of a stock Android experience. If you don't mind TouchWiz, you can install a ROM like CleanROM which gets rid of Verizon's bloat with a few extra perks.
If you're not into installing custom ROMs, you could still take advantage of rooting by freezing unwanted apps which hinder battery life and run other root-only apps like AdFree which block ads. Also, you can avoid waiting for Verizon to push out updates and install the leaks early.
Click to expand...
Click to collapse
I already have the JB update available. I am just waiting a while, to see if it causes any unintended problems. Specifically I'm looking to see if it adversely affects battery life or signal strength.
I'm doing the research and seeing what the differences are between rooting and unlocking the GSIII and the Evo. Right now, I'm fine with the stock ROM. It's way better than anything that I had on my Evo (and I tried them all). Right now, I just want to be able to run apps requiring root.
usmaak said:
I already have the JB update available. I am just waiting a while, to see if it causes any unintended problems. Specifically I'm looking to see if it adversely affects battery life or signal strength.
I'm doing the research and seeing what the differences are between rooting and unlocking the GSIII and the Evo. Right now, I'm fine with the stock ROM. It's way better than anything that I had on my Evo (and I tried them all). Right now, I just want to be able to run apps requiring root.
Click to expand...
Click to collapse
In my experience, it's usually difficult to avoid OTA updates for long if you're not rooted. I would usually go to sleep and find later that my phone updated itself.
I haven't heard of any battery issues with JB, but I don't see why anyone would want to stick with ICS at this point. Google Now alone is worth it.
Quacker said:
In my experience, it's usually difficult to avoid OTA updates for long if you're not rooted. I would usually go to sleep and find later that my phone updated itself.
I haven't heard of any battery issues with JB, but I don't see why anyone would want to stick with ICS at this point. Google Now alone is worth it.
Click to expand...
Click to collapse
I don't want to avoid OTA updates. I want it, I just want to wait a few days. I deferred it until 12/19.
I just want to make sure that:
1. I can still get OTAs with root, and...
2. There is a way to keep root if I accept the OTA.
I do want JB, but I've gotten screwed by OTAs in the past, on the Evo. I just want to be as certain as possible.
Quacker said:
No point in doing that now because you will likely receive the OTA update within days, which removes root. You could technically install the leaked OTA manually right now (check the dev section), but since you're running stock you'll just receive it automatically. I wouldn't bother.
Click to expand...
Click to collapse
I delayed the update earlier today. I saw in several posts that Voodoo Root Keeper keeps root. So still curious to root now or after OTA update...?
Sent from my SCH-I535 using xda app-developers app
usmaak said:
I don't want to avoid OTA updates. I want it, I just want to wait a few days. I deferred it until 12/19.
I just want to make sure that:
1. I can still get OTAs with root, and...
2. There is a way to keep root if I accept the OTA.
I do want JB, but I've gotten screwed by OTAs in the past, on the Evo. I just want to be as certain as possible.
Click to expand...
Click to collapse
You can get OTA with root. Just don't freeze any apps.
You can keep root with OTA Rootkeeper. I haven't heard of it failing for anyone with the recent update.
You could always re-root in JB.
---------- Post added at 07:16 PM ---------- Previous post was at 07:09 PM ----------
OnceAMatrixMan said:
I delayed the update earlier today. I saw in several posts that Voodoo Root Keeper keeps root. So still curious to root now or after OTA update...?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Up to you. Rootkeeper does work with this update. I suppose rooting in ICS is easier, but the JB method isn't all that difficult either.
Quacker said:
You can get OTA with root. Just don't freeze any apps.
You can keep root with OTA Rootkeeper. I haven't heard of it failing for anyone with the recent update.
You could always re-root in JB.
---------- Post added at 07:16 PM ---------- Previous post was at 07:09 PM ----------
Up to you. Rootkeeper does work with this update. I suppose rooting in ICS is easier, but the JB method isn't all that difficult either.
Click to expand...
Click to collapse
So, I should be all set if I complete section 1, steps 1 - 7 of this post: http://forum.xda-developers.com/showthread.php?t=1762709
True statement?
usmaak said:
So, I should be all set if I complete section 1, steps 1 - 7 of this post: http://forum.xda-developers.com/showthread.php?t=1762709
True statement?
Click to expand...
Click to collapse
Yep! Then install and use Rootkeeper.
I just rooted myself before I received OTA for the following reasons:
1) I didn't want to use ODIN
2) Didn't want to worry about using Triangle Away
This was my first time rooting, and it was effortless. I used droidstyle's guide. The only thing I did differently was use a modified Debugfs (w/SuperSU), since my phone didn't like the original Debugfs (w/superuser).
The modified Debugfs can be found here: http://forum.xda-developers.com/showthread.php?t=1883984
nufan said:
I just rooted myself before I received OTA for the following reasons:
1) I didn't want to use ODIN
2) Didn't want to worry about using Triangle Away
This was my first time rooting, and it was effortless. I used droidstyle's guide. The only thing I did differently was use a modified Debugfs (w/SuperSU), since my phone didn't like the original Debugfs (w/superuser).
The modified Debugfs can be found here: http://forum.xda-developers.com/showthread.php?t=1883984
Click to expand...
Click to collapse
Doesn't the counter only get tripped when you flash a ROM? Just rooting won't trip it, will it?
Quacker said:
Yep! Then install and use Rootkeeper.
Click to expand...
Click to collapse
One more question, and I am off to give it a try. Is there any way to uproot the phone once it is rooted? You know, just in case I need to bring it in for service if something goes wrong with it.
rooting S III 4.1.1
so I have been thinking about rooting my S3, and did the research and found these two very well explained instructions.
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1875914
My question is does either one still work for S3 with JB (since they were posted when S3 had ICS).
Thank you!
newtodroid_1 said:
so I have been thinking about rooting my S3, and did the research and found these two very well explained instructions.
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1875914
My question is does either one still work for S3 with JB (since they were posted when S3 had ICS).
Thank you!
Click to expand...
Click to collapse
Nope they both are ics only. Here it's the only way right now for jb
http://forum.xda-developers.com/showthread.php?p=35418324
Sent from my SCH-I535 using xda app-developers app

plz help! cannot install any rom

rooted razr hd on most current ota...installed most recent safestrap since cannot unlock bootloader...created a rom slot 1 and try to flash a rom but they all fail...originally trying http://true-android.blogspot.com/2013/12/update-motorola-droid-razr-hd-xt926-to_16.html but it failed so tried slimkat but also failed....idk what to do please help
I'm actually having a similar issue in the same situation with hd maxx. Rooted with locked bootloader so used Safestrap. I was able to install the rom but can't boot into it. I'm just seeing a black screen. Let me know if you find a way to get the rom loaded correctly.
r4zrm4xxx said:
rooted razr hd on most current ota...installed most recent safestrap since cannot unlock bootloader...created a rom slot 1 and try to flash a rom but they all fail...originally trying http://true-android.blogspot.com/2013/12/update-motorola-droid-razr-hd-xt926-to_16.html but it failed so tried slimkat but also failed....idk what to do please help
Click to expand...
Click to collapse
jigz23 said:
I'm actually having a similar issue in the same situation with hd maxx. Rooted with locked bootloader so used Safestrap. I was able to install the rom but can't boot into it. I'm just seeing a black screen. Let me know if you find a way to get the rom loaded correctly.
Click to expand...
Click to collapse
I'm going to go out on a limb and say that the info in that blog is inaccurate. All of those "how-to's" state that you need SafeStrap, except for Pac that says you need CWM. I'm hoping it's just a verbage mix up and he meant to say "TWRP" instead of "SafeStrap." If he meant SS, he's going to make a lot of soft-bricks. Those ROMs should not work unless you have an unlocked bootloader. They won't work with a locked bootloader and SafeStrap. The OP of those how-to's needs to dig in a little more. All of the threads for those respective ROMs on XDA and elsewhere specifically state that you need an unlocked bootloader. Root =/= unlocked bootloader. Heck, even the CM Wiki states that you need an unlocked bootloader. If your BL was unlocked and you were using SafeStrap, you would probably get those ROMs to work. However, since you cannot unlock your BL (and haven't been able to since the May update), you probably won't be able to use those ROMs. I think the person that threw that blog together did it pretty hastily, without researching. The original post was put up just a few hours ago and it hasn't been very long since the root exploit popped up.
With all of that^^^ being said, there are only a few SS compatible ROMs out there and they're all stock based. I believe Rage HD and Nexesque will work on SS. There is also a DST ROM running around that should work. DST is a debloated stock ROM with no VZW crap in it.
CM wiki: http://wiki.cyanogenmod.org/w/Xt926_Info
RikRong said:
I'm going to go out on a limb and say that the info in that blog is inaccurate. All of those "how-to's" state that you need SafeStrap, except for Pac that says you need CWM. I'm hoping it's just a verbage mix up and he meant to say "TWRP" instead of "SafeStrap." If he meant SS, he's going to make a lot of soft-bricks. Those ROMs should not work unless you have an unlocked bootloader. They won't work with a locked bootloader and SafeStrap. The OP of those how-to's needs to dig in a little more. All of the threads for those respective ROMs on XDA and elsewhere specifically state that you need an unlocked bootloader. Root =/= unlocked bootloader. Heck, even the CM Wiki states that you need an unlocked bootloader. If your BL was unlocked and you were using SafeStrap, you would probably get those ROMs to work. However, since you cannot unlock your BL (and haven't been able to since the May update), you probably won't be able to use those ROMs. I think the person that threw that blog together did it pretty hastily, without researching. The original post was put up just a few hours ago and it hasn't been very long since the root exploit popped up.
With all of that^^^ being said, there are only a few SS compatible ROMs out there and they're all stock based. I believe Rage HD and Nexesque will work on SS. There is also a DST ROM running around that should work. DST is a debloated stock ROM with no VZW crap in it.
CM wiki: http://wiki.cyanogenmod.org/w/Xt926_Info
Click to expand...
Click to collapse
Hey thanks a lot for the very helpful and informative info I appreciate it much. Looking into as ROMs now hopefully bootloader can be unlocked in near future
Sent from my XT912 using XDA Premium 4 mobile app
r4zrm4xxx said:
..... hopefully bootloader can be unlocked in near future
Sent from my XT912 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
while someone may have tripped and fell into a big pile of root, thats not going to happen for the bootloader. you can bank on that.
i had this issue today with safestrap 3,65 when flashing any stock roms on slot 1 and it was a no go, i installed safestrap ver 3.12 and that did the trick for me.

The [GT-I9505][Leaked firmware] I9505XXUFNA1 (Android 4.4) - Open Europe (OXA) [10-01

The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
killer5000 said:
The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
neo4uo said:
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
Click to expand...
Click to collapse
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
ZPaul2Fresh8 said:
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
Click to expand...
Click to collapse
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
neo4uo said:
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
Click to expand...
Click to collapse
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
ZPaul2Fresh8 said:
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
Click to expand...
Click to collapse
Let us know, or pm and let me know how it goes
known bugs
Hi so far after using for the last two days I notice when holding the home button for open apps what ever you press will always open the last app used and not what you have selected!
Andy the native Samsung e mail app continuously tells me about e mails I've viewed
That is all so far!
what kernel are you using?
neo4uo said:
Let us know, or pm and let me know how it goes
Click to expand...
Click to collapse
Well after hours of farting around with their build and mine, I pretty much lost interest with the ROM now. Their build definitely has WiFi broken. I'm not sure if it's kernel related or not.
I think I'm with you on waiting for this to improve before using. Besides CM11 with Google Experience Launcher is looking and feeling great this past month...
Here is a like to Echoe13_4.4.2Deodex_12JAN2013.zip it works but you need to loki patch it and wifi don't work.
http://www.androidfilehost.com/?fid=23311191640113279
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Loki only has to be flashed on the At&t variant of the S4 after installing a zip that was not an At&t rom. The WiFi issue I believe is from not updating the bootloader via OTA and possibly kernel tweaks as well but it will get there. We have great devs for this device.
Sent from my SGH-I337 using XDA Premium HD app
scalamusical said:
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Click to expand...
Click to collapse
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
C13v3r0n3 said:
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
Click to expand...
Click to collapse
what kernel were you guys using on the echoe roms? I couldn't get past the boot screen and it hung using the i337m Canadian variant which should be the same as their TMO version minus the leaked bootloader.
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
rfb813 said:
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
Click to expand...
Click to collapse
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
TheAxman said:
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
Click to expand...
Click to collapse
I didn't know there was a nlthread on this on my native device. I Have been posting on the Tmobile thread since the leak first came out.
I also unpacked both Leaks and repacked only their respective boot, system and cache files and successfully flashed via Odin. the cool part was that I didn't lose root and only needed to add the new supersu. I had a titanium backup zip which I also flashed.
the problems are as follows
1. No WiFi. attempting to flash KT kernel bricked it. had to start all over
2. Security settings caused a FC. so couldn't enable installation from unknown sources.
3. Restoring user apps using Titanium backup (after freezing all Knox apps) worked. but adding any system apps caused a bad series of forced closures
so unless u have got an unlimited data plan, this is just something to play around with for now it would seem
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
guerouig said:
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
Click to expand...
Click to collapse
The bootloader would block odin from accepting the full package. The best u can do is pick n choose parts to flas like i did. And you'll end up with a similar scenario
But you could use this modified version and search for Magical unicorn kernel and see
http://forum.xda-developers.com/showthread.php?t=2608134
@gangsta101: so what bits did you chose to flash? is AP and CP and exclude BL and CSC for instance?

[Q] flashing locked bootloader doesn't stick?

So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
vax1170 said:
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
Click to expand...
Click to collapse
Well your almost right. First off you for sure can root. Second you can install custom roms with safestrap. Its limited to tw roms atm. There have been a hand full of people who upgraded just to use safestrap. I wouldnt recomend it right now because its alittle buggy.
RedBullet said:
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
Click to expand...
Click to collapse
Wife's phone. She doesn't want to mess with it.
I think I figured it out, looks like I had a custom recovery installed. Flashed that to stock and locked bootloader and all is fine now. Running latest and greatest. Just what the missus is looking for...
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
ThePagel - Thanks. One one of my phones was cursed with an accidental OTA 4.3 upgrade. Nice to know something is in the works, I'll dig up that thread and watch it.
vax1170 said:
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
Click to expand...
Click to collapse
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
RedBullet said:
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
Click to expand...
Click to collapse
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
landshark68 said:
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
Click to expand...
Click to collapse
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
It sure is sad but true. Im thankful google blessed us with the nexus 5
RedBullet said:
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
Click to expand...
Click to collapse

[FIRMWARE] VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image

WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
First!
Hairiest chest?
Can't wait till you guys crack this open for us unlocked folks!
i need to send my phone back into verizon. if i odin this i will be cool right?
Cannot wait for baseband update, hopefully it will be pulled separate soon.
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
ruokuo said:
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
Click to expand...
Click to collapse
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
kuronosan said:
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
gherman222 said:
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
Click to expand...
Click to collapse
Towelroot works.
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
v1ncent said:
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
Click to expand...
Click to collapse
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Sent from my SCH-I535 using XDA Free mobile app
MIKEYSAKZ said:
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Click to expand...
Click to collapse
Thanks - I have patience and definitely planning on waiting. That's why I still have an unlocked bootloader
prdog1 said:
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Click to expand...
Click to collapse
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
leroyinc said:
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
Click to expand...
Click to collapse
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
mms works, didnt know why wont work sms
leroyinc said:
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
mms works, didnt know why wont work sms
Click to expand...
Click to collapse
Make sure you are in Global mode before try any of this. If go with Software updater it is going to update you to 4.4.2. Not sure if can stop after repair or not. If that 4.3 tar in odin don't fix this is about only option I know of. Since bootloader is locked cannot use the fixes we have for this problem.
http://www.verizonwireless.com/support/devices/knowledge_base.html/80200/
open1your1eyes0 said:
WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
Click to expand...
Click to collapse
Is it safe to flash the modem only, in recovery, with existing mf1 firmware?
Thanks.
Sent from my SCH-I535 using XDA Free mobile app
I am on MF1 rooted and unlocked but I have had the phone since it's release and have no interest in installing AOSP ROMs. I do need root because I have to be able to use root explorer or similar so I can edit the "keys" system files to disable the "WAKE" function of the home key. I keep my phone in my back pocket and it constantly turns on if the home key has wake enabled.
Before I flash this I wanted to confirm that flashing this No-Wipe Factory Image with Odin, I can root with Towelroot and install Root Explorer? Would I also be able to install TW based ROMs like a new Clean Rom if Scott gets one figured out? Would I also be able to create nandroids using Clockwork or TWRP?
Lastly, Since my most recent install of CR 8.2 my phone's behavior has been a bit sketchy (random reboots, laggy, etc). I assume if I flash this stock image it should return my phone to whatever level of performance "stock" yields, without any of my current, likely self imposed, performance issues?
I have never had a phone this long and expect I'll get a new one whenever there really is a "next big thing", but I don't think we're there yet.
Thanks in advance.
Going back to stock
So, if I want to go back to stock, this is the way?
I'm on beanstalked / MF1 rooted and unlocked of course. But I'd like to get the phone back to stock condition so I can sell it here soon.

Categories

Resources