Modem goes to PHONE, i9505g_mfd_stock.tar.md5 goes to PDA.
[GT-I9505G] 4.3 OTA update fails on APNHLOS assert - Error: Status 7
- Thread starter illogic6
- Start date
Thanks! I was able to flash the files, then download the 4.3 update OTA and installed it successfully. Thanks to all of you guys for your amazing work on this.
A big ask, but do people think we could flash this on an i9505, and try and get the OTA to 4.3 from a stock 4.2.2 i9505G rom.
I don't think we're quite there yet.. but.. THAT is where I hope all this effort ends up.
Yes, please guys make it happened. Wish we could install stock android on gt-i9505 int. And be always able to do OTA's just like Google edition owners. Not to mention having the same partition but that's probably not gonna happen..
Sent from my GT-I9505G using xda app-developers app
Sent from my GT-I9505G using xda app-developers app
Hell yeah. I'll upload the 4.2.2 modem files when I get to my laptop. I'll also teach everyone exactly what I did so people can do this on their own for future updates. I'm very glad I was able to contribute to the Samsung community!
Sent from my Xoom using Tapatalk 4
Okay read most of this thread and understood some of it. So questions
I have a GE S4 that all I have done is unlock the bootloader + root and then change the recovery. Then I took a recovery image before changing the rom which I just restored to. What exactly would I need to do to get the 4.3 OTA update.
My baseband version is 19505GUEUAMFD and the build number is JDQ39.I9505GUEUAMFD. I would like to get the 4.3 update so I can move my stock backups to 4.3
I have a GE S4 that all I have done is unlock the bootloader + root and then change the recovery. Then I took a recovery image before changing the rom which I just restored to. What exactly would I need to do to get the 4.3 OTA update.
My baseband version is 19505GUEUAMFD and the build number is JDQ39.I9505GUEUAMFD. I would like to get the 4.3 update so I can move my stock backups to 4.3
Good to know. Is there a link to get the stock recovery? I didn't think to back that up when I started all this. I found this thread but someone posted that using those doesn't get OTA updates but I'm not sure what else they have done to their phone through.
You found the right thread. You only need the recovery img from that zip. That's what I used to restore my recovery partition to stock for 4.2.2.
Sent from my Xoom using Tapatalk 4
---------- Post added at 09:24 AM ---------- Previous post was at 08:48 AM ----------
http://www.mediafire.com/download/dtgrcyv9ux8g4u8/modem_422.tar.md5
There is a 4.2.2 baseband odin flash. It should work to downgrade the baseband in theory. It's different than the ones provided in the 4.2.2 full dump. A little explanation is in order. (Ok, so, this is going to be a long explanation with a lot of technical details.)
What I've done is rip open the update ota and look at the scripts contained within. The one I was originally looking for was how they build the recovery img. Simply put, they apply a recovery-from-boot.p to the boot.img file that's contained within the update zip. That one was fairly trivial to perform. Basically copy the boot.img and the recovery-from-boot.p to your /sdcard and run the applypatch command in a su shell to spit out the recovery.img file. The applypatch command for that looks like this:
The baseband files were more complicated. The ones extracted from 4.2.2 and included in the 4.2.2 full dump didn't match the sha1 hash for the applypatch commands in the update-script. Here's the relevant lines from the update-script:
So what they're doing is patching the baseband partitions with the .p patch files. Basically, what we wanted to do is apply the patch files to the extracted baseband files. But since the hashes didn't match, the applypatch wasn't going to work. Frack! Then I realized...they include a size param in the apply patch. When you use dd to extract the partitions, it extracts the whole thing. So, I took just the number of bytes from the dd extracted file that the applypatch uses and BOOM! Sha1 hashes match the expected for the new files. Now for the applypatch commands. Like before, I copied the files to my /sdcard and then ran:
I copied them back off the /sdcard, renamed them, and followed the standard process for creating an odin tar md5 from them. That's how I've created them and the process we can use going forward for both recovery and baseband updates. Enjoy!
Sent from my Xoom using Tapatalk 4
---------- Post added at 09:24 AM ---------- Previous post was at 08:48 AM ----------
http://www.mediafire.com/download/dtgrcyv9ux8g4u8/modem_422.tar.md5
There is a 4.2.2 baseband odin flash. It should work to downgrade the baseband in theory. It's different than the ones provided in the 4.2.2 full dump. A little explanation is in order. (Ok, so, this is going to be a long explanation with a lot of technical details.)
What I've done is rip open the update ota and look at the scripts contained within. The one I was originally looking for was how they build the recovery img. Simply put, they apply a recovery-from-boot.p to the boot.img file that's contained within the update zip. That one was fairly trivial to perform. Basically copy the boot.img and the recovery-from-boot.p to your /sdcard and run the applypatch command in a su shell to spit out the recovery.img file. The applypatch command for that looks like this:
Code:
su
cd /sdcard
applypatch boot.img recovery.img 6a1bef2e13ea3b9a4284565d560f7a2c0a17bf5d 9775360 07f4bc5b3cb20428a40d74dd0cff8a147d7155ef:recovery-from-boot.pThe baseband files were more complicated. The ones extracted from 4.2.2 and included in the 4.2.2 full dump didn't match the sha1 hash for the applypatch commands in the update-script. Here's the relevant lines from the update-script:
Code:
ui_print("Patching NON-HLOS modem image...");
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/apnhlos:9018112:de2de0523a88ce0781eb125b563ac0bb176bcb7e:9181952:c15e52d975b0b46478798a436c3feca3d4b755d7",
"-", c15e52d975b0b46478798a436c3feca3d4b755d7, 9181952,
de2de0523a88ce0781eb125b563ac0bb176bcb7e, package_extract_file("patch/NON-HLOS.bin.p"));
set_progress(0.894324);
ui_print("Patching MDM modem image...");
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/mdm:51976960:14ce52dce17261030fa5807a4d6d02b2ad061370:51944192:a43358aa04912437a98f3348a63d9bc88f3d7af4",
"-", a43358aa04912437a98f3348a63d9bc88f3d7af4, 51944192,
14ce52dce17261030fa5807a4d6d02b2ad061370, package_extract_file("patch/modem.bin.p"));So what they're doing is patching the baseband partitions with the .p patch files. Basically, what we wanted to do is apply the patch files to the extracted baseband files. But since the hashes didn't match, the applypatch wasn't going to work. Frack! Then I realized...they include a size param in the apply patch. When you use dd to extract the partitions, it extracts the whole thing. So, I took just the number of bytes from the dd extracted file that the applypatch uses and BOOM! Sha1 hashes match the expected for the new files. Now for the applypatch commands. Like before, I copied the files to my /sdcard and then ran:
Code:
su
cd /sdcard
applypatch NON-HLOS.bin NON-HLOS_43.bin c15e52d975b0b46478798a436c3feca3d4b755d7 9181952 de2de0523a88ce0781eb125b563ac0bb176bcb7e:NON-HLOS.bin.p
applypatch modem.bin modem_43.bin a43358aa04912437a98f3348a63d9bc88f3d7af4 51944192 14ce52dce17261030fa5807a4d6d02b2ad061370:modem.bin.pI copied them back off the /sdcard, renamed them, and followed the standard process for creating an odin tar md5 from them. That's how I've created them and the process we can use going forward for both recovery and baseband updates. Enjoy!
THANK YOU ALL!! I went from MG8 to MH1 without any issues!!! Will install stock recovery and try to update to 4.3 again.
YOU ARE ALL AMAZING! =)
Here's an update (without wiping!) =)
Last edited:
Here's an update (without wiping!) =)
Could you please wrap those images in HIDE tags? They're giant. Not sure if it's displaying the same on your browser, but on mine they're huge. (See attached)
4.2.2 Full Restore Package with Modem is done thanks SamuriHL I will be uploading and updating links by tomorrow
Sent from my GT-I9505G using Tapatalk 2
Sent from my GT-I9505G using Tapatalk 2
odin APNHLOS error (NON-HLOS.bin)
Hi, good time ,,,I am a home user , i have samsung j510f and upgrade this J510FXXU2BRB2 4file next flashed 1154TWRP_3.0.2_SM_J5_2016_Nougat_7.1.1 by odin And installed tis packages last year:
1154XposedInstaller_3.1.4 - Greenify-ROOT-4.0.1-Mod
it worked well but yesterday i wanted to upgrade again the mistake started from here!!! I took my mobile to the recovery mod and delet every data and reset factory from recovery mod!!!!!!!!next stoped on samsung logo!!!!
i go download mod that flash by new rom THR-J510FXXU2BRE2-J510FOJV2BRD1 4file but error APNHLOS!!!
i try many rom 4file , 1file by odin does not work and error APNHLOS!!!
next try Z3X_SAMSUNG_TOOL_PRO_29.5_Crack that did not work!!!error APNHLOS!!!
next download COMBINATION_FA60_J510FXXU2AQB2 and flash bye ODIN 307 Justttttt and only by ODIN 307!!!!!now it turns on but if try flash again warns error APNHLOS!!!
What should I do to correct?Please help me....Thank you very much
I send the results flash for you in link
Hi, good time ,,,I am a home user , i have samsung j510f and upgrade this J510FXXU2BRB2 4file next flashed 1154TWRP_3.0.2_SM_J5_2016_Nougat_7.1.1 by odin And installed tis packages last year:
1154XposedInstaller_3.1.4 - Greenify-ROOT-4.0.1-Mod
it worked well but yesterday i wanted to upgrade again the mistake started from here!!! I took my mobile to the recovery mod and delet every data and reset factory from recovery mod!!!!!!!!next stoped on samsung logo!!!!
i go download mod that flash by new rom THR-J510FXXU2BRE2-J510FOJV2BRD1 4file but error APNHLOS!!!
i try many rom 4file , 1file by odin does not work and error APNHLOS!!!
next try Z3X_SAMSUNG_TOOL_PRO_29.5_Crack that did not work!!!error APNHLOS!!!
next download COMBINATION_FA60_J510FXXU2AQB2 and flash bye ODIN 307 Justttttt and only by ODIN 307!!!!!now it turns on but if try flash again warns error APNHLOS!!!
What should I do to correct?Please help me....Thank you very much
I send the results flash for you in link
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7WE HAVE A FIX
- See this post: http://xdaforums.com/showpost.php?p=44329396&postcount=35 (Mirror for the modem here.)
- Then this post: http://xdaforums.com/showpost.php?p=44332874&postcount=54
- i9505g_mfd_stock.tar.md5 can be found here: http://xdaforums.com/showthread.php?t=2388504
Obviously, these flashes are all done at your own risk. If you break your phone, we will laugh at you. Please shower @SamuriHL with your thanks.
~~~~~~~~~~~~~~~~~~~
The other thread was beginning to become difficult to read, so let's use this as our main hub for tackling this issue.
If you flashed one of the GT-I9505G 4.3 leaks, and cannot apply the 4.3 OTA, you are probably affected by this issue. Attached is a photo of what this error looks like.
I will do my best to continually update the first two posts with up to date information.
Here are the MH1 4.3 modem files: https://mega.co.nz/#!FsozybQD!AvrykxBO2jvx7hJL8mehmBl8GohfM5HerQ73nOeTh6Y
Here are the MFD 4.2.2 modem files: https://mega.co.nz/#!SdwWnIQK!CMGuL2Q0cNSRPJKJyPTicA6sW0JykFRU8xyhdo7bWMk
Here are the mount points for the GT-I9505g:
~~~~~~~~~~~~~~~~~~~
Things we've tried to flash baseband MH1:
- Packaging NON-HLOS.bin and modem.bin in a tar and flashing with Odin. Flash errors out with a Fail(Auth) message.
- Pushing these two bins by Heimdall to the appropriate devs. Both fail. Will grab the specific error message when I get home.
- Zipping and flashing the BINs in TWRP. Flash completed successfully for me. Still shows old baseband when you reboot to system.
- DD'ing bins to appropriate devs with root ADB shell. Appears to write successfully. Still shows old baseband in About Phone menu.
- Fastboot oem lock, fastboot oem unlock, then attempting to flash the baseband
6
I just need information. I have a patched modem.bin and patched NON-HLOS.bin. I want to make an ODIN flashable file for someone to try. NOTICE I SAID TRY!!!
Whoever does this, it's going to be experimental until someone has the, uh, nerve to try flashing it.
Info I need. Which file is added to the tar first? modem.bin or NON-HLOS.bin?
---------- Post added at 11:04 PM ---------- Previous post was at 10:31 PM ----------
WARNING: This is completely untested! Flash at your OWN RISK!!!
http://www.mediafire.com/?xtp9844uj42ov58
That is my ODIN flashable modem updater for 4.3. It should bring you up to the MH1 baseband if it works. The modem.bin and NON-HLOS.bin were created from patched 4.2.2 files using applypatch...the same as what the OTA update does.
Seriously, though, I have not tested this so I really only want someone WAY more experienced in S4 land than I am to flash this. I'm not new to android by any means, but, my experience up to this point has been in Motorola land. I genuinely hope this works and if it does I'll document how I created this and the recovery img fully for everyone's amusement.5You found the right thread. You only need the recovery img from that zip. That's what I used to restore my recovery partition to stock for 4.2.2.
Sent from my Xoom using Tapatalk 4
---------- Post added at 09:24 AM ---------- Previous post was at 08:48 AM ----------
http://www.mediafire.com/download/dtgrcyv9ux8g4u8/modem_422.tar.md5
There is a 4.2.2 baseband odin flash. It should work to downgrade the baseband in theory. It's different than the ones provided in the 4.2.2 full dump. A little explanation is in order. (Ok, so, this is going to be a long explanation with a lot of technical details.)
What I've done is rip open the update ota and look at the scripts contained within. The one I was originally looking for was how they build the recovery img. Simply put, they apply a recovery-from-boot.p to the boot.img file that's contained within the update zip. That one was fairly trivial to perform. Basically copy the boot.img and the recovery-from-boot.p to your /sdcard and run the applypatch command in a su shell to spit out the recovery.img file. The applypatch command for that looks like this:
Code:su cd /sdcard applypatch boot.img recovery.img 6a1bef2e13ea3b9a4284565d560f7a2c0a17bf5d 9775360 07f4bc5b3cb20428a40d74dd0cff8a147d7155ef:recovery-from-boot.p
The baseband files were more complicated. The ones extracted from 4.2.2 and included in the 4.2.2 full dump didn't match the sha1 hash for the applypatch commands in the update-script. Here's the relevant lines from the update-script:
Code:ui_print("Patching NON-HLOS modem image..."); apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/apnhlos:9018112:de2de0523a88ce0781eb125b563ac0bb176bcb7e:9181952:c15e52d975b0b46478798a436c3feca3d4b755d7", "-", c15e52d975b0b46478798a436c3feca3d4b755d7, 9181952, de2de0523a88ce0781eb125b563ac0bb176bcb7e, package_extract_file("patch/NON-HLOS.bin.p")); set_progress(0.894324); ui_print("Patching MDM modem image..."); apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/mdm:51976960:14ce52dce17261030fa5807a4d6d02b2ad061370:51944192:a43358aa04912437a98f3348a63d9bc88f3d7af4", "-", a43358aa04912437a98f3348a63d9bc88f3d7af4, 51944192, 14ce52dce17261030fa5807a4d6d02b2ad061370, package_extract_file("patch/modem.bin.p"));
So what they're doing is patching the baseband partitions with the .p patch files. Basically, what we wanted to do is apply the patch files to the extracted baseband files. But since the hashes didn't match, the applypatch wasn't going to work. Frack! Then I realized...they include a size param in the apply patch. When you use dd to extract the partitions, it extracts the whole thing. So, I took just the number of bytes from the dd extracted file that the applypatch uses and BOOM! Sha1 hashes match the expected for the new files. Now for the applypatch commands. Like before, I copied the files to my /sdcard and then ran:
Code:su cd /sdcard applypatch NON-HLOS.bin NON-HLOS_43.bin c15e52d975b0b46478798a436c3feca3d4b755d7 9181952 de2de0523a88ce0781eb125b563ac0bb176bcb7e:NON-HLOS.bin.p applypatch modem.bin modem_43.bin a43358aa04912437a98f3348a63d9bc88f3d7af4 51944192 14ce52dce17261030fa5807a4d6d02b2ad061370:modem.bin.p
I copied them back off the /sdcard, renamed them, and followed the standard process for creating an odin tar md5 from them. That's how I've created them and the process we can use going forward for both recovery and baseband updates. Enjoy!4I just need information. I have a patched modem.bin and patched NON-HLOS.bin. I want to make an ODIN flashable file for someone to try. NOTICE I SAID TRY!!! Whoever does this, it's going to be experimental until someone has the, uh, nerve to try flashing it.
Info I need. Which file is added to the tar first? modem.bin or NON-HLOS.bin?
---------- Post added at 11:04 PM ---------- Previous post was at 10:31 PM ----------
WARNING: This is completely untested! Flash at your OWN RISK!!!
http://www.mediafire.com/?xtp9844uj42ov58
That is my ODIN flashable modem updater for 4.3. It should bring you up to the MH1 baseband if it works. The modem.bin and NON-HLOS.bin were created from patched 4.2.2 files using applypatch...the same as what the OTA update does.
Seriously, though, I have not tested this so I really only want someone WAY more experienced in S4 land than I am to flash this. I'm not new to android by any means, but, my experience up to this point has been in Motorola land. I genuinely hope this works and if it does I'll document how I created this and the recovery img fully for everyone's amusement.
Amazeballs. I flashed this via ODIN and it successfully updated my firmware (confirmed with the RootBox ROM I was running). Then I ODIN flashed i9505g_mfd_stock.tar.md5, factory reset, and rebooted into recovery. Applied the OTA zip without error. Now I'm all up and running on MH1, etc. Note: I did not need to unroot. When the OTA had finished, the SuperSU installer still came up (damn frog).
So THANK. YOU.2
Hell yeah. I'll upload the 4.2.2 modem files when I get to my laptop. I'll also teach everyone exactly what I did so people can do this on their own for future updates. I'm very glad I was able to contribute to the Samsung community!
Sent from my Xoom using Tapatalk 4 - Packaging NON-HLOS.bin and modem.bin in a tar and flashing with Odin. Flash errors out with a Fail(Auth) message.
New posts
-
-
-
Question Serenity now....been trying to adb sideload stock os to my phone
- Latest: Appreciative
-