yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Bait-Fish:
The below files are from my stock Dev Edition using Philz custom backup and restore. Unzip and place the folder into your CWM or TWRP directory. These are untested since I just made them with Philz recovery. The usual warnings apply. Use at your own risk.

Boot only

https://app.box.com/s/x3img6dpm7tb4l8nbzvq

76ed901b213734ea5b5a0773b97397c7

Modem only

https://app.box.com/s/3obrft2ldqx1gy6qif0l

c7c39edde244f87ce9d852b5c17f7f26

Radio only

https://app.box.com/s/nv131xqb104tqf5ddgbd

ec70eed7c3c3590f81e7f244d3043084

Boot, modem, and radio all-in-one

https://app.box.com/s/rzs8nahgstknytx8m08h

80973dceb6cec7dedd66303e4e7be81f
[Verizon Samsung Galaxy S 4] wtherrell:
Great! I think that is what we were looking for.
[Verizon Samsung Galaxy S 4] Bait-Fish:
One thought about my boot linked above. I dd'd Asharad's boot.img to get the Dev kernel back after having obtained root with the old kernel swap/root method. So, not necessarily untouched there, but his boot was virgin so I'm confident it is the same.
[Verizon Samsung Galaxy S 4] markwebb:
Ok, am a bit slow today. So now that we have these files, do we ODIN? What do we do with them? Is someone compiling them to create a stock recovery for the Dev phone? Sorry, long day here and am confused. LOL
[Verizon Samsung Galaxy S 4] Bait-Fish:
I was under the impression we were closer to ODIN with the dd'd files since there seems to be some success tar/md5'ing. But, reading open1your1eyes0' comment in a thread elsewhere from a few months ago that the dd blocks don't play nicely with ODIN tempered my enthusiasm for a full system ODIN image of our making.

sextape's image is from the manufacturer which explains the different file types within his.

Unless someone figures something out, this is all we have.
[Verizon Samsung Galaxy S 4] equake:
I would think that tarring the img files would get us ODIN files. Of course we would need to figure out the Factory ODIN image structure to make sure all the pieces are there.
[Verizon Samsung Galaxy S 4] asharad:
It's not that simple.

CWM doesn't provide a backup of every partition needed. It only gives:

- System

- Data

- Boot

- Recovery

- Cache

- Modem

- Radio

The stock ODIN flash includes other partitions not found in a CWM backup:

- aboot

- hidden

- non-hlos

- rpm

- sbl1, 2, 3

- tz

Also the ODIN flash does not include Radio, only Modem. Additionally, the ODIN flash utilizes several file formats such as mbn, ext4, and bin. I've tried researching mbn, but haven't found any information related to compiling/compressing/packing an mbn file. The ext4 should be pretty easy. Bin files are also something I'm not too sure about.
[Verizon Samsung Galaxy S 4] equake:
bin files shoud be self executing files, mbn files are related to the modem/radio. Maybe its time to get these from the source code. I'll have a look but in the end without the actual files its a shot in the dark. Since Samsung is having their dev conference in Oct maybe they will have more info available.

Whats interesting is the GPe version doesn't have any official binaries either since its not controlled by AOSP like the nexus devices.

My 2 cents.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I meant to post this a couple days ago. I have a retail GS4 which I plan to sell so I used sextape's full stock ODIN image to flash back to stock. I dd'd the partitions before and after and compared MD5s. I find it odd that they don't match better.

Edit: I posted previously what files matched between the retail and Dev Edition. Trying to figure out what is similar... Which appears to be everything that matched previously.
[Verizon Samsung Galaxy S 4] asharad:
That is kinda odd. I would expect the "persdata" partitions to be different. "recovery" as well, if you were running a custom recovery.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Recovery was different between the two (TWRP vs Philz) so I expected that. The root method, same for both, used the same boot.tar so that was expected to have a matching boot.

I didn't attempt MD5 on system or userdata due to their size. That, and I had modified system on the previous. They weren't worth the time.
[Verizon Samsung Galaxy S 4] EMSpilot:
Recovery via Odin

I downloaded Philz recovery to my Dev Phone via Odin and now I cannot get into recovery.

Any Idea's? The phone boots up ok and I get the unlocked logo with the word custom!!

Thanks for any help
[Verizon Samsung Galaxy S 4] equake:
You just need to boot with the correct key combos namely power+volume up
[Verizon Samsung Galaxy S 4] EMSpilot:
Recovery

I did use volume up and power. Get the blue recovery in left hand corner then I get Unlocked logo and custom then it boots phone. It never goes into recovery. Does someone have a good link to a Tar file with a recovery for the dev phone with no LOKI?
[Verizon Samsung Galaxy S 4] wtherrell:
Post #8 of this thread.
[Verizon Samsung Galaxy S 4] EMSpilot:
I did use that link

That is the link I used. Is there a link to TWRP recovery in a tar?

Thanks
[Verizon Samsung Galaxy S 4] old&slow:
Try volume up + home + power then at the samsung splash screen let go of power and hold volume up and home until recovery opens.
[Verizon Samsung Galaxy S 4] EMSpilot:
Nice!!!

That worked Thanks!!!!
[Verizon Samsung Galaxy S 4] asharad:
Getting into recovery has been a bit quirky for me. Try this.

Hold volume up and power until you see the blue text. At the blue text let go of the power button. Continue to hold the volume up the phone will reboot and show the blue text again. At the second sight of the blue text let go of the volume. The phone will reboot again this time into recovery.

This usually works for me.
[Verizon Samsung Galaxy S 4] old&slow:
No problem..glad you got it:thumbup:
[Verizon Samsung Galaxy S 4] EMSpilot:
TWRP with Philz

Would you have a link to TWRP with Philz touch?

Thanks Again
[Verizon Samsung Galaxy S 4] equake:
This works for me too or use goo manager to reboot into recovery.
[Verizon Samsung Galaxy S 4] old&slow:
Sorry, I sure don't:confused:
[Verizon Samsung Galaxy S 4] Bait-Fish:
TWRP and Philz (CWM) are two different recoveries. Here is a link to an ODIN flashable non-loki version for the Dev Edition GS4. The recovery flashable zip version is located in the same place, here.

Before doing that, I suggest downloading Quickboot from Play store (if you already have root) and use it to reboot to recovery. Like someone else mentioned, Goo Manager and ROM Manager can reboot to recovery.

It sounds like you're just having trouble getting the key combo right to me.

Edit: Asharad's method is how I have experienced too.
[Verizon Samsung Galaxy S 4] EMSpilot:
Thanks

Thanks I was just getting ready to flash a 4-1 reboot zip that modifies android.policy.odex. But I will try the Play Store first.

---------- Post added at 04:41 PM ---------- Previous post was at 04:27 PM ----------

Does anyone know if you can drop a modified eri.xml on the dev phone to change the carrier label etc?

Thanks
[Verizon Samsung Galaxy S 4] wtherrell:
I never found one. After rooting I downloaded Goomanager and installed TWRP from within its settings. I am given to understand that there is a method for converting the flashable TWRP zip files to tar. md5 but have not tried it.
[Verizon Samsung Galaxy S 4] EMSpilot:
TWRP

Are you having any issues with TWRP? It is my favorite!!
[Verizon Samsung Galaxy S 4] wtherrell:
No real issues. And I am on the much maligned 2.6 version. I find that if I need to back up radios and modems TWRP doesn't seem to have that option. Philz Touch has this and can back up in either CWM or TWRP format. I prefer the UI of TWRP and it allows me to back up to my 64gb sdcard whereas Philz Touch doesn't see it at all. So I end up using both.
[Verizon Samsung Galaxy S 4] dalerp:
I still feel like I'm new to this. I took the plunge and installed PhilZ Touch recovery. Currently I'm making back ups and am currently looking to install a ROM. (Looking at AOSP type of ROMs) My understanding is for standard S4s Loki is used to get around locked bootloader issues. If this is the case then given that this is the norm do I need to look around to check and see ROMs that explicitly state are non-Loki'd?
[Verizon Samsung Galaxy S 4] sparky697:
No I don't think so. It's the recovery that is loki'd not the Roms.
[Verizon Samsung Galaxy S 4] dalerp:
What about kernels?
[Verizon Samsung Galaxy S 4] Bait-Fish:
There has been a lot of discussion about kernels and use of scrosler's dev modules throughout this thread. I don't have experience there yet.
[Verizon Samsung Galaxy S 4] sparky697:
I haven't had to use any mods yet either but I have only flashed the 3 versions of eclipse so far. It takes so long to back up and install a new ROM that I haven't had the time to do it as much. Lol.
[Verizon Samsung Galaxy S 4] Firemedic:
The Dev modules work like a charm when flashing any Kernel. I flashed KTs kernel and then the Dev modules and things have been working awesome, No issues. Without the Dev modules Wifi won't work and I am sure there are a few other things as well.
[Verizon Samsung Galaxy S 4] wtherrell:
Without them I would have returned the phone and wait for Nex5. scrosler's dev modules made roming viable for me on this phone.
[Verizon Samsung Galaxy S 4] equake:
Has anyone tried the stock ME7 Kernel and does it work without flashing the Dev modules?
[Verizon Samsung Galaxy S 4] wtherrell:
Not here. Haven't seen the need. I'm on Hyperdrive 8.1 with Elite kernel & the modules. Would be interesting if it worked without the modules, though.
[Verizon Samsung Galaxy S 4] asharad:
I'm afraid to try that.
[Verizon Samsung Galaxy S 4] clank714:
Heh, seems like not too much different from the dev version to the normal version, oh well.
[Verizon Samsung Galaxy S 4] markwebb:
Yes and no. At least with the Dev edition boot loader is already unlocked and you don't have to go thru that Loki process. Moreover the original retail version which contains the MDK build is now very hard to find, and you can only root the newer AME build since a custom recovery has not been established and the boot loader can't be unlocked.
[Verizon Samsung Galaxy S 4] asharad:
The key difference is the Dev version isn't locked.
[Verizon Samsung Galaxy S 4] rmanaka:
I'm running Bonestock 1.1.3 with KT kernel using defaults. I have not flashed [MENTION=426561]scrosler[/MENTION]'s modules and everything works for me.
[Verizon Samsung Galaxy S 4] dalerp:
Locked hilessAs

I tried CM, but I had no network and camera was broken but wifi works. Does that mean I need the dev modules?
[Verizon Samsung Galaxy S 4] wtherrell:
If wifi works but no Internet connectivity the dev modules solved it for me.
[Verizon Samsung Galaxy S 4] dalerp:
Dev modules did nothing.
[Verizon Samsung Galaxy S 4] Bait-Fish:
[MENTION=335907]sound-mind[/MENTION] posted in the bounty thread about how he bricked his Developer Edition. I figured some here would be interested.

And, what he means about the MDK is on the way is that he sent Safestrap author Hashcode a S4 to develop on. Great news having Hashcode onboard!
[Verizon Samsung Galaxy S 4] old&slow:
If what you mean is that you could not activate, no phone #, no imei, not connected to vzn network then you should try a different recovery like official cwm. That's what I had to do. I was using Philz touch and worked fine for 4.2.2 ROMs but would not work on 4.3. I hope that helps.
[Verizon Samsung Galaxy S 4] dalerp:
It makes sense since I am currently using a 4.2 ROM and Philz Touch. I could try TWRP or CWM but both look like they are using Loki.

http://xdaforums.com/showthread.php?t=2292112

http://teamw.in/project/twrp2/181

I heard that there is a version of TWRP without Loki but I could never find it.
[Verizon Samsung Galaxy S 4] old&slow:
Not sure about non-loki twrp but you can install cwm through ROM manager and the official cwm is not lokified.
[Verizon Samsung Galaxy S 4] dalerp:
That did the trick! :victory:

One last thing: is it safe to assume that I can still use the latest CWM to restore backups I made with Philz Touch? I made a backup of stock before I started flashing and would like access to that in case of issues like GPS.
[Verizon Samsung Galaxy S 4] old&slow:
Best bet is to us the same recovery you made the backup with. Find a .zip of that recovery that you can flash in cwm.:)
[Verizon Samsung Galaxy S 4] Bait-Fish:
I understand all the recovery nandroids are compatible. Make a backup of your present system before trying.
[Verizon Samsung Galaxy S 4] dalerp:
One last thing I just realized is that with Philz Touch the recoveries are stored in my internal memory as expected. For some reason, however, I cannot find where the recoveries are stored in CWM. CWM cannot see my Philz recoveries and I cannot find my CWM backups, even when I use a file explorer.
[Verizon Samsung Galaxy S 4] old&slow:
I just looked and the backup I made with Philz is under Clockworkmod/backup. Mine is on the ext sdcard but that's where I told it to put it. But when you do find it you'll have to move it to the ext SD because that's the only place official cwm looks.
[Verizon Samsung Galaxy S 4] dalerp:
- I don't have an external SD card.

- I can get to my Philz Touch recoveries from a file explorer and even extract it. I can't get to them from CWM, as it doesn't go to the emulated/0 directory at all for backups/restores.

- Any backups I made from CWM I can only access from CWM. I can't find them in the file system and is placed under sdcard directory according to CWM.
[Verizon Samsung Galaxy S 4] old&slow:
When I looked it didn't even give the option to restore from internal mem.:confused:
[Verizon Samsung Galaxy S 4] EMSpilot:
TWRP for Verizon GS4 Dev Phone

I have been working with Dees_Troy on a TWRP recovery for the Verizon GS4 Dev Phone. I will be testing soon and post a link when we have a working product!!
[Verizon Samsung Galaxy S 4] wtherrell:
Been using TWRP on my Vzw dev phone for some time now. Both 2.5 & 2.6. You mean they don't work? I will welcome your version. What improvements may we look forward to?
[Verizon Samsung Galaxy S 4] EMSpilot:
NON LOKI version

This will be a clean NON-Loki version. As we do not need loki with a Dev Phone.
[Verizon Samsung Galaxy S 4] wtherrell:
Ok. Did not realize I was using lokied recoveries. How can one tell? Everything seems to work fine.
[Verizon Samsung Galaxy S 4] equake:
Couldn't we just flash one from Goo Manager? But that would have to be flashed from an already custom recovery I suppose.
[Verizon Samsung Galaxy S 4] wtherrell:
Don't know. My understanding is that if you are rooted, goomanager can install TWRP regardless of whether you already have a custom recovery installed.
[Verizon Samsung Galaxy S 4] Skeetch79:
Just a quick question to clarify since I am new to the Dev Phone scene and I just read all 30 pages of this thread in one sitting after a long day at work.

I have Philz Touch Recovery installed on my Dev Phone, if I take both the Boot.img and Recovery.img's referred to in this thread by Bait-Fish, et al and convert them into ODIN flashable files then flash them will that revert me to MDK stock Boot and Recovery? (My system is only rooted, no other mods made).

I did make a nandroid after flashing Philz Touch Recovery in ODIN, except I installed Su/SuperSu and rebooted the phone before making the nandroid <-bonehead move on my part
[Verizon Samsung Galaxy S 4] Bait-Fish:
Since you haven't changed your kernel, you only would need to ODIN the recovery.img (after you first tar.md5 it properly to be ODIN flashable). That would restore the stock recovery.

Using PhilZ, I suggest you make a custom kernel backup now too so you have that at your disposal in recovery as you bounce between ROMs and kernels.

Is there a way to flash in recovery a zip that would remove SU/SuperSU?
[Verizon Samsung Galaxy S 4] Skeetch79:
So in order to change the .img file to an ODIN flashable file I would just issue these commands via Cygwin?

tar -H ustar -c recovery.img > recovery.tar

md5sum -t recovery.tar >> recovery.tar

mv recovery.tar recovery.tar.md5

And to reiterate, this is for the Galaxy S4 Developer Edition on MDK (stock) right?

Also I thought I had come across at some point a flashable zip which would remove Su/SuperSu. I have seen apps like Ginger Unroot which unroot the phone, but I am not sure which devices are supported.

But, great thread! Tons of great information, you guys rock!
[Verizon Samsung Galaxy S 4] Skeetch79:
**DELETED**
[Verizon Samsung Galaxy S 4] oakley470:
Have you verified this set of commands now?
[Verizon Samsung Galaxy S 4] Skeetch79:
I did in fact verify the commands with both the boot.img and recovery.img downloaded from this thread.

I had installed cygwin and then opened up a cygwin terminal from the desktop shortcut created. I copied the boot.img and recovery.img files to the following directory on my PC: c:\cygwin\home\uinjg (uinjg is the username i am logged into windows as, yours will differ. The img files are placed within the folder created after the terminal window opens inside the "home" directory not within the "home" directory itself)

I issued the commands without problem. I have not flashed these particular files, however I did flash a CWM recovery img file downloaded from clockworkmod's website. I have not had any problems.
[Verizon Samsung Galaxy S 4] oakley470:
Thanks! please let me know if you flash them back and are able to successfully go back to stock
[Verizon Samsung Galaxy S 4] cawaller:
[Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!![/QUOTE]

Newbie to Samsung and the Dev edition. Have rooted and rommed 2 different HTC devices and 3 different Motorola devices but still confused on how to with the Samsung.

Did anyone ever get a thread started for Dev Owners to do this? I began reading through this forum and I am not any closer to being clear on how to root or rom this phone than I was when I started reading.
[Verizon Samsung Galaxy S 4] equake:
Newbie to Samsung and the Dev edition. Have rooted and rommed 2 different HTC devices and 3 different Motorola devices but still confused on how to with the Samsung.

Did anyone ever get a thread started for Dev Owners to do this? I began reading through this forum and I am not any closer to being clear on how to root or rom this phone than I was when I started reading.[/QUOTE]

Dev Edition has unlocked bootloader. To root is fairly straight forward.

1) Install ODIN on your PC

2) Download an ODIN custom recovery

3) ODIN flash a custom recovery like Philz (Thats what I'm using), TWRP.

4) Copy SuperSU.zip to your S4

5) Flash SuperSU

6) Ur rooted check with root checker or use voodoo root keeper

The trick is to get ODIN flashable files which are tarball images. Search around these forums/threads and you will find some.

ODIN is like fastboot for MOTO but specific to Samsung devices.

This is the first retail Samsung I have (Also have the Gnex but that doesn't really count)
[Verizon Samsung Galaxy S 4] wtherrell:
Newbie to Samsung and the Dev edition. Have rooted and rommed 2 different HTC devices and 3 different Motorola devices but still confused on how to with the Samsung.

Did anyone ever get a thread started for Dev Owners to do this? I began reading through this forum and I am not any closer to being clear on how to root or rom this phone than I was when I started reading.[/QUOTE]

1. Drivers

2. Download a recovery to your PC. You are going to install this recovery to your phone using Odin. It should be a. Tar. Md5 format.

3. On your PC get into Odin.

4. Connecting phone to PC via USB. Be sure "USB debugging" is checked.

5. Once Odin shows your device. Select PDA mode. Browse to the recovery and select it in Odin. Push the file to your phone from Odin.

6. You should now have a custom recovery on your phone.

7. Download chainfire's SuperSU zip and flash from the recovery. Once complete you will be rooted.

Follow this outline. You will find links & help in these forums.

If on dev edition be sure to get unlokied recovery.

Sent from my Hyperdriven GS4 I545 Dev Edition
[Verizon Samsung Galaxy S 4] Skeetch79:
I was able to successfully flash the boot and recovery images from this thread all the while keeping my rooted stock system. However, I am still seeing the Samsung Custom boot screen with the open lock icon and in Settings->About Phone->Status->Device Status I see Custom. I have stock Recovery, Boot and System with Root. How can I clear this or am I seeing Custom because I am rooted? When entering download mode (volume down + Power, then Volume up to select) I see both Binary and System statuses as Custom. How can I reset everything back to Official? Will TriangleAway help or am I missing something else? Thanks.
[Verizon Samsung Galaxy S 4] equake:
Since you have created the Odin flashables maybe you will be so kind enough to past those in the Dev forum.

Thanks
[Verizon Samsung Galaxy S 4] Skeetch79:
I can surely post them, but they were created from Bait-Fish's boot and recovery image files using Cygwin and the following command lines:

tar -H ustar -c recovery.img > recovery.tar

md5sum -t recovery.tar >> recovery.tar

mv recovery.tar recovery.tar.md5

Place both the boot.img and recovery.img files inside of C:\cygwin\home\<user name>\ folder and run the above commands. Substitute "boot" for "recovery" when creating the ODIN flashable boot file.

Still want me to create a new thread with the two files?
[Verizon Samsung Galaxy S 4] Roland_D:
Hello everybody!

The process to get custom recovery and boot seems quite straightforward... I have a few questions though. I apologize but I just spent $700 (HOLY CRAP) for this phone... my wife has a bounty on my head and I really would like not to brick it cause my next phone will be a disposable one from Walmart.. So that said I have a few questions I hope you guys can answer.

1) Is there any other recovery beside Philz that would work with it? Assuming a recovery can work with a phone and not the others which I am not sure of...

2) Is there a way to get the Dev Ed back to when it came out of mom Samsung's womb (aka odin factory image)? or it's just a normal MDK image? although I think MDK's bootloader is locked... so, yeah I am confused about this... In case I brick my phone how to I start over from a clean slate?

Thanks guys!
[Verizon Samsung Galaxy S 4] Skeetch79:
Yeah that $700 is pretty steep!

To answer your last question, a few of us are trying to obtain the Factory Images for the Developer Edition. It runs firmware JDQ39.I545OYUAMDK with the same baseband. The retail phone runs firmware VRUAMDK. I would be very reluctant to flash the VRUAMDK firmware on our developer device. I guess you can say, though, that both the retail version and the Developer version run MDK software, just different versions.

You can always boot your phone into download mode, flash Philz Touch Recovery, reboot into Recovery, create a Nandroid and then flash SuperSu if you wish for root. Within this thread are links to download the stock Recovery.img and stock Boot.img if you need them.

It would be nice to have a safety net of sorts to fall back to. Even contacting Samsung directly yields no answers. I explained I was curious as to whether Stock Firmware was available and they said maybe Best Buy or my Carrier could flash the device back to stock. Um, why would B.B or Vzw have it and not Samsung? Probably what Vzw and B.B. has is the VRUAMDK firmware not ours.
[Verizon Samsung Galaxy S 4] Roland_D:
Oh that's hilarious! I wouldn't take any of my device to the geek squad not even if I had to...

So it's not possible to dump everything there is on a CLEAN DevEd and pack it up to be odin flashable in any way?

The info about the firmware version was very useful and scarily EASY to overlook... thanks. I downloaded all the files I need from this thread I just wish there was a sticky for DE... such an expensive phone should have clearer instructions and links to prevent it's users from bricking it..