Related
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.
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
I should start by saying I am by no means experienced with unlocking bootloaders or hacking firmware, so if this is a completely noob idea then forgive me but I thought I might as well see if I could help. Anyways, on to my idea; as we all know, the 4.3 bootloader is locked for good. So what if one was to corrupt the bootloader, like brick it on purpose to a point where the bootloader doesn't recognize any update being pushed, and then unbrick the phone with an older unlockable bootloader. Am I losing my mind due to having the locked 4.3 or is this plausible?
And while I have a thread open, could someone explain a few questions I have about knox? If knox is what is causing the bootloader to be locked and there's ways to disable knox, then wouldn't disabling knox make the bootloader unlockable?
ericcue said:
I should start by saying I am by no means experienced with unlocking bootloaders or hacking firmware, so if this is a completely noob idea then forgive me but I thought I might as well see if I could help. Anyways, on to my idea; as we all know, the 4.3 bootloader is locked for good. So what if one was to corrupt the bootloader, like brick it on purpose to a point where the bootloader doesn't recognize any update being pushed, and then unbrick the phone with an older unlockable bootloader. Am I losing my mind due to having the locked 4.3 or is this plausible?
And while I have a thread open, could someone explain a few questions I have about knox? If knox is what is causing the bootloader to be locked and there's ways to disable knox, then wouldn't disabling knox make the bootloader unlockable?
Click to expand...
Click to collapse
This won't work.
The new update changes the keys on the entire bootloader, it's impossible to corrupt the bootloader to a point of failure because the entire thing is hard coded into the board itself. The processor is specifically able recognize the vrucml1 bootchain, and it won't boot without it, unless someone finds a way to bypass that entire mechanism (which I would consider nearly impossible.
Knox is not causing the bootloader to be locked. Verizon patched our work around for unlocking the bootloader and pushed it. Knox is simply a non reversible flash counter for rooting your device. It's coded in the bootloader and system apps to detect this.
Sent from my SCH-I535 using Tapatalk 2
Ah I see. I guess I had trouble understanding that an OTA could completely and irreversibly lock a bootloader. There's got to be some kind of exploit for this at some point right? I'm not sure I can handle this 4.3 nonsense anymore!
And thanks for the knox explanation, I used to hate sprint for the things they did (like booting me for roaming) and now verizon is starting to tick me off.
ericcue said:
Ah I see. I guess I had trouble understanding that an OTA could completely and irreversibly lock a bootloader. There's got to be some kind of exploit for this at some point right? I'm not sure I can handle this 4.3 nonsense anymore!
And thanks for the knox explanation, I used to hate sprint for the things they did (like booting me for roaming) and now verizon is starting to tick me off.
Click to expand...
Click to collapse
There is probably no chance for an exploit to completely unlock a bootloader.
Hardware hacking is almost impossible because of the type of encryption it takes to make the processor and bootchain recognize each other. It's sensitive, and you need to match the numbers specifically to perform a boot. Everyone is familiar with an md5 code, this is a fairly simple algorithm, and we all know that the slightest change in a bad download will generate a completely different md5 sum. In this case, the algorithm is much more complex, and pretty much impossible to match and trick the phone into booting an incorrect bootloader. This is why straight up hacking a bootloader an impossible feat, so we mostly make work arounds.
All our unlocked bootloader was is a very early aboot block. The bootchain trusts the aboot file, and the aboot file trusts anything you put in the recovery and system partitions. Since the new bootchain requires a signed aboot file for ML1, it makes this exploit insignificant and the aboot file doesn't trust anything else you stick in the recovery or system partition.
Loki was another exploit that was patched. Kexec is an example of a work around, and so is safestrap, but these types of workarounds won't unlock the bootloader and allow aosp Rom flashing.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
There is probably no chance for an exploit to completely unlock a bootloader.
Hardware hacking is almost impossible because of the type of encryption it takes to make the processor and bootchain recognize each other. It's sensitive, and you need to match the numbers specifically to perform a boot. Everyone is familiar with an md5 code, this is a fairly simple algorithm, and we all know that the slightest change in a bad download will generate a completely different md5 sum. In this case, the algorithm is much more complex, and pretty much impossible to match and trick the phone into booting an incorrect bootloader. This is why straight up hacking a bootloader an impossible feat, so we mostly make work arounds.
All our unlocked bootloader was is a very early aboot block. The bootchain trusts the aboot file, and the aboot file trusts anything you put in the recovery and system partitions. Since the new bootchain requires a signed aboot file for ML1, it makes this exploit insignificant and the aboot file doesn't trust anything else you stick in the recovery or system partition.
Loki was another exploit that was patched. Kexec is an example of a work around, and so is safestrap, but these types of workarounds won't unlock the bootloader and allow aosp Rom flashing.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You are a bundle of endless info. Thank you for breaking it down like this!
Edit: I have been curious for awhile about the technical aspect of everything you detailed.
That was amazing lol thanks for clearing all that up. Now I guess the race is on to find safestrap compatible roms. I'm running wicked sensations right now through safestrap and it seems pretty good but I was looking for a rom that could force 4g
SlimSnoopOS said:
You are a bundle of endless info. Thank you for breaking it down like this!
Edit: I have been curious for awhile about the technical aspect of everything you detailed.
Click to expand...
Click to collapse
I wish I knew more coding details, like what this stuff specifically looks like, but it's interesting researching all this material.
These are the kinds of questions I like, they really make you think about what's happening. I wish more users posted questions like these. One day someone might post something that might actually work. It's good creative thinking.
Sent from my SCH-I535 using Tapatalk 2
Kexec will allow flashing of aosp roms in addition to safe strap.
Sent from my SCH-I535 using Tapatalk
Dadud said:
Kexec will allow flashing of aosp roms in addition to safe strap.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Kexec might be able to, but it depends of that exploit has been patched or not, that kernel mechanism can also be shut down to disallow booting of a 2nd kernel. If the modules are written a certain way you're stuck with that initial boot.
Safestrap can't, it relies on a stock kernel to run, so unless someone makes an aosp rom to run with a 4.3 touchwiz kernel it won't work.
Sent from my SCH-I535 using Tapatalk 2
How did hashcode get cm 10.2 on the droid 3 using kexec and safe strap?
Sent from my SCH-I535 using Tapatalk
I love this thread so much. Thanks BadUsername and everyone else! So why exactly can't we use Kexec?
YevOmega said:
I love this thread so much. Thanks BadUsername and everyone else! So why exactly can't we use Kexec?
Click to expand...
Click to collapse
Getting kexec functionality isn't the easiest process. The holes that allowed kexec on 4.0.4 may have been patched due to the new Linux 3.0 kernel updated in newer versions.
Some developer would have to work on finding that loophole and enabling a second kernel to run.
Hashcode was able to do this on Motorola devices by rewriting the kernel modules to run differently. The way he did it wouldn't work for us anyway because they used OMAP devices. We have a qualcom processor, the loophole he used to enable kexec is completely different then what we would need to enable.
Additionally, it may not even be possible to enable kexec. The whole idea of a locked bootloader is to prevent this from happening. Loopholes constantly get patched, making enabling these types of workarounds increasingly more difficult.
Eventually the loophole that allows safestrap to even run will likely get patched. It's just the nature of making phones increasingly more difficult to root and unlock.
I hope someone has the time and passion to work on kexec, but I wouldn't necessarily count on it. There's likely a reason why it was never implemented on the s4.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Getting kexec functionality isn't the easiest process. The holes that allowed kexec on 4.0.4 may have been patched due to the new Linux 3.0 kernel updated in newer versions.
Some developer would have to work on finding that loophole and enabling a second kernel to run.
Hashcode was able to do this on Motorola devices by rewriting the kernel modules to run differently. The way he did it wouldn't work for us anyway because they used OMAP devices. We have a qualcom processor, the loophole he used to enable kexec is completely different then what we would need to enable.
Additionally, it may not even be possible to enable kexec. The whole idea of a locked bootloader is to prevent this from happening. Loopholes constantly get patched, making enabling these types of workarounds increasingly more difficult.
Eventually the loophole that allows safestrap to even run will likely get patched. It's just the nature of making phones increasingly more difficult to root and unlock.
I hope someone has the time and passion to work on kexec, but I wouldn't necessarily count on it. There's likely a reason why it was never implemented on the s4.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
*Sigh*
YevOmega said:
*Sigh*
Click to expand...
Click to collapse
It's not the worst thing. In my opinion this phone runs really well on touchwiz roms anyway. Give some time for more roms to come out. Tkrom, cleanrom and jellybeans will all be spectacular when they come out.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's not the worst thing. In my opinion this phone runs really well on touchwiz roms anyway. Give some time for more roms to come out. Tkrom, cleanrom and jellybeans will all be spectacular when they come out.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I totally agree with you. With root and a different launcher, I'm doing fine right now. Really wanted that new quick settings on Paranoid though.
Sent from my SCH-I535 using Tapatalk
Anyone else think that the information that BadUsername posted should be made a sticky?
Should have just rooted when you first got the phone haha
Sent from my SCH-I535 using xda app-developers app
XdrummerXboy said:
Should have just rooted when you first got the phone haha
Click to expand...
Click to collapse
You can gain root access on 4.3, but still can't unlock the bootloader.
The 4.3 OTA has truly downgraded the performance of my phone, so I'm not holding out much hope that 4.3 safestrapped ROMs will do much else - Samsung has rather let me down with this update (even outside of working with Verizon to lock the darn thing down much more tightly).
I used to say that custom ROMs were not needed, because the stock OS ran so well. Since the 4.3 OTA, it feels slower than when it first came with 4.0.4 (?) and has some of the old WiFi and Bluetooth issues back, again. On both of our Galaxy S III phones, btw. Not quite so fun, anymore.
- ooofest
ooofest said:
You can gain root access on 4.3, but still can't unlock the bootloader.
The 4.3 OTA has truly downgraded the performance of my phone, so I'm not holding out much hope that 4.3 safestrapped ROMs will do much else - Samsung has rather let me down with this update (even outside of working with Verizon to lock the darn thing down much more tightly).
I used to say that custom ROMs were not needed, because the stock OS ran so well. Since the 4.3 OTA, it feels slower than when it first came with 4.0.4 (?) and has some of the old WiFi and Bluetooth issues back, again. On both of our Galaxy S III phones, btw. Not quite so fun, anymore.
- ooofest
Click to expand...
Click to collapse
Oh, I didn't catch that. Thanks for the info. And ooofest, were you over at overclockers.uk? I thought I recognized that name from there, maybe it was only here though.
I've honestly lost track of the rooting requirements for this phone after I rooted. Best decision I've made with this phone! But I was nervous to do so...
I agree, it wasn't too terrible when it had 4.0.4, but compared to Cyanogenmod there's no comparison on which is smoother!
Sent from my SCH-I535 using xda app-developers app
XdrummerXboy said:
Oh, I didn't catch that. Thanks for the info. And ooofest, were you over at overclockers.uk?
Click to expand...
Click to collapse
Not that I recall, sorry. I used to be more active here and about, but then decided to go back into stock for 2013 and ramp up the rooting, unlocking, optimization, etc. in 2014.
It would always be ready to re-root and unlock, yes?
Well, never say "always."
XdrummerXboy said:
I agree, it wasn't too terrible when it had 4.0.4, but compared to Cyanogenmod there's no comparison on which is smoother!
Click to expand...
Click to collapse
Indeed.
- ooofest
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 ..
So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?
All guides and info threads are linked in my signature and will answer almost all your questions
I'm not sure of all these "problems" you're referring to. Basically, idiots have the most problems. Normal people don't really have any
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Basically, idiots have the most problems. Normal people don't really have any
Click to expand...
Click to collapse
this. i have been rooted since day one and have ZERO problems.
I think this: http://forum.xda-developers.com/showpost.php?p=54746284&postcount=8
Applies here too, what do you think, @rootSU?
Right. Root doesn't modify files that can cause an issue assuming you're doing it right. I'd highly recommend NOT using a toolkit and rooting yourself and unlocking the bootloader yourself, it assures nothing goes wrong and you get some experience.
rootSU's guide are a treasure trove of information, take a looksie.
unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.
simms22 said:
unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.
Click to expand...
Click to collapse
So would unlocking the boot loader void the warranty?
Spectrys said:
So would unlocking the boot loader void the warranty?
Click to expand...
Click to collapse
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked
simms22 said:
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked
Click to expand...
Click to collapse
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
yup. anything that needs to be flashed will go through your custom recovery, which needs an unlocked boitloader to get flashed onto your device. then youll use that recovery to flash things, and make backups.
Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
Unlocking the bootloader is a requirement in order to use a custom recovery. And most mods are installed by flashable zips in recovery. So yes kind of required.
Sent from my Nexus 5 using Tapatalk
Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?
Spectrys said:
Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?
Click to expand...
Click to collapse
If you click the link in my signature, theres a thread about ota. All guides and info is there. Every question you've asked today is answered there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Pretty sure you told me that earlier, thanks.
Looking at it now.
Spectrys said:
Pretty sure you told me that earlier, thanks.
Looking at it now.
Click to expand...
Click to collapse
Yepp. Loads of good stuff there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
sure
root is best thing to do . just root and install custom kernel
MohamedHusseinMohamed said:
root is best thing to do . just root and install custom kernel
Click to expand...
Click to collapse
you do not need root to install custom kernels
all you need root for is to change system files. well, that's all root does, is give you permission.
Spectrys said:
So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?
Click to expand...
Click to collapse
You have to unlock the boot loader in order to root. Personally at this time I would not root because of android L around the corner. With rooting, you can longer receive ota's. Yes it fun to tweak but if I were in your position I wouldn't....
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
With rooting, you can longer receive ota's.
Click to expand...
Click to collapse
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick
rootSU said:
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick
Click to expand...
Click to collapse
Personally, I think that if you don't know how to update manually and are completely reliant on OTAs, then you shouldn't have root access in the first place because you don't know what you're doing.