Related
I was doing some reading and came across this interesting article. I hope our devs can UN dm-verify our stock kernel.
It may make rooting future devices much more difficult. I wonder what bug crawled up Google's butt.
http://www.xda-developers.com/android/google-taking-aim-at-device-modders-in-android-4-4-kitkat/
Sent from my LG-D800 using XDA Premium HD app
There always seems to be work around on every new version but this looks like bad news. Read the whole thing. Scary stuff for locked bootloaders.
Sent from my VS980 4G using xda app-developers app
So do we get the pitchforks out and commence advance on LGs social media, etc? To get them to churn out an official build, of course.
It's a great phone and I bought it knowing they might not be quick on the draw. Didn't consider that 4.4 might make all these ROMs all for naught. Still, I needed a faster phone and this certainly fits the bill!
At same time I did know that short of a GSM Nexus that I couldn't have guarantee of latest Android.
I'm stuck on Verizon until March 2013. I can then slap a GSM Sim in, hopefully. But I paid retail so it's not like I want to buy a new phone anytime soon.
Well. I have myself to blame. Again. But I am off contract in March and this will never happen to me again!
Sent from my VS980 4G using Tapatalk
I am hopeful that when 4.4 comes out our devs will be able find a way for us to upgrade from 4.2 to a custom rooted 4.4 with out any issues. I do think that even stock unrooted this phone is fantastic it is carrier iq that is killing me. I'm sure att will put it in 4.4 also. Even though it was the carriers idea LG allows it to happen so I blame them also.
Sent from my LG-D800 using XDA Premium HD app
Are all G2s bootloader locked? Including the international D802? Or only the carrier branded ones?
Sent from my LG-D802 using xda premium
sacredsoul said:
Are all G2s bootloader locked? Including the international D802? Or only the carrier branded ones?
Sent from my LG-D802 using xda premium
Click to expand...
Click to collapse
LG to my knowledge locks the bootloader on all its devices regardless of carrier.
This is troubling. The reason I chose the G2 was because it was the closest thing to the Nexus 5 on Verizon and had good developer support. Hopefully our fantastic developers will figure out a solution.
From what I understand, unless we upgrade to the official 4.4 LG ROM, there is no chance of this happening. Is that correct ?
I guess I'm selling the g2 for the nexus 5
Sent from my LG-D800 using Tapatalk
This is rubbish man..
sidthegreatest said:
From what I understand, unless we upgrade to the official 4.4 LG ROM, there is no chance of this happening. Is that correct ?
Click to expand...
Click to collapse
That's my take on it. It is built into the 4.4 kernel. I wonder if this had anything to do with Google buying Motorola in August. Lock the phones way down for the carriers.
Sent from my LG-D800 using XDA Premium HD app
If there will not be a 4.4 rom within 3 months guess it is a dirty shot for those who bought it and want to buy it like me
Looks like I'll be rolling with Nexus devices from now on. I guess it was bound to happen though, I'm sure OEM's wanted another security layer because of bootloader work a rounds. On the upside though, there will be less threads on device release days asking for root and ROM ETA's!
Sent from my Nexus 7
the funny thing even though android are opensource, the phones and hardware are not. Thats where improvement is. If you create an abstraction layer, where due to propriatary stuff its closed and updateable by vendor. Another layer, the OS can go on top, thusly eliminating hardware dependancy as well as increasing updatability. OS and security issues can then more easily be adressed, without the now unduable vendor involvement needed in integrating the new OS with all the hardware specifics. Given the entropy rate of new phones coming out, its undoable. This last, as wel as commercial reasons is why updates and fixes for security holes dont come fast. As of yet.
Right now we see the true devs juggling various devices as the rate of entropy in new devices is higher then more true devs coming in. Devices not even picket up by community cause there are no devs for it. The breaking point has come.
A new design must be made for this momentum, a new standard
Sent from my LG-D802
The bootloader may be locked, but since custom recovery is available our kernel can be modified...so we should be okay...right?
Sent from my VS980 4G using Tapatalk
hhhmmmm not enjoying reading this thread
brucipher said:
The bootloader may be locked, but since custom recovery is available our kernel can be modified...so we should be okay...right?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
right. as long as you can flash custom kernels all this stuff should not be a problem.
it's about time to build some kitkat
KitKat has been out for like 5 days. Let's give the developers some time before everyone starts freaking out for no reason. They always find a way.
brucipher said:
The bootloader may be locked, but since custom recovery is available our kernel can be modified...so we should be okay...right?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I think people who are already rooted will be ok , they will just need to avoid the official 4.4 until a custom rom is built. The bigger problem will be for new unrooted owners. I would imagine it being tricky to flash a custom kernel without the ability to root. I also agree in time the devs will figure something out.
TheBiles said:
KitKat has been out for like 5 days. Let's give the developers some time before everyone starts freaking out for no reason. They always find a way.
Click to expand...
Click to collapse
Intub8 said:
I think people who are already rooted will be ok , they will just need to avoid the official 4.4 until a custom rom is built. The bigger problem will be for new unrooted owners. I would imagine it being tricky to flash a custom kernel without the ability to root. I also agree in time the devs will figure something out.
Click to expand...
Click to collapse
I just uninstalled recovery and was about to unroot and return to store, you guys gave me the slap in face I needed. Going to keep my badass phone now, thanks, drinks on me.
I'm considering buying this phone. Can anybody tell me where the DNA is with official OTA updates and whether or not it's unlockable and rootable? Thanks!
It doesn't have official kit kat, yet.
It is unlockable and rootable.
Thanks. So did it get 4.3? And if so, is it unlockable? I only like ask because the Note 2 and HTC One both got OTA 4.3 recently and neither bootloaders have been unlocked.
Sent from my SCH-I605 using xda app-developers app
GoodTimesDT said:
Thanks. So did it get 4.3? And if so, is it unlockable? I only like ask because the Note 2 and HTC One both got OTA 4.3 recently and neither bootloaders have been unlocked.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
The DNA recently got upgraded via OTA to sense 5, 4.2.2, and root/unlock ready. It is slated to get sense 5.5 and 4.4 kit Kat by march via ota. I would go with this phone, it's my favorite phone all around in a long time with the exception of the Sony Xperia Z but that's not available on Verizon.
Sent from my HTC6435LVW using xda app-developers app
GoodTimesDT said:
Thanks. So did it get 4.3? And if so, is it unlockable? I only like ask because the Note 2 and HTC One both got OTA 4.3 recently and neither bootloaders have been unlocked.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
It has not yet gotten 4.3 and probably won't I think if we get a update now it'll be 4.4 or just updates for bug fixes. As for dev support it's there all the way kicking butt and taking names lol. This device is very easy to unlock the bootloader and root if you have any experience at all with that sorta thing. Got this phone about 8 months ago and I don't regret it at all!!!
Sent from my dlx using Tapatalk
Awesome. Thanks to you all. I had the Incredible and Thunderbolt, then ventured off to the RAZR, GNex, and now Note 2.. All unlocked and rooted. And I have to say, I miss HTC. I like stock Android too though. And with the Note 2 being locked with its recent update, it is undesirable to put it nicely. Thanks again.
GoodTimesDT said:
Awesome. Thanks to you all. I had the Incredible and Thunderbolt, then ventured off to the RAZR, GNex, and now Note 2.. All unlocked and rooted. And I have to say, I miss HTC. I like stock Android too though. And with the Note 2 being locked with its recent update, it is undesirable to put it nicely. Thanks again.
Click to expand...
Click to collapse
Same with the GS4, the updates killed unlock. Fortunately I was able to unlock it befoer the update. In some way I feel sad for those who later bought the phone but couldn't unlock it.
I'm glad jcase and beaups have an unlock method for this phone that hasn't been thwarted. I'm surprised the DNA's continued unlockability, good porcessor, and great screen hasn't attracted far more people.
DNA will not receive official 4.3 and will leapfrog to 4.4 by end of march (as said by HTC on Twitter) pending Verizon approval. It is still 50/50 chance of us seeing 4.4 as Verizon has to approve it.
Verizon loves their devices locked down, so I am sure they are extremely peeved that rumrunner released so soon for our device. This means it may not receive 4.4 unless HTC finds a way to lock it down harder.
Sent from my DNA using my mind.
My power button crapped out on my S3 and I'm looking at the DNA. Know someone that may trade. I'm REALLY concerned about the 16 gb of internal only storage. What were they thinking!?
Sent from my SCH-I535 using xda app-developers app
kude87 said:
My power button crapped out on my S3 and I'm looking at the DNA. Know someone that may trade. I'm REALLY concerned about the 16 gb of internal only storage. What were they thinking!?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I had the same concern at first but I haven't had a problem it's hard to take up 16 gb on a phone unless your trying to
Sent from my HTC6500LVW using Tapatalk
Got the phone today..
So I got the phone today and it's currently running 4.1.1 / Sense 4+, 2.04.605.2 710RD. Should I just unlock it as such or update it and then unlock? Any input?
GoodTimesDT said:
So I got the phone today and it's currently running 4.1.1 / Sense 4+, 2.04.605.2 710RD. Should I just unlock it as such or update it and then unlock? Any input?
Click to expand...
Click to collapse
You could unlock now or later, the unlock method works non matter what firmware you're on :good:
If you want to run the stock OTA 4.2 update you might want to update first and the root. I have heard people having problems with the OTA update failing with rooted phones.
I was already rooted and installed an image of the update from the dev forum.
Sent from my HTC6435LVW using xda app-developers app
GoodTimesDT said:
So I got the phone today and it's currently running 4.1.1 / Sense 4+, 2.04.605.2 710RD. Should I just unlock it as such or update it and then unlock? Any input?
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=2584151
I got mine today, and these instructions worked perfectly. Someone helped me there and had great responses. Give him the thanks.
Sent from my HTC6435LVW using xda app-developers app
kude87 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2584151
I got mine today, and these instructions worked perfectly. Someone helped me there and had great responses. Give him the thanks.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks! I actually already did it just a little while ago. I took one OTA update which brought me up to 2.06.x and then I just used moonshine.. Worked flawlessly.
GoodTimesDT said:
Thanks! I actually already did it just a little while ago. I took one OTA update which brought me up to 2.06.x and then I just used moonshine.. Worked flawlessly.
Click to expand...
Click to collapse
Same here. I just de-bloated everything and am messing with xposed already. This phone smokes my S3 in terms of feeling fluid. That touchwiz interface was laggy unless I had CM11, and then had camera and signal issues. Pretty happy right now, even though I gave up my SD card. :thumbup:
Sent from my HTC6435LVW using xda app-developers app
GoodTimesDT said:
Thanks! I actually already did it just a little while ago. I took one OTA update which brought me up to 2.06.x and then I just used moonshine.. Worked flawlessly.
Click to expand...
Click to collapse
Nice, enjoy. I love mine and have plenty of space with the CM11 snapshot from 1/4.
The DNA is truly a great device, I don't see myself replacing it for a long time (unless it breaks)
With the latest OTA, the DNA is finally unlockable/rootable with the rumrunner method. I actually just s-off'd mine something like 10 minutes ago.
Axinex said:
With the latest OTA, the DNA is finally unlockable/rootable with the rumrunner method. I actually just s-off'd mine something like 10 minutes ago.
Click to expand...
Click to collapse
what do you mean finally? weve been rootable since the original release date(minus about 3 months)
All,
I have the Verizon Galaxy S4 Developer Edition. I purchased this one b/c it had an unlocked bootloader and I like to install custom recoveries so I can install custom ROMs. Originally, it came with the MDK firmware on it and I was able to root it and install a custom recovery.
I applied the OTA MJ7 update. While I am able to root the device, I have not been able to install a custom recovery. After doing a ton of reading and soft bricking, everyone says that the latest firmware locks down the bootloader so that you cannot install custom recoveries.
Here lies my confusion...I bought the Developer Edition so my bootloader would never be locked and I could always install custom recoveries. Is there something I'm missing? Is it possible for me having a Developer Edition phone to install a custom recovery even though I'm on build I545VRUEMJ7?
In talking with Samsung support, they said that the bootloader will NEVER be locked with any updates on the Developer edition. Any information or help is much appreciated.
Thanks,
Jonathan
Where did you purchase it from?
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
Where did you purchase it from?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I purchased it directly from the Samsung website. I tried to post the link but it wouldn't let me since I haven't made enough posts. If you google "galaxy s4 developer edition", it is the first non-advertised link that shows up. That's where I purchased it from.
If you take the cover and battery out, it says Developer Edition on the phone.
jontjioe said:
I purchased it directly from the Samsung website. I tried to post the link but it wouldn't let me since I haven't made enough posts. If you google "galaxy s4 developer edition", it is the first non-advertised link that shows up. That's where I purchased it from.
If you take the cover and battery out, it says Developer Edition on the phone.
Click to expand...
Click to collapse
As i understand it when you took the update it locked your bootloader, but please anyone correct me if im wrong
See that's what I thought too... That the update possibly locked my bootloader but how can I check if it is locked or not?
Sent from my SCH-I545 using xda app-developers app
michaelg117 said:
As i understand it when you took the update it locked your bootloader, but please anyone correct me if im wrong
Click to expand...
Click to collapse
Thats what I've heard too. I'm no expert in the Dev S4, but I think I've seen a thread or two stating the same kind of problem. Which is crazy if you ask me.
Edit
I know Surge1223 I think posted the Dev Edition MDK firmware somewhere on here, I suggest maybe checking with him, maybe you can flash that back in your phone and be good?!
If nothing else, find that thread and ask him what to do... My guess is he'll have an answer for you.
I've read that it can re lock your phone and ive also read that the updates will not lock it up.... So I'm not really sure.
Good luck though!!!
Sent from my SCH-I545 using XDA Premium 4 mobile app
jontjioe said:
See that's what I thought too... That the update possibly locked my bootloader but how can I check if it is locked or not?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
If you took the OTA, you no longer have the same bootloader and in effect locked the bootloader on your phone. Far as I know.
safestrap enabled, Hyperdrive driven
jontjioe said:
All,
I have the Verizon Galaxy S4 Developer Edition. I purchased this one b/c it had an unlocked bootloader and I like to install custom recoveries so I can install custom ROMs. Originally, it came with the MDK firmware on it and I was able to root it and install a custom recovery.
I applied the OTA MJ7 update. While I am able to root the device, I have not been able to install a custom recovery. After doing a ton of reading and soft bricking, everyone says that the latest firmware locks down the bootloader so that you cannot install custom recoveries.
Here lies my confusion...I bought the Developer Edition so my bootloader would never be locked and I could always install custom recoveries. Is there something I'm missing? Is it possible for me having a Developer Edition phone to install a custom recovery even though I'm on build I545VRUEMJ7?
In talking with Samsung support, they said that the bootloader will NEVER be locked with any updates on the Developer edition. Any information or help is much appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
You locked your bootloader.
You used ODIN to install a MJ7 OTA file?
Consumer firmware can be installed on a Dev. edition, but it locks the bootloader.
They should have said something about that. They didn't?
I don't think you are going to get anywhere with support unless you send the phone back for a replacement. IMHO
tech_head said:
You locked your bootloader.
You used ODIN to install a MJ7 OTA file?
Consumer firmware can be installed on a Dev. edition, but it locks the bootloader.
They should have said something about that. They didn't?
I don't think you are going to get anywhere with support unless you send the phone back for a replacement. IMHO
Click to expand...
Click to collapse
Yeah, I used ODIN to flash MJ7. Sucks. I will just have to be more patient next time and not flash the latest thing right away. Seems like it is taking forever for someone to crack this bootloader.
jontjioe said:
Yeah, I used ODIN to flash MJ7. Sucks. I will just have to be more patient next time and not flash the latest thing right away. Seems like it is taking forever for someone to crack this bootloader.
Click to expand...
Click to collapse
most likely, the bootloader won't be cracked. Too much security in place
decaturbob said:
most likely, the bootloader won't be cracked. Too much security in place
Click to expand...
Click to collapse
How bad is it that people like him hey a Dev Edition that SHOULD always stay unlocked in my opinion, then are able to lock it back up?!?!
To me that's ridiculous. I'd be more than pissed if that was me.
There was a thread somewhere on here containing a conversation between that person and Samsung I think, and the Sammy rep told that person that the Dev Edition would never be locked even through any OTA.
Seems like such a circle jerk dealing with those people, I've fired off a couple emails myself just for laughs to Samsung about various things, and that's all they do is BS us.
What a shame, a Dev S4 that is just like my locked up mj7 S4.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I am an owner of a DevS4. What the OP did was definitely not a good thing. The DevS4 came originally with I545OYUAMDK. The retail S4 came with I545VRUAMDK. The only difference is that the DevS4 has a different ABOOT partition which allows for the unlocking. By applying the MJ7 OTA or ODIN file he essentially over-wrote his ABOOT partition, locking his phone down and turning it into a regular retail S4. The DevS4's are now sold with I545OYUEMJ7 - he applied I545VRUEMJ7. Unless Samsung will help him out by flashing the firmware to his phone so he can go back to Developer state, he is SOL with a DevS4 now turned into a locked down retail S4.
I only say this based on what I have seen/witnessed.
I've seen this happen before and Samsung took the phone and flashed the correct firmware, not saying you'll be so lucky but search around and you may find what I'm remembering.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Crazy. Dev edition phones should have an efuse that prevents locking. Trying to flash locked firmware should fail.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Crazy. Dev edition phones should have an efuse that prevents locking. Trying to flash locked firmware should fail.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Exactly. Lot of money for something that can easily be screwed up.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Just goes to show they don't have a real interest in a Dev device.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Just goes to show they don't have a real interest in a Dev device.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Not so sure if it a case of not having interest, I just don't think they thought it out fully. They produced them and spent the money investing in it. There is a Note 3 Developer edition as well. They just didn't fully think out the implications of support, updating, etc. Which is a shame. The Samsung Developer Device program could have been huge if it was executed properly. To take a retail device, change a few letters from "VRE" to "OYU", slap a sticker on it and call it a developer device, while it still contains KNOX and other developer unfriendly aspects was poor execution.
Maybe there should be a caution sticky here to not ODIN Consumer Ed images onto Dev Ed devices.
Its odd that Samsung even has this program but I guess they want devs to create Samsung Apps for carrier devices.
Skeetch79 said:
Not so sure if it a case of not having interest, I just don't think they thought it out fully. They produced them and spent the money investing in it. There is a Note 3 Developer edition as well. They just didn't fully think out the implications of support, updating, etc. Which is a shame. The Samsung Developer Device program could have been huge if it was executed properly. To take a retail device, change a few letters from "VRE" to "OYU", slap a sticker on it and call it a developer device, while it still contains KNOX and other developer unfriendly aspects was poor execution.
Click to expand...
Click to collapse
DEV owners gotta understand wtf they are doing
Listen I feel sorry for the OP but it's completely his fault for flashing a consumer device image. I know if I were Samsung I wouldn't expect people who buy DEVELOPER editions to do something as silly as that.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hey guys,
I apologize in advance if i am not up to speed on all the posts and news of S4 development.
My Verizon S4, is still running ME7 and i guess i keep waiting to get unlocked bootloader but it seems that probably will never happen since there are so many builds beyond that already.
Just to verify, ME7 and any of the later builds still have locked bootloader is that right?
Would you guy recommend that i do the update and switch to something newer? Hyperdrive is great, but running it through Safestrap is not ideal. At the same time i don't want just running a stock TouchWiz, which is the worst every.
Anyway, i am sorry if these are newb questions.
stamina11 said:
Hey guys,
I apologize in advance if i am not up to speed on all the posts and news of S4 development.
My Verizon S4, is still running ME7 and i guess i keep waiting to get unlocked bootloader but it seems that probably will never happen since there are so many builds beyond that already.
Just to verify, ME7 and any of the later builds still have locked bootloader is that right?
Would you guy recommend that i do the update and switch to something newer? Hyperdrive is great, but running it through Safestrap is not ideal. At the same time i don't want just running a stock TouchWiz, which is the worst every.
Anyway, i am sorry if these are newb questions.
Click to expand...
Click to collapse
I really don't understand your comment on Hyperdrive and safestrap. I can go nearly 48hrs between charging my battery...I can customize to my heart content...everything works with no fcs. ..no reboots. You are definitely out of the loop
Sent from my SCH-I545 using XDA Premium 4 mobile app
stamina11 said:
Hey guys,
I apologize in advance if i am not up to speed on all the posts and news of S4 development.
My Verizon S4, is still running ME7 and i guess i keep waiting to get unlocked bootloader but it seems that probably will never happen since there are so many builds beyond that already.
Just to verify, ME7 and any of the later builds still have locked bootloader is that right?
Would you guy recommend that i do the update and switch to something newer? Hyperdrive is great, but running it through Safestrap is not ideal. At the same time i don't want just running a stock TouchWiz, which is the worst every.
Anyway, i am sorry if these are newb questions.
Click to expand...
Click to collapse
Glad I found your post, as I have been laying low for a while now and had the EXACT same question! I've been on HyperDrive RLS9.1 for a few months and, while I'm totally happy with it, I'm getting the itch to flash. I know the "ROMs that work with SS/ME7" thread is no longer updated and since 4.4.2 leaked, I'm wondering the same thing as you: would it be wise to update the OS past ME7? I'm pissed that as soon as I got my phone I let it OTA to ME7, but I had read everyone talking about NOT updating as they would likely lock out SS and such.
So, if I update (or flash) to a newer version, are there any significant benefits, or should I stick on ME7?
adamklo said:
Glad I found your post, as I have been laying low for a while now and had the EXACT same question! I've been on HyperDrive RLS9.1 for a few months and, while I'm totally happy with it, I'm getting the itch to flash. I know the "ROMs that work with SS/ME7" thread is no longer updated and since 4.4.2 leaked, I'm wondering the same thing as you: would it be wise to update the OS past ME7? I'm pissed that as soon as I got my phone I let it OTA to ME7, but I had read everyone talking about NOT updating as they would likely lock out SS and such.
So, if I update (or flash) to a newer version, are there any significant benefits, or should I stick on ME7?
Click to expand...
Click to collapse
Right now you can still use SafeStrap with the updated bootloaders. And there are more ROM options for you too. Yes you will update your bootloader to a Knox one but people are still actively trying to find an exploit on those. If you want my opinion yea go ahead and update... But think about it in the end its your call
Sent from my unknown using Tapatalk
Can you point me to a thread that can walk me through the latest update/upgrade process?
Sent from my SCH-I545 using Tapatalk 4
It's been two months since I posted last. My original question still remains: can someone show/tell me the process to upgrade my VZW S4 ME7 to a more recent build and the ROMs that available for it?
Sent from my SCH-I545 using Tapatalk 4
adamklo said:
It's been two months since I posted last. My original question still remains: can someone show/tell me the process to upgrade my VZW S4 ME7 to a more recent build and the ROMs that available for it?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
There are threads and videos available to check out so in 2 months you haven't research anything?
sent by safestrap enabled bajarom
There's a lot going on and it's very overwhelming.
Sent from my SCH-I545 using Tapatalk 4
So I did a little searching before posting so don't ream me please ??
1) Does the dev edition s4 also have a locked bootloader? That would be f'in whack.. If it us unlocked and my second q doesn't pan I may try and swoop one up. ..
2) I have a friend with a tmobile s4 that he cracked the digitizer and just reported it lost... If I took his board could I unlock it to big red? If so what would be the consequences?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Zooandbio4me said:
So I did a little searching before posting so don't ream me please ??
1) Does the dev edition s4 also have a locked bootloader? That would be f'in whack.. If it us unlocked and my second q doesn't pan I may try and swoop one up. ..
2) I have a friend with a tmobile s4 that he cracked the digitizer and just reported it lost... If I took his board could I unlock it to big red? If so what would be the consequences?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The Dev Edition S4 normally does not have a locked bootloader. I say normally because some users took an Over The Air update which did lock the bootloader. So it depends on whether the bootloader is a stock MDK bootloader or if the user took a subsequent OTA update which in turn locked / changed the bootloader. Also, there is no factor image for the Dev Edition, so if it is locked it is going to stay locked for the foreseeable future. As for your second question, I'm not sure that will work. I think the firmware differences between TMO and Verizon plus the difference between GSM and CDMA will not be easy to overcome. But I don't know that for sure.
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe. The users who locked then up did so by using Odin and retail firmware.
Just throwing that out there.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe. The users who locked then up did so by using Odin and retail firmware.
Just throwing that out there.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I don't take that as you being a know it all, you're probably right. I just know some Dev owners did something to lock their bootloaders I just assumed (wrongfully) that it was an OTA of some sorts. Sorry for the misinformation.
Mistertac said:
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe.
Click to expand...
Click to collapse
I know one user who received his DevEd about the same time as me. He received an OTA that locked his bootloader. I have never received an OTA, and I'm still running stock (more or less) DevEd.
It's funny how I bought the DevEd, because I wanted a guarantee that I could ROM the device. But I fell in love with the stock OS, and don't care if I ever have KitKat.
asharad said:
I know one user who received his DevEd about the same time as me. He received an OTA that locked his bootloader. I have never received an OTA, and I'm still running stock (more or less) DevEd.
It's funny how I bought the DevEd, because I wanted a guarantee that I could ROM the device. But I fell in love with the stock OS, and don't care if I ever have KitKat.
Click to expand...
Click to collapse
No kidding? I didn't know any of them got OTAs. At least you have the option to flash whatever you want if you did get bored with stock.
Sent from my SCH-I545 using Tapatalk