yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Roland_D:
True...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] equake:
Its been stated here that ME7 will SW lock the bootloader but the HW is unlocked. Unfortunately there is no exposed method to unlock the bootloader ie via fastboot. The GPe devices can be unlocked using fastboot.

All the nexus devices are bootloader locked by defaulted but can be unlocked using fastboot.

My 2 cents
[Verizon Samsung Galaxy S 4] lortay78:
Making a TWRP nandroid now, but I forgot to wipe data first. I'll have to do it again after it finishes. No root, just stock with custom recovery.
[Verizon Samsung Galaxy S 4] Skeetch79:
This whole thing bothers me, though. When you check for an OTA does it not check against your Build.prop or what software is loaded on your phone? (Hence why someone on a custom ROM cannot receive an OTA - they need to revert to stock first in order to receive the OTA) Our build prop states different build numbers, etc than the Retail Version. I find it hard to believe that a Developer Edition phone will receive the exact same OTA as the Retail Version. It may bump us up to ME7 from MDK but it should be something along these lines: I545OYUAMDK -> I545OYUAME7...we should not go to the retail version of I545VRUAME7.

Now, if Verizon

does

push an update specifically for the Developer Edition phone and it does software lock the bootloader then there will be a giant uproar.

We purchased this phone through Samsung at a great cost in order to get the freedom of ROM'ing, Root'ing, etc. VZW agreed to let this S4 variant on their network knowing it had an unlocked bootloader, but as long as it was sold by Samsung at full retail cost.

All the reports of Developer Phones being locked after receiving the ME7 update I question a few things:

1. Did someone load the Retail Version OTA on their phone?

2. Has anyone posted screenshots form their device showing the new build number and baseband?

3. Our phone is not expected to receive an OTA anyway until October along with the Retail Version - how are people receiving this ME7 OTA on their Developer Device?

4. Any many other other questions.......

My 2 cents! :) LOL
[Verizon Samsung Galaxy S 4] Roland_D:
1. They odined me7 not received the ota

2. Not that I know of

3. See 1

4. It makes 2 of us... And possibly many more...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] Skeetch79:
They ODIN'd ME7 onto their phone - what is the full build number? Where did they get ME7 to ODIN onto their phones?
[Verizon Samsung Galaxy S 4] equake:
I think it was the OP of this thread that got ME7 thru vzw software upgrade assistant

But this has not been confirmed by anyone else. I have both KIES and vzw upgrade assist and both say my firmware are not eligible for update.

OTA has always say it's up to date
[Verizon Samsung Galaxy S 4] Roland_D:
it was the vzw factory image... The build number was supposedly the same as the consumer since it WAS the consumer firmware..

The user that I know of anyways was sound-mind... You can pm him and ask him... Tho for me it would be a sore subject...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] Skeetch79:
So that is what I trying to say, those that fear receiving the OTA from VZW while on the Developer Edition and having their bootloader software locked should not have to worry as long as VZW pushes those with the Developer Device an OTA catered to only the Dev Device. As I said, it should be somewhere along the lines of I545OYUAME7. Having said that, I would still be wary of any OTA.

Now if VZW accidentally pushed a Consumer ME7 update prematurely, especially to someone with a Dev Device, then there is a problem

I have had the same experience as you do through VZW Software Upgrade and KIES. Our device is not supported. Also, when I check for an OTA, I too receive the message I am up to date.
[Verizon Samsung Galaxy S 4] Roland_D:
Guys obviously the only purpose of the me7 ota was to lock the bootloader for good... But what worries me is not taking the ota... As you can see from my sig don't think it will happen any time soon, but rather that we have no factory image to Odin at all as a safety net... The only ones we would have are the mdk and me7 consumer...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] equake:
The other possibility for those that did in fact receive the ME7 update is that the phone is an Consumer Ed with the wrong MDK Firmware and the Bootloader was always locked.

Since there is no way to check the Lock Status nor the HW differences between Dev and Consumer its all speculation at this point.
[Verizon Samsung Galaxy S 4] Roland_D:
I really would like for someone more competent than me to explain us if it's even possible to prevent odining a firmware on merely a sw base... Without blowing any efuse or similar.. Cause if that's not possible then you might be right.

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] markwebb:
Dump has been sent to a dev. Let the fun begin!
[Verizon Samsung Galaxy S 4] guyd:
Kernel boot.img dump, or more?

Which dev did you send it to if I may ask?

EDIT: Scott of CleanROM fame has made a ROM out of it!
[Verizon Samsung Galaxy S 4] locofocos:
Update?

What's the latest news on this? If I understand...

Recovery- post 8 http://xdaforums.com/showpost.php?p=43265779&postcount=8

Root- post 12 http://xdaforums.com/showpost.php?p=43269530&postcount=12 (which should work with the stock kernel, per post 15)

Roms- post 18 http://xdaforums.com/showpost.php?p=43270757&postcount=18

Kernels- ?

If I can summarize, recovery- got the non-loki version, root- flash the right zip file in recovery, roms- should work the same, and kernels...? I'm really looking at buying the VZW Dev. Edition soon. My Gnex got me hooked on crack flashing, lol, and Verizon just has such good coverage and unlimited data for me (and no spare lines to upgrade). Would they devote a subforum, or maybe a sub-subforum to the VZW Dev. Edition? Awesome work figuring this out! Thanks :)
[Verizon Samsung Galaxy S 4] 808phoneaddict:
Dev edition has been backordered for what seems like forever... Not sure when they'll finally have stock...
[Verizon Samsung Galaxy S 4] markwebb:
FIRST THING: MAKE A NANDROID BACKUP BEFORE YOU INSTALL CUSTOM RECOVERY.

The only issue with ROMing is that the Dev Edition has a different baseband than the regular edition: some ROM"s won't work on wifi. I do have a patch from a dev which works on a few of the ROM's but not all. Changing the kernel might also help but I never changed the kernel.
[Verizon Samsung Galaxy S 4] equake:
Why would the dev edition have a different baseband? It's the same h/w

except with an unlocked bootloader.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I compared the kernel numbers on my Dev with the consumer version and they were both the same. Though now after rooting the dates are different on it but the number is the same. Not sure if that's good or bad. How would I get the original kernel back? Do I even need it back or is the prior version okay?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
There's a philz_touch_5.08.5-jfltevzw.tar.md5 version as well. Any reason to not use the latest one?
[Verizon Samsung Galaxy S 4] markwebb:
It should work. The original one linked is proven, at least on mine.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
After trying motochopper (basically step 3 from the rooting guide) and having it fail, I used the One Click method to root. It worked and I was able to install CWM and make a backup. Only now the kernel date is April instead of May, which is what it was when it came out of the box. Any way of getting the original May dated kernel back?
[Verizon Samsung Galaxy S 4] wtherrell:
Both of those methods replace the stock kernel, I think. Which is why I plan to Odin a tar file custom recovery onto mine then flash the SuperSU root package zip. That should leave kernel intact. Perhaps some of the devs can extract the dev ed kernel and post a link?

Many Roms contain their own optimized kernels as well. For future reference Trickster Mod and Franco Kernel Updater both contain a kernel backup & restore utility that I have found very handy. Hope this helps a little.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Thanks for the tips! I'll post and see if anyone would be willing/able to provide me with the original kernel. I'm assuming I could use the Franco Kernel Updater to replace it? Or could I use ODIN as well? Still trying to figure out what all these things do/are used for :D
[Verizon Samsung Galaxy S 4] wtherrell:
If you download the zip file for the kernel you can just install it from your custom recovery. Just like flashing a rom.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Sweet! Now I just hope someone replies to my request.
[Verizon Samsung Galaxy S 4] abe_cedar:
original kernel

I will back up my kernel using francos'. ( does not work tried it o a note 2 needs to be done some other way)

My device comes in today.

which one click root did you use?

Did you use this Philz_touch_5.06.6-jfltevzw.tar.md5 or the latest?

thanks
[Verizon Samsung Galaxy S 4] Kaiya_FL:
That'd be so awesome! Thanks bunches :good:

I used the [TOOL](ROOT)(RECOVERY) i545 all-in-one root + recovery installer Updated 7-8-13 to root. That's what overwrote my kernel, I think. I didn't find out about the Philz process (and this thread) until after. So now I'm not sure if I should use ODIN to install either the 5.06 or 5.08 tar or just leave things as is.
[Verizon Samsung Galaxy S 4] wtherrell:
Just dawned on me. Only way I know how to make Nandroid is from custom recovery. How do I do it beforehand? I also have experiences where Nandroid backup made with one recovery could not be restored from a different recovery.

OMG, knock at the door.................... my new GS4 dev edition is finally here! Not much sleep tonight!

More questions later.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Since poor Abe's phone was stole, can anyone else provide me with a stock kernel zip for the dev? Please :cyclops:
[Verizon Samsung Galaxy S 4] locofocos:
Interesting. Trickster Mod didn't give me the option, and Franco Kernel Updated told me that this feature isn't supported on this device. Hmm. I've got a Nandroid backup made using Phil's CWM recovery. I'll pick that apart and see if I can find the kernel. (running MDK here on my Dev Ed.)

EDIT- Alright, here ya go. This came from a stock Verizon S4 Developer Edition running the MDK build. I installed Phil's CWM recovery and pulled this "boot.img" from the backup. http://db.tt/a87Grh2g

Definitely not in a flashable zip quite yet. This thread may give you a lead on extracting just the kernel and making a flashable zip- http://xdaforums.com/showthread.php?t=1821500

EDIT 2- Here's the relevant line (for the boot.img) from my nandroid.md5 file-

d7d0693384050fb4b6bbdafefbeafd18 boot.img
[Verizon Samsung Galaxy S 4] shellux:
You don't need root to install a custom recovery on a dev device. I've installed CWM, TWRP, and Philz now in the last couple hours without issues through odin. You can convert the .img files of the recoveries to .tar.md5 using http://xdaforums.com/showthread.php?t=2281287 and flash them through odin under pda. Then just boot to recovery by holding volume up and home while powering up and you can flash your rom. I have come across a couple roms where wifi refused to turn on. I've been able to remedy that by flashing in a new kernel through recovery and so far all is well.
[Verizon Samsung Galaxy S 4] Skeetch79:
I have been contacting the Admin over at sammobile.com (which hosts various firmwares) about finding our stock firmware, but he has not been able to so far. Also it seems as if the majority of the firmware at that site is non-USA.

Checking samsung-updates.com also yields similar results.

As we discussed. Someone does have the firmware, but our chance of getting it close to nil.
[Verizon Samsung Galaxy S 4] Roland_D:
Well here is the thing... We don't even need to host it anywhere... From the looks of this forum we owners of a DE are VERY few... We could even pass it to each other via db or other.. I just wish sextape or whoever would give it away..

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] Skeetch79:
I absolutely agree. What more can we do?
[Verizon Samsung Galaxy S 4] equake:
True to a certain extent. Its interesting to note that even the Consumer Ed FW is not on the sammobile site. It is available for SPR, TMO, ATT. So I'm not sure where they get source from.

As I mentioned before, I chatted with a VZW support guy and although he has no Exp with Samsung Dev Eds he has a Moto Dev device and the updates are on Motos Dev site.

Maybe the best way to get more insight/info is to go to the Samsung Dev conference coming up in Oct
[Verizon Samsung Galaxy S 4] Roland_D:
I'll try to contact him and see if something can be done... I just don't wanna bother the guy... I'm sure he has his reasons for not posting it...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] equake:
Unless you are aquainted, don't bother I've already messaged him on the board to no avail.

The other Dev is the person who developed CleanROM who might have something lying around. He created the first Dev stock de-odexed rooted ROM.
[Verizon Samsung Galaxy S 4] Roland_D:
Yeah but it's from a user dump if I'm not mistaken... I mean I have a (actually 2 just in case ;) ) nandroid completely stock myself (with modified recovery of course) but I still would love the Odin tar.md5...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] equake:
I think you are correct but I was under the impression he may have the image but is holding back a bit.

My 2 cents.
[Verizon Samsung Galaxy S 4] jpcalhoun:
I got my DEV yesterday and it came with the same firmware...straight from Samsung. Do you have a link to the version of PHILZ Touch?
[Verizon Samsung Galaxy S 4] equake:
There is a thread in the original development subforum
[Verizon Samsung Galaxy S 4] markwebb:
I also have the system and boot dump but with recovery installed. Would that help us?
[Verizon Samsung Galaxy S 4] jpcalhoun:
Thanks, I'll check it out. Tired of no recovery.
[Verizon Samsung Galaxy S 4] wtherrell:
Post #8 & 23 of this thread have links to recovery.
[Verizon Samsung Galaxy S 4] markwebb:
this link isn't working: http://d-h.st/users/philz_touch/?fld_id=18376#files
[Verizon Samsung Galaxy S 4] Roland_D:
Google philz touch 5... The first link to xda it's your link

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] markwebb:
Thanks and understood, but the link to download the correct Verizon Samsung version does not work. Even trying on office computer.
[Verizon Samsung Galaxy S 4] Roland_D:
Here get it from my DB... https://dl.dropboxusercontent.com/u/24424301/philz_touch_5.06.6-jfltevzw.tar.md5
[Verizon Samsung Galaxy S 4] Skeetch79:
This may not be the latest version but it is the one that I use. Get it from my DropBox.

Extract the tar.MD5 from the zip file and flash via odin using download mode on the phone and the PDA field within ODIN.

https://www.dropbox.com/s/v7yrv92jqx9weub/philz_touch_5.08.5-jfltevzw.zip

---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------

Ooh beaten to the punch!
[Verizon Samsung Galaxy S 4] Roland_D:
Well yours is the latest version... Or at least later than mine... Lol

I'll get it from you... Anyways I really don't remember where I downloaded it from the other day..

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE

---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------

Hold on a sec this is a boot.img... can it be flashed in odin??? I thought it had to be tar.md5.... :confused:
[Verizon Samsung Galaxy S 4] equake:
That is indeed the older version which I have installed. Philz posted the latest 5.15.x version but the site is down at the momemt.

Have any of you used a 64GB SD with the version of recovery. Some folks have said it does NOT function. I'm giong to give it a try tonite.
[Verizon Samsung Galaxy S 4] Roland_D:
My question stands... Shouldn't it be tar.md5? That looks like s flashable zip to me not Odin...

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] Skeetch79:
the file I posted is a ZIP which needs to be extracted to yield the tar.md5, odin flashable file.
[Verizon Samsung Galaxy S 4] Roland_D:
I extracted it and there is a recovery.img file....

Sent from Eclipse TW edition on a Samsung Galaxy S4 DE
[Verizon Samsung Galaxy S 4] Skeetch79:
Oh boy, my bad, uploaded the Recovery flashable zip.....I need to have my head examined!.....:-O

How is this? https://www.dropbox.com/s/7hhwsnj52ofif21/philz_touch_5.08.5-jfltevzw.tar.md5
[Verizon Samsung Galaxy S 4] Roland_D:
Bingo!
[Verizon Samsung Galaxy S 4] Bait-Fish:
Dev Host was just up a few minutes ago when I checked.
[Verizon Samsung Galaxy S 4] wtherrell:
Older version would not work with 64gb exFat sdcard. It was 5.06.6 I believe. Newer 5.08.5 working fine. I presume that latest also works.
[Verizon Samsung Galaxy S 4] equake:
Thanks, mine should work sicne I'm on 5.08 will update to 5.15 once I can get the files from distro site.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Since nobody has come forward with a ODIN flashable version, I took the plunge (painless actually).

Using cabloomi's tool modified by evilmansin, I tar.md5'd the system image. It is zipped to save space.

Like the warning previously, this is untested. Use at your own risk.

UPDATE (2): system.tar.md5 is failing in ODIN. Not sure why.

system.tar.zip

http://www.4shared.com/zip/CD_FDjGC/systemtar.html

MD5

6F6AFC600F5473D1DA97A745DFBAE570

system.tar.md5

MD5

A1830FFD3B058B6F405047BDD87CD717

Update 9/30: I used a slightly different command to generate a new tar.md5. I pinged SamuriHL to get his command string for tar/md5'ing files. That's how this new one is built.

tar -H ustar -c system.img > system.tar
md5sum -t system.tar >> system.tar
mv system.tar system.tar.md5

I also modified the batch file to use the source/destination file name of "system" instead of "recovery" as was originally used. I'm not sure if the different naming, then finally changing its output file name from recovery.tar.md5 to system.tar.md5 caused the issue. In any case, hopefully this one will work *fingers crossed*
[Verizon Samsung Galaxy S 4] Roland_D:
Holy smokes... Thanks!

So untested huh?

Who is going to try it? :P
[Verizon Samsung Galaxy S 4] lortay78:
I'm not sure if this belongs here, but I'm wondering something: Since we have a truly unlocked bootloader, does anyone know if it would be theoretically possible to make the system partition smaller and give us a bigger "/sd card" when running a run smaller than tw like cm?

This is way beyond my comfort level, but I'm just curious. Thanks.
[Verizon Samsung Galaxy S 4] Toddricks:
I think I will give it a shot tomorrow. Heck what can happen........Will report findings when I flash this puppy. I want my gs4 dev edition in a factory state when I sell it.
[Verizon Samsung Galaxy S 4] Roland_D:
You are the man... Let us know!
[Verizon Samsung Galaxy S 4] Bait-Fish:
I have been considering trying SafeStrap. That's why I tar.md5'd the system image, in case something goes wrong. I just need to free up some space first. The multiboot feature is alluring.
[Verizon Samsung Galaxy S 4] Toddricks:
Ok gonna have to wait a little longer guys. I have to redownload the file due to invalid md5 hash message in odin. I was hoping to do this early today but will be later today. Fingers crossed.
[Verizon Samsung Galaxy S 4] Bait-Fish:
The system.md5.tar? That shouldn't be, but then again you are the first to try (thanks!).

Does the zip file MD5 match I posted? Does the unzipped system.md5.tar also match the MD5 I posted?

The method I posted using had two batch files to process the system.img into tar.md5. Both worked successfully as an experiment, and both had matching MD5s.
[Verizon Samsung Galaxy S 4] Toddricks:
I did not check to see if md5 matched. Redownloading file now. Will verify md5 before transfer to pc
[Verizon Samsung Galaxy S 4] Toddricks:
Downloaded zip and extracted files md5 sums match. Fails in odin with invalid md5 sum.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Damn. That's not reassuring. ODIN 3.07 (or latest version...) using PDA section? Just trying to cover all the bases.

Having used both batch files to create the same output (matching MD5), using a process that seems to work for other people in cabloomi's thread, well, that lent me great confidence it would be successful.
[Verizon Samsung Galaxy S 4] Toddricks:
Yes, using odin 3.07 in pda. Gonna keep trying.

Edit: just redownloaded to re verify md5. All sums match posted md5's. Will try odin flash later.
[Verizon Samsung Galaxy S 4] invisiblek:
Can someone with the dev edition model please get me a dump of their param partition? (You'll need to be rooted in order to do this)

dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/sdcard/param.img

There should be no personal information on this partition, but if you are paranoid, PM it to me please.

Thanks!
[Verizon Samsung Galaxy S 4] EMSpilot:
Here you go

Here you go.

https://www.dropbox.com/sh/uzu4ygm63rp0l4y/OriKfrB8yd
[Verizon Samsung Galaxy S 4] invisiblek:
Hmm, something isn't right there. They are all showing as 20 byte files. =/

That particular partition (mmcblk0p19) should be just over 6mb
[Verizon Samsung Galaxy S 4] krnnme:
Hey guys I was wondering what was the build number that your Dev edition s4 came with

And what's the SKU on the back?

Was wondering if the s4 I got from craigslist is a Dev edition one

Thanks
[Verizon Samsung Galaxy S 4] Skeetch79:
Build JDQ39.I545OYUAMDK, baseband I545OYUAMDK. Look under the battery, if it says Developer Device than you are all good. .. if not than sorry.

BTW - not that it matters if the phone doesn't have "Developer Device" beneath the battery - but the SKU is SCHI545ZKV
[Verizon Samsung Galaxy S 4] Toddricks:
Your gs4 is a consumer device
[Verizon Samsung Galaxy S 4] Skeetch79:
Are you saying mine is a consumer device? Why do you say that?

Mine clearly says Developer Device beneath the battery and the bootloader is unlocked - I flashed Philz Touch Recovery and installed Su along with other mod's. I am 100% sure mine is a developer device.
[Verizon Samsung Galaxy S 4] Roland_D:
Yeah don't worry it's a Dev Dev... You got the right baseband and all... And your boot loader is unlocked... Maybe his is a consumer one lol...

Anyways I really hope we'll get to have an Odin flashable image for our phone... It make me feel much better to know we have that kind of safety net.. Thanks everybody for the work you're putting into this.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I'll PM it now.

Update: Done
[Verizon Samsung Galaxy S 4] Skeetch79:
I know what I have! :) I ordered it straight from the Samsung website. I would never trust Craigslist for these types of purchases - especially Dev Phones! The fact that there was question as to whether the device was dev or not is disturbing. If you are going into purchasing one of these devices - from anywhere - you should do some research and know what to look for in order to verify what you have in front of you.

I am not holding my breath for the ODIN flashable images - but I did see this via twitter last week in regards to HTC hosting their Dev Device images: http://www.androidpolice.com/2013/0...ndroid-4-3-rom-for-developer-edition-htc-one/ and http://www.htcdev.com/devcenter/downloads
[Verizon Samsung Galaxy S 4] krnnme:
Cause the thing is

I went ahead and rooted using motochopper

Only did step 3

Then I installed twrp through goomanager and it all went through smoothly

And when I bought the s4 I wasn't expecting to buy a Dev edition
[Verizon Samsung Galaxy S 4] Roland_D:
I think whoever sold it to you would have mentioned selling you a $650 phone... It most probably was an mdk... In that case you lucked out big time!