yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] PetrichorXFi:
I'd wait till the OP returns prior to trying anything. From what I understand from reading these posts, it sounds as if this process has to be done exactly right. In the event something is done "wrong", the phone has been modified and no longer useful to get us bootloader/kernel access.

Keep it up! I'd be glad to help in any way I can, I have the Vzw GS4 with ***VRUAME7 build.

Would my current boot.img differ because I had a virgin Vzw GS4 prior to updating to the VRUAME7 build. AFTER updating to VRUAME7 I rooted using the pwn method per

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

. Will my boot.img differ from someone who has rooted PRIOR to the VRUAME7 build?

I don't know how to decompile/extract the .img files, yet perhaps a dev can extract the code, put it on say... Google Docs, and have the community add comments to particular lines of code that are of interest?
[Verizon Samsung Galaxy S 4] rajat12345:
I'm pretty sure you could use any 1 click root

I might need someone to test for me because I'm on vacation for the weekend and I forgot my phone at home so if anyone is willing to test on the me7 update that would be great just post here or pm me.
[Verizon Samsung Galaxy S 4] r_hippy:
Stock rooted me7 no recovery took the ota to see if I could save root the day the ota Hit. It's

My daughter's phone.

Mine is rooted with recovery

Pm me If you need something tested. After 4 Pm est I'm available.

Edit * sorry it's not a dev edition, just remembered
[Verizon Samsung Galaxy S 4] Kaiya_FL:
No, don't use a 1-Click Root.

I did it and it replaced my dev kernel with one from the consumer version.

I have an ME7 consumer version I can test on tonight and this weekend if needed. I can even put it back to stock, unrooted, if needed.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Edit: You beat me :cool:

The 1-click replaces original MDK kernel with MD2, then Motochopper root, then replace back the MDK kernel. There is some difference in kernels between the retail GS4 and the Dev. I recall Kayia_FL found that out having used a 1-click and took a couple days for someone to supply a boot.img take from someone's nandroid who didn't use that method. The version numbers are different.

If we root that way, we change the boot.img you seek, correct?

---------- Post added at 09:00 AM ---------- Previous post was at 08:48 AM ----------

Thinking further, even if, there was a way to ODIN Super User in, I think it would not have root because of the MDK kernel.

I'm thinking that the best route having two phones to work with is have each of us use different methods. That way recovery can be had from at least one...
[Verizon Samsung Galaxy S 4] equake:
Anyone try ADB reboot bootloader to get into fastboot mode? Just wondering.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Fastboot doesn't work with the S4. It's been replaced by Download/ODIN.
[Verizon Samsung Galaxy S 4] equake:
Apparently on the GE fastboot does work but I was wondering what that command does to the DEV edition.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
It does nothing. I tried when I was wanting to flash back to the original Dev kernel. The phone isn't recognized by the 'fastboot devices' command.
[Verizon Samsung Galaxy S 4] equake:
I'll try when I get back home, but wondering if the command takes the phone into bootloader mode which is fastboot mode. Although the hard keys don't bring up fastboot which is surprising since all other devices it works.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Several have tried to get it to work. The phone is recognized when you do 'adb devices'. You can then get ADB to reboot into bootloader mode. From there typing any fastboot commands do nothing. On the phone it shows it being in "download" mode. Download mode it what ODIN uses to flash through.

Or at least that's my take on how it all works, LOL!
[Verizon Samsung Galaxy S 4] BraddahBoi808:
This is great! Some major progress being made. I'm willing to test anything out. Still on stock ME7
[Verizon Samsung Galaxy S 4] Bait-Fish:
If I don't hear anything from you [MENTION=4298922]rajat12345[/MENTION], I will go ahead with ODIN'ing kernels, root, and get you the recovery portion for sure.

[MENTION=4139454]asharad[/MENTION], are you good with that? You could ODIN a recovery on, flash Super User, and do the rest of the data gathering for rajat12345.
[Verizon Samsung Galaxy S 4] asharad:
I'm willing to do that, as long as someone gives me some really good instructions. I've never used Odin, and I don't know which recovery to use.

I was a lot more brave on my droidx, because those phones were non-brickable thanks to SBF.

Can we wait a little longer for OP to come back. All this is pointless if he is gone.
[Verizon Samsung Galaxy S 4] SamuriHL:
That's a decent plan.
[Verizon Samsung Galaxy S 4] thedeveloper1:
Is there a way we can erase the recovery partition and then dd twrp or cwm?
[Verizon Samsung Galaxy S 4] ztkryan:
You can dd twrp that's how I installed recovery on my S4

http://teamw.in/project/twrp2/181
[Verizon Samsung Galaxy S 4] Bait-Fish:
He posted four hours ago and didn't interject anything specific so I take it as a go ahead. I'll wait for sure. I may not even be able to do anything until 7 or 8 PM PDST anyway.

Thanks Sam for the confirmation.
[Verizon Samsung Galaxy S 4] Cruiserdude:
I think the poster was referring to ME7, in which case it won't boot. I'm not sure if you can dd it there in the first place, but it will fail the signature check as is, if you're on ME7.

Sent from my VZW Galaxy S4 Google Play Edition :)
[Verizon Samsung Galaxy S 4] SamuriHL:
Can't dd without root.
[Verizon Samsung Galaxy S 4] asharad:
OMG, I opened up the ODIN software. I'm very intimidated! :eek:
[Verizon Samsung Galaxy S 4] SamuriHL:
You have to know what you're flashing. ODIN itself isn't terribly difficult. Most of the time you're going to flash using the PDA section. But don't go indiscriminately checking or unchecking things. That can cause problems. Generally you simply want auto-reboot checked and nothing else. Generally. Other than that you put your phone in ODIN mode, connect it, make sure ODIN can see it, select the tar md5 file using the PDA button, and flash away. BUT, and here's the HUGE WARNING!!!! Flashing the WRONG file to your phone can permanently brick it. Know what you're flashing.
[Verizon Samsung Galaxy S 4] asharad:
:eek:

The TWRP website says I must be rooted to install. So now I'm gonna look at CWM.
[Verizon Samsung Galaxy S 4] SamuriHL:
You're telling me they don't provide an ODIN package that can flash it?? You need to be rooted to dd it or to have Goo install it, but, for ODIN not so much.
[Verizon Samsung Galaxy S 4] Bait-Fish:
guyd wrote this in the Dev Edition thread.
[Verizon Samsung Galaxy S 4] asharad:
Yep.

From the TWRP webpage for the Verizon S4: Our images are already modified with loki so you just need to root then flash with GooManager.
[Verizon Samsung Galaxy S 4] SamuriHL:
That's for the non-dev version. A dev version is unlocked and doesn't need hocus pocus to flash recovery.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
And with the Dev edition Loki isn't needed because the bootloader is already unlocked, correct?
[Verizon Samsung Galaxy S 4] SamuriHL:
I don't have time to do this, but, basically someone needs to take the img file from the dd command on that page and 'odin-ify it'. Then the unlocked dev phone people can odin flash it.

---------- Post added at 06:21 PM ---------- Previous post was at 06:20 PM ----------

Yup. Like I said you have to take the raw img file (the one that's on the link for the dd commands) and then create an odin flashable tar md5 with it. Then you can flash it without root. They didn't do that because it'd potentially screw up a consumer phone.

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

http://techerrata.com/file/twrp2/jfltevzw/openrecovery-twrp-2.6.0.0-jfltevzw.img

That file. Do this to it in cygwin:

tar -H ustar -c openrecovery-twrp-2.6.0.0-jfltevzw.img > twrp_recovery.tar

md5sum -t twrp_recovery.tar >> twrp_recovery.tar

mv twrp_recovery.tar twrp_recovery.tar.md5

Then you should have an ODIN flashable zip. WARNING: NO ONE but an unlocked dev edition user should attempt to odin flash it or you WILL cause immense problems for yourself.
[Verizon Samsung Galaxy S 4] asharad:
OMG, my heart is pounding. I just completed my first ODIN transfer, and the phone booted properly. Thank you LORD!
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Is that a stock dev image file made with TWRP? What happens if you have CWM?
[Verizon Samsung Galaxy S 4] asharad:
I transferred Phil's recovery to my phone, and ODIN worked. However I cannot get my phone to boot into recovery. I'm holding VolumeUP + POWER until I see the blue text in the top left corner, and then I release both buttons. Then the phone reboots normally. Any suggestions?

EDIT**** NEVERMIND. That's kinda quirky, but I finally got in.
[Verizon Samsung Galaxy S 4] SamuriHL:
HUH?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
What is that openrecovery-twrp-2.6.0.0-jfltevzw.img a file of? If it is a backup/recovery made with TWRP does it matter when you try to ODIN flash it that you're using CWM as a recovery?
[Verizon Samsung Galaxy S 4] frr1:
nice alright root the phone so we can get this boot loader unlocked already
[Verizon Samsung Galaxy S 4] SamuriHL:
It IS twrp. It's an IMG file of TWRP recovery.
[Verizon Samsung Galaxy S 4] Ryno77:
I was a little confused too. I believe Sam was showing you how to make an Odin flashable recovery using a twrp image....minus the loki patch. Just stock twrp for Odin.
[Verizon Samsung Galaxy S 4] SamuriHL:
Correct. An odin flashable file to install TWRP recovery on dev edition phones.
[Verizon Samsung Galaxy S 4] asharad:
I'm running Phil's recovery and rooted. Otherwise completely stock. Not all of these files are available to copy.

/dev/block/mmcblk0p22 ... got it

/dev/block/mmcblk0p23 ... got it, but I'm running custom recovery

/dev/block/mmcblk0p32 ... doesn't exist

/dev/block/mmcblk0p29 ... file exists but ADB freezes trying to copy
[Verizon Samsung Galaxy S 4] Bait-Fish:
Great job, asharad! Flash the latest SuperSU from TWRP and you should have root. Get Terminal Emulator and before issuing the commands rajat12345 listed, type su and enter. The prompt will change and the commands should work. I am behind you a couple hours unfortunately :)

Edit: You posted right before I did, so you updated your progress... I see you ADB'd.
[Verizon Samsung Galaxy S 4] asharad:
yeah, I was tired of using the terminal apk. I'm trying to copy the system.img, but it just seems to hang. Any idea how long it should take? It appears to be 1GB.
[Verizon Samsung Galaxy S 4] SamuriHL:
15 minutes potentially. It will take a while.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Yeah, probably a big file. My terminal is just sitting there too. Devlog.img did not copy for me either.

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

Whoops, ran out of space. Guess I'll send it to the external. Don't have time at the moment.
[Verizon Samsung Galaxy S 4] asharad:
Heh, me too. Gotta figure out how to move apps to SD...

edit.......... I'm not going to be able to upload the system.img file. It's a least 5GB. My primary ISP is a 3G stick capped at 20GB. I suppose I could upload it from the phone, but I'm already at 5GB for the month on my unlimited plan. I don't want VZW to cut me off.
[Verizon Samsung Galaxy S 4] frr1:
If its unlimited they wont we need the file so we can get unlock bootloader its important
[Verizon Samsung Galaxy S 4] samiamapirate:
Fingers crossed..and toes..and arms..legs..etc...

Ahhhhh! I am hoping and praying that you are able to achieve the unlock! I have money ready to pay for the bounty so best of luck to you! ANYONE - help this guy out!!!
[Verizon Samsung Galaxy S 4] thesoldier:
Upload using your 4g connection without worry, people on these formus frequently use up to 100 GB monthly and have said VZW doesn't say a thing.
[Verizon Samsung Galaxy S 4] Harleydroid:
Oh forget Verizon. Ur unlimited brother. Man I'm following thread you guys are awesome
[Verizon Samsung Galaxy S 4] asharad:
EDIT.... links retracted
[Verizon Samsung Galaxy S 4] ntb81:
I use 25-30gb a month and the only comment I've ever gotten was from a VZW corporate store clerk who told me that it was impressive but didn't come close to the top users he had seen. You're on your way to being a hero!
[Verizon Samsung Galaxy S 4] asdecker:
Thank you guys so much for working in this!
[Verizon Samsung Galaxy S 4] sokrboot:
^^^^ THIS
[Verizon Samsung Galaxy S 4] BraddahBoi808:
Thanks sooo much asharad! This is great news. Hopefully you guys can get this baby unlocked by the end of the weekend :thumbup:
[Verizon Samsung Galaxy S 4] bajasur:
Watching thread closely... keep up the positive vibes
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Reading through this thread and I'm a little confused on what folks are doing here exactly.

Is someone trying to dd the bootloader from the developer edition to the standard one on VRUAME7 build? Maybe someone can summarize/clarify here what is trying to be tested.

If it is the above and you guys are doing what I'm thinking, then 95% chance that won't work and will likely cause a hard brick. We tried a similar experiment by dding MDK partitions onto ME7 device and it hard bricked (this will be the case for everyone so DO NOT even try it out of curiosity).
[Verizon Samsung Galaxy S 4] fenguepay:
Correct me if im wrong but if this works it basically turns a regular gs4 into a dev edition?
[Verizon Samsung Galaxy S 4] resurektz:
I'm pretty sure thats what hes trying to acomplish.
[Verizon Samsung Galaxy S 4] Bait-Fish:
You'd have to ask rajat12345. All we know is what he's posted to this thread. I'm all for helping though.

And on that note . . .

/dev/block/mmcblk0p22

boot.img

REMOVED

MD5 f1c9645dbc14efddc7d8a322685f26eb

This file is most likely NON-STOCK, or at least parts of it. I flashed pre-release kernel MD2 to obtain root with Motochopper.

/dev/block/mmcblk0p23

recovery.img

REMOVED

MD5 da6a0d097e307ac52ed9b4ad551801fc

/dev/block/mmcblk0p32

devlog.img

Failed, nothing copied.

/dev/block/mmcblk0p29

system.img

REMOVED

MD5 a58b0d0b50439774fd7a2ff3e01360c9

MD5 is for the unzipped system.image file.

MD5 hashes were calculated on phone.

Terminal Emulator log. TE truncated long lines.

xx@android:/ $ su

lk0p22 of=/sdcard/boot.img <

20480+0 records in

20480+0 records out

10485760 bytes transferred in 0.656 secs (15984390 bytes/sec)

lk0p23 of=/sdcard/recovery.img <

12288+0 records in

12288+0 records out

6291456 bytes transferred in 0.406 secs (15496197 bytes/sec)

lk0p32 of=/sdcard/devlog.img <

/dev/block/mmcblk0p32: cannot open for read: No such file or directory

blk0p29 of=/sdcard/system.img <

/sdcard/system.img: write error: No space left on device

18986786+0 records in

18986785+0 records out

9721233920 bytes transferred in 804.106 secs (12089493 bytes/sec)

blk0p29 of=/storage/extSdCard/system.img <

20439040+0 records in

20439040+0 records out

10464788480 bytes transferred in 1923.288 secs (5441092 bytes/sec)

root@android:/ #
[Verizon Samsung Galaxy S 4] asharad:
Mine is 9GB.............. It was only 4 when saving to external storage because dd ran of space. If you write it /storage/extSdCard/ it will probably be 9GB.
[Verizon Samsung Galaxy S 4] rmanaka:
Guys, if either of you could make the boot.img Odinable then I will root using the MD2/Motochopper method and then dump the stock recovery. I think we can get back to stock Developer's Edition with both the stock kernel and the stock recovery Odinable?
[Verizon Samsung Galaxy S 4] asharad:
I don't even know where to start.
[Verizon Samsung Galaxy S 4] rmanaka:
[MENTION=4139454]asharad[/MENTION],

Oops, got behind the updates! [MENTION=2812087]SamuriHL[/MENTION] or [MENTION=3884716]Kaiya_FL[/MENTION] or anyone can you help? I don't have a Linux box handy at the moment.
[Verizon Samsung Galaxy S 4] asharad:
Tell me how, and I'll try.
[Verizon Samsung Galaxy S 4] SamuriHL:
Link Removed

All I've done is taken the boot.img from the link above and made it odin flashable. You are responsible for whatever it does if you decide to flash it.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I'm not home at the moment so u can't do anything unfortunately :(
[Verizon Samsung Galaxy S 4] rmanaka:
Sorry, double posted above but I edited the post while you were replying to me. [MENTION=2812087]SamuriHL[/MENTION] posted how to get a tarball from the TWRP image dump (and I copied your boot.img dump to my Dropbox - Thanks, Great job!).

I don't have a machine that I can do that on right now, guess at some point in the near future I will have to fire up my Linux box.

Since I want to dump the stock recovery I can't drop the boot.img into a CWM package to flash.
[Verizon Samsung Galaxy S 4] SamuriHL:
FYI, Cygwin. :)
[Verizon Samsung Galaxy S 4] Bait-Fish:
My dump above includes the actual stock recovery. Motochopper was the method I rooted with specifically to guarantee that.

Asharad used the recovery root method and guaranteed a good boot.img.

Combine all the good and we are complete I believe. :cool:
[Verizon Samsung Galaxy S 4] rmanaka:
Thanks, [MENTION=2812087]SamuriHL[/MENTION]!

I'll dump the stock recovery. Assuming (ha ha, I know) a good dump of the boot.img, I don't see why Odining your tarball as the last step of the MD2 root procedure wouldn't give me rooted stock, do you? :what:

---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------

[/COLOR [MENTION=2812087]SamuriHL[/MENTION], got it, thanks!

I'll dump the stock recovery before I flash your tar.tar sauce! Hopefully even if it borks I can get back to download mode and flash the retail MDK kernel.
[Verizon Samsung Galaxy S 4] SamuriHL:
Not a clue. I don't have one of the VZW S4 variants you crazy kids are playing with. :) Root for me is simple....install TWRP recovery, flash supersu zip in TWRP, $$$$. :D I've only been on the S4 for less than a couple weeks now. I'm well versed in the Moto world, but, I'm still learning when it comes to the Samsung world. But I've come along nicely I think. ;)

---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------

Ok. I've removed the file from my MF account just so I don't do something stupid and accidentally flash it some day. Enjoy!
[Verizon Samsung Galaxy S 4] rmanaka:
Wow! So I guess no need for me to redo all of your great work! So if someone makes a tarball from your recovery.img we should be GREAT to Go! :thumbup:
[Verizon Samsung Galaxy S 4] Bait-Fish:
So, where/how to upload a 9.75GB file? I'm sure Box won't let me and I don't have enough Dropbox space. I could set up a home FTP but not sure how stable that would be, especially non-resumable if it got interrupted.

What are you using, [MENTION=4139454]asharad[/MENTION]?
[Verizon Samsung Galaxy S 4] SamuriHL:
4shared should do it. Stupid auto correct.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Awesome. Thanks.

Hey, a Xoom. I loved my Xoom!
[Verizon Samsung Galaxy S 4] Loglud:
OK so I have now been watching this thread all day and thought that I would point out my findings and a little bit about how the boot loader works. The boot loader is actually a secondary boot loader the primary boot loader cannot be modified. In order for this theory to work two things would need to occur the boot loader that is on the Dev edition would need to be signed. This means that its signature would be able to be verified by the primary boot loader using a SHA-256 Hash. If it is verified then the aboot partition does not check for the signature of boot. This would make it so you could boot the unsecure aboot. However ... I highly doubting this works. Though with that being said there is something that is changing that is making it so that you cant touch the boot loader. I know he says he cant dd the old boot loader and make it work. However this tells us something very important there is something else on chip being modified maybe nv flash or something. Because if it wasnt the signature check of a old boot loader would not fail. If that makes me think that there's a flag for most reason boot loader version get stored somewhere, and if done correctly, you might be able to roll back if you can find it.
[Verizon Samsung Galaxy S 4] BraddahBoi808:
If you PM it to me I could upload to my box account w/ 50 GB of storage
[Verizon Samsung Galaxy S 4] SamuriHL:
Rockin' it for a few more months until the nx10 comes out.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
You sir have been the closest to explain this properly thus far.

If you're interested in researching a bit more about the the Qualcomm booting process you might want to take a read at Dan Rosenberg's excellent and thorough explanation from two links below. qFuses and eMMC play a big importance as well as the PDL (which is normally hardcoded into the ROM and write-protected).

http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html

http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html
[Verizon Samsung Galaxy S 4] asharad:
I will use my personal web host, and make the file available via PM. The upload would have finished by now, but I was mucking with my phone and accidentally cancelled the upload. So I've started again. Tomorrow I will make the files available to those who ask, so to protect my webhost from abuse.

At this point, I'm done. I am merely trying to help the OP achieve his goal, whatever it may be. I don't know what he's planning or if it will work.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Thanks for the offer. I believe I got it sorted out with 4shared. Zipping it got it much smaller and easier.

[MENTION=4139454]asharad[/MENTION]. I zipped mine to 13% of the original size, 9.8G to 1.3 or so. That should help tremendously. It did for me.

Upload complete and PM to OP sent.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Can you post MD5s for your files, [MENTION=4139454]asharad[/MENTION]? I just realized, call me slow, that all I need to do to get my boot (kernel) back to stock is reverse the dd command in terminal using your boot.img. I just want assurance beforehand that it's not corrupted across the net beforehand.
[Verizon Samsung Galaxy S 4] Galaxys4bean:
If you need help checking the md5 sum download this and click create md5 and click on file. Then it automatically copies the md5 so post it here.

Do it for all.

http://www.mediafire.com/?hghppacl9awdz1j

Virustotal link https://www.virustotal.com/en/file/...d9667e37a7757e545c67fc67/analysis/1376146250/
[Verizon Samsung Galaxy S 4] asharad:
EDIT.... links removed....

---------- Post added at 10:16 AM ---------- Previous post was at 10:04 AM ----------

[/COLOR]

Thanks, I will do that. I have a question though. Does the system.img contain any personal information?
[Verizon Samsung Galaxy S 4] Bait-Fish:
That I was wondering myself. Or, does it contain any device specific information that you generally don't want public. I don't know the answer.

Any insightful reader care to chime in? 10GB seems like a lot of data, like the whole kit and caboodle. That concern is partly why I have only PMd the OP the link.

Edit: Oh, and thanks for the MD5s!
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Nice! So now how do we make use of these? Is the recovery.img a complete recovery to put it all back to stock?
[Verizon Samsung Galaxy S 4] SamuriHL:
No, the system partition doesn't contain any personal info. That's stored in your data partition.
[Verizon Samsung Galaxy S 4] asharad:
My files are from a rooted, custom recovery otherwise stock. Baitfish's files are rooted, custom kernel otherwise stock.

What you do with them I don't know.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Anything hardware specific, IMEI, serial, etc.?
[Verizon Samsung Galaxy S 4] SamuriHL:
http://xdaforums.com/showpost.php?p=44486091&postcount=128
[Verizon Samsung Galaxy S 4] Southern_mind:
Is the op still looking into this or not?