yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] sub1287:
If it where easy it would be done by now. It is a much more complex process then the majority of people here seem to realize.
[Verizon Samsung Galaxy S 4] Surge1223:
I knew that it was deleting it thats why I posted the whole preceding section as shown below. I didn't say it made the recovery.img I was more making light of the fact that we were all so skeptical of whether system/recovery.img would exist before shutdown, and technically it does. Sorry i guess I could have mentioned it before I just thought it was funny and ironic after all the crap we gave the guy.

ui_print("Removing unneeded files...");

delete("/system/CSCVersion.txt", "/system/SW_Configuration.xml",

"/system/VODB/en_US/checked", "/system/VODB/en_US/en_US-ak

------------------------------then we finally reach this little gem--------------------------------

"/system/lib/libSGIEffect_SmartController.so",

"/system/lib/libSecAvatar.so", "/system/lib/libSmartPhotographer.so",

"/system/lib/lib_SamsungRec_V03009.so",

"/system/lib/lib_SoundAlive_V01013h.so",

"/system/lib/libgoogle_recognizer_jni.so",

"/system/lib/libsensorhubcontext.so",

"/system/tts/lang_SVOX/lh0pt2en-US22_sg.pil",

"/system/tts/lang_SVOX/lh0pt2en-US22_sg_0.pil",

"/system/tts/lang_SVOX/lh0pt2en-US22_sg_1.pil",

"/system/tts/lang_SVOX/lh0pt2en-US22en-US_ta.pil",

"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil",

"/system/recovery.img");
[Verizon Samsung Galaxy S 4] SamuriHL:
Right but it doesn't exist at shutdown. It MAY exist during the upgrade but even that is questionable. They just don't want any remnants of it anywhere. LOL. Just because they have a delete in there for it doesn't necessarily mean it exists. :)
[Verizon Samsung Galaxy S 4] Dolphlungegrin:
You're making it really hard to not keep and MDK GS4 sitting on my desk. . .
[Verizon Samsung Galaxy S 4] SamuriHL:
An MDK S4 is great. Loki support and custom roms. Just never take any OTA updates and there's nothing to worry about.
[Verizon Samsung Galaxy S 4] Dolphlungegrin:
Well. . . it's a long story but it was sent to me because I thought my phone was broken and I called Verizon to get a replacement. They sent me the MDK. Mine is ME7. I fixed my phone but I got a lot of flak on here for saying that I might keep the MDK anyway and send the ME7 back . .
[Verizon Samsung Galaxy S 4] sub1287:
Keep the MDK or you'll regret it.
[Verizon Samsung Galaxy S 4] Sage_F:
I don't understand why you would let a group of people "force your hand". Do whatever you want and screw anyone that tries to get on their moral high horse, knowing full well that most would do exactly what they are telling you not to do.
[Verizon Samsung Galaxy S 4] RaptorMD:
Send back the ME7 and keep the MDK and ignore those who gave you flack. Jealousy is an ugly image to see but if you can rock a custom ROM I would.
[Verizon Samsung Galaxy S 4] Erisnoob:
If I was wrong or out of line I'm sorry. Here's the back story.

http://xdaforums.com/showthread.php?t=2404397
[Verizon Samsung Galaxy S 4] oakley470:
So do we have a way to return to stock (no samsung unlock icon) yet for the dev edition? I see some boot.img posted here but still don't want to root my dev edition until i know i can get it back.
[Verizon Samsung Galaxy S 4] Dolphlungegrin:
In their defense I did sort of proposition my potential devious intent with a sort of evil noob twinge that anyone might attempt to smack down. It also lead me to believe that this was really frowned upon by this community. . .I felt my standing in the community was worth more than the phone. It seems that's not the case and after reading all of the threads about the ME7 bootloader I can't help but think I'll be kicking myself in a few months if I have to buy the dev edition and sell this phone in order to flash.

It's quite alright, we've hashed it out already. I asked for an opinion, I got an answer. Next time I'll keep my thieving debauchery to myself. :laugh:
[Verizon Samsung Galaxy S 4] Erisnoob:
No problem. :cool:
[Verizon Samsung Galaxy S 4] sokrboot:
...crickets...

...tumbleweed...

..sound of a hawk circling overhead...

Is this thread dead?

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] Bloodcrav:
Looks it. This thread is like having blue balls!
[Verizon Samsung Galaxy S 4] oakley470:
I just had a chat with Samsung technical support stating i was a developer in need of the stock firmware for my device. They informed me that a local best buy store would have the ability to obtain that for me. Personally i feel this information is useless because why would anyone at best buy know how/ have the tools to obtain this. But if someone wants to try good luck:good:
[Verizon Samsung Galaxy S 4] equake:
I had the same chat apparently. The Samsung store in BB maybe able to unbrick a phone because they can get at the FW from Samsung but it is doubtful any of the reps are knowledgeable to do such.

I chatted wtih a VZW rep and he mentioned that Motorola handles it slightly differently for their Dev phones but the FW still takes a while to get downstream to the user.
[Verizon Samsung Galaxy S 4] oakley470:
Well I uploaded a request for the firmware to the samsung updates wwebsie thats hosts all the others. Lets hope they can work some magic and get it for us
[Verizon Samsung Galaxy S 4] equake:
Doubtful it will be available since those sites are not Samsung. I suppose the stock Consumer Edition factory image may take us back to OOB but no one has tried.

There is a ROM that is stock/deodexed/rooted for Dev Edition but that is not a factory image.
[Verizon Samsung Galaxy S 4] SamuriHL:
The stock factory image will not downgrade you. It will fail to flash even if you were able to get your hands on it. And uh, considering that a 4.3 ODIN factory image for our GPE, an unlocked phone, was REMOVED FORCIBLY by Samsung, if you do manage to get a leaked factory image, grab it and run for dear life before Samsung does the same. I don't understand their reluctance to leave that stuff alone. Moto doesn't like it, but, they don't give takedown notices for it. And let's be honest....having those images out there actually reduces the amount of warranty returns from bricking.
[Verizon Samsung Galaxy S 4] oakley470:
I don't need/want it for downgrading. As far as I know the developer edition never even got the me7 update? (My phone still has mdk firmware and tells me that is the mostmost up to date) I want the stock Image so if I need to after rooting, get it back to no longer showing Samsung custom/the padlock
[Verizon Samsung Galaxy S 4] SamuriHL:
That's fine. I just wanted to make sure people understood that getting an official ODIN flashable firmware wasn't going to "get around" the downgrading issue. You're telling me, however, that you can't apply the OTA on a dev edition? That seems...odd. It should be identical to the consumer edition except for an unlockable bootloader.
[Verizon Samsung Galaxy S 4] equake:
I'm not sure what you meant by downgrade. I agree that Samsung seems to be reluctant to release images but there are images for the GS3 which are easily found so its kinda a hit or miss.

I've read that the GPe version has numerous bugs especially surrounding the SD card enablement in 4.3 so it maybe cause for them to remove it.

My 2 cents

---------- Post added at 11:20 AM ---------- Previous post was at 11:14 AM ----------

The Dev Edition ships with a different version of the MDK FW i545OYUAMDK vs i545VRUAMDK. Since I don't have a consumer edition I can't really tell if it is actually different but anecdotally some people have said that the kernel is a diffrerent Build.

Both KIES and VZW S/W Upgrade Assistant don't recognize the device as supported.
[Verizon Samsung Galaxy S 4] oakley470:
Yeah but from day one it doesn't let me, just keeps saying im up to date, and kies says I can't do it with my phone model with that program. Anyone else with a dev edition having this problem??
[Verizon Samsung Galaxy S 4] SamuriHL:
I mean someone on ME7 thinking they're going to find a MDK ODIN factory image and being able to downgrade their phone. That won't work. And you have to be careful....ODIN flashable doesn't necessarily mean "from Samsung". Meaning it could just be a partition rip from a phone. That's NOT the same as the images coming from Samsung as the sha1 hashes won't match on a ripped partition and hence won't be "signed".

As for the GPE, no they had a 4.3 leaked build that was posted. That one had even more bugs so it's possible that's the reason they forced everyone to pull it. But I've not seen an official 4.3 Samsung ODIN image. The GPE community created a 4.2.2 and 4.3 ODIN flashable image by pulling the partitions from the phone (and a little "Samuri Magic (tm)" thrown in for good measure on the modem and recovery images to ensure those were signed) but those aren't the same. Of course, on a GPE it hardly matters except for the modem.

---------- Post added at 02:23 PM ---------- Previous post was at 02:22 PM ----------

Well that is definitely interesting. Good to know.

---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------

It would seem I was mistaken. See above.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
The kernel is OYUA as opposed to VRUA and it dated May not April. No clue what other differences there are though.
[Verizon Samsung Galaxy S 4] equake:
Yep, same here tried both kies and vzw s/w upgrade assistant. This convo should continue on this thread.

This thread should be closed because it seeems to be a dead end
[Verizon Samsung Galaxy S 4] Surge1223:
This is a better thread than the bootloader unlock discussion in the general forum though. Much less cluttered.
[Verizon Samsung Galaxy S 4] equake:
Guilty of continuing this thread, even a dump of the stock DevEd partitions converted to an ODIN image would be helpful for unbricking eventhough if its not official.

I suppose we can take the the Consumer ED MDK source code and change everywhere that the BUILD version is reference to OYUAMDK and would create an ODIN image. Of course I've never built a ROM from source code so this is all hypothetical.

Both the MDK and ME7 FW source code are available in the Samsung Developer Repo.

My 2 cents
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Did anyone ever upload the stock Dev modem file? When I flashed to Darkslide it put the ME7 baseband on it and I'd like to get the original one just in case. I figure piece by piece an "as close to stock as it can get" image might be able to be recreated.
[Verizon Samsung Galaxy S 4] Surge1223:
If someone is willing to upload it im interested in it as well, If you need help making the stock image let me know.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I have both a CWM and a TWRP backup from rmanaka that are rooted stock with custom recovery. I also have the stock recovery img file as well. I think I am just missing the stock modem and the knowledge to turn them into something usable in ODIN.
[Verizon Samsung Galaxy S 4] asharad:
I can upload them. Would these be the files you are looking for?

lrwxrwxrwx root root 1970-01-06 17:53 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 17:53 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 17:53 modemst2 -> /dev/block/mmcblk0p12
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I'm guessing so. Any idea how to make one ODIN/CWM/TWRP flashable file out of them?
[Verizon Samsung Galaxy S 4] Surge1223:
Wait, your not planning on flashing a modem tar from the dev edition to consumer one are you? I wanted the file to examine the file, plus the partitions are different and I don't know if the md5 matches up. I don't think it would work.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I have a Dev edition phone. When I flashed Darkslide (the ME7 based ROM) it overwrote the original Dev modem files on my phone. I'm looking for them to be able to do a restore back to factory, or as close as possible, should the need arise :)
[Verizon Samsung Galaxy S 4] Surge1223:
I know how to make the odin package but is there no flashable dev modems or roms based on the stock dev build?
[Verizon Samsung Galaxy S 4] asharad:
I'm willing to upload those files, if I can get some assurance they don't contain any IMEI data or phone numbers.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I have not see any ROMs (or anything else) based off of the Dev build.
[Verizon Samsung Galaxy S 4] asharad:
modemst1 and modemst2 are identical. The same md5 hash. When I open them with a hex editor, the are completely blank (filled with zeroes).

---------- Post added at 06:14 PM ---------- Previous post was at 05:57 PM ----------

mdm is mounted at /firmware-mdm

Is that what you want?
[Verizon Samsung Galaxy S 4] Surge1223:
No, we the file needed is modem.bin, preferably from a stock tar image.

---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------

Actually sorry I read your post wrong mdm contains the modem.bin in it. But it has to be from the original dev edition build
[Verizon Samsung Galaxy S 4] asharad:
hey, no problem. I can help with that.

mdm.img

MD5 - 7f9f7eca2aba8a2f8521f7cff3942668
[Verizon Samsung Galaxy S 4] Surge1223:
Thanks, could you post the results using the commands below through adb?

adb shell

su

dd if=/dev/block/mmcblk0p2 of=/sdcard/modem.bin

dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
[Verizon Samsung Galaxy S 4] asharad:
root@android:/dev/block/platform/msm_sdcc.1/by-name # dd if=/dev/block/mmcblk0p2 of=/sdcard/modem.bin

lock/mmcblk0p2 of=/sdcard/modem.bin <

105528+0 records in

105528+0 records out

54030336 bytes transferred in 11.343 secs (4763319 bytes/sec)

root@android:/dev/block/platform/msm_sdcc.1/by-name # dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin

lock/mmcblk0p1 of=/sdcard/NON-HLOS.bin <

25544+0 records in

25544+0 records out

13078528 bytes transferred in 2.641 secs (4952112 bytes/sec)

Sorry if I misunderstand. Did you want those text results, or do you want the files? If the latter, you already have the first one. The mdm.img file I posted is mmcblk0p2. I'll have the other shortly.
[Verizon Samsung Galaxy S 4] equake:
Scotts ROM is Based off the Dev Build but it pre-rooted/deodexed. I have not tried it so cannot confirm or deny....
[Verizon Samsung Galaxy S 4] Surge1223:
Are the mdm files exactly the same size? If not ill need both if they are the same then I just need the second one. Thanks
[Verizon Samsung Galaxy S 4] asharad:
Ok, I'm getting confused. Let me explain what I've done:

A file list using "ls -l" shows mdm is the same as mmcblk0p2, which you call modem.img

lrwxrwxrwx root root 1970-01-06 17:53 mdm -> /dev/block/mmcblk0p2

This is the file that I posted in the above link:

dd if=/dev/block/platform/msm_sdcc.1/by-name/mdm of=/storage/extSdCard/mdm.img

Are we on the same page?
[Verizon Samsung Galaxy S 4] Surge1223:
Yes I didn't notice that, you should download that instead of flashing an odin tar of the modem.
[Verizon Samsung Galaxy S 4] old&slow:
Scott's rom doesn't include the modem.
[Verizon Samsung Galaxy S 4] Surge1223:
Oh the post said it was a dump of the dev phone I thought he mightve included it.
[Verizon Samsung Galaxy S 4] asharad:
These are from a dev phone, original firmware

mdm.img <- /dev/block/mmcblk0p2

MD5 - 7f9f7eca2aba8a2f8521f7cff3942668

apnhlos.img <- /dev/block/mmcblk0p1

MD5 - e850e23f9c2bd97527b132aaecb0474d
[Verizon Samsung Galaxy S 4] Bait-Fish:
I dropped by the Samsung booth at Best Buy today and spoke with the rep. He said all he could do was flash the retail GS4 firmware. Nothing available Dev Edition-wise.
[Verizon Samsung Galaxy S 4] sokrboot:
^^^ THIS!

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] michaelg117:
So what I get from reading through this is that unlocking the boot loader was a go, but then it wasn't permanent..? Right?

Sent from Navi
[Verizon Samsung Galaxy S 4] :
It was never a go
[Verizon Samsung Galaxy S 4] michaelg117:
What exactly do you mean

Sent from Navi
[Verizon Samsung Galaxy S 4] :
He never unlocked the bootloader
[Verizon Samsung Galaxy S 4] Addiso:
It was just a workaround
[Verizon Samsung Galaxy S 4] Skeetch79:
I actually called Samsung yesterday and spoke with Tech Support. I called to see if there are Developer Images available. She had never heard of anything along those lines and asked what they were. So I explained as simply as I could what stock images (firmware) was. I used the Motorola Wifi Xoom as an example and stated that Motorola hosted software images through their Developer Portal strictly for the case in which you screwed something up; you could reload the software and bring it back to Out of the box, Factory state. She said the only thing she could recommend would be to do a FDR. :-O

I told her that it is a developer phone and that we would want the images to repair anything we may have messed up or in preparation for an OTA. She said to take the phone to the vendor which I purchased it from. I told her that I purchased it from Samsung's website. She quickly told me that Samsung does not sell phones from their website, that I would have gotten the phone from my carrier (Verizon) or from a store like Best Buy.

She said she was on the Samsung website and could not see any options to purchase a phone. I told her to go to the homepage and then I proceeded to literally walk her through the process of searching for the phone, going to the product page and then choosing the "shop" button to add it to the cart. She did everything step by step. She was shocked, solely for the fact that it was right in front of her that Samsung sold a phone - albeit the phone is listed under accessories! She placed me on a hold to speak with her manager and eventually back to tell me that the phone is not supported by Samsung since it is a developer device and that any support would come from my carrier. SMH!

Gotta love it!
[Verizon Samsung Galaxy S 4] Bait-Fish:
Deleted: Posted mistakenly, wrong thread.
[Verizon Samsung Galaxy S 4] SamuriHL:
If it's unlocked you can put it in fastboot mode and use fastboot boot recovery.img and it should temporarily boot a custom recovery so you can root. Doing it this way won't overwrite the stock recovery so you can pull it. Use cwm or twrp to root it by flashing the supersu zip.
[Verizon Samsung Galaxy S 4] asharad:
Thanks. Any idea where I can find the supersu.zip? Chainfire's website is down.
[Verizon Samsung Galaxy S 4] SamuriHL:
Pm'd you a link to my dB.
[Verizon Samsung Galaxy S 4] Galaxys4bean:
yessss, so excited right now!

Keep us updated man!

Thanks for the hard work!
[Verizon Samsung Galaxy S 4] asharad:
Don't get excited. I'm still trying to figure out what fastboot is and how I can use it to root.....
[Verizon Samsung Galaxy S 4] Galaxys4bean:
I know, but we have hope now!
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Fastboot is usually included in with ADB except it doesn't work on the S4. That's why we have ODIN and Download mode.
[Verizon Samsung Galaxy S 4] SamuriHL:
Well you need a custom recovery image like cwm or twrp. The fastboot boot recovery.img was just a template. Once in fastboot mode you can try that to temporarily boot into cwm or twrp, then use install and select the zip I linked you to. But the fastboot command... You replace recovery.img with whatever the filename is for twrp or cwm.
[Verizon Samsung Galaxy S 4] sub1287:
Might be easier for you to do it rather then teach Sam. ;)
[Verizon Samsung Galaxy S 4] SamuriHL:
My gpe device ain't gonna help you poor vzw users. ;)
[Verizon Samsung Galaxy S 4] rmanaka:
Yes, problem is that without root we cannot get "su", and without "su" cannot get read permissions for /dev

I think we can get rooted by running Odin, flashing the MD2 kernel, running Motochopper, and flashing the Dev kernel but that means that we would need a Odinable Dev kernel. This will also technically modify /dev/block/mmcblk0p23 so the first dump would be invalid unless the flash of the Dev kernel was a truly stock boot.img?

Anybody have instructions on how to make a full dump of the phone to get a return to stock tarball?

No fastboot mode on Vzw S4 so can't boot a temporary recovery image to root.
[Verizon Samsung Galaxy S 4] asharad:
Man, I'm sorry, but I really don't understand. Maybe a little more step by step?

---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------

Thanks. I was hoping I understood some of this. The last thing I want to do is render my device useless to OP.
[Verizon Samsung Galaxy S 4] SamuriHL:
I have to sleep soon but there are threads for the ig505 on how to do this process for rooting. You basically do the same thing only substituting twrp or cwm for your phone. If it's a device phone and unlocked it should work without having to overwrite any partitions.
[Verizon Samsung Galaxy S 4] rmanaka:
Phew, this thread moves so fast sometimes so you can't edit a post without getting way behind! :)
[Verizon Samsung Galaxy S 4] asharad:
I'm having trouble booting to fastboot mode. I can get into recovery and ODIN. But the key combination I was given for fastboot (both volume keys + power) just boot normally.
[Verizon Samsung Galaxy S 4] rmanaka:
Same here... Lots of reading and research but without the true return to stock (Developer's Edition) I haven't rooted either!

You would think that since Samsung made the full retail profit from the sale of the Dev edition they would be nice to release the stock image for the phone! (or is that something they expect a developer to dump on their own?)
[Verizon Samsung Galaxy S 4] asharad:
I was sent on a wild goose chase. S4 doesn't have fastboot. http://xdaforums.com/showthread.php?p=44189334&highlight=fastboot#post44189334

It's getting late, and the OP isn't around. So I'm going to bed soon and we can try again tomorrow. I will be available at about 5:30PM CENTRAL time tomorrow. My phone is still non-rooted original stock DEV edition. See you later.
[Verizon Samsung Galaxy S 4] rmanaka:
Thanks, I will research that!

We can get ADB Sideload mode so I wonder if we can root this way since Fastboot is not available?
[Verizon Samsung Galaxy S 4] thedeveloper1:
Heres s dump from rooted me7

http://dobastudios.com/dumpingimgs.zip
[Verizon Samsung Galaxy S 4] TechSavvy2:
Its download mode in Sammy devices. Vol down + home key + power key
[Verizon Samsung Galaxy S 4] Bait-Fish:
I also have a pure stock Dev Edition and can help. I have been pinging around trying to get someone to get root using the ME7 DooMLoRD based version (perf_event exploit). It would get us root on this Dev Edition without touching boot and recovery as far as I know. DooMLoRD and PWM978 have not replied to PMs and no one else in that thread have chimed in on how to use DooMLoRD's script to get the addresses to make it work. I am sure our older MDK version can be rooted with this method since it works on the newer ME7.

Another question. Can SU be flashed from ODIN? I see SuperSU mention it's MobileODIN flashable. I am unsure if our device/s supported. MobileODIN Lite mentions a flash kernel. Would that "taint" any of the necessary dumps?

Sorry for the questions, but new to Samsung and ODIN.

Edit: Maybe between asharad and I, we can use two different methods. One using ODIN to flash a recovery, after which everything but the recovery should be good for rajat12345. The other ODIN using the original MDK to MD2 kernel Motochopper method, to grab the recovery image. Something to that effect. Thoughts?

Edit x2: Mobile ODIN requires root so that's not an option.
[Verizon Samsung Galaxy S 4] SamuriHL:
No. Apparently the vzw version doesn't have it. My gpe does. For us it's volume up and down then power. That is different then Odin mode.