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.
Related
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
dear all,
has anybody tried this? http://forum.xda-developers.com/showthread.php?t=1940630
Already rooted, going to try it on a demo phone at work,
sent from my giant f$%&en Q
I tried it today works great, thanks posting it here i wanted root but didnt want unlock it.
Sent from my XT897 using xda app-developers app
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
bryanfritz1 said:
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I unlocked and trashed the stock recovery and ported TWRP immediately after getting the device...
BUT with that said, typically stock recoveries will only flash signed/stock stuffs. So I doubt you'll be able to install anything aftermarket with their stock recovery... Obviously I don't know if this is true or not, I never even had stock reco on long enough to find out .
This worked great for me. No unlocked bootloader prior to running the script.
Now if only I could get wifi tether working...
bryanfritz1 said:
Thanks a lot for confirming this as I am in the same boat. I will eventually unlock based on the fact that I hear you can't have custom recovery unless you unlock. I also came from a samsung epic and I haven't quite gotten the moto lingo down so I don't quite follow the boot and fastboot stuff yet. I think i have pieced together that moto has a better stock recovery than Samsung therefor you don't necessarily need a custom recovery to flash stuff if unlocked, but please correct me if I have assumed to much. Thx again.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
no stock recovery can flash OTA's and thats all
i was wondering how long it would take people to find this . reason why i dindt post it? next OTA that comes and wipes it out youve gutta wait until a new exploit is found... or unlock the bootloader and flash a recovery.
Install ota rootkeeper from the market and you will keep root through an update. Works great. I obviously haven't used the app on the photon q but it worked on a few other devices.
Having said that, sometimes updates come with different bootloaders and sometimes you don't want a newer bootloader.
That's the whole question, actually. I've got a new Maxx HD that has stock ROM, locked bootloader and has never had root, and if it's already running 9.18.79. Has any method been found to either root it and/or unlock the bootloader?
No method available that successfully roots this version yet.
mryoung0042 said:
No method available that successfully roots this version yet.
Click to expand...
Click to collapse
Actually, what I've read since getting the phone yesterday seems to differ just a bit from "no way to root". There's a thread on droidrzr.com that spells out what seems like a reasonable way to achieve root on an XT926 running 9.18.79. The thread is here http://www.droidrzr.com/index.php/topic/23729-rsd-scripts-samurihls-razr-hd-emporium/ I don't know if it works. I'll likely try it later this morning (need more coffee first).
However -- Everything I've read so far says that I'm out of luck in terms of getting the bootloader unlocked. That sucks because, well, we ought to be able to use our devices as we see fit. But If I am able to get root I'll be able to use most of the functionality I need.
One more thing I read (and forgot to bookmark) is that, if the root method above works on updated XT926s, I should be able to install Safestrap and maybe flash an older ROM that used Safestrap. I don't know if that's true and I don't know yet if I'll need that but one of my first goals when I get a new Razr HD is to find a way to get rid of the Navigation Bar and use PIE Control. I struggled mightily with that before the bootloader unlock was released because I'm just not smart enough to decompile my systemui and all that stuff.
I apologize I totally misread your post. Yes root is still possible but unlocking the bootloader is not at the moment.
Sent from my DROID RAZR HD using xda app-developers app
mryoung0042 said:
I apologize I totally misread your post. Yes root is still possible but unlocking the bootloader is not at the moment.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Maybe it'll be OK. Obviously it'd be best to be able to unlock the bootloader but I've been able to root the phone, install Safestrap and install a couple of "older" ROMs. For my purposes that's probably enough. I can run any app I want, I can eliminate the Navbar that I hate (using PIE Control instead) and I'm rid of the Verizon bloat. Not ideal but not terrible either.
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 ..
I've been working on some stuff on my own but I am stimm pretty vanilla about android development in general (although that doesnt mean I havent developed anything else). Anyhow, I just wanted to ask exactly what effect the bootloader has on installing roms and such. I realize that this prevents anything besides touchwiz roms but I would like to know the in depth. It is my understanding that a stock kernel is required but what else?
carlofabyss said:
I've been working on some stuff on my own but I am stimm pretty vanilla about android development in general (although that doesnt mean I havent developed anything else). Anyhow, I just wanted to ask exactly what effect the bootloader has on installing roms and such. I realize that this prevents anything besides touchwiz roms but I would like to know the in depth. It is my understanding that a stock kernel is required but what else?
Click to expand...
Click to collapse
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.
I guess I would check this out.
http://forum.xda-developers.com/sho....2] - I535VRUDNE1-Dump / Dev Discussion ONLY!
I would also pm the devs there if you really want to take this project over.
Good luck!
sjpritch25 said:
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.
Click to expand...
Click to collapse
Apologies, I didnt acknowledge that in my post, but I am well aware that yeah safestrap does not at all give you the same freedom. So wait how are you on the unlocked bootloader and stuck? That's interesting. Safestrap is essentially not an actually replacement to your stock recovery it just allows you to flash modified stock based roms to a rom slot if you are on a locked bootloader. But if you are unlocked then in theory you should be able to flash cwm and start fresh. Also being on ML1 however, shouldnt you be locked to begin with?
razz1 said:
I guess I would check this out.
http://forum.xda-developers.com/sho....2] - I535VRUDNE1-Dump / Dev Discussion ONLY!
I would also pm the devs there if you really want to take this project over.
Good luck!
Click to expand...
Click to collapse
This is interesting, I thought everything had pretty much been abandoned for either too much of a challenge or new devices. Thanks
sjpritch25 said:
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.
Click to expand...
Click to collapse
Same here. It's nice to be on an unlocked bootloader however. I'm on ML1 myself and never had any major issues. Safestrap basically allows you to use a different slot which doesn't touch the locked bootloader. On the 4.3 update which locked the bootloader there were several TW roms to chose from but when it comes to the newest baseband of NE1 your limited to stock and one other rom.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2