yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] playaprez35:
LOL Na it's all good, believe me, I understand. Actually what you do for a living sounds very cool. Trust me, I didn't make any errors. In life I try to be very precise, and plan for every contingency. I'm a former Experience Consultant for Samsung. By the way you missed the: "-t" in the second line of the code. A few things I've learned about Electronics: They're kind of like people, and a mixed bag of skittles. So results may vary, and sometimes you have to have faith. Faith in your own abilities, as well as others. Now I'm not trying to preach religion to you by any means, but sometimes it's good to have faith in people. Faith, that they are just as capable as you are. (Phew) Now with that being said lol, I'm very appreciative of your generous offer. And I humbly accept. So I'm going to hold you to that lol!

Thank you for all of your assistance.

P.S. What is dd'ing by the way?

---------- Post added at 06:10 AM ---------- Previous post was at 05:27 AM ----------

TWRP is still not working on my phone smh. I attempted flashing both versions given.

Does the following make any difference? if my phone says:

Could not do normal boot.

ODIN MODE

PRODUCT NAME: SCH-I545

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x1

CSB-CONFIG-LSB: 0x30

MODE: Developer

WRITE PROTECTION: Enable

I'm open to any suggestions.
[Verizon Samsung Galaxy S 4] Skeetch79:
FYI: http://xdaforums.com/showthread.php?p=50075392
[Verizon Samsung Galaxy S 4] ryan1869:
I've read enough on here to know you can't go backwards on the retail version, but does the same restriction exist on the dev version? Is it just as simple as ODIN flashing the MDK boot\recovery from Skeetch79's post, and now I've got the MDK bootloader. Then I would think I could easily get TWRP and CM working at that point...or create a very expensive paperweight.

It would be nice if I can figure this out, since I'm stuck in the exact same boat as playaprez35. My biggest reason for wanting the dev edition in the first place was to be able to run AOSP type builds and not have to wait for Verizon\Samsung to load up the newest version of Android with new and improved bloat.
[Verizon Samsung Galaxy S 4] k1mu:
If you flash a non-Developer edition recovery bootloader to your Developer phone, you will end up with a locked bootloader. You will have wasted the money you paid to get an unlocked, no warranty device, and have NO ability to flash custom kernels, ROMs, etc. Be very sure that you understand what you're flashing, since once it's locked, you're not going to be able to recover.
[Verizon Samsung Galaxy S 4] Skeetch79:
I can assure that all the files which I have hosted have been extracted from my developer edition S4. 100% developer bred files!
[Verizon Samsung Galaxy S 4] k1mu:
Sorry - I did not intend to question your specific files, just to tell the poster that they need to be careful where the stuff they're flashing comes from.
[Verizon Samsung Galaxy S 4] Skeetch79:
Ha! All good! :)
[Verizon Samsung Galaxy S 4] Surge1223:
I know this post was from a long time ago, but do you happen to remember who it was you talked to and/or how I can get a hold of them?
[Verizon Samsung Galaxy S 4] Skeetch79:
Wow that was a while ago and look what we have done since then. He always went by the screen name Admin, but I am pretty sure that it was Sextape of XDA fame (sxtpdevelopers....sxtp...sextape). I also believe Garwin was involved as well.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Ok, now I'm confused. I have a Verizon Dev S4 with TWRP 2.5.0.2 installed as my custom recovery and my bootloader is not locked. Before TWRP I had installed a Philz recovery, and obliviously my bootloader and it didn't lock my bootloader. So, are you saying that TWRP is a "Developer edition"? I'm not trying to start an argument here, just trying to better understand your comment.
[Verizon Samsung Galaxy S 4] Skeetch79:
I have installed both TWRP and Philz and have not experienced my bootloader locking. I am not sure exactly what he is trying to say, but I think he is referring to installing a bootloader from a retail device or installing an OTA which is intended for the retail device. You can install Philz or TWRP with no issue or fear of locking your bootloader.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Thanks Skeetch79, after giving it some thought I agree with you. By the way, thanks tons for developing and sharing those .tar files. Those could be a life saver for a noob like me.
[Verizon Samsung Galaxy S 4] k1mu:
What he said was wrong. What I meant to say is that you can flash a factory *bootloader*, which will flash just fine but leave you with a locked bootloader. Sorry for the confusion.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Well, I don't see what he said as incorrect. If fact, to me, you're saying the same thing. The bottom line here is understand what you're doing before you do it.
[Verizon Samsung Galaxy S 4] k1mu:
Sorry, you missed the sarcasm. He is me. As in, it was my post that was incorrect.

I corrected the post to say bootloader, so if you read it now it's (hopefully) correct.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Not a problem.
[Verizon Samsung Galaxy S 4] ryan1869:
So I think the M3 snapshot of CM11 might have started to shed some light on my ROM issues but do these error messages mean anything to the devs here:

Failed to mmap aboot

Error loki-ifying the boot image

It seems to me like part of the problem is that the with my dev edition MI1 bootloader it's still trying to apply the MDK loki patch, which of course will fail on MI1. It seems like the loki.sh file is referencing a loki_bootloaders and unlocked_bootloaders files, and I tried adding my bootloader version to the unlocked one, but ended up with the same result. It seems like it's not even going through that script, because based on my reading of it, the whole thing should have just written out an "unknown bootloader" message since my i545OYUMI1 wasn't in either file the first time I tried it, yet I still got a loki error. I'm a bit stuck, since I would think on the unlocked dev edition I could just skip this loki step all together.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Surge1223 needs a Dev Edition owner with one of the newer firmware versions to help him.

Details of the file he needs are here.
[Verizon Samsung Galaxy S 4] Surge1223:
Originally I needed either another OYUEMJ7 or OYUEMK2 dev aboot, but seeing as not too many people are on that version then OYUAMDK will work as well, not ideal but better than nothing.

I just need someone to send me their dev aboot, doesnt matter what build or rom your on just as long as you've never sent your dev aboot to me before and that you do have a developer edition device.

adb shell

su

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/dev_aboot.mbn
[Verizon Samsung Galaxy S 4] Skeetch79:
I have my dev aboot from MDK tucked away somewhere. I will dig it out and send it

Just sent a PM over with link to DevS4 MDK aboot.mbn
[Verizon Samsung Galaxy S 4] ryan1869:
I could provide you with my OYUMI1 aboot, if it would help. I know it's probably not what you're looking for but it seems to share more in common with MJ7 and MK2 than it does with MDK.
[Verizon Samsung Galaxy S 4] Surge1223:
Unfortunately the MI1's are the oddballs lol. The good news is that the difference between two dev aboots is virtually the same as the difference between a dev aboot and a corresponding retail aboot. And the difference is minimal, 512b.
[Verizon Samsung Galaxy S 4] ryan1869:
An oddball is a bit of an understatement, kind of stuck in the middle with nowhere to go it seems.
[Verizon Samsung Galaxy S 4] markwebb:
Do you still need the OYUAMDK aboot? I have mine...
[Verizon Samsung Galaxy S 4] MehStrongBadMeh:
You should send it to him. The more aboots surge gets his hands on, the more likely he'll be able to discover a way to unlock retail edition devices (maybe).
[Verizon Samsung Galaxy S 4] jhasty01:
Incase anyone needs this for extracting aboot from their Dev
[Verizon Samsung Galaxy S 4] joemaster725:
Dev edition roming

Ok, so i would like a bit of guidance on how to rom this phone. i will start off by saying i am no stranger to roming phones( first smartphone was droid 2 global, which i romed the crap out of when i was using it), and have been roming phones ever since froyo. however, it has been about 1.5 years since i have romed my last phone, and have a few questions about roming jellybean/ kitkat:

1. what current roms will work for the dev edition phone, if any? i am currently on the stock Samsung s4 rom (4.2.2, 1545yuamdk), rooted, with cwm recovery (i like cwm more than twrp). if there are any cyanogen, or stock google roms that work with this phone (4.4.0 would be the version of android i want to flash to)

2. What would be the best way to back up/restore my kernel on the off chance that something does get borked, and i do soft- brick my phone? i have done quite a few nandroid backups, but am under the impression that nandroid does not backup/restore kernels.

3. I know a few people have romed their phone, but have had issues getting on the cellular network once romed. What modules will be needed to re-enable cell service on this phone?

I am familiar with how early android works, how linux works, and how to navigate and alter both, but am not familiar with the structure of samsung s4. any insight would be greatly appreciated!
[Verizon Samsung Galaxy S 4] joshm.1219:
1. You can flash all of the roms

2. As long as the "boot" part is checked in your nandroids, you have a kernel backup

3. The modules are for safestrap users, you shouldn't have problems and if you so, try a different kernel
[Verizon Samsung Galaxy S 4] equake:
Well, its either not mounted or its a corrupted format.
[Verizon Samsung Galaxy S 4] wtherrell:
Well that worked out fine. Got my TiBu backups from Gnex over to the S4 and selecting which apps+data to restore.

---------- Post added at 05:32 PM ---------- Previous post was at 05:03 PM ----------

Hmm. It's mounted in one sense. I can play music from it, view pictures, access documents, even move app data to it with foldermount. But CWM can't mount it nor does apps2sd see it. I formatted it in the phone when I first inserted it. Mounted it from settings & thought all was okay. Finally found the Nandroid in /data/media once I got E S File Explorer setting. (Still don't know exactly how I did that). Backup took 3.2Gb. Ouch! BTW, what's the difference between "external_sd" and "sd_ext"?

Isn't this fun?

Would next step be copying card content to PC & reformat card from CWM? :confused::rolleyes:

.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I think both point to the same place, your external SD card. It's just different naming convention. I noticed when I do a CWM backup it always says sd_ext not found. In my S4 according to Root Explorer & My Files it's called extSdCard.
[Verizon Samsung Galaxy S 4] DustL82:
Google Play Edition ROM

I've installed the play edition ROM on my GS4 and can't seem to get my GPS working. Anyone else having this issue? Potential solutions?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Installed Darkslide's ROM & Kernel. Getting it all set up now. Didn't flash the Kernel at first but then the Wifi wouldn't connect so I installed it an all seem good. Though I do get these warnings that some bad program is trying to run and I should reboot. I'm guessing it might be spazzing about some of the root required software? I'm interesting in seeing how it connects to my car's bluetooth. Read a couple comments that it solved the reading texts through the car stereo issue.

Will update more as the phone gets used.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
If anyone else tries Darkslide's ROM and gets the "Detection Information" message, just freeze the 3 Knox system apps and it'll go away :good:

So far, granted it was just overnight, things seem to be running good.
[Verizon Samsung Galaxy S 4] 808phoneaddict:
The Verizon developers edition never came back in stock did it?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
It's been back in stock for awhile but Samsung is not fulfilling backorders for some reason. Just go here and order it again:

http://www.samsung.com/us/mobile/cell-phones/SCH-I545ZKDVZW
[Verizon Samsung Galaxy S 4] Bait-Fish:
My order Thursday is in DFW shipping via UPS with an active tracking number.
[Verizon Samsung Galaxy S 4] locofocos:
I've been trying different roms to varying success (Hyperdrive's notification pulldown was choppy, Synergy had poor standby time even on a clean flash, but you may have a better experience! BoneStock is great, though not as feature rich). I kept running into the problem with wifi not turning on. I read there was a zip somewhere with some modules that might help, but couldn't find it. After some searching, I finally turned this up-

http://xdaforums.com/showpost.php?p=42093261&postcount=3. That made my wifi work fine in BoneStock using the included kernel.

Alternatively, many of the custom kernels out there seemed to fix the problem, if you go that route.
[Verizon Samsung Galaxy S 4] wtherrell:
PhilzTouch Recovery. Updated to latest version but it won't work with my external sd card. Installed TWRP using Goomanager. It works seamlessly with my 64gb exFat Samsung card.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I had to format my 64GB card to Fat32 for Philz to recognize it. Works like a charm now :)
[Verizon Samsung Galaxy S 4] locofocos:
Interesting. My "SanDisk Ultra 64 GB MicroSDXC Class 10 UHS-1" card worked fine in recovery with the latest version (philz_touch_5.08.5-jfltevzw.tar.md5). It was already formatted as exfat from the factory, so I kept it like that. I have problems with the stock exfat format in some roms using the provided kernel, but often flashing another kernel makes it work fine.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Oh my bad, I'm running CWM 6.0.3.2 Touch not Philz. It didn't like the exFat the my Samsung 64 GB MicroSDXC Class 10 UHS-1 card came formatted with. The ROM (Darkslide's) worked just fine with it but booting in CWM and trying to back up, it wasn't recognized.
[Verizon Samsung Galaxy S 4] markwebb:
Did it arrive today?
[Verizon Samsung Galaxy S 4] rmanaka:
I ordered one on Thursday and had to have it held at UPS for will call pickup as the representative who took my order over the phone totally messed up the delivery address! By the way, I am one of the ones who ordered it two weeks ago with a discount coupon and then had Samsung cancel the order! Picked up the phone on Friday and had it activated in a corporate VZ store yesterday. I used a corporate store as my buddy wanted my rooted MDK phone so long as it could be insured and he could keep his unlimited plan. The VZ rep did both and actually kept my Development phone on the Assurion insurance. Don't know if it will be honored or if they will just refund the premiums if there is a legitimate hardware failure. I also have a Square Deal plan that I previously purchased for an S4 so I think I will check to see if they will cover the phone.

---------- Post added at 04:36 PM ---------- Previous post was at 04:16 PM ----------

Ugh, couldn't edit my post in Tapatalk HD to change the signature. BTW, Samsung "said" that they would credit me for the overnight shipping because of the cancelled first order. We'll see!
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I had to call a couple of times. They finally sent me a screen shot showing the delivery refund. Of course it will still take "7-10 business days depending on your bank" for it to hit my account.

Glad you got your phone. Let me know what Square Trade says about the warranty. Kinda thinking about it since I paid out the nose for this thing :cyclops:
[Verizon Samsung Galaxy S 4] equake:
bump. I wonder if asurion offers anything.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Yeah, it was delivered this afternoon. I have only charged it, but not turned on yet. I want to see if I can get a pure nandroid before anything, rooting or recovery, etc. If it was only as easy rebooting to a temporary recovery as easy as it was on my Nexus 10 (fastboot). We don't have that option, correct?

Edit: Plus, I was trying to see where in VZW I can add/swap devices and that hasn't been apparent yet. I know I can just swap the SIM. I just want to do it right.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
On the left side when you are in your VZW account, under Device Management is a link that says Activate or Switch Device. You'll need the IMEI number. That's how I did it. Piece of cake :)
[Verizon Samsung Galaxy S 4] jstoneky:
I previously purchased a square trade warranty for a retail S4. When I returned it and ordered the dev version (within 30 days), I called square trade and they gave me a full refund for the original warranty, and applied it to a new warranty on my Developer Edition.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Was the warranty for the Dev edition different than the regular S4? Cause I notice on their website they just say Galaxy S4, nothing about Dev Editions.
[Verizon Samsung Galaxy S 4] jstoneky:
I used the regular S4, said the vendor was Samsung, and sent in the receipt which clearly says Developer Edition. They approved it and added it to my account. Just like they don't have different version listed for the 16GB vs 32GB, I looked at it like this is just another version of the same device.

I found nothing on their site saying they wouldn't cover developer editions.
[Verizon Samsung Galaxy S 4] equake:
If we install the retail version stock S4 MDK will we get OTA to ME7? Just curious.
[Verizon Samsung Galaxy S 4] wtherrell:
Now THAT'S scary!!
[Verizon Samsung Galaxy S 4] Bait-Fish:
Having received my Developer Edition yesterday, I've been attempting to get it set up today. From what I gather, everyone is using either of two methods. The old MDK to MD2, root it, and back to MDK kernel (Dev Edition now). Or, ODIN a recovery, boot to recovery, and flash the latest SU of your choice.

I am hoping to get backup copies of the boot.img and recovery.img before modifying much if anything. If I had root, I could accomplish that. Since I don't want to touch the kernel, neither of those methods are for me.

The current ME7 root method doesn't work because the addresses needed are different on our kernel, from what I gather. I am hoping DooMLoRD or someone else can help with using his simplified script to find those addresses and get the ME7 method working for our/all MDK versions. It's just over my head.

Am I over thinking things? I like having fallbacks. I don't see the Dev Edition image at http://opensource.samsung.com/ either.
[Verizon Samsung Galaxy S 4] wtherrell:
By far the easiest way on the Dev Edition is to Odin a custom recovery onto the phone then use that to flash chainfire's SuperSU update. That way you retain all the OYUAMDK Kernel, baseband, etc. You'll be stock, rooted except for a wonderful custom recovery. Just make a Nandroid before flashing anything else. If you plan to use a 64gb sd card I would recommend TWRP as recovery as it seems to handle the large exFat cards much better than the others, at least for me.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
We definitely need some sort of plain stock recovery image even if it's got recovery and SU on it with nothing else changed. I FUBAR'd mine so I don't have a stock recovery to go back to.
[Verizon Samsung Galaxy S 4] markwebb:
You do not need to you use all the old MDK method on the developer edition remember it ships with an unlock bootloader so is totally unnecessary.

all you need to do is to add a custom recovery and root!
[Verizon Samsung Galaxy S 4] Bait-Fish:
Understood. But if/when we need a stock recovery image, do we have one yet for the Dev Edition?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I know that now but at the time I got mine no one was sure how to go about rooting it so I did it wrong and ended up with the consumer version kernel on it. It was only after several days and my phone being customized that I was able to flash back the dev kernel and do a backup. But it wasn't a stock (nothing else on it) backup.

So a clean stock recovery image is really needed :)
[Verizon Samsung Galaxy S 4] markwebb:
Good! Yes, someone needs to upload a clean stock recovery image of the dev edition.

How did you get the dev kernel? Is there a link?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Locofocos posted a clean boot.img file with it in there in this post: http://xdaforums.com/showpost.php?p=44128402&postcount=39
[Verizon Samsung Galaxy S 4] wtherrell:
Kaiya_FL, any thoughts on the Darkslide vs our dev stock rom? I know it is supposed to offer Apps2sd support but what else? I checked & all my apps together are taking up only 1.2 gb. So am questioning whether I want or need a ME7 rom at this point. How much Bloatware does it actually remove & how much storage space does it actually free up?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I have had no problems with the ROM at all, though I did have to flash the kernel that came with it because WiFi wouldn't work. Other than that, it's been perfectly stable. Almost all of the Verizon and Samsung bloat is gone. The My Verizon app and the S Voice, Health, Memo, and Translator apps are still there. Maybe one or 2 others that I froze/uninstalled. I'm only using slightly more space than you, 1.5GB so I haven't used the Apps2SD yet. But, there's always the foldermount app in the Play store if you switch to a MDK ROM. If you do use Darkslide's just remember to freeze the Knox apps to get rid of the annoying message about unauthorized apps.
[Verizon Samsung Galaxy S 4] equake:
Has anyone created/posted a clean Dev Stock NonRooted MDK ODIN image?

Isn't the retail stock recovery the same as the Dev Stock Recovery? I've seen postings of the stock recovery that can be flashed/pusehed on the sxtp forums.
[Verizon Samsung Galaxy S 4] oakley470:
So have we been able to determine yet if need be can we go back to complete stock Dev edition? Like remove the custom firmware warning and triangle and essentially restore phone to out of the box state? Desperately want to get rooted and remove this verizon garbage but want to make sure i can get back to this point safely if necessary. Thanks in advance for anyone who can answer this
[Verizon Samsung Galaxy S 4] markwebb:
I would like to see this as well. I think there might be a slight difference with retail stock.
[Verizon Samsung Galaxy S 4] rmanaka:
Same here! I have avoided rooting as well as custom recovery until we have a stock recovery. I'm hoping that the Dev edition isn't just a cosmetic issue that Samsung is using to placate the Development community.

ADB backup of the stock rom always fails. Without fastboot mode I don't know how to load a temporary recovery to generate a nandroid backup of the stock os and without a temporary root procedure I don't know how to get to the su/dd process to dump the partitions.

If anyone feels like walking me through the process to dump the rom I will be happy to factory reset and start from scratch.

:)
[Verizon Samsung Galaxy S 4] equake:
Does Kies work on this model? If so, maybe that is how everything can be reset to Factory.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Okay, I'm just Googling some stuff and I have no idea if it will work but here are some links to full backups without root using ADB not fastboot:

http://www.howtogeek.com/125375/how...kup-without-rooting-or-unlocking-your-device/

XDA post: http://xdaforums.com/showthread.php?t=1420351
[Verizon Samsung Galaxy S 4] Bait-Fish:
Mine was delivered Monday and I haven't really used it, partly because I would like to help and have this virgin device.

Pity. Fastboot would make this a non-issue, so easy.

Edit: I haven't read technical info on ADB Backup, but it sounds like that's backing up user data and apps, not the system, recovery, etc.

Lightbulb: Anybody here with a Dev phone have root but still stock recovery? Using Terminal Emulator we could copy out the stock recovery...