yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] rmanaka:
Good information but that's what I can't get to successfully complete! :mad: ! I haven't tried a compressed backup so the file is huge and so far won't complete...

Thanks!

---------- Post added at 09:12 PM ---------- Previous post was at 08:54 PM ----------

Just musing... What if we flash the MD2 kernel, do the Motochopper root exploit and then restore the Development Edition kernel. Dump the stock recovery and package it into a zip . If somebody else flashes a custom recovery without root and then creates a stock minus recovery package, would we have a two step flash back to stock Development MDK?

Am I missing something here?
[Verizon Samsung Galaxy S 4] Bait-Fish:
If someone here has rooted the MDK to MD2 to MDK ODIN way and still has a stock recovery, you can use these commands in Terminal Emulator.

su
cat /dev/block/mmcblk0p21 > /storage/emulated/0/recovery.img

That will copy the recovery to the file recovery.img on your internal storage.

Edit below: You posted while I was composing

Seems reasonable. I guess that's what I was getting at above but didn't say explicitly to go back to the Dev kernel. :cool:
[Verizon Samsung Galaxy S 4] Bait-Fish:
There has been no word back regarding my preferred hope to modify the ME7 root method to MDK so I wouldn't have to flash anything.

Tomorrow I will likely go ahead with the ODIN MD2, Motochopper root, copy out the stock recovery, then ODIN back Dev MDK. Then with TWRP or CWM I'll get a fresh, clean stock nandroid to put out there for you.

Some questions. What's the preferred recovery to use? I read TWRP was having some issues requiring multiple wipes on some ROMs, like it was still leaving traces causing dirty flash symptoms.

Is there anything that I may need to sanitize out of it? Maybe device specific info, IMEI, or such.

It would be nice to make a single ODIN flashable stock image like the retail sxtape one.
[Verizon Samsung Galaxy S 4] asharad:
I'm sitting here with a stock Dev edition, non-rooted. Unfortunately I know so little, I'm not sure how I can be any help.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I'm using CWM because I heard of the TWRP issues. I wish I had some advice for you. I've googled how to create an ODIN recovery file but none of it made much sense to me. Most of it looks like it needs to be done in a Linux environment either real or virtual. Been a long time since I really dabbled with Linux.

---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------

Go to this thread:

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

Read the posts there. rajat12345 is looking for someone with a stock dev device. If you're not sure what he's asking, PM him and I'm sure he can walk you through it :)
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I think there was issue with the latest version of TWRP. If you went back one version everything was fine. And it was just some people having problems, not everyone. That's another reason why an ODIN flashable stock recovery would be best so it didn't matter what recovery you use. I think :)
[Verizon Samsung Galaxy S 4] asharad:
Is there a method to root the DEV edition without wiping out the DEV kernel?
[Verizon Samsung Galaxy S 4] wtherrell:
Installing recovery with Odin then using that recovery to flash chainfire's SuperSU update to root preserves the Dev kernel.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Looking at the process earlier in the thread (post #8), they flashed Philz custom recovery and then flashed SuperSU to get root. Neither of these will replace the Dev kernel, if I am reading that post correctly. Maybe someone will reply who knows for sure how to do it since I'm not sure if having a custom recovery will mess up what rajat12345 is working on. Maybe flashing SuperSU with ODIN? This is the link for the ODIN flashable SuperSU zip but I keep getting a server error when I try to go there:

http://download.chainfire.eu/supersu

Maybe if you search the Dev forums there will be another link for it.
[Verizon Samsung Galaxy S 4] asharad:
I've been looking for it.... nothing but dead links.
[Verizon Samsung Galaxy S 4] Bait-Fish:
SU flashed in ODIN sounds perfect, what I've been seeking a couple days now. Is that possible? SuperSU lists it as MobileODIN flashable. I am not sure our model is supported. I am quite new to ODIN and Samsung devices.
[Verizon Samsung Galaxy S 4] asharad:
What's the worst thing that could happen if I try? Could I brick the device?
[Verizon Samsung Galaxy S 4] Bait-Fish:
Unsure without other's feedback. Let's wait to hear from rajat12345 in his thread.

Edit: Just read and realized Mobile ODIN is root only, so that's out of the question.
[Verizon Samsung Galaxy S 4] wtherrell:
I dl'd the modules. Haven't tried it yet but could you be so kind as to list the kernels that worked for the wifi. I tried Hyperdrive rom & ran into no wifi issue. I'm puzzled why stock dev ed kernel has the same problem on those roms. KT Kernel would turn on but but kept disconnecting due to "low Internet connectivity". So would appreciate some leads on kernels that work for this issue.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
When I first installed Darkslide's ROM, WiFi didn't work. I flashed the Custom Team Project Elite kernel from the Darkslide page. Wifi started working again and I haven't had an issue since.

I'm confused too as to why the dev stock ROM didn't work.
[Verizon Samsung Galaxy S 4] silver7x:
So I have been reading a lot of the posts on XDA (I have just finished reading this entire thread) and I am a lot confused. I just got my Dev Edition in the mail and couldn't wait to install a new ROM on it (I really wanted a clean 4.3 build, but cant seem to find one for Verizon).

Whats confusing me the most is that before I bought the phone I read at multiple sites that it would have an unlocked boot loader which means I can easily install custom ROMS on it. But based on what I am reading here (and a quick check I did on my phone) it is not rooted, further more, most of the ROMS for the i595 wont work because it is a Dev Edition.

so I guess I have 2 questions

(1) what are the benefits, if any, to having a Dev edition.

(2) is there a straight forward way for me to change my rom and keep those benefits.

Thanks
[Verizon Samsung Galaxy S 4] Kaiya_FL:
1) The Dev edition has and always will have an unlocked bootloader. No special tricks need to unlock it to be able to flash ROMs and mods. You do still need to root your device and the easiest way found is to use ODIN to flash a custom recovery and then with the custom recovery, flash SuperSU. That way none of the dev files change. It's still pure stock.

2) Depending on the ROM, you may need to install a custom kernel too. Keep in mind the kernels that the custom are all based off of consumer edition kernels, which may differ from the dev one. No one's been able to answer what the differences are. I know there are some differences in the Bluetooth profiles that come with the dev and consumer editions. Though I don't know if those profiles are stored in the kernel or in the ROM.

We hope to have one of the folks with a new, stock dev edition provide us with some sort of stock recovery image.

I'm not an expert (I don't even play one on TV) but I hope that helps a little :)
[Verizon Samsung Galaxy S 4] asharad:
Here is my understanding but I could be wrong. The advantage is the bootloader is unlocked and you can install any rom that works on the commercial version. You can also root it.

On the downside if you do those things it is no longer a stock developer device. Nor is there a method available to return it to stock.
[Verizon Samsung Galaxy S 4] silver7x:
Cant boot(vzw_s4_dev_MDK_PhilCWMbackup).img restore it to original?

---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------

It helps a lot... I guess what you are telling me is that I should have gotten the google play edition..

Thanks again
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Is that an actual .img file? If so what's the link to download it?

And if you're on Verizon, the Google Edition would do you no good. It only works on ATT & T-Mobile.
[Verizon Samsung Galaxy S 4] Bait-Fish:
There is no Verizon Google Edition.
[Verizon Samsung Galaxy S 4] equake:
The bootloader is unlocked but all ROMS are written for a custom recovery and there is no factory image so returning to its Clean state is impossible.

I wondering if the retail stock recovery can be used? Anyone want to try?

My 2 cents
[Verizon Samsung Galaxy S 4] Bait-Fish:
I will post up my stock recovery once we start getting images for rajat12345 in the other thread.
[Verizon Samsung Galaxy S 4] wtherrell:
[

I'm confused too as to why the dev stock ROM didn't work.[/QUOTE]

In the thread locofocos referred to, scrosler's answer is that the required dev edition modules are not contained in the boot.img
[Verizon Samsung Galaxy S 4] Kaiya_FL:
In the thread locofocos referred to, scrosler's answer is that the required dev edition modules are not contained in the boot.img

Ah. So if I flashed the Dev kernel back and installed the module zip, then WiFi should work? That's the only thing I had problems with when I first flashed Darkslide.
[Verizon Samsung Galaxy S 4] wtherrell:
Ah. So if I flashed the Dev kernel back and installed the module zip, then WiFi should work? That's the only thing I had problems with when I first flashed Darkslide.[/QUOTE]

That's what I understand. I believe the sequence is: Flash rom then kernel then modules & then boot system. Going to try it tomorrow when fresh & have more time. If this works it's a brave new world!
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I may have to do a FDR and then try that process so I can get the Dev kernel back. I love the Darkslide ROM. Super smooth and have had no problems. Let me know how yours goes.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Any of you able to flash the Dev kernel via ODIN. I checked out the link to convert recovery.img to tar.md5 for ODIN. A little unsure if that would work. Interested in your feedback as I need to get back on that kernel
[Verizon Samsung Galaxy S 4] Bait-Fish:
[PSA] WARNING. ANYBODY WITH A DEVELOPER EDITION, DO NOT FLASH THE IMAGES FROM rajat12345's THREAD. BRICK POTENTIAL.

I was about to flash asharad's boot.img but decided to do some homework. It appears the blocks don't match what was requested by rajat12345 and the name of the image.

See this post for details.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Here is the proper recovery.

recovery.img (10MB)

/dev/block/mmcblk0p21

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

MD5 6e14b9d5158d4c05609f0ea2c02cfb17
[Verizon Samsung Galaxy S 4] rmanaka:
Has anyone been able to use Chainfire's MobileODIN? I downloaded from Play last night after rooting but could not get beyond the device check.

Also, after using Philz's method of rooting I cannot remove the Samsung Custom open padlock even using Triangle-Away.

Am I doing something wrong?

Thanks!
[Verizon Samsung Galaxy S 4] Bait-Fish:
No, haven't tried it. Seemed interesting. I had been looking around for ODIN'ing the superuser binary and thought mobile could help. Sadly, it needs root in the first place.

Is our SCH-i545 supported by Triangle Away?
[Verizon Samsung Galaxy S 4] rmanaka:
I think that the consumer SCH-I545 is supported but the DEV edition is not (at least not until Chainfire returns from vacation and can review the dump files). When I tried to use, Triangle Away borked my recovery partition but fortunately I was able to "recover" by dd'ing [MENTION=4211058]Bait-Fish[/MENTION]'s dumped stock recovery.img. I think I could have also ODIN'ed Philz's touch CWM recovery as well. :silly:

TA did not remove my custom padlock, however.
[Verizon Samsung Galaxy S 4] asharad:
Yes, you could have done that. I did it my Dev phone.
[Verizon Samsung Galaxy S 4] wtherrell:
That's what I understand. I believe the sequence is: Flash rom then kernel then modules & then boot system. Going to try it tomorrow when fresh & have more time. If this works it's a brave new world!

Success! Flashed Hyperdrive rls7 using its stock kernel. Rebooted. Wifi would not turn on. Using Twrp wiped cache, dalvik. Dirty flashed the developer modules, rebooted. Wifi began to work

immediately. Rom looks great so far. Now exploring the tons of customizations available in it. Brave New World, folks! The simple addition of the dev ed modules seems to enable Roms & kernels to work with our developers edition that otherwise would not.♥

.

---------- Post added at 04:29 PM ---------- Previous post was at 03:36 PM ----------

We owe gratitude to scrosler for making the dev ed modules available and to locosfocos for pointing us to where to find the file. This is great! Thanks.
[Verizon Samsung Galaxy S 4] jstoneky:
Ive been using Synergy rom with the stock dev kernel and the dev modules from Scotts rom thread. Any rom that overwrites the kernel I just advanced restore the boot.img from my first backup I took as soon as I ODINed phils recovery.
[Verizon Samsung Galaxy S 4] rmanaka:
Hmm. I just downloaded his Modules.zip, wiped and then flashed (had to agree to flash the unsecured zip), rebooted and found that it killed my wifi on Bonestock1.1.3 which is a ME7 variant.

Reflashed Ktoonz 8–9 kernel and wifi was restored.

I tried the same procedure on my Bonestock1.1.3 install. Kills Wifi. Restoring Ktoonz kernel brings back Wifi.

I think if you are flashing a MDK variation of a ROM then the stock Development kernel is appropriate. If you are flashing a ME7 based ROM then Ktoonz or Elite kernels may be necessary to make Wifi (and smartstay as well as PIP) work correctly.

Just be aware of the charging while phone off bug with the Elite and Ktoonz kernels, especially if you only have one battery. You might not be able to turn on the phone if the battery has been completely discharged even with a battery pull!
[Verizon Samsung Galaxy S 4] jstoneky:
Interesting, I tried Bonestock and had wifi working with the stock Development kernel and the Dev modules. There is a slight chance I forgot to flash the dev modules, but I'm pretty sure I did.
[Verizon Samsung Galaxy S 4] rmanaka:
Eek! Looks like the html tags in the quoted messages above are borked!

I should have stated Ktoonsez kernel instead of Ktoonz! Sorry KT!

---------- Post added at 10:26 PM ---------- Previous post was at 10:19 PM ----------

Haha I see you fixed them while I was replying (the tags that is) :sly:

I flashed Bonestock1.1.3 from factory reset... Could not turn on Wifi when the phone was finished activating (icon grey and not responsive) /dead in setup menus).

Let the phone restore on 4G (thank goodness for unlimited LTE) and then flashed kernel.

I wish I could use the stock Development kernel!
[Verizon Samsung Galaxy S 4] Bait-Fish:
In the interest of keeping Dev Edition resources in this thread, asharad posted his boot image. Be sure to thank him.

I know we already have a boot image available, but I am all for having multiple redundant options. Many thanks to locofocos for sharing his.

I used this boot.img to successfully restore my kernel.

Now that we have a stock recovery image, a return to stock image can be made, right? I haven't really thought it through our researched. Is having an ODIN image like the No Wipe Factory Restore one best? I wonder if open1your1eyes0 could lead us down that path.
[Verizon Samsung Galaxy S 4] asharad:
I've been thinking the same thing. But because I'm a complete noob, I don't know where to start. I
[Verizon Samsung Galaxy S 4] Bait-Fish:
I PM'd open1your1eyes0 for info on his factory Restore image method. That's a good one to recover from soft brick. In the end, having that and a full wipe image like sextape's is best in my opinion. I love having options :)
[Verizon Samsung Galaxy S 4] equake:
Bump +1
[Verizon Samsung Galaxy S 4] Bait-Fish:
I was just reading at scrosler's forum about how to make a ROM from a stock ODIN package, thinking of getting insight to reverse the process, and he had a link there which is more what I was looking for. The partition blocks are going to be different than the OP lists in the guide. I'm thinking that peeking into other ODIN stock images could help figure out what's necessary and what's not.

[GUIDE][HOW-TO] Create custom ODIN packages by das7982
[Verizon Samsung Galaxy S 4] sparky697:
Ok I'm a total noob to Samsung and only knew enough about my Bionic to be dangerous. Got my dev s4 last week and have been reading up before I do anything to it and this is what I have so far. I have Odin, philz and supersu all downloaded already so all I need to do is use Odin to flash Philz and Philz to flash su right? I can make backups to use in cwm to get me back to that point but we don't have anything yet to get all the way back to factory right? Figured asking this now is better than asking someone to help me unbrick my phone later. :)
[Verizon Samsung Galaxy S 4] asharad:
You are correct.
[Verizon Samsung Galaxy S 4] equake:
This might have been asked already in this thread or others but has anyone used the Retail Edition ODIN Factory Stock image on the Dev Edition?

If not, does it pose any bricking issue if that version is used? If so, why?

I know it does not take us back to Factory conditions but this is just a thought. Does anyone have an S3 Dev Ed vs S3 Consumer Ed for comparison. It seems that the S3 versions are available on KIES but not the S4?
[Verizon Samsung Galaxy S 4] Bait-Fish:
My PM to open1your1eyes0 has gone unanswered. Looking into his no wipe stock restore, and sextape's full stock restore from which it was based, makes it appear more difficult than I was hoping. I am guessing their ODIN images have ALL the stock bits. More than a simple boot.img, restore.img, system.img, and possibly empty userdata.img for full "wipe." It all still is a bit over my head and free time at the moment.

Maybe a good start would be to pull all the partition blocks listed by-name just for safe keeping/future use.

Sure would be nice to get something from Samsung. Their open source site actually holds the code to compile. Does Samsung ever post restore images?
[Verizon Samsung Galaxy S 4] asharad:
I'm still willing to help anyway I can, as long as it doesn't involve the userdata partition. :D

I'm still stock, except for root and recovery. I did edit wallpaper.apk to replace one of the images. Other than that... stock.
[Verizon Samsung Galaxy S 4] equake:
Do u want to be the guinea pig to unroot and flash Consumer Edition Stock Recovery because those are available?

Just my 2 cents
[Verizon Samsung Galaxy S 4] asharad:
no :confused:
[Verizon Samsung Galaxy S 4] Bait-Fish:
That sounds like bad news to me. I would trust an official OTA on the Dev Edition more than flashing the retail GS4 onto the Dev Edition.
[Verizon Samsung Galaxy S 4] Jetdr:
I really wish I wasnt so confused but here goes.....

I am pretty sure I understand the rooting and installing the custom recovery.

My question is.. After rooting and custom recovery what ROMS can I run? All of the ROMs available are Lokied. I am a huge CM fan for the most part but I like playing with the TW roms also.

What do I have to do different with my DEV phone?

I've never felt like this big of a Noob before. I have been rooting and installing ROMs since the Hero days.
[Verizon Samsung Galaxy S 4] wtherrell:
You should be able to run most any of the roms ported for Vzw. However you may have to play around with different kernels. For instance, I am running Hyperdrive rom on mine. At first wifi, bluetooth would not work. Tried different kernels with varying degrees of success. Finally settled on the stock hyperdrive kernel but had to flash the dev edition modules supplied by scrosler in one of his rom threads in order to get wifi and bluetooth to work. . Now I am really enjoying this phone.

Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
[Verizon Samsung Galaxy S 4] jstoneky:
Jetdr,

You can run any of the ROMs with varying degrees of success. I have tried majority of them with the included kernels and with the dev stock kernel. What you have to do is flash the dev modules I've included below after most ROMs for WiFi and other little things to work. These are from Scotts ROM and I take no credit for them.

I currently use TW eclipse with dev modules and stock dev kernel. It runs very well.

http://db.tt/sUzRzvkX
[Verizon Samsung Galaxy S 4] Jetdr:
Thanks for the responses!! Im goin in!!
[Verizon Samsung Galaxy S 4] equake:
It seems the getting back to oob is going to be futile since it's my understanding to dump the partitions u need root and to get root u need a custom recovery so unless u can reverse engineer the recovery Ur already modded stock...

My 2 cents
[Verizon Samsung Galaxy S 4] Bait-Fish:
asharad rooted via ODIN/recovery and got an "out of the box" fresh boot.img. I rooted using the kernel swap/Motochopper method to get the recovery.img. I guess by rooting, we probably added superuser into the system image. If someone hasn't rooted yet and only has recovery via ODIN, then doing a nandroid should get an untouched image there. Hmm... Links to boot and recovery are in this thread.
[Verizon Samsung Galaxy S 4] equake:
Can you do a Nandroid without Root? Have you guys tested the boot.img, and recovery.img?

My Dev is still pristine other than my data of course lol.
[Verizon Samsung Galaxy S 4] Bait-Fish:
With a straight out of the box Dev Edition, you can ODIN on a custom recovery (CWM, TWRP) and do a nandroid straight away. Root is not necessary to get the custom recovery on due to the unlocked bootloader. After you perform that first nandroid, then flash the latest superuser binary, while still in recovery, and you now have root. Your first nandroid should restore you to factory except for the recovery. Then get the stock recovery image I posted and flash it. That should get you to OOB fresh.

Someone did use my recovery.img successfully. The only catch I can think of is making my dd'd image file flashable from recovery or ODIN. That should be it. I don't think anyone has gone that far yet...

Edit: And, I have used asharad's boot.img successfully to get back to the Dev kernel. Locofocos was the first to post the boot.img from his nandroid which Kayia_FL used successfully. So, many working bits are out there.
[Verizon Samsung Galaxy S 4] equake:
What is the latest update on getting the stock dev ROM ODIN imaged? I guess the last piece would be the radio being pulled.

Have you tried using another radio such as the ME7 Radio or Consumer Ed MDK Radio? Will this have a bad consequence?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I am running the consumer ME7 radios right now will no ill effects. Don't even know what, if any, the differences are between the ME7, the MDK, and the Dev radios. I would guess the Dev & MDK are more similar since the ME7 only came out the latest update.

As far as a stock ROM ODIN image, haven't had any luck with that. Tried creating an ODIN flashable from a 95% stock CWM recovery and it failed completely. This is all still super new to me though so I probably missed a step or something somewhere.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I started looking into what's available for the retail GS4. open1your1eyes0 has an ODIN image that doesn't wipe your data but can recover you from a soft brick. It's based off of sextape's full wipe ODIN image. Looking inside those didn't look familiar enough to me (new to this level of skill, and Samsung) to feel confident that I have all the bits ready to do such. I PM'd open1your1eyes0 but got no response. sextape or garawynn might be good options but I'm just a bit discouraged lately and lacking time (small children at home).

Edit: I ended up dd'ing every stinkin' partition on the phone for safe keeping last night. Not sure if that will help in the future toward getting an image built.
[Verizon Samsung Galaxy S 4] Toddricks:
I ran it for a few minutes on mine while downloading beans rom. No issues at all. Running mdk stock kernel and radio.
[Verizon Samsung Galaxy S 4] equake:
So you ran the Consumer Ed MDK radio and Kernels on a Dev Ed phone with no issues?

Does that mean the Consumer Ed Recovery and ROM would be fine too?