yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] odawgx:
I have tried with GooManager and it didn't work. I am having trouble finding a Zip file for this device. Do you have any that will allow me to install from within recovery?

Every time I try to install, it takes me to download mode. Philz is the only one that seems to be working.
[Verizon Samsung Galaxy S 4] odawgx:
UPDATE:

I was able to install the latest ClockworkMod recovery using Recovery Flasher.

The issue is with TWRP on this device and I notice many people are having similar issues...

Is there a version that is known to work better on the S4?

Thanks

Omar

---------- Post added at 10:57 PM ---------- Previous post was at 10:23 PM ----------

Still can't get custom ROMS installed even with the latest version of Clockwork.

I am wondering if something is wrong with this specific device although it looks like it's still in Developer mode on ODIN
[Verizon Samsung Galaxy S 4] asharad:
I'm running TWRP. It works fine for me so far, but I've not flashed any ROMs. The version of TWRP that I'm using can be found on the TWRP website and flashed from Philz recovery.
[Verizon Samsung Galaxy S 4] odawgx:
Sorry for my ignorance. I looked on the TWRP website and all I saw was .img files and I am not sure how you flash that from within Philz. Is there a special step?

Thanks

Omar
[Verizon Samsung Galaxy S 4] Bait-Fish:
TWRP 2.5.0.2 is the most recommended version for the S4. Loki doesn't seem to matter from my experience.
[Verizon Samsung Galaxy S 4] odawgx:
Thanks for your reply and the link. I tried to install it from within Philz and it rebooted into Download Mode. I had to flash Philz back from Odin to get my Recovery back.

It's very strange. I can flash ClockworkMod without a problem, but TWRP always won't boot. I can't install ROMs using Philz either. Either get a black screen of it freezes.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Did you get your Dev Edition recently? Maybe yours is a newer firmware. Most of us are MDK.
[Verizon Samsung Galaxy S 4] odawgx:
Yes. I did and you are correct. Mine is not running MDK. It is running MJ7...Maybe that's the problem.

Why would they sell a developer edition that doesn't allow you to install ROMS?

That's a very disappointing.... :(
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Aside from the kernel, what else is in the boot.img file? Could I just flash that instead of digging out the kernel (I'm reading up on unpack & such just in case)? Or will I lose root and have to figure out how to redo it?
[Verizon Samsung Galaxy S 4] wtherrell:
Ok. Got my dev edition up& running. Franco Kernel updater seems to work on mine. Brings up way to name the kernel & asks where I want to save it.

Won't save. guess you have to be rooted first. EDIT: Nope, still doesn't work. Option gone from Trickster Mod as well.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Can you save the stock Dev kernel and post a link to download it?
[Verizon Samsung Galaxy S 4] wtherrell:
Great info on converting. img to .tar.mf5.

Much thanks for this.

Since Philz is already in .tar format I will give it a try 1st. Once rooted I can switch to twrp using Goomanager if I see a need to change.
[Verizon Samsung Galaxy S 4] markwebb:
Yes, the baseband is different on the Dev Edition. Scott from CleanRom fame has posted a module to fix with his and other ROM's, though it doesn't work on a few such as Snyergy and RAGE.
[Verizon Samsung Galaxy S 4] shellux:
I flashed the ME7 baseband while I was trying to get my wifi to work and that didn't change anything. So I installed the latest ChronicKernel through recovery and right now I'm running Hyperdrive without any issues...yet
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Any idea why my phone would be recognized in ADB but not in Fastboot? I get a device listing when I do ADB Devices but nothing when I do a fastboot devices so I can't flash the boot.img I have. The Samsung USB drivers are installed and USB Debugging mode is enabled. I'm befuddled on how else to get the stock Dev kernel back on the phone :confused:

Nevermind. I figured it out and now have the appropriate stock Dev kernel installed. Making a proper CWM backup so I can start playing with ROMs next :D
[Verizon Samsung Galaxy S 4] wtherrell:
Looks like you found the dev stock boot.img (kernel) somewhere?

Seems philzTouch can flash just the boot.img from a nandroid backup under advanced restore option. I kinda like this recovery for this reason even though I really like TWRP'S interface better.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Yes, locofocos, provided it in this post: http://xdaforums.com/showpost.php?p=44128402&postcount=39

So I just dropped it in a CWM back up and then chose just "Restore Boot" from the Advanced Restore. I also had to delete the nandroid.md5 file and replace it with a blank to skip the checking cause it failed (obviously) before I did that. It'd be interesting to see what the differences are between the dev and non-dev Pre ME7 kernels.

Only thing I haven't figured out is why my device was recognized by 'adb devices' but not 'fastboot devices'.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
So what ROMs has anyone tried on the Dev edition? I was looking at trying Darkslide's ME7 ROM for the Apps2SD without needing a special app or Hyperdrive. Can't make up my mind :laugh:
[Verizon Samsung Galaxy S 4] wtherrell:
Got my heart set on hyperdrive. Figure Breen will incorporate 4.3 before long. Might as well try darkslide while we wait. That's what we crackflashers do! Got to get Tibu set up for cloud & restore some apps / data from Gnex 1st. Let us know how you like those new roms.
[Verizon Samsung Galaxy S 4] locofocos:
My bad, didn't even think about the MD5. Here's the relevant line in the nandroid.md5 file, just to be safe. OP updated as well.

d7d0693384050fb4b6bbdafefbeafd18 boot.img
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Will Tibu help make restoring apps & settings quicker/easier? That's the one thing I don't look forward to is having to redo all that. Will probably try Darkslide this weekend when I have time to fix any issues that may arise and so I can read through all the documentation again.

---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------

Sweet :) That will help out anyone else who makes the bone head move I did :good:

Had to laugh though because I spent hours researching how to do it and when I finally got it to work, it took less than 2 seconds :laugh:
[Verizon Samsung Galaxy S 4] wtherrell:
TiBu helps me a lot that way. Forget backing up to the cloud though. Uploads take forever and usually fail after a few minutes. Guess I'll just move TiBu file from Gnex to PC & Then to S4 & see how that goes.

.
[Verizon Samsung Galaxy S 4] wtherrell:
Before flashing a new rom I want to check to be sure my Nandroid backup is there. Tried looking for it with ES File Explorer with "show hidden files" turned on. Could not find it. Nandroid was made using Philztouch. Supposed to be in sdcard >Clockworkmod, but no backup folder or file shows up. The backup file really ate a lot of internal storage space but why can't I see it?
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Are you certain you selected backup to SD card/External when you did it? Did you look for the folder in the phone's internal storage? I use the CWM Touch and Root Explorer from the Play store and can see my folder & files on my SD card.
[Verizon Samsung Galaxy S 4] wtherrell:
That's what I'm using also. Can't find it either place.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Try using this https://play.google.com/store/apps/details?id=com.mobile_infographics_tools.mydrive or some other disk analyzer to find out where and how big the files are internally. Might help you locate the backup.
[Verizon Samsung Galaxy S 4] wtherrell:
Thanks, couldn't find it with that either.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Hmmm... I'm at a loss. Only thing I can suggest is try making another backup now that you know what is where and see if it shows up.
[Verizon Samsung Galaxy S 4] Bait-Fish:
That's probably where the issue is. Surge1223 may have some insight. He didn't have a Dev Edition but does have good knowledge of the differences.
[Verizon Samsung Galaxy S 4] equake:
I believe the current VZW S4 Custom Recoveries are not built for JB 4.3/4.4 ie MJ7 ROM. TWRP version 2.6.x should support JB 4.3 kernels so you should try to ODIN a clean version.

My 2 cents
[Verizon Samsung Galaxy S 4] odawgx:
Thanks so much. I gave that a try but unfortunately, my phone didn't like it.

I guess I will wait to see if a new version of TWRP recovery will install.

Thanks again everyone.

Omar
[Verizon Samsung Galaxy S 4] equake:
Have you tried to use ODIN or are you using GooManager? If you are using ODIN you must find a TAR version to use. Another way is to use ADB and the dd command.
[Verizon Samsung Galaxy S 4] odawgx:
Unfortunately, I tried both methods and it doesn't appear to be working. TWRP will not boot and take me to Download mode. Only Philz and CWM actually boot up but I can't flash ROMs in it...
[Verizon Samsung Galaxy S 4] equake:
You can also try flashify to install within the OS. I originally used Philz and was able to flash all types of stuff but TWRP seems to be the more reliable Recovery.

Last resort try installing Safestrap.

As always follow the instructions and be aware of brickage.

My two cents
[Verizon Samsung Galaxy S 4] playaprez35:
I Can't Install any Roms

Someone please HELP, I've been having issues installing a Rom on my device. I've noticed that countless others may be having the same issue. So hopefully this knowledge may help them too. I have tried everything that I could think of independently, so I figured this would be the best place to troubleshoot. I'm hoping that someone can bless me with their infinite wisdom. I have a newer Verizon Galaxy S4 Dev Ed. running: Android 4.3/ Software version MJ7. It was shipped that way directly from Samsung. I have flashed both Philz, and CWM through Odin to no avail. The installation of the custom recoveries themselves; however, was successful. I was even able to install SuperSU, so I'm finally stock rooted. Nonetheless, I can not install

any

custom rom. The closest I've ever been was with: PAC-Man ROM on CWM 6.0.4.4.

But I ended up getting stuck in a boot loop. So I was wondering if anyone could tell me: What it is, I'm doing wrong? Or is there any known way to remedy the situation?....."Riddle me this, Riddle me that"

Please and Thanks!!!
[Verizon Samsung Galaxy S 4] jpcalhoun:
I also have a DEV S4. Try using TWRP 2.5.0.2. I used PHilz for awhile when I first got my S4. Sometimes it worked ok and sometimes it didn't. There is a .tar version and zip version of TWRP. You can flash the zip version in recovery with Philz and TWRP will replace it without issue. Since using TWRP I've never had an issue flashing any ROM. Go here for zip version of TWRP::http://d-h.st/gLS
[Verizon Samsung Galaxy S 4] playaprez35:
Thanks, but do you know if there will be any issues since I have the Verizon Ed.???

Just curious because the download link that you gave me says

jflteatt

, and for my phone it usually says

jfltevzw

...

Just wondering also, do you know where I could find a .tar.md5 version of TWRP 2.5.0.2.??? I've tried using Cabloomi's Method, but it didn't work for me.

Sorry to bother you, but thanks again.

---------- Post added at 01:30 PM ---------- Previous post was at 12:48 PM ----------

Yeah I tried flashing that version of TWRP you gave me through Philz, and it didn't work. It just booted my phone into download mode.

So do you, or anyone else know of a TWRP 2.5.0.2. jfltevzw??? Or something else that may work on the Verizon Developer Edition???

Please Help!!!
[Verizon Samsung Galaxy S 4] jpcalhoun:
Sorry...that is the link I have in my bookmarks for TWRP. I the file I downloaded from that link was the vzw file and that is the file I have saved. They have obviously changed the download file. There is a 2.6 on the TWRP home page but I don't know how well that version works on the S4. If you PM me with an email address I'll send to you via email.
[Verizon Samsung Galaxy S 4] playaprez35:
Yeah I tried that too, smh. I flashed the newer version of twrp also to no avail. Both the website, and Goo manager was ineffective. They all ended in the same result, booting into download mode. And I don't know how to use adb. I'm guessing that my phone just doesn't like TWRP, because both Philz, and CWM install fine. At least through Odin that is. Maybe a .tar.md5 version of twrp would work. I'm not sure if I did something wrong, when I initially rooted the device, or what... My phone still says Developer, when I boot into download mode so I'm not sure. Unless these custom recoveries don't play well with Android 4.3. I can't return the phone, so I'm stuck. I may just sell it or attempt to trade with someone. Heck, I would love to find one of those older MDK versions. Hopefully one of these all knowing, powerful DEVS can help me. I don't want to lose money on this $700 paper weight. If you think about it, it's kind of like false advertising on Samsung's part. Their website says that the phone ships with 4.2.2. Eh, Thanks for your time anyway.
[Verizon Samsung Galaxy S 4] jpcalhoun:
I have have flashed 4.2 and 4.3 ROMs on my phone with TWRP 2.5.0.2 with no problem. I'd be glad to send you the verizon version if you PM me. If I understand you right you can get into recovery by holding down volume up and power at the same time, it that correct? If you can get into recover then you can flash the zip file I have. You can also check root by downloading Root Checker for the Play Store and check to see if you really have root access.
[Verizon Samsung Galaxy S 4] ryan1869:
I've been running into the same problems, I can root or flash philz or CWM all day long, but TWRP (any version, installed pretty much every way possible) fails to boot, and any ROM I flash won't boot. I tried with CM11 (1/31 before the recent boot issues) but it got stuck at the Samsung boot screen, so I went back to my stock nandroid backup. I was really hoping to get an AOSP ROM running since it was kind of the main reasons I chose to spend the money on the dev edition instead of just getting a retail Verizon one.

I have a feeling this has a lot to do with my device being a newer dev edition, and it came with the MI1 build pre-loaded, and not MDK. I really figured since the dev edition is shipped unlocked that it wouldn't have been a big deal, and the problem was with the retail versions and their locked bootloaders.
[Verizon Samsung Galaxy S 4] playaprez35:
Thanks for sending me the files, and yes I can get into either Philz/CWM recovery. I press and hold the power, home, and vol. up buttons simultaneously.

Then I release all three when I see Samsung Custom. The blue writing appears on the top left corner of the screen that says: "Recovery Booting", and I'm in. If I wait until I see the blue writing to release the buttons, it doesn't work. It boots the phone normally, I'm not sure why. Once I'm in, I touch install zip from sdcard. I then proceed to where I have the file saved, and hit install. I didn't extract anything. Everything goes through, and appears to be fine. So I then reboot the phone into recovery mode, but am unable because the phone boots into download mode instead. I have also installed Root Checker Basic, and yes it did indeed confirm that

I do

have root access. The SuperSU permissions popped up, and everything. So I have no clue whats going on, and this has been happening for awhile now. Anytime I flash a version of TWRP recovery from the phone itself. Maybe I have a faulty motherboard, or something I don't know. That's why I was looking for a Odin flashable version of TWRP. What was the last 3 letters of your Software/Baseband version, on your phone when you bought it? Mine is MJ7 stock out of the box, so I'm also trying to determine if this issue is caused by the newer version of the Android firmware 4.3....... I'm also starting to wonder if my kernel is locked, which doesn't make sense. Considering that this is a Developer Edition phone idk.

Thanks again, I'm still hopeful!

---------- Post added at 06:19 PM ---------- Previous post was at 05:53 PM ----------

Thank You

ryan1869

, I was starting to think I was crazy. That or I was doing something wrong. It's good to know that I'm not the only one having this issue, and Ml1 was released well before MJ7. It is; however, unfortunate that many of us are in the same boat. Between Verizon, and or Samsung I think someone did this intentionally. Although there were minor issues with different release versions of the S4. I Think that's why they speedily sent out all of those updates to further lock everything down. Trying to be slick, or sneaky I don't know. What I don't understand is how they can attempt to dictate to you, what to do with your property. Considering the fact that you paid $700 for a device they claim to be a "Developer Edition". Like I said previously it's false advertising, and highway robbery. If I wanted a device to be stock rooted, I would've just purchased the retail edition. I'm starting to think that AT&T might not be so bad. They have faster data speeds, better battery life, and seem to be more current with GSM vs. CDMA. At least with the rest of the world anyway. Either way at the end of the day I'm still stuck with and American cellphone service provider. So what can you do???

I am still thankful, for anyone's help.
[Verizon Samsung Galaxy S 4] k1mu:
What's the complete build number on your developer phone?

The booting into downloader mode is not supposed to happen after a custom flash on a dev phone.
[Verizon Samsung Galaxy S 4] wtherrell:
I found one on tech errata website. It was for jfltevzw and the had several numbered versions back as well as latest.
[Verizon Samsung Galaxy S 4] playaprez35:
The Complete build number is: JSS15J.I545OYUEMJ7

Both the box and order invoice say: GS4 SCH-I545ZKDVZW

The Kernel version is:

3.4.0

se.infra@R0302-07 #1

Mon Nov 4 15:15:28 KST 2013

The odd thing is that Baseband version, and IMEI both say: Unknown

Is this unusual? Because I never inserted my SIM card when setting up the device, I used Wi-fi. Before I started my current search for a remedy, I had also initially used the standard MJ7/MK2 root method for retail phones. Could this be the problem?

Thanks for the inquiry, I'm trying to keep hope alive.
[Verizon Samsung Galaxy S 4] playaprez35:
No Dice

Thanks for the tip. I downloaded two different versions of TWRP. The problem is the downloads are .img files. I tried using Cabloomi's method, and Cygwin, apparently I have no clue how to convert .img files to .tar.md5.

I was all hyped up too lol. Normally when I flash a custom recovery through Odin it says: "Recovery" in the box above Com. Whatever the reason be it my novice, or my phone it didn't work. I followed the step by step instructions to the letter.... Do you know how to convert .img files to .md5?? Because I'm pretty much lost at this point. Kind of "Living on a prayer" here, but I'm starting to feel like I'm close to an answer/explanation.

Thanks again.
[Verizon Samsung Galaxy S 4] Skeetch79:
Copy the img file you have to the following directory (if cygwin is installed to c:\cygwin): c:\cygwin\home\(your windows login name)\. You may see some files starting with a period (i.e. .bash).

For recovery.img:

Run the following commands from your cygwin terminal window:

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

md5sum recovery.tar >> recovery.tar

mv recovery.tar recovery.tar.md5

---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------

Those are 3 separate command lines
[Verizon Samsung Galaxy S 4] playaprez35:
Thanks, but that still didn't work. So here's what I've got:

Copying skeleton files.

These files are for the users to personalise their cygwin experience.

They will never be overwritten nor automatically updated.

`./.bashrc' -> `/home/Playaprez35//.bashrc'

`./.bash_profile' -> `/home/Playaprez35//.bash_profile'

`./.inputrc' -> `/home/Playaprez35//.inputrc'

`./.profile' -> `/home/Playaprez35//.profile'

Playaprez35@Playaprez-PC ~

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

tar: recovery.img: Cannot stat: No such file or directory

tar: Exiting with failure status due to previous errors

Playaprez35@Playaprez-PC ~

$ md5sum -t recovery.tar >> recovery.tar

Playaprez35@Playaprez-PC ~

$ mv recovery.tar recovery.tar.md5

I've tried this several times with several .img files. I have no idea what the issue is. It could be the .img files, my computer, my version of Cygwin, or me. I sincerely hope it isn't the latter.

Any suggestions???
[Verizon Samsung Galaxy S 4] Bait-Fish:
[MENTION=4939386]Surge1223[/MENTION] had mentioned that it takes using a Hex editor to trim off some excess zeros at the end of file img file to make it as if it's "signed." This is what I recall. Cabloomi's method didn't work for me either.
[Verizon Samsung Galaxy S 4] Skeetch79:
Dumb question, but did you copy the recovery.img file into the /home/Playaprez35/ directory?

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

Also, use the same punctuation. i.e. recovery.img vs Recovery.img

---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------

Never had to do any trimming in my experience. Then again they were files that I obtained directly from dd'ing each corresponding partition
[Verizon Samsung Galaxy S 4] Surge1223:
I can't/haven't tested either of these twrp recoveries below so use at your own peril. They are for jfltevzw, just made into Odin tars for the dev edition owners (that means don't flash them if you have a retail S4)

TWRP-2.5.0.0-devjfltevzw.tar.md5

md5:772b4069d98fe513eb307b009e56f6cd

TWRP-2.6.3.1-devjfltevzw.tar.md5

md5:1346ebe2351aab5de66d449db49cd5a8

As a bonus since this is a dev edition thread...heres the new dev modem. It flashes fine in Odin, I know you guys may remember my tars only semi-working back when we were trying to build OYUAMDK, but I have gotten pretty proficient at it lol. Download below (this can be used by either dev or retail S4's)

I545_OYUEMK2_modem.tar.md5

md5: b2d308b75c25e1a9d35fef664f29c2cf

​
[Verizon Samsung Galaxy S 4] equake:
Any difference between this modem and the Consumer Ed Modem?
[Verizon Samsung Galaxy S 4] playaprez35:
Not a dumb question at all, I just want to help solve this riddle. And I have no problem with being thorough, but to answer your question, yes I did copy/rename the file properly. "recovery.img" I'm just glad that someone got the ball rolling. I'm at work right now, so I can't test it out. Plus some of what you guys are talking about, is just a little above my level of comprehension. I think that it has been broken down enough for me to understand. Thank you everyone for all of your help.

Special shout out to

Surge1223

!!! I'll keep you guys posted.
[Verizon Samsung Galaxy S 4] Skeetch79:
I am dumbfounded by this. Sorry to be obsessing, I guess that is my nature and all (being a scientist I obsess over theories and stuff). It will be my downfall! LOL

A few last things and I will drop it. I believe you renamed the file to recovery.img, but make sure it isn't recovery.img.img or something like that. Enable extensions of known file types to be shown within Windows Explorer. Lastly, type the 3 command lines exactly, even copy and paste them if need be:

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

md5sum recovery.tar >> recovery.tar

mv recovery.tar recovery.tar.md5

I will drop it at this point. It still baffles me though. But if you need any of us to provide you with boot, recovery, radio, modem or system tar.md5's let us know. I should have some on hand! :)