Develop Bugs

[Q] B117 update - assert failed: apply_patch_check

Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!

Same issue updating error
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
ouzoliny said:
Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!
Click to expand...
Click to collapse

Hi there,
nope, I haven't found the way. I tried a few more time since the post, no change, still the same problem. I have posted the message on huawei support, no reply. I'm at the stage of no-trying anymore, waiting for the next update and see...
Mrpinkman said:
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
Click to expand...
Click to collapse

I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?

rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
up

rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.

extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks

i have the same problem
rutenio3 said:
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks
Click to expand...
Click to collapse
assert faild: apply_patch_check("/system/app/MyBitCast.apk". "7e89b40472e4fe3d1459fb19f02b2901f281cea9".
"01c881b5cd2aad035329684eddd0471644914bb2")
update.zip is not correct

Format Sdcard And Try Again. If It Didnt Work Download Latest B125 And Try Again Hope This Works.

Please supply more info about this fix.
extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
Please explain: what line should be erased from this file?
Thanks

rainbringer said:
Please explain: what line should be erased from this file?
Thanks
Click to expand...
Click to collapse
Yes please explain a little further. I am having update issues as well.
My Huuawei Ascend Mate MT1-U06 Found an OTA Update HwOUC, I downloaded it, and when I try to apply the update it fails.

[Q] flashing F4k's kernel

o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log

sysKin said:
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
Click to expand...
Click to collapse
What ROM are you using?
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.

TNCS said:
What ROM are you using?
Click to expand...
Click to collapse
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
TNCS said:
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
Click to expand...
Click to collapse
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
minzip: Can't create containing directory for "/system/etc/init.d/90hardlimit": Not a directory
set_perm: chown of /system/etc/init.d/90hardlimit to 0 0 failed: Not a directory
set_perm: chmod of /system/etc/init.d/90hardlimit to 755 failed: Not a directory
script aborted: set_perm: some changes failed
Click to expand...
Click to collapse
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.

sysKin said:
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
Click to expand...
Click to collapse
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.

TNCS said:
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
Click to expand...
Click to collapse
Thanks for your help TNCS. Five more posts and I'll be able to post in that thread
In the meantime I hope F4k doesn't mind a private message.

[Q] Zip flashing problems

Hi all,
I'm trying to replace the font on bubor's CM11 ROM by means of flashing one on of the ZIPs available at http://forum.xda-developers.com/goo...-fontster-betas-flashable-font-packs-t2513985
I am using bubor's TWRP v2.7.1.
The problem I first encountered when trying to flash a font was the error message "Error executing updater binary" and thus the flashing "Failed". Based on the advice at http://forum.xda-developers.com/showthread.php?t=2290009 , I figured it would probably be a good idea to replace the update-binary with the one found in my ROM's ZIP, so I did that.
However, the ZIP still doesn't flash. Although I no longer get the "Error executing updater binary" message, now TWRP simply tells me "Error flashing zip" without offering me any explanation.
Please can you help with this, and apologies for the noob question. I have tried installing the ZIP from both internal and external SD. My SD's are swapped - could that have something to do with it?

- downlaoded http://www.mediafire.com/download/40x5qm44a24p0dg/CantarellFontPack.zip
- downlaoded http://dualhoki.vim.hu/bubor/dev/keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.

bubor said:
- downlaoded /CantarellFontPack.zip
- downlaoded keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
Click to expand...
Click to collapse
I'm sorry for not being detailed enough.
I tried following your steps but unfortunately the flashing still failed. I eventually got it to work after a combination of actions, but I think the most crucial one was changing the write permissions of the \system\fonts folder from "drwxr-xr-x" to "drwxrwxrwx".
Thanks for your efforts in any case, I really appreciate all the work you're doing.

October Security OTA won't install on rooted Nexus 5x with stock Android 7.0

Hello. When I bought my Nexus 5X, it had Android Marshmallow on it. I immediately rooted it and flashed TWRP using the Nexus Root Toolkit (NRT) and it went well.
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted) I was able to go through the update successfully with that current setup. Of course I had to re-root my phone after that.
But the 46.7MB October Security Update won't install via OTA. I've tried:
re-rooting it with the latest TWRP (via NRT)
re-flashing the stock recovery (via NRT)
but the OTA still wouldn't get installed. I checked the recovery log and it showed this line:
Code:
installing lge.bullhead updater extensions
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
script aborted: E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
E:unknown command [log]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
But I checked the build.prop file and found this:
Code:
ro.build.desciption
google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Where could that google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys have come from? How do I proceed with the OTA? I've yet to try FlashFire because it won't detect the downloaded OTA file and I've yet to download that 1.2GB factory OTA file.
Also why only now am I having problems with OTA? It should have happened during the Android 7.0 update, right? I would like it very much if I could do this without wiping my data. Please help. Thank you.

d4ryl3 said:
Hello. When I bought my Nexus 5X, it had Android Marshmallow on it. I immediately rooted it and flashed TWRP using the Nexus Root Toolkit (NRT) and it went well.
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted) I was able to go through the update successfully with that current setup. Of course I had to re-root my phone after that.
But the 46.7MB October Security Update won't install via OTA. I've tried:
re-rooting it with the latest TWRP (via NRT)
re-flashing the stock recovery (via NRT)
but the OTA still wouldn't get installed. I checked the recovery log and it showed this line:
Code:
installing lge.bullhead updater extensions
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
script aborted: E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
Source: google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Target: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Verifying current system...
E3001: Package expects build fingerprint of google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys or google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys; this device has google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys.
E:unknown command [log]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
But I checked the build.prop file and found this:
Code:
ro.build.desciption
google/bullhead/bullhead:7.0/NRD90R/3141966:user/release-keys
Where could that google/bullhead/bullhead:6.0.1/MMB29Q/2480792:user/release-keys have come from? How do I proceed with the OTA? I've yet to try FlashFire because it won't detect the downloaded OTA file and I've yet to download that 1.2GB factory OTA file.
Also why only now am I having problems with OTA? It should have happened during the Android 7.0 update, right? I would like it very much if I could do this without wiping my data. Please help. Thank you.
Click to expand...
Click to collapse
The update will fail because you have modified /system. Update using NRT then apply root. I don't use that tool so that's up to you to figure out.
Alternatively, update using fastboot and reflash root afterwards. Follow the guide below:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

d4ryl3 said:
Along came the Android 7.0 OTA and I only had to remove the saved fingerprints and PIN (to make TWRP see the phone as decrypted)
Click to expand...
Click to collapse
BTW you didn't "decrypt" the phone. It was still encrypted. You just changed the password used to encrypt the storage of the unique encryption "keys", that were used to encrypt your phone, to "default_password", which TWRP knows about and can try automatically to retrieve your encryption keys.

SlimSnoopOS said:
The update will fail because you have modified /system. Update using NRT then apply root. I don't use that tool so that's up to you to figure out.
Alternatively, update using fastboot and reflash root afterwards. Follow the guide below:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I went away and
Downloaded the OTA zip file
Installed the Android SDK tools, connected my device and rebooted it into TWRP
Then went to Advanced -> ADB Sideload
Then from the command prompt, typed "adb sideload /path/to/OTA/zip/file" and hit enter
It took a few minutes to 100%, then I rebooted my phone and all is well and updated now.
Thank you so much for redirecting me to the proper solution.

sfhub said:
BTW you didn't "decrypt" the phone. It was still encrypted. You just changed the password used to encrypt the storage of the unique encryption "keys", that were used to encrypt your phone, to "default_password", which TWRP knows about and can try automatically to retrieve your encryption keys.
Click to expand...
Click to collapse
Oh, all right. Thanks for the clarification and duly noted. :good:

d4ryl3 said:
I went away and
[*]Downloaded the OTA zip file
Click to expand...
Click to collapse
Can you share the link for NRD90R>NBD90W, I'm still stuck on NRD90R and don't want to flash the full OTA (I don't want to flash full image every month and run down the flash rewrites).

MarvinOl said:
Can you share the link for NRD90R>NBD90W, I'm still stuck on NRD90R and don't want to flash the full OTA (I don't want to flash full image every month and run down the flash rewrites).
Click to expand...
Click to collapse
Sorry for not being clear, but I used thr whole 1.2GB OTA zip file for this.
Was also wondering if there's a simpler way of doing this considering the October update was just ~46MB.

Offical update to Nougat for N920A step by step. Enjoy !!!!

From The Moderator Oka1 - There are no viable links in this OP therefore, I am closing
Thanks
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC6. 1.41 GB file seems to me like nougat update.
Nougat Update Here S4CQB2-to-U4EQC6
MD5 checksum : 903aa5c5f26f430133481c4a2cfcdb69
Thanks for ABD instruction @ColoMtn
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC6-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
For who may need it this is S4CQA1 to U4QC6 update. File is around 1.5 GB and MD5 is 23d4d4c58330b618001e76fc468732d9

Congratulations! Hopefully 928a will have it soon

vista1984 said:
Congratulations! Hopefully 928a will have it soon
Click to expand...
Click to collapse
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.

I just wanted to thank you for this, going to do it now!!!! This day keeps getting better and better!!!!!

norbarb said:
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC5. 1.41 GB file seems to me like nougat update.
Nougat Update Here
Thanks for ABD instruction @ColoMtn
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC5.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC5.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC5.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
Can anyone show a screen shot of the "About Device" section of the phone settings after applying this update? Thank you in advance!

Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.

ifanr said:
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.

norbarb said:
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
Click to expand...
Click to collapse
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.

ifanr said:
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
Click to expand...
Click to collapse
I post it MD5 in first post.

norbarb said:
I post it MD5 in first post.
Click to expand...
Click to collapse
Matched.I'll try some other ways to work it out.Tks.

ifanr said:
Matched.I'll try some other ways to work it out.Tks.
Click to expand...
Click to collapse
You may try removing .zip extension and try again. Sometimes works

i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip

jerrycoffman45 said:
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
Click to expand...
Click to collapse
Two resons :
1. corrupted file
2. file in wrong place

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
I post it link to raw file try other one or re-download.

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
jerrycoffman45 said:
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
Click to expand...
Click to collapse
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.

norbarb said:
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
Click to expand...
Click to collapse
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.

ifanr said:
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
Click to expand...
Click to collapse
ALL WHO TRY PLEASE STOP. Seems like uploaded file got corrupted. I'm uploading once more

norbarb said:
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
Click to expand...
Click to collapse
It's very thoughtful of you. If you have time please post it at your convenience.