yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 General] kprice8:
Believe I just heard about Sprint this morning on the radio that you can get a Galaxy S5 from them at 0% interest for 24 months (2 year contract length at a price of $27.02/month) and a plan from them as well. So expect to pay anywhere from $65-90 to them/month INCLUDING the price for the phone with the monthly bill +taxes. Hope this helps.
[Verizon Galaxy S 5 General] thuddome:
+1
[Verizon Galaxy S 5 General] Dennisg34:
Not sure about TWRP but if you buy the developer S5 it will be rooted already..
[Verizon Galaxy S 5 General] thuddome:
Not so fast, bootloader unlocked, not rooted
[Verizon Galaxy S 5 General] claytonjn:
Right, but if that build of TWRP will work then it's as easy as flashing SuperSU or equivalent.

I know a lot of ROMs switched over to universal jflte builds for the S4 rather than carrier specific (jfltevzw) builds, so I was hoping that was the case for TWRP with the S5.
[Verizon Galaxy S 5 General] thuddome:
The bounty for root on the S5 is at $12,000, guessing it's not that easy. My S4 (MDK) was that easy. S5 Dev will be here tomorrow. We'll see.
[Verizon Galaxy S 5 General] Dennisg34:
BL unlocked and can be rooted, hint why it's a dev edition

S4 took a out 3-4 weeks, which is about how long the S5 has been out. This is phone has lots more security so it'll take a little longer
[Verizon Galaxy S 5 General] claytonjn:
It's not that easy if the bootloader is locked, and the lock is encrypted. If the bootloader is unlocked/unencrypted like with a Nexus device or Developer Edition then it's as easy as getting a custom recovery because in recovery you have root access so you can flash a SU binary for root access in the ROM.
[Verizon Galaxy S 5 General] firejackson:
Well I'm not worked about getting the s5 just bought it for Verizon from bestbuy of contract to keep my unlimited data so I can just return it get the sprint one start a plan with sprint and should be good to go no contract right

---------- Post added at 04:03 AM ---------- Previous post was at 03:59 AM ----------

Or does anyone know is a sprint gs5 would work on ting
[Verizon Galaxy S 5 General] thuddome:
Here's the root method, just like the S4 (MDK) - http://xdaforums.com/showpost.php?p=52497162&postcount=9
[Verizon Galaxy S 5 General] droidstyle:
Yes but you need a compatible recovery to flash the superuser.zip to root. i am guessing the the T-mobile S5 twrp recovery will work as the T-mo N3 twrp recovery did for the VZW N3.
[Verizon Galaxy S 5 General] McAtom:
Future Upgrades?

So I just ordered the S5 Dev and it should be here tomorrow... But at the time of ordering I didn't realize how piss poor Samsung is about releasing updates / supporting their dev phones and it is concerning me.

How hard will it be to update to android 4.5... 4.6? 5.0? Is there any way to pick apart their OTAs for the non-dev and port that to our dev phones without losing unlocked status? I hope to keep my next phone for a couple of years at least and if I can't upgrade my android version that will devalue the dev edition significantly.

How hard would it be for someone with limited knowledge to pick up the ROMs that they make for the non-vz devices and convert them to vz dev? I've been itching to get into development for some time now and would be willing to learn, however I'm a noob at development so It'll be a learning curve for sure.

Do the files exist that we'd need to customize the kernel or do a debloated ROM?

On the lines of the last question, how hard is it to get an odin file for the dev edition? I'd like to be able to flash back to factory in case I port a rom wrong and flash it and it softbricks me. Is this what the custom recovery is for? So we can make a backup of all partitions and flash back?
[Verizon Galaxy S 5 General] kprice8:
No disrespect meant to you with my question I am about to pose. But did you read the other posts regarding this Edition(Addition) of phone and the posts contained herein?
[Verizon Galaxy S 5 General] claytonjn:
Awesome, I thought it would be that easy... ordering now!
[Verizon Galaxy S 5 General] Skeetch79:
Owning a Developer Device from Samsung, get very familiar with the phrase "Red Headed Step Child"

Your offiicial firmware will forever be stuck on what it is shipped with, in this case with the DevS5 4.4.2. You can piece meal files together to create your own updates/ROMs if you are so adventurous, just do not overwrite your ABOOT ever or the boot partition with a retail verison...your phone will then be locked without any support to unlock it.

Samsung has never and will never post ODIN files or recovery files for the developer devices. Once you achieve root, I am sure you can surely tweak your kernel with some of the apps and files out there. Either find a debloated ROM or create one yourself. Again, do not mess with installing non-dev boot files or overwriting your ABOOT (therein lies the secret to unlocking your device - hence botch up your ABOOT, possibly risk locking your phone)

Again, Developer Edition devices for Samsung have no ODIN tars available. None officially for that matter, maybe some that have been created by the community, but nothing official.

So first thing to do after rooting your phone is to dd all your partitions (back them up). That way if you ever need to recover you have your own files to recover from. Also, before flashing ROM's...make a nandroid backup.

I have the DevS4 and wish I could sell it yesterday. The Developer program from Samsung is horrible. Moto and HTC at least support their developer devices.
[Verizon Galaxy S 5 General] McAtom:
None taken, and I did - I guess I should clarify, my questions are more around if I wanted to get into development for the vz dev phone, how hard would it be? Would it even be possible with the files we have?

Thanks for bearing with me, I'm totally new to development and am not 100% up on the terms / parts. I'm slowly learning.

Thanks for the reply! That's disheartening... Gives me a bit to noodle on, may be that I chose the wrong company to go with a dev device on. :(

Appreciate the info!
[Verizon Galaxy S 5 General] thegrants82:
I actually jumped the gun with purchasing my Dev S5. Returning it next week.
[Verizon Galaxy S 5 General] Skeetch79:
I don't want to force anyone to not get the Dev S5 or change their minds about it. I simply state my experience and gripes....if you want a good phone with an unlocked bootloader and don't care about OTA's or updates then don't necessarily stray away from the phone.

Why would you return it?

---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------

I don't want to sway your decision. I guess I am just passionate about my gripes. The galaxy S4/S5 is a solid device.
[Verizon Galaxy S 5 General] thuddome:
For all the guys who are contemplating a Dev model; I have the opposite opinion. I have the Dev S4 (MDK) and haven't had any issues. I don't have to run Safestrap, I haven't had the majority of the problems everyone else has (I think mostly caused by safestrap) and life is good (running Hyperdrive 15, waiting for 16 - 4.4.2). I think there was 2 or 3 different Dev models of the S4 and I think the majority of the issues you are referring to were the later Dev models. Getting OTA or official updates doesn't matter to me because I run custom ROMs which have the OTA disabled anyway and the custom ROMs are usually months ahead of Samsung's official releases anyway. Concerning your phone getting "locked" I had never even heard of that until this thread. I know that Samsung created a counter for how many times you reset the phone but there's the Triangle app to reset that and even if you didn't reset it who cares how many times you've reset it (unless you want to get Samsung's support, who does that)? Maybe it's just been blind luck for me but I can show you a lot of guys who want my MDK version of the S4 because they are tired of the issues with safestrap and not having an unlocked phone. As I posted already in this thread, we already have custom recovery and root working on the Dev S5. There's already multiple S5 custom ROMs created for other carriers, I would think Verizon ROMs would be soon to come.
[Verizon Galaxy S 5 General] Skeetch79:
You never had any of the issues stated and can shy away from SafeStrap because you are still on MDK. Once they updated to MJ7 and MK2, things changed. On MDK, things were still fine - loki exploit still existed. On either MJ7 or MK2 Philz seemed to work nearly 100% of the time whereas TWRP was hit or miss. SafeStrap always seemed to work, even though it used TWRP for its recovery. Samsung updated the devices at the factory before sale once a new Android Version came out. Couple that with the absence of software updates for the DevS4 and you have the current situation - various Android Versions across the board for the DevS4 and it never received an OTA, just an update before sale. I have seen the recoveries and ROMs and those are definitely working solutions. I just wish Samsung had thought more about their developer program and supported the devices like Moto and HTC do for theirs.
[Verizon Galaxy S 5 General] McAtom:
Just got off the phone with support

Hey guys, quick update - Just got off the phone with Samsung Tech support, I wanted to get an 'official' Samsung rep to answer, and they did.

Question: What happens if I accidentally 're-lock' my developer device, am I hosed?

Answer (Paraphrased): If a device is flashed incorrectly and re-locked, it will be possible to either ship the device back to Samsung and have it re-unlocked, or go to a local store and have them re-unlock it.

Followup Question: If that needed to be done, what would the fee be?

Answer: (Paraphrased): There would be no fee for the software, though if any internal parts or hardware needed replacing there would be a fee for that.

However, as we all know, if it isn't in writing it didn't happen, so I've put an email request in with that question as well as a question around android version upgrades, and I'll update this thread with their reply.
[Verizon Galaxy S 5 General] thuddome:
Also in the essence of full disclosure, my company pays for all my phones and such so getting the Dev S5 is not a financial issue for me. My S4 with Hyperdrive is fantastic so it will be a while before I give it up. It's going to be an interesting comparison - S4 MDK w/ Hypderdrive 16 (4.4.2) vs S5 Dev w/ stock 4.4.2.
[Verizon Galaxy S 5 General] KarlStyles:
Good to know, hopefully the email you receive has the same answer. Thanks for checking that out!
[Verizon Galaxy S 5 General] thegrants82:
You didn't sway me. I jumped the gun before researching it. Over the last 48 hours I have read nothing positive about Samsung support with their Developer phones. Hardware and software. I wouldn't have imagined that it was actually that bad but apparently it is. I don't see any advantage to purchasing a Samsung Dev unit for any long term use after researching it more thoroughly. My bad. I have had Dev units in the past but not from Samsung. The S4/S5 are solid devices, no doubt but the Samsung Dev program is a joke.
[Verizon Galaxy S 5 General] razzrmaxx:
Who cares about Samsung dev program, we got XDA-Developers
[Verizon Galaxy S 5 General] hEaTLoE:
If you're ready to purchase a phone outright though, why not go for the Dev device? If there's NOTHING out there to crack the retail phones and you finally want to update, just flash the retail OTA and then you'll have the same retail phone as everyone else. That's my thought process anyway.
[Verizon Galaxy S 5 General] Skeetch79:
Flash the retail OTA and lock your phone down. Flash the retail ODIN and you will lock your phone down.You WILL have a retail phone. Say goodbye to ever really getting your Dev mode back again, unless Samsung tech support has real sympathy for you and will take their time to re-unlock the device after you send it to them.
[Verizon Galaxy S 5 General] hEaTLoE:
100% correct, but then it's no worse off than starting with a retail device from the get-go. At least you have the opportunity to play with the phone and flash ROMs (less ABOOT) which to me is worth it. If you're paying $600 for either, the Dev is better IMO unless warranty is a concern.
[Verizon Galaxy S 5 General] thuddome:
And to add to this, ODIN is only an issue if you want to flash official Samsung stock tar files which is usually not the case for the average guy. That's why we all want an unlocked phone is to get away from the stock images. So here's the bottom line, if you are wanting to develop your own ROMs and need to flash the official ROMs to start your build then the Dev version from Samsung in somewhat of a pain with the possible locking and having to have Samsung re-flash/unlock for ya. For the average guy who just wants to install .zip custom ROMs created by someone else you probably won't ever have any issues with ODIN or locking.
[Verizon Galaxy S 5 General] equake:
Where did you email to? I doubt you will get any answer. They will probably state that it's up to Verizon or something to that nature.

My 2 cents
[Verizon Galaxy S 5 General] ravenofdoom:
Except that if you're on a Dev edition build, your chances are slim to none of every getting an OS / kernel upgrade. You'll likely be stuck on 4.4.2 for all eternity (much like how the GS4 Dev I believe is still stuck on 4.2.2 because Samsung has historically provided zero support for updates to the OS that maintains unlocked bootloader).

I personally would take my chances having root and hoping for safestrap on a retail version with a warranty than living on a Dev edition device that is locked onto one official OS/kernel. Yes, you can update to other custom ROMS, but the kernel will still be on whatever the phone was at the time of purchase... so no better off than folks who might have retail + safestrap (if that happens). And yes, you could always flash retail atop your dev edition device, but what the heck's the point of that (probably will have to send the phone back at your cost to Korea for them to re-unlock it on 4.4.2 OS/kernel by the time Android 5.0 is already out for retail, but unavailable to Dev Ed to stay unlocked).
[Verizon Galaxy S 5 General] thuddome:
I'm running 4.4.2 on my Dev S4, everything is fine. And you can call me on it, I think I uploaded a screen on this thread.
[Verizon Galaxy S 5 General] ravenofdoom:
Is 4.4.2 that you're running a TW/Samsung OTA build? If not, what're you running? At least my concern is that there's no pathway for running stock OTA, but at the same time having the unlocked bootloader for easy root. A GPE rom might be nice, but it'd still be a carry-over from GSM with slipped in radios (and potential for bugs / radio issues, which I've experienced in the past) on Verizon.
[Verizon Galaxy S 5 General] thuddome:
I was running Hyperdrive 15 (4.3) which anytime soon should be 16 with 4.4.2 but loaded VRUFNC2 and it's fine, no problems. If you want to run stock with OTA then get a retail S5. The entire point of Dev is for custom ROMs. I don't understand this argument of I want everything unlocked (dev version) but I want to run stock with OTA????? [MENTION=4600715]sbreen94[/MENTION] - With Hyperdrive you get OTA, that's how he rolls... :highfive:
[Verizon Galaxy S 5 General] Skeetch79:
You are correct that there were never any over the air updates for the developer version. But as time went on samsung updated the developer devices at the factory as new builds came out. The result was one phone with numerous build versions depending on when it was sold. The Developer has only seen versions: I545OYUAMDK (4.2.2)(initial build), I545OYUEMJ7 (4.3), I545OYUEMK2 (4.3)(latest build). I believe that if the community could, they could put together an update for all developer s4 devices to upgrade to MK2.
[Verizon Galaxy S 5 General] McAtom:
Apologies for my naivety, I genuinely don't know the answers to these and am trying to learn.

What stops us from extracting the newer android versions and putting them on our dev versions without overwriting aboot? Do we lose unlocked status if we overwrite anything else, or is it just aboot we have to leave untouched?

Also, what about AOSP, would it be possible to port later versions of android AOSP to the dev. edition?

Why are we locked into one kernel? Is there something that stops us from modifying the kernel or porting a kexec kernel?

Thanks in advance!
[Verizon Galaxy S 5 General] thuddome:
S4 Dev running 4.4.2 with latest kernel. Runs great!
[Verizon Galaxy S 5 General] thuddome:
Nice!
[Verizon Galaxy S 5 General] markwebb:
And what is your secret to this?
[Verizon Galaxy S 5 General] equake:
Note that he is running a leaked build and not the official OTA build of 4.4.2.
[Verizon Galaxy S 5 General] thuddome:
Here's the build, no secret - http://xdaforums.com/showthread.php?t=2721118

---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------

This was a response to the statement that you couldn't run 4.4.2 on the S4 Dev phone. For some reason everyone thinks you cannot upgrade the build on a Dev phone which is completely false.
[Verizon Galaxy S 5 General] thuddome:
I thought more about your question. I think the answer is in which S4 do you have. I have the original, first developer model (MDK). As far as I know this was the only true dev model. I see on here other guys saying the MK2 and MJK or whatever were dev models but their devices were not loki'd so I would say they aren't really dev models. If you look at the screen shot I posted, I'm running the latest kernel and the latest official build from Verizon. It was specifically built for MDK. It runs perfect, no issues at all. I'm waiting for Hyperdrive 16 which will also be 4.4.2 and I will load it on my MDK which will be as simple as flashing the zip. I do not run safestrap nor do I need to. I was on 4.3 but ran into a few issues which the entire world was seeing so I jumped to this MDK built 4.4.2 which is nothing more than the Verizon build right out of the box.

So let me explain what's going on here, the guys that keep saying "dev phone doesn't have an OTA or official build" these are the guys that had the MK2 versions of the S4. They are having to run safestrap which by what I'm seeing on here, causes a ton of issues so they want updates from Samsung OTA or an official build release. They are stuck because they can't just flash anything, they have to have safestrap builds. Which Samsung will never create. With the MDK I can flash anything pretty much. On my S4 I started running Hyperdrive RLS1 and now we are on 16, so every version of Android you can think of. All the different versions have ran without issue for the most part, any issues were related to the ROM, not the phone. I don't care if Samsung has an OTA or Official build because I can get ROMs that are way ahead of Samsung's release if they even had one and our custom ROMs are better anyway.

I hope this helps, I know there's a lot of confusion on here, there always is. I've been doing this a long time. We've been through all this before with HTC and others with locked boot loaders and such, it always works itself out or we make it work. Safestrap is an example of that, it's a work around for phones that are locked.
[Verizon Galaxy S 5 General] Skeetch79:
The unfortunate thing with the Developer units is that they run the same exact software as the consumer units. Dev MDK = consumer MDK, Dev MK2 = consumer MK2, etc etc. So what you said is kind of true. The loki exploit that was present for consumer MDK was present for Dev MDK, once MJ7 and MK2 rolled around, the loki exploit was patched not only for consumer S4 but also Dev S4. I for one, am a victim of that. I was able to be upgraded to MJ7 then MK2 and noticed how wrong a decision that was. IU wanted the latest Android version and didn't think that it would introduce any difficulties or frustrations since I had a Dev unit. MDK was definitely more liberal and forgiving when it came to running ROMs and custom recovery. MJ7 and MK2 was hit or miss with recoveries. Basically Philz Touch recovery ran great 99.9% of the time while TWRP was definitely hit or miss and SafeStrap worked fine as well (even with having TWRP as its recovery). With MJ7 and MK2 you only could, for the most part, TouchWiz based ROMs, nothing else really seemed to jive all that well, even with using SafeStrap. MDK was definitely the better Android version to stay with as far as flexibility went.

Buying an MDK Dev S4 unit from Samsung is near impossible, since they update their Dev devices as newer iterations of android are released. Which, as I have said earlier, leads to the situation we see: some Dev S4 owners have MDK (they bought the device when it first came out), some Dev S4 owners have MJ7 and some have MK2 (they bought the device more recently).

Quick Poll though: Do you think KitKat would be worthwhile or desirable for the Dev S4?
[Verizon Galaxy S 5 General] thuddome:
I have both the S4 MDK and the S5 Dev, both running Kitkat. IMO I would stay with the S4 because there's more development for it now. The only difference with the S5 is the slightly bigger screen, waterproofness, heartbeat monitor, and the better camera. I'm actively using the S5 but as soon as Hyperdrive 16 drops I'll be jumping back over to the S4. I've got Xposed and everything running on my S5 and there's not much novelty in using the S5. Hyperdrive ROMs are great and I'm anxious to see Scott's work, running 4.4.2 is secondary for me.

BTW, you are right, I got my Dev S4 2 weeks before the initial S4 consumer version dropped.
[Verizon Galaxy S 5 General] equake:
I definitely think KitKat is good for the Dev S4. There are some caveats such as SD support and other quirks.
[Verizon Galaxy S 5 General] Skeetch79:
As far as SD support is concerned, maybe since we can root our device then that could be worked out.
[Verizon Galaxy S 5 General] Droid9684:
Cant root this device on mac..... help?

I've tried to run JOdin3 on here and the software didnt work properly and I'm not able to use crossover or Wine on Mac. Nor do I have access to windows computer. I've been stuck on stock since delivery on May 12th. I have ADB for Mac installed along with Kies3. Any suggestions?

I couldn't get TWRP tar file to flash in JODIN3 on Mac.

https://www.dropbox.com/s/dyqi3q00ta...2013.17.17.jpg

I followed this video except i had to download ojdin3 because website version was a blank screen.

https://www.youtube.com/watch?v=MiPR...e_gdata_player
[Verizon Galaxy S 5 General] ajent:
I'm looking to buy a new VZW phone to replace my razr hd maxx. Since I have unlimited data I have to buy the phones outright, so was thinking about GS5 developer edition. I also have unlimited AT&T plan, and noticed the GS5 shows LTE band 4,13.

One of AT&T's LTE bands is also 4, so this would be excellent if it worked. Can the VZW GS5 run on AT&T after carrier unlock, with AT&T LTE?

thanks :good:
[Verizon Galaxy S 5 General] razzrmaxx:
Hi there, I was in your shoes about a month ago with and unlocked Razr maxx HD which I still have with a broken screen so I went ahead and bought the s5 dev and I was able to get everything I had on my maxx hd and I love this phone. These are some of the apps I have and mods I got on it so far & this is what it looks like on my stock self moded s5 dev, I can't wait for them custom roms to hit the paypal market :D

Edit: I also have busybox installed & seeder but I removed the apps since they're not needed after. And on this benchmark test I was tethering at the time, I've hit above 37000 with the blazed kernel and battery is gravity.
[Verizon Galaxy S 5 General] sem1845:
HAve you tried using vmware? That's what I used to flash mine with my mac.
[Verizon Galaxy S 5 General] realgadawg:
I ordered mine this past Saturday. How long did it take Samsung to send a tracking number to you? I'm still avoiding for mine.
[Verizon Galaxy S 5 General] razzrmaxx:
If you ordered it Saturday it takes them 24 hrs to process the order but Sunday don't count and Monday either since it was Memorial day, I say sometime between tonight and 12 noon.
[Verizon Galaxy S 5 General] realgadawg:
Thanks, I called and spoke with a rep. They swear that I should get it tomorrow. But I've gotten no new emails.