yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Surge1223:
Can you copy the output or tell me exactly what was before and after. What was the nand fail message? Was it at nand write start?

---------- Post added at 11:06 PM ---------- Previous post was at 10:59 PM ----------

Also, your running odin as admin, have the latest samsung usb drivers, and no kies software on your pc corrrect?

Edit: at this point im breaking all the links, and making this final odin image that should eliminate any outliers, if this one doesnt work then Ill concentrate on helping Toddricks restoring his system (if it isnt working) and then ill investigate longer as to what the error is. I would encourage you to explore the odin image yourselves to see if you find any errors.

Edit: has come to my attention that the non-halos.bin ,and modem are need to be trimmed, i forgot the modem needs to be signed, I'm 100% sure that was the issue. Flash the mdk modem and non-halos in case you accidently flashed this.

I545OYUAMDK_MODEM_RECOVERY_KERNEL.tar.md5

Download here

MD5:

Edit:changed file 10/6/2013
[Verizon Samsung Galaxy S 4] Toddricks:
Don`t concentrate on helping me. That is what I am trying to do by flashing these files. My system is fine besides the fact that it has consumer firmware and rom on right now. Yes I would like to have it developer edition stock but it can wait. My worst case scenario is a bad flash, send dev device to Samsung and pay for a reflash.

Answers to above questions: yes to all. I am attaching a screen shot of odin 3.07 after fail.

I would try the above download but the link is down.
[Verizon Samsung Galaxy S 4] Chris123NT:
Doesn't flashing a consumer firmware lock your bootloader or am I wrong?
[Verizon Samsung Galaxy S 4] Bait-Fish:
markwebb got ME7'd locking it down.

Toddricks, did you ODIN retail MDK (sextape's)?
[Verizon Samsung Galaxy S 4] Toddricks:
Yes but mdk version as far as I know my boot loader is unlocked. If it is locked then oh well I still have root access and custom recovery. As well as another mdk gs4 to play with.

How do I tell if bootloader is still unlocked? (seriously)
[Verizon Samsung Galaxy S 4] Chris123NT:
Easy way to test your bootloader is to odin a non-loki'd recovery like philz touch (the one without the loki patch), worst case just odin back to a loki'd one.
[Verizon Samsung Galaxy S 4] Toddricks:
Could not get philz to flash. I guess I screwed up and let my boot loader get locked. Gonna call samsung tomorrow to check on a price to get it back. May just have to use it as a lokid device if the cost is to much. At least for now it is rooted with custom recovery.
[Verizon Samsung Galaxy S 4] Chris123NT:
What do you mean you couldn't get it to flash? It refused to flash or it flashed and gave you that unauthorized software screen.
[Verizon Samsung Galaxy S 4] Toddricks:
Flash failed in odin. Maybe i didnt do something right.

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

When in download mode what should my write protection show? Enabled or disabled. Mine shows write protection enabled if it matters

Just curious

This is on gs4 dev device
[Verizon Samsung Galaxy S 4] Bait-Fish:
Mine says "WRITE PROTECTION: Enable" too, but right above that it says, "MODE: Developer."
[Verizon Samsung Galaxy S 4] Chris123NT:
This is the latest ODIN package http://d-h.st/Qnn

Does yours say MODE: Developer above the write protection bit? Mine does.
[Verizon Samsung Galaxy S 4] Toddricks:
Does not say developer mode.
[Verizon Samsung Galaxy S 4] Chris123NT:
Ouch, yeah then your bootloader got locked.
[Verizon Samsung Galaxy S 4] Roland_D:
So I guess all those tests weren't reliable...
[Verizon Samsung Galaxy S 4] Chris123NT:
Yeah, I'm guessing that when he ODINed a consumer image it blew a qfuse or some crap, preventing him from flashing anything dev phone related, similar to what happened when people got screwed by the ME7 OTA and they couldn't ODIN back to MDK.

EDIT: BTW I'm pretty sure aboot.mbn is the bootloader, so if we wanted to make a ODIN image for the dev phone just make one that doesn't include aboot this way ODIN will NOT touch the bootloader, or anything else we wouldn't want it to touch. not 100% sure about this bit though, trying to wrap my head around all of this still.
[Verizon Samsung Galaxy S 4] Surge1223:
The bootloader is a simplified way that people refer to the the partitions of modem (or mdm) sbl1, sbl2, sbl3, aboot, tz, and rpm they then instruct the kernel to load android. Thats for our device, but the bootloader partitions change depending on the device. If you look above I already said there would be no way I would include aboot or sbl1 in an odin package unless it was for someone already hardbricked or a a similar issue.
[Verizon Samsung Galaxy S 4] Surge1223:
As far as progress on this, the fact that I knew it was the apnhalos (NON-HLOS) partitoin that messed up the odin image before you posted the results is good news. Sorry im usually more careful than that, its been a long week. Luckily fixing the issue is pretty straightforward. And by all means if you have any input on this feel free to both discuss and express your concerns.
[Verizon Samsung Galaxy S 4] Toddricks:
I succesfully flashed dev modem on my developer device. Running beans 7 on mdk so my wifi is now non working(a non issue for me). Trying to do my part and help the smart guys put a dev odinable stock image together.
[Verizon Samsung Galaxy S 4] Surge1223:
Guys I need someone who still is on stock dev system (doesnt matter if you're rooted or not) to zip the contents of /system/lib/modules, I need the contents of that folder to get the kernel to work. Remember it has to be on stock dev (not mdk or me7). Thanks.
[Verizon Samsung Galaxy S 4] Roland_D:
I have a backup of my stock ROM... Is that good enough? It's not rooted... Just custom recovery.
[Verizon Samsung Galaxy S 4] oakley470:
From stock unmodified dev edition,holding out for this backup so please keep it up so I can mess with this bad boy!
[Verizon Samsung Galaxy S 4] Surge1223:
Thanks guys. Also Roland_D, I might need that rom. I have scotts deodexed root dev rom. I odexed it, removed su (root), busybox etc. and its basically a stock rom now. But since yours is pure, that would really be preferable. Let me know if this is possible, for now ill continue with what I have.

Edit: Nevermind I got it downloaded from Bait-Fish's post. I got 4shared works again. Thanks anyways though.
[Verizon Samsung Galaxy S 4] Roland_D:
OK great... If you need anything else I think we are all at your disposal...

Thanks for working on this, you are greatly appreciated...
[Verizon Samsung Galaxy S 4] Surge1223:
Alright guys. Its posted, so future updates will be here
[Verizon Samsung Galaxy S 4] Bait-Fish:
Thank you VERY much, Surge1223! I am not sure if/when I will need these, but am utterly grateful for your help!
[Verizon Samsung Galaxy S 4] markwebb:
??? Is this a stock recovery image? I read the post you linked to but am confused as it seems to indicate that if I used this it would lock my device??? Thanks!
[Verizon Samsung Galaxy S 4] Surge1223:
No it doesn't lock your device in anyway. For people on MDK or ME7 i was saying that it wouldn't help them unlock theirs. Also I was saying that if you had a developer edition of the device and you accidently flashed me7, Im not sure it would help you get back to the unlocked state.
[Verizon Samsung Galaxy S 4] markwebb:
Understood..well, since I am the OP of this thread (LOL LOL) and since I already returned a locked dev device within the 30 day warranty and now have a completely unlocked 2nd dev device well past the 30 day warranty, I will NOT touch this..until things are 100% certain. :)

But with that, am THRILLED about all of this work and effort! Thank you so much!
[Verizon Samsung Galaxy S 4] asharad:
Thank you surge. I really appreciate your efforts!
[Verizon Samsung Galaxy S 4] multivacac:
I've read through this thread and the

[Firmware][unofficial]1545OYUAMDK ODIN TAR] thread linked above, apologies if I missed a more relevant thread but information specifically for the developer edition seems to be mostly in these two threads.

I used Odin to load Philz recovery and loaded the SuperSU as described in the thread but ran into trouble when trying to flash the OctOS rom (This may have been an obvious mistake but from reading through the threads it looked like I could try any standard Verizon S4 rom and included the dev modules).

When trying to boot up now I am stuck on the the Samsung splash screen with the Custom Unlock symbol. When I try to boot into Custom Recovery mode I see the blue text at the top of the screen then it appears to restart and sit again.

I can still access the Download mode. I tried reloading philz recovery with Odin but wasn't able to boot the recovery. I then tried to follow the directions in the thread above to load the 1545OYUAMDK (this was where I was when I began) files but still can't boot into recovery or anything else. I have the initial backup I made with philz recovery too if there is a way to recover from them.

I am guessing I haven't bricked my phone, but just don't have the files and such on it needs to boot. Could I grab one of the known working roms like darkslide and possibly flash through adb or something?

Any help is greatly appreciated.
[Verizon Samsung Galaxy S 4] Skeetch79:
The latest ROM has some boot issues try the ROM one step before the latest. Wipe data and cache, factory reset. Then install the ROM one before the latest
[Verizon Samsung Galaxy S 4] Surge1223:
Wait, if you flashed that Odin image in that thread?, did it fail? Did aboot flash!?! It would be greatly helpful if you could answer a few questions for us. So you're saying that whenever you try to boot into recovery the blue text appears in the upper left but then the phone just restarts again? Okay if that's the issue, then this is what you do:

Remove the battery, then re-insert your battery a few minutes later. Next while holding vol up, press and hold the power button and immediately after plug the phone into the charger, if the blue text disappears and the phone trys to reboot again then let go of vol up and power and press them immediately after the phone tries to boot again (essentially im saying just constantly try to issue the command to reboot into recovery, don't let it try to boot the os.) If you get your timing right with the charger and boot sequence, you should be able to get into recovery and flash a new recovery, and hopefully restore your files. Please get back to us with any progress/issues you've made.
[Verizon Samsung Galaxy S 4] Bait-Fish:
The OctOS devs also highly recommend TWRP, v2.5.0.2 being agreed upon as being the most stable.

I have been using the OctOS, October 22, Donald version successfully since it came out. And, I haven't had the need to flash modules to make it work either.

--OctOS Powered VZW GS4 Dev Edition
[Verizon Samsung Galaxy S 4] multivacac:
I did try flashing the Odin image in the thread with Heimdall (I originally tried to post in that thread, but I don't have enough posts). I hadn't used Heimdall before, so at first I made my own .PPT from my device and then was adding the partitions manually and I didn't get any errors when I hit start. I am pretty sure I tried this with the aboot. Then when after rebooting I got stuck on the Samsung Unlock screen.

Then I realized there was a SGR.pit in the file and selected that and it put the partitions in the Partitions section automatically. I got stuck at the same point when trying to reboot.

I didn't get see errors in Heimdall and the Status bar went to 100% both times. I apologize I am a little new to this so I am pretty sure I did something wrong in the process so my feedback may not to helpful. Let me know if there is anything I am being unclear about or can clarify.

I was able to boot into the recovery following your instructions, I forgot I had tried loading the TWRP recovery image as a last attempt last night before making the thread. I loaded the PhilZ recovery and am copying my backup files onto a usb drive (I am using an OTG cable as I didn't have a sd card) right now to try and restore. (If the backup files made with PhilZ recovery are of any use I can post them, I made the backup right after loading PhilZs through Odin) .

Thanks for the advice about OctoOS, I saw that TWRP was the recommended method and that was a dumb mistake on my part. My current plan is to try and load my files from the backup, then flash TWRP and try the donald version.

Thanks everyone for your help.
[Verizon Samsung Galaxy S 4] multivacac:
Just wanted to let you guys know I got everything sorted.

I wasn't able to reload my original backup (I copied it off the phone after making it with Phil Z's recovery). Maybe I uncompressed it and forgot and thats why it couldnt find it.

After trying that I flashed back to TWRP and loaded the previous of OctOs and that got me going.

One sort of quirk I think might be left over from using Phil Z is there seems to be a symlink for my internal SD card (When I was in Phil Z I used it to point to the internal SD to load flash some files).

Thanks for all the help.
[Verizon Samsung Galaxy S 4] markwebb:
Can you do me a favor? I "think" i have that build, but am discovering in most NON TW Roms , call forwarding doesn't work. Can you test for me? Basically, it lets me enter 72* and as soon as I enter the forwarding number, it closes and doesn't allow me to enter the forwarding number. I do use this device as a phone and this is important to me.

If it does work, do you have a link to file for that build just in case? Thanks!
[Verizon Samsung Galaxy S 4] Bait-Fish:
Mark, I tried it, *72+(10 digit forward #). Heard two short beeps and it hung up. Tested it working, forwarded good. Used *73 to disable the forward and hard another couple short beeps and it hung up again. No FC.

The OctOS version I am using is Aroma-10-22-2013-donald.zip. I tried the October 31 release a couple times but the kernel weirdness on that one pushed me back to the previous build.
[Verizon Samsung Galaxy S 4] markwebb:
Thanks! Strange..on most non-TW ROMS, as soon as I begin to enter the 10 digit forwarad #, it hangs up w/o completing. I will try it when I get home.
[Verizon Samsung Galaxy S 4] abe_cedar:
not been able to boot into rom

mark,

I have messed up my device. It has phil recovery on in and beans b7 version in there. I can boot into recovery but every time after beansintall it kicks me back into download mode. I have done a twrp like backup using phil recovery but I get and error ( is prob corrupted),

Any ideas how to bring this back to life?

Maybe there is an aroma setting in which I can flash and boot.

Any odin tar images?

I have tried the tar below but it cannot get the aboot.

thanks

http://xdaforums.com/showthread.php?t=2483619
[Verizon Samsung Galaxy S 4] jpcalhoun:
Well, I'm not Mark, but let me try to help. Does your computer recognize your phone? If not do you have the Samsung drivers loaded on the computer? If the answer to either question is no then install the S4 drivers on your computer and see if it will recognize the phone. If it does then copy a different ROM onto your external sd card and try to flash it. If you have the S4 drivers on your computer but the computer still doesn't recognize your phone then take the external sd card out of your phone and put it in your computer or card reader and copy a different ROM onto your sdcard. Then return your sdcard to your phone, enter recovery, do a complete wipe/clean and factory reset and then flash the different ROM. If you're looking for a different ROM there are a number of good ones on XDA. I recommend Eclipse 2.0 or the latest SLIM ROM. Both a stable.

After getting your phone up and running I would consider using TWRP 2.5.0.2. I used PhilZ recovery for awhile and had trouble flashing certain ROMs. I've never had an issue with the recommended version of TWRP. I can't explain the difference between the two recoveries, but TWRP has never failed me.
[Verizon Samsung Galaxy S 4] abe_cedar:
Jp,

Thanks for the answer. I wonder where I can get a zip file for TWRP in this link there are only img files. I will try eclipse.

Beans mentioned in the N3 thread he has unsigned kernel.He said that a signed kernel after a flash would kick the device back into download mode. I mean are there unsigned kernels out there I can have?

Does the TWRP 2.5.0.2 works since is for a lokied device?

Thanks
[Verizon Samsung Galaxy S 4] jpcalhoun:
Go to the TWRP web site. You can find a zip file there. You have to look around for the download page, but it is there. Just put the TWRP zip on your sdcard after you get things running and flash, it will replace the PhilZ recovery. If you flash Eclipse it will come with a ktoons signed kernel built for TW ROMs. Like I mentioned, the Eclipse TW 2.0 ROM available here on XDA is a great ROM.

Here is a 2.5.0.2 download I used. It works with no problem. Go here:http://d-h.st/gLS
[Verizon Samsung Galaxy S 4] abe_cedar:
thanks

I will try and report back.

much appreciate the support here.

Thanks
[Verizon Samsung Galaxy S 4] jpcalhoun:
No problem. Good luck.
[Verizon Samsung Galaxy S 4] sparky697:
I was thinking of changing to twrp from Philz as well. The backups aren't interchangeable are they? Guessing I should reload stock, then change to twrp, make backup then flash whatever?
[Verizon Samsung Galaxy S 4] jpcalhoun:
You're right. The backups are not interchangeable. Reloading stock and going from there is a good plan.
[Verizon Samsung Galaxy S 4] abe_cedar:
I was able to flash y...mdk from scrolser. It boots into the rom but it gets stuck at activating. I have tried several modems no luck. I had the sim in the phone .

Any ideas?

Tia
[Verizon Samsung Galaxy S 4] jpcalhoun:
Hmm, not sure what's going on here. What did you flash? Did you flash a baseband (modem) or did you flash a complete ROM?
[Verizon Samsung Galaxy S 4] abe_cedar:
I have tried several modems. Scott's rom does not have the modem in. The reason I've tried the modem is that the phone gets stuck at activating..

I can turn it on and off but no network and no wifi
[Verizon Samsung Galaxy S 4] Bait-Fish:
Did you flash the Dev modules scrosler posted in his ROM thread?
[Verizon Samsung Galaxy S 4] abe_cedar:
Yes and still no network.

It could be the efs
[Verizon Samsung Galaxy S 4] Jetdr:
I have had my Dev Phone since October. I have ran various ROMs without issues until just recently. I wanted to try the new HyperDrive ROM. I installed the ROM and all was well. The phone booted and all was good, I let the phone sit for 5 minutes before touching anything. I then (following Directions), rebooted the phone...and thats were all hell has broken loose. The phone will NOT boot up. I can reload the ROM and the phone will boot all the way up. I can use the phone (everything works..Nice ROM). As soon as I try to do a reboot, or just power the phone off and then try to restart it is just sit on the "Samsung" start page with the open lock that says Custom on it. The only way I can get the phone usable again is to wipe it completely and re load the ROM. Doesn't matter what ROM I load. This happens with EVERY ROM I have tried. I have completely wiped the phone and tried to do a restore from one of my orginal Back Ups and I get the same behavior. The phone will boot up just fine but will not boot again from a power off state.

Anyone have any ideas? I am stumped.
[Verizon Samsung Galaxy S 4] Jetdr:
Bump please.. Any one?
[Verizon Samsung Galaxy S 4] willstilson:
I've had that happen on a non-dev edition quite a few times. I was running TWRP recovery. I switched to CWM and it's been fine since. Not sure it;s related, but maybe worth a shot.
[Verizon Samsung Galaxy S 4] Jetdr:
I will try CWM again. I've been and was on Philz CWM and the problem was still there. I'll try it again.
[Verizon Samsung Galaxy S 4] markwebb:
My Dev edition began doing that a few months ago and I was using Philz; had to abandon it. Try Twrp 2502 version which seems the most stable.
[Verizon Samsung Galaxy S 4] Jetdr:
That was it!!! Thanks so much for this suggestion!! Using TWRP 2.5.0.2 did the trick. I am now able to reboot my phone. YEA!!!
[Verizon Samsung Galaxy S 4] abe_cedar:
link

Can you please post a link to the TWRP u are using. There is a loki versus non loki issue.

Thanks
[Verizon Samsung Galaxy S 4] asharad:
I'm not sure what you mean. I'm using TWRP from the TWRP website. It works fine on my DEV phone.
[Verizon Samsung Galaxy S 4] abe_cedar:
U mean the verizon version?

On note 3 from verizon I use a twrpnfrom a tmob twrp. That is why I am asking

Tia
[Verizon Samsung Galaxy S 4] asharad:
Beware, this thread is for the Developer version of the Verizon GS4. And to answer your question yes, I use the TWRP version that is listed for my phone on the TWRP website. If you are using a Note 3, you should check the Note 3 forums for help. Following instructions for the wrong phone can cause you troubles. You probably know that already, but I want to be sure I don't lead you astray.
[Verizon Samsung Galaxy S 4] wtherrell:
So glad I spent the extra money for the dev edition, when I see all the hassle others are going through. And I got to keep my unlimited.
[Verizon Samsung Galaxy S 4] asharad:
I agree.
[Verizon Samsung Galaxy S 4] odawgx:
Has anyone had any luck flashing any ROMS on the developer edition?

I was able to get my custom recovery installed, but every time I flash a ROM, I get a black screen and it won't boot.

Is there a list of ROMS that work with the developer edition?

I confirmed that my bootloader is still in Developer mode and if I flash back to my nandroid backup, it works fine.
[Verizon Samsung Galaxy S 4] Bait-Fish:
My only experience is with OctOS. The devs there only support TWRP, especially v2.5.0.2.

Have you tried booting to recovery using the "three finger salute?" This was not my find, but does work for me.

From having your phone shut down (off), hold the home button, volume, and power buttons. Let go of power when you see rebooting to recovery. It will likely reboot but keep holding the home and volume buttons until that second time into recovery.

Maybe that will work for you.
[Verizon Samsung Galaxy S 4] wtherrell:
Currently running Hyperdrive 12 on mine.

Looks like perhaps you left out rooting the device. Now I know that some say that root is included with the rom but I flashed Chainfire's SuperSU / root zip combo before trying any roms. I have been able to flash several roms including Hyperdrive versions 8 thru 12 with very few problems. At first I had to flash scrosler's dev ed modules to get wifi to work but not lately.
[Verizon Samsung Galaxy S 4] sparky697:
I've run both aosp and eclipse tw on mine with no issues. What recovery are you using? That has been the problem for some in the past.
[Verizon Samsung Galaxy S 4] odawgx:
I am using Philz recovery as listed earlier in this thread. I have no problem switching to TWRP. I was going to flash it to see if that makes a difference.

Does the stock ROM have to be rooted before I can flash a custom ROM, even if I am flashing it through recovery?

Pardon my ignorance, but I thought flashing a ROM wipes out everything done in the stock ROM including root.

Do I need a special version of TWRP for the developer edition? I noticed that the one for the Galaxy S4 (VZW) on TWRP's website says it's already been loki'd. Will that cause a problem?

Thanks to everyone for their time and assistance.

Omar
[Verizon Samsung Galaxy S 4] odawgx:
I have been having a heck of a time with this. The only recovery that will install is Philz and it won't let me install any ROMs. I have installed SuperSU-1.9.1 and the device is rooted.

Any ROM I install will not actually boot up and any other recovery besides Philz just takes me to Download Mode with an "unable to boot" error message.

Philz works fine but it won't let me install any ROMs. I feel like I am definitely missing a step here.
[Verizon Samsung Galaxy S 4] equake:
Try installing TWRP using Philz.