Verizon Galaxy S5 Developer Edition

Search This thread

joderme

Senior Member
Jun 13, 2010
554
299
Good to know that it is coming, however, it is very sad to know that no updates are provided to this phone.

Sure you can install whatever roms you want, however, if the carrier branded locked down that no boot loader bypasses are available then kiss any rom choices goodbye (save the international version roms) as no one will develop for it.
 

jackdubl

Senior Member
Aug 14, 2010
946
207
Good to know that it is coming, however, it is very sad to know that no updates are provided to this phone.

Sure you can install whatever roms you want, however, if the carrier branded locked down that no boot loader bypasses are available then kiss any rom choices goodbye (save the international version roms) as no one will develop for it.

Are you talking about roms built off of the retail version won't work for this because the retail bootloader would also be required? Is this true?

https://copy.com?r=cScoov
 

Elite49

Senior Member
Jul 5, 2011
776
60
Good to know that it is coming, however, it is very sad to know that no updates are provided to this phone.

Sure you can install whatever roms you want, however, if the carrier branded locked down that no boot loader bypasses are available then kiss any rom choices goodbye (save the international version roms) as no one will develop for it.

Most probably wouldn't develop for this anyway same with S3 D.E.
 

prdog1

Senior Member
Mar 10, 2012
9,102
5,466
Houston, Texas
Are you talking about roms built off of the retail version won't work for this because the retail bootloader would also be required? Is this true?

https://copy.com?r=cScoov

Most probably wouldn't develop for this anyway same with S3 D.E.

If they can build roms for Carrier version they will work on Dev unit. Just no Safestrap required. Development will be dependent on if Safestrap or another bootloader bypass is made functional. All roms developed on S3 and S4 work on their Dev Editions. There is no difference in the device besides bootloader unlocked. :cool:
 
  • Like
Reactions: Gunthermic

brizey

Senior Member
Aug 6, 2011
2,451
620
If they can build roms for Carrier version they will work on Dev unit. Just no Safestrap required. Development will be dependent on if Safestrap or another bootloader bypass is made functional. All roms developed on S3 and S4 work on their Dev Editions. There is no difference in the device besides bootloader unlocked. :cool:

Still need someone to get all the modem stuff worked out--international ROMs are not really automatic. And likely no GE or AOSP. I have an MDK S4. Going to keep it for a while then later dater VZW.
 

markwebb

Senior Member
Avoid it like the plague. Samsung never updated the S4 and never released a factory image. I would never buy another Samsung Dev edition phone again. Not worth the price. I get more mileage from Nexus 5 and moto x... Each at least half the price.



Sent from my SCH-I545 using xda app-developers app
 
Last edited:
  • Like
Reactions: Skeetch79

leyvatron

Senior Member
Dec 6, 2007
3,024
399
Los Angeles
Wow! A developer version that nobody will get because no files are released.
Get this and you will never get an update....

Come one Verizon, What is the point of this!

Sup Baja... thanks for the Note 3 roms.
 
Last edited:
  • Like
Reactions: bajasur

BeansTown106

Inactive Recognized Developer
Dec 22, 2011
3,694
54,414
BeanTown USA
Hopefully they will release the Odin files this time. ................

Sent from my SM-N900V using xda app-developers app

will never happen because of how developer editions are made. they are a waste of money no updates are possible each aboot is signed with the device key to "unlock it" and that can only be done at samsung, so basically no way to update it without loosing the dev edition status and unlocked bootloader.
 

bajasur

Retired Forum Moderator
Sep 19, 2012
4,041
10,523
San Clemente
will never happen because of how developer editions are made. they are a waste of money no updates are possible each aboot is signed with the device key to "unlock it" and that can only be done at samsung, so basically no way to update it without loosing the dev edition status and unlocked bootloader.

Exactly......confused on why they are still referring to these as "developer editions"...... :banghead:

Sent from my SM-N900V using xda app-developers app
 

BeansTown106

Inactive Recognized Developer
Dec 22, 2011
3,694
54,414
BeanTown USA
Exactly......confused on why they are still referring to these as "developer editions"...... :banghead:

Sent from my SM-N900V using xda app-developers app

to make money off people who strictly wanna use aosp i guess?

at this point if u want to get a s5 that u can use for roms etc

SM-G900R4 (US Cellular)
SM-G900T (T-Mobile US)
SM-G900P (Sprint)
SM-G900T1 (Metro PCS)

all have unlocked bootloaders put your $$ where your mouth is and lets stop supporting verizon

PSA: dont buy locked devices and expect them to be rootable/moddable because the time will come when the devs get tired of it.
 
Last edited:

Firemedic

Senior Member
May 12, 2007
130
83
will never happen because of how developer editions are made. they are a waste of money no updates are possible each aboot is signed with the device key to "unlock it" and that can only be done at samsung, so basically no way to update it without loosing the dev edition status and unlocked bootloader.


I have the GS4 dev edition, I run custom roms, I keep the radios up to date and it works like a charm. I have no issues with it at all. I am running HD15 at the moment and it is amazing. No reboots. I am not really seeing a need for an update at this point.

I have a friend who is running 4.4.2 roms on his GS4 Dev and also has absolutely no problems.

I am not seeing it but perhaps in the future it will need an update but at that point I will probably have moved on to something else.
 
  • Like
Reactions: thuddome

BeansTown106

Inactive Recognized Developer
Dec 22, 2011
3,694
54,414
BeanTown USA
I have the GS4 dev edition, I run custom roms, I keep the radios up to date and it works like a charm. I have no issues with it at all. I am running HD15 at the moment and it is amazing. No reboots. I am not really seeing a need for an update at this point.

I have a friend who is running 4.4.2 roms on his GS4 Dev and also has absolutely no problems.

I am not seeing it but perhaps in the future it will need an update but at that point I will probably have moved on to something else.

s4 isnt bad but note 3 is there is almost no way to run a 4.4 rom with the 4.3 bootloader on the note3 because of how they implemented the dtb.img in the kernel and s5 for sure will have the dtb.img system intact like note 3
 

joderme

Senior Member
Jun 13, 2010
554
299
to make money off people who strictly wanna use aosp i guess?

at this point if u want to get a s5 that u can use for roms etc

SM-G900R4 (US Cellular)
SM-G900T (T-Mobile US)
SM-G900P (Sprint)
SM-G900T1 (Metro PCS)

all have unlocked bootloaders put your $$ where your mouth is and lets stop supporting verizon

PSA: dont buy locked devices and expect them to be rootable/moddable because the time will come when the devs get tired of it.

Sadly this isn't going to work as altruistic of an idea that it may be.

Enthusiasts are such a small percentage of the population... Even if we do buy devices that are on networks that allow unlocked bootloaders that % will be small. They won't even notice something even if all enthusiasts switched. Phones like the SGS5 and the iPhone 5s will still sell in massive numbers in the US despite being locked down. Most folks don't really care or are too lazy to delve into the custom realm.

The devs are all we have in some instances, especially when a user likes the hardware, despite the anal nature of the carrier and/or manufacturer.

I'd like to think devs aren't taking money from Samsung and others to give up their exploits but unfortunately money makes the world go round.
 

ryanbg

Inactive Recognized Developer
Jan 3, 2008
858
1,739
movr0.com
will never happen because of how developer editions are made. they are a waste of money no updates are possible each aboot is signed with the device key to "unlock it" and that can only be done at samsung, so basically no way to update it without loosing the dev edition status and unlocked bootloader.

I'm pretty sure that the dev edition signatures are hashed with the CID. That's how they get each device to have a unique key. Also, did you guys notice that there is no ExtCSD accessible on MSM8974/Note3 and newer devices? The RPMB happens to be the same size... I am wondering what would happen if we flipped the MMC_BOOT_PART_ACC bit to 0x3 (enable R/W RPMB), or enable R/W access to mmcblk0boot0 and 1. There's definitely something unique about these developer edition devices and how they utilize features of JEDEC standard. Again, it's sort of useless to know the signature is hashed with the CID without having the key to hash them with... but as far as I can tell, that hashing is all done on the device... I'm recompiling mmc_utils source to include some commands that shouldn't be messed around with (thanks @Hashcode) all in the name of science.

UPDATE: Have you guys ever seen the partition layout for these devices?
Code:
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
1 heads, 16 sectors/track, 3816960 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1               1     3816960    30535679+ ee EFI GPT
Partition 1 does not end on cylinder boundary

Disk /dev/block/mmcblk0p1: 15 MB, 15728640 bytes
4 heads, 16 sectors/track, 480 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

[B]                Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1p1   ?    12158374    29994462   570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(357, 116, 40) logical=(12158373, 2, 5)
Partition 1 has different physical/logical endings:
     phys=(357, 32, 45) logical=(29994461, 2, 3)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p1p2   ?     2635774    32886216   968014120  65 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(288, 115, 43) logical=(2635773, 3, 3)
Partition 2 has different physical/logical endings:
     phys=(367, 114, 50) logical=(32886215, 0, 2)
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p1p3   ?    29216898    59467339   968014096  79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(366, 32, 33) logical=(29216897, 3, 10)
Partition 3 has different physical/logical endings:
     phys=(357, 32, 43) logical=(59467338, 1, 9)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p1p4   ?           1    56831664  1818613248   d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
     phys=(0, 10, 0) logical=(56831663, 3, 16)
Partition 4 does not end on cylinder boundary[/B]

Partition table entries are not in disk order

Disk /dev/block/mmcblk0p10: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p10 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p11: 14 MB, 14680064 bytes
4 heads, 16 sectors/track, 448 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p11 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p12: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p12 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p13: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p13 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p14: 11 MB, 11534336 bytes
4 heads, 16 sectors/track, 352 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p14 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p15: 13 MB, 13631488 bytes
4 heads, 16 sectors/track, 416 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p15 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p16: 13 MB, 13631488 bytes
4 heads, 16 sectors/track, 416 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p17: 7 MB, 7330816 bytes
4 heads, 16 sectors/track, 223 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p18: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p18 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p19: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p19 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p2: 60 MB, 60227584 bytes
4 heads, 16 sectors/track, 1838 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
[B]
                Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p2p1   ?    12158374    29994462   570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2p2   ?     2635774    32886216   968014120  65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p2p3   ?    29216898    59467339   968014096  79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p2p4   ?           1    56831664  1818613248   d Unknown
Partition 4 does not end on cylinder boundary[/B]

Partition table entries are not in disk order

Disk /dev/block/mmcblk0p20: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p21: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p21 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p22: 9 MB, 9437184 bytes
4 heads, 16 sectors/track, 288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p22 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p23: 2843 MB, 2843738112 bytes
4 heads, 16 sectors/track, 86784 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p23 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p24: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p24 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p25: 27.1 GB, 27158101504 bytes
4 heads, 16 sectors/track, 828799 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p25 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p3: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p3 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p4: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p4 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p5: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p6: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p6 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p7: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p8: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table

Disk /dev/block/mmcblk0p9: 10 MB, 10485760 bytes
4 heads, 16 sectors/track, 320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p9 doesn't contain a valid partition table

Disk /dev/block/mmcblk0rpmb: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0rpmb doesn't contain a valid partition table
 
Last edited:

droidstyle

Inactive Recognized Contributor
May 7, 2011
6,471
3,604
Fort Wayne
I am running 4.4.2 TW and still on the 4.3 bootloader. :)

Thanks to the leak we got or else ot would not be possible.

I agree tho Samsungs Developer Edition is a joke. However I will continue to buy them since I purchase my device out right to keep unlimited data. At least this way I am unlocked and can root right off the bat opposed to waiting for a root method....just sayin. If the new update is worthy of taking then I can decide to take it and turn the device into a locked retail at my discretion.

I will say 4.4.2 is not a big improvement over 4.3 other then download to ext. Sd works again, but I could live without something like that to keep root and stay unlocked.
 

Scott

Retired Recognized Developer
Avoid it like the plague. Samsung never updated the S4 and never released a factory image. I would never buy another Samsung Dev edition phone again. Not worth the price. I get more mileage from Nexus 5 and moto x... Each at least half the price.
Sent from my SCH-I545 using xda app-developers app
Exactly!


Sadly this isn't going to work as altruistic of an idea that it may be.

Enthusiasts are such a small percentage of the population... Even if we do buy devices that are on networks that allow unlocked bootloaders that % will be small. They won't even notice something even if all enthusiasts switched. Phones like the SGS5 and the iPhone 5s will still sell in massive numbers in the US despite being locked down. Most folks don't really care or are too lazy to delve into the custom realm.

He didint say he was going to shut Verizon down... He said stop supporting them.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Guys, make a safe backup of your developer aboot, that way if you accidentally lock, you can re-unlock your device.

    Code:
    dd if=/dev/mmcblk0p6 of=/sdcard/aboot.bak

    Copy aboot.bak somewhere safe.

    Anyone who's locked their Developer Edition device and HAS a backup, please contact me and I will assist you in re-unlocking. You must have your original Developer Edition aboot.

    ALSO, would you guys be interested if I wrote a small tutorial on how to create your own updates/tars for Developer Editions?
    4
    guys, DO NOT FLASH muniz_ri's ROM file, it contain a retail bootloader. This will messed up the bootloader on your Dev. Ed. phone.

    Update: for some reason my ROM do not update some of the firmware files correctly, please use Misterxtc's OA8 Dev-Edition Firmware Only INSTEAD of Ktoonsez kernel.

    Here is a version of the munirz_ri's file with the aboot and recovery removed, as well as as the update script edited. DOWNLOAD

    I was able to update my Verizon Dev. Ed. GS5 to 5.0 following this:
    - Prerequisites: Custom Recovery installed (Download the latest TWRP Recovery by Ktoonsez from: http://xdaforums.com/showpost.php?p=53276341&postcount=1. Yes it is a TMobile GS5 forum, but he files are the same for our VZN GS5)
    - Download the Dev. Ed. Stock rooted Lollipop ROM, copy it on your SD Card
    - Download and copy on your SD Card the Touchwiz Lollipop 5.0 VERSION of Ktoonsez Kernel from http://xdaforums.com/showpost.php?p=53276341&postcount=1 (Yes it is a TMobile GS5 forum, but he files are the same for our VZN GS5)
    - Download and copy on your SD Card Misterxtc's OA8 Dev-Edition Firmware Only
    - Reboot into TWRP, make a backup of every partition
    - in TWRP, Wipe -> Advanced wipe -> Wipe Dalvik Cache, System, Data, Cache
    - in TWRP, install the Modified ROM file. DO NOT REBOOT at the end
    - in TWRP, install the Ktoonsez Kernel TW 5.0
    - Switch off the phone
    - Reboot into Download mode Volume Down + Home + Power
    - use ODIN 3.09+, AP button, to flash OA8_Dev_Ed_Firmware.tar.md5
    - in TWRP, Restore ONLY the DATA from your previous backup.
    - in TWRP, Wipe -> Advanced wipe -> Wipe Dalvik Cache, Cache
    - Reboot, wait for ART do do its thing during the first boot (long wait during the Verizon logo, even longer optimizing apps)
    - Install your favorite tool to Disable or Freeze to system apps (Titanium Pro in my case)

    Now optional (but recommended):
    - Freeze or disable "SecurityLogAgent" to avoid the dangerous security nagging
    - Freeze or disable all the Knox apps while you are at it.

    - Reboot, enjoy
    4
    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.
    4
    Exactly......confused on why they are still referring to these as "developer editions"...... :banghead:

    Sent from my SM-N900V using xda app-developers app

    to make money off people who strictly wanna use aosp i guess?

    at this point if u want to get a s5 that u can use for roms etc

    SM-G900R4 (US Cellular)
    SM-G900T (T-Mobile US)
    SM-G900P (Sprint)
    SM-G900T1 (Metro PCS)

    all have unlocked bootloaders put your $$ where your mouth is and lets stop supporting verizon

    PSA: dont buy locked devices and expect them to be rootable/moddable because the time will come when the devs get tired of it.
    4
    Hopefully they will release the Odin files this time. ................

    Sent from my SM-N900V using xda app-developers app

    will never happen because of how developer editions are made. they are a waste of money no updates are possible each aboot is signed with the device key to "unlock it" and that can only be done at samsung, so basically no way to update it without loosing the dev edition status and unlocked bootloader.