Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Firmware][Unofficial][ODIN]S4 DevEd[boot/recovery/radio/modem][MDK-MJ7-MK2-NC5]

OP Skeetch79

22nd June 2014, 08:24 PM   |  #91  
k1mu's Avatar
Recognized Contributor
Flag Virginia
Thanks Meter: 1,580
 
1,925 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Quote:
Originally Posted by gavron

Further update in case this helps anyone else or triggers a thought.

When using Philz to flash CM11, Philz reports

E: Error loki-ifying the boot image.

I have manually pulled aboot.img, boot.img, and ran loki_tool to find out that:

Code:
/data/local/tmp # loki_tool patch boot aboot.img boot.img out.lok
Loki tool v2.1
[-] Failed to find function to patch.
From examining the source code it appears the code in loki_patch.c looks for
a set of patterns ("fingerprints") of the target code. The new VZW DEV ROM Aboot
does not appear to have any of those.

Is this the right conclusion? Do I need to wait for someone to release a new loki_patch
that can handle this new aboot... or is there a different method?

Thank you all,

Ehud

If you have a Developer Edition phone, the bootloader is unlocked. You don't need to use Loki to bypass it.
23rd June 2014, 03:01 PM   |  #92  
Skeetch79's Avatar
OP Senior Member
Flag West Milford, NJ
Thanks Meter: 164
 
235 posts
Join Date:Joined: Oct 2010
More
Quote:
Originally Posted by gavron

EDIT: Update: Your version of Philz works fine! Thank you! And also, I have a clockworkmod nandroid backup that doesn't work (com.google.gapps constantly dies on the restored version), a TWRP backup that works great to get back to virgin Samsung OS, and am now doing a Philz backup as well.

Thanks for lots of good info. I will try your version of Philz and see if that runs or gives me the no run error.
(Note: I use linux but am confident that heimdall flash is equivalent to Odin. It worked for TWRP and CWR...)

- Why did I try VRUAMDK? Originally when I got the first one of these (DEV) it was running VRUAMDK.
At the time I could flash whatever I wanted. TWRP + CM11 ran fine. Then I put the wet-apply screen protector
on it and the digitizer&screen died. While repairing that, Samsung "did me a favor" and flashed it locked.
After six months of back and forth I now have two of the I545OYUFNC5s and they allow me to flash SOME
things with no issues.

- I cannot get CM11 or CM10 or Team Gummy ROMS to work now. THEY DID WORK ON THIS PHONE
BACK before I gave it to Samsung. I'm assuming the new Aboot is preventing them from running.

- I *can* get a touchwiz-based Jely-Bean to run (jfltevzw_JellyBeans_B7) if I select its installer's safestrap
option. This also provides the seandroid enforcing message and 30+ seconds later times out and boots
the rom.

- What is the ultimate goal of my use of this dev phone? I would like to run custom builds based on CM10&CM11
to test various things. I currently have a DEV VZW MotoX, a DEV TMO MotoX, and these two DEV VZW S4s.
SO I get when you're saying "we were all n00bs but please do research ..." and "...you can install kernels and
systems..." My requirements are not that complex, but I'm unable to get CyanogenMod to run. THAT right now
is the biggest hurdle.

Thanks for taking the time to detail your answer! I hope I've clarified further.

E

Sorry it has taken me a while to reply, busy weekend with the 3 kids, 2 dogs, wife and other family. Glad to hear Philz worked for you. It has basically been my go to recovery. After the upgrade from MDK I have not had any success with TWRP, the Loki exploit was patched after MDK which is also why the amount of ROMs which you can run have dwindled (hence why you are having issues with CM Roms) - with MDK you could basically run anything! Oddly enough, SafeStrap ran fine while I was on MJ7/MK2 and that utilized TWRP as it's recovery - had no issues with TWRP in this fashion, just as a standalone recovery.

I find it hard to believe that the original Firmware on your Dev phone was I545VRUAMDK, when Developer phones would have run I545OYUAMDK, unless Samsung forgot to change the baseband/Build information. Interesting nonetheless.

My experience with Samsung has been less than par as well. I started out with an OYUMDK and after paying close to $700 in September of last year for the phone and then finding out we would never have software updates, etc, I sent an email to someone at Samsung. That started a ball rolling where I was able to have the device upgraded to MJ7 then MK2 and then finally NC5. It shouldn't have to be that way. (Some argue is not the point of having a Developer phone - and I agree, but software upgrades are nice. The Moto Developer Ed phones get upgrades, as well as the HTC Developers). After my time with this device - which I cannot complain about the Camera, though TouchWiz sucks - I will definitely look to get back in the Moto world with one of their Developer Edition phones. I took a chance with Samsung after having a Droid X, Droid Bionic and Droid Razr and stepped outside of my comfort zone . I should've stayed within the Moto walls!

But I hope I can help moving forward if you have any other questions or issues.
23rd June 2014, 07:38 PM   |  #93  
00negative's Avatar
Senior Member
Thanks Meter: 151
 
555 posts
Join Date:Joined: Aug 2010
I got rid of the custom system status on mine but can't get rid of the custom binary designation?? And triangle away doesn't seem to reset the flash counter. Chainfire's G+ says that had been an issue on 4.3 devices that show a custom system status or binary.

Odin won't let me flash stock radio files says Auth (fail). Any one have any ideas?

Dev edition with MJ7 currently

Sent from my SCH-I545 using Tapatalk
19th September 2014, 12:15 AM   |  #94  
Member
Thanks Meter: 6
 
65 posts
Join Date:Joined: May 2008
This whole topic is very confusing. If the dev. edition phone comes with mdk2 can it be downgraded to mek or mdk and does this have to be done with`these developer edition files in the op? thanks in advance.
19th September 2014, 06:01 PM   |  #95  
00negative's Avatar
Senior Member
Thanks Meter: 151
 
555 posts
Join Date:Joined: Aug 2010
Quote:
Originally Posted by rnh

This whole topic is very confusing. If the dev. edition phone comes with mdk2 can it be downgraded to mek or mdk and does this have to be done with`these developer edition files in the op? thanks in advance.

Assume you mean emk2, but the answer I think is no unless you had the mdk bootloader partition still because of Knox I think but been awhile since I have thought about this mess.
23rd September 2014, 08:25 PM   |  #96  
Senior Member
Thanks Meter: 37
 
311 posts
Join Date:Joined: Oct 2010
Anyone tested the NC5 ROM on their Dev Ed?
23rd September 2014, 08:48 PM   |  #97  
Skeetch79's Avatar
OP Senior Member
Flag West Milford, NJ
Thanks Meter: 164
 
235 posts
Join Date:Joined: Oct 2010
More
Quote:
Originally Posted by equake

Anyone tested the NC5 ROM on their Dev Ed?

I have the official NC5 Rom on my Dev Ed and it seems to run very well. Knox is easy to disable. Root is easy to achieve. Enabling writing to the External SDCard is easy (even though it is a PIA that they disabled it in KitKat). I have an "upgrade" package here: http://forum.xda-developers.com/gala...store-t2820232

Backup your ABOOT partition. I have used the emergency restore which I created on my NC5 to return to rooted NC5 numerous times without issue.
20th December 2014, 05:28 PM   |  #98  
BDAZZG1's Avatar
Senior Member
Flag Prescott Valley, AZ
Thanks Meter: 111
 
165 posts
Join Date:Joined: Jul 2011
Donate to Me
More
Quote:
Originally Posted by Skeetch79

I have the official NC5 Rom on my Dev Ed and it seems to run very well. Knox is easy to disable. Root is easy to achieve. Enabling writing to the External SDCard is easy (even though it is a PIA that they disabled it in KitKat). I have an "upgrade" package here: http://forum.xda-developers.com/gala...store-t2820232

Backup your ABOOT partition. I have used the emergency restore which I created on my NC5 to return to rooted NC5 numerous times without issue.

Hey Skeetch, Are you still around bud? I've got a mucked up Dev Ed SCH-I545 that maybe you can shed a little light on. I purchased it with MDK on it (it worked fine of course) When I received it I was happy to find your thread with these NC5 files and stupidly dove right into Odin. All went well until reboot... BLACK SCREEN Nothing more The device is now only recognized by my PC as Qualcomm HS-USB QDLoader 9008. Been there, Done that with the Moto's. I read here that you are/were deep into Moto as well. I've been developing Moto since the OG Droid needless to say I'm not new to this game lol. Anyhow, it was then, (I know I know... stupid right?) that I decided to dig deeper into what I had just done to my device. Your tarball includes the .tz partition which I believe is what caused my brick due to still being on MDK aboot. You had mentioned Samsung actually updated your device which proves my theory as to why the file works fine on your device. I assume you have their official Dev Ed NC5 aboot image on yours? Again I am basing my theory on my Motorola knowledge. If I could only turn back the hands of time I would have removed that .tz from the tarball. But what's done is done. Any thoughts or suggestions would be greatly appreciated. Thanks!

P.S. I do have access to a RIFF box and may actually end up purchasing it if necessary.
Yesterday, 04:31 PM   |  #99  
Skeetch79's Avatar
OP Senior Member
Flag West Milford, NJ
Thanks Meter: 164
 
235 posts
Join Date:Joined: Oct 2010
More
Quote:
Originally Posted by BDAZZG1

Hey Skeetch, Are you still around bud? I've got a mucked up Dev Ed SCH-I545 that maybe you can shed a little light on. I purchased it with MDK on it (it worked fine of course) When I received it I was happy to find your thread with these NC5 files and stupidly dove right into Odin. All went well until reboot... BLACK SCREEN Nothing more The device is now only recognized by my PC as Qualcomm HS-USB QDLoader 9008. Been there, Done that with the Moto's. I read here that you are/were deep into Moto as well. I've been developing Moto since the OG Droid needless to say I'm not new to this game lol. Anyhow, it was then, (I know I know... stupid right?) that I decided to dig deeper into what I had just done to my device. Your tarball includes the .tz partition which I believe is what caused my brick due to still being on MDK aboot. You had mentioned Samsung actually updated your device which proves my theory as to why the file works fine on your device. I assume you have their official Dev Ed NC5 aboot image on yours? Again I am basing my theory on my Motorola knowledge. If I could only turn back the hands of time I would have removed that .tz from the tarball. But what's done is done. Any thoughts or suggestions would be greatly appreciated. Thanks!

P.S. I do have access to a RIFF box and may actually end up purchasing it if necessary.

Sorry it took me this long to reply, I have been traveling with family. I am so sorry to hear about your situation. Where I can suggest to start at this point is Surge's thread with the MDK emergency recovery ODIN tar. That may bring your device back. http://forum.xda-developers.com/show....php?t=2483619.

Hard lesson to learn, but before flashing any firmware to your Dev Ed device, I would have rooted it and then dd'd (pulled) all partitions. That way an original backup would exist in case things went awry. You would then be able to build you own ODIN tar and bring your device back.

EDIT: I have some of the files which Surge included in his original MDK Odin. If you need some of them or all of them please let me know and I can find a way to get it/them to you.

EDIT 2: look here for an example on how to create your own ODIN tars....: http://forum.xda-developers.com/show....php?t=2637686

Here is a .bat file I created to pull the partitions from an NC5 Dev Ed device. All files are saved to the extSdCard which can be pulled later.

@echo off

adb shell "su -c mkdir /mnt/extSdCard/NC5dump"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/NC5dump/aboot.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/apnhlos of=/mnt/extSdCard/NC5dump/NON-HLOS.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/mnt/extSdCard/NC5dump/backup.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/mnt/extSdCard/NC5dump/boot.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/mnt/extSdCard/NC5dump/cache.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier of=/mnt/extSdCard/NC5dump/carrier.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/mnt/extSdCard/NC5dump/efs.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/mnt/extSdCard/NC5dump/fota.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/mnt/extSdCard/NC5dump/fsg.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/hidden of=/mnt/extSdCard/NC5dump/hidden.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/mnt/extSdCard/NC5dump/m9kefs1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/mnt/extSdCard/NC5dump/m9kefs2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/mnt/extSdCard/NC5dump/m9kefs3.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/mdm of=/mnt/extSdCard/NC5dump/modem.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/mnt/extSdCard/NC5dump/modemst1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/mnt/extSdCard/NC5dump/modemst2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/mnt/extSdCard/NC5dump/pad.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/mnt/extSdCard/NC5dump/param.lfs'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persdata of=/mnt/extSdCard/NC5dump/persdata.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/mnt/extSdCard/NC5dump/persist.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/mnt/extSdCard/NC5dump/recovery.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/mnt/extSdCard/NC5dump/rpm.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/mnt/extSdCard/NC5dump/sbl1.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/mnt/extSdCard/NC5dump/sbl2.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/mnt/extSdCard/NC5dump/sbl3.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/mnt/extSdCard/NC5dump/ssd.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/NC5dump/system.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/mnt/extSdCard/NC5dump/tz.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/mnt/extSdCard/NC5dump/userdata.img.ext4'"


To find partition names and locations enter this command either into your terminal app on the phone (need to be rooted of course) or through an ADB shell command prompt on the PC (again, need to be rooted): ls -l /dev/block/platform/msm_sdcc.1/by-name/
Last edited by Skeetch79; Yesterday at 04:37 PM.

Post Reply Subscribe to Thread

Tags
developer, edition, i545oyuamdk, i545oyuemj7, i545oyuemk2
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes