Database Info

[HELP] HTC on e8sd MM update install ERROR

hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic

Might be due to bad zip file! Download the update again and try!

Kianush said:
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Click to expand...
Click to collapse
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.

generalugh28 said:
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
Click to expand...
Click to collapse
thank you for the information, but as I mentioned in op my phone is already all stock, I havent ever moded or rooted or anything, it's stock locked bootloader

Have the exact same issue. My device is compelitely stock. Tried flashing the recovery from the downloaded OTA but still got the sama error. Hopefully someone will be able to resolve the issue.

if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.

@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.

sam5154 said:
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
Click to expand...
Click to collapse
Hi, thanks for this. I will try this once i got home.
But i have one questions, mine is Vietnam MEC_DUGL with stock lollipop 5.0.2. The RUU only available for stock lollipop 5.0.1. Can I use this RUU or should I look for specific RUU for lollipop 5.02?
Thanks!

Kianush said:
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
Click to expand...
Click to collapse
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.

sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else

Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Have you tried the suggestion above? Let me know the result! Thanks man

sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??

Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Kianush said:
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Click to expand...
Click to collapse
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html

bataskhayal said:
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
Click to expand...
Click to collapse
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!

Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Yes bos, i also did the recovery trick but still cant make it work. So the only solution we havent try is to flash RUU which i doubt also will make it work since my phone also factory stock. So i guess will stay in 5.0.2 for a while.

Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Hi, I have managed to finally update my Vietnam HTC One E8 dual SIM (MEC_DUGL) to Android 6.0. The problem that cause the error is the error recovery file, hence I re-install the RUU to get the correct recovery.img file. Below are the steps :
Note : Try with your own risk
1. My device is currently stock 5.0.2 no root and locked. Before starting the update process please make sure to backup all of your important data. Im using the stock HTC backup software, when you restore your device after you finished your update process, it will re-install your currently installed apps , contacts, settings, etc.
2. Download RUU for your device here : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I downloaded :
[Vietnam][DUAL][M8sd][mec_dugl][CID HTC__059][OPAJ20000] :
[Lollipop 5.0.1][2.35.425.2] : LINK
Seems not match with my current software (5.0.2), but eventually it will do the magic.
3. Flash RUU. NOTE : You will lose all of your data in your internal phone memory. Make sure to backup all of your important files.
Steps:
1) Download RUU.
2) Rename RUU to 0PAJIMG.zip (the first character is a zero, NOT A LETTER O)
3) Put renamed 0PAJIMG.zip on your external_SD
4) Boot into your bootloader and make sure your in hboot and let it update its RUU.
5) No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed RUU file to external_sd
6) After you have updated your RUU, make sure to remove the 0PAJIMG.zip from your external_sd because it will ask to update your RUU everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing RUU again).
7) Done!
Source : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
4. Reboot your phone, now your phone is back to factory stock, connect it to wifi, no need to set up any account, just go directly to software update from Settings > About > Software Updates. Just install all the available software updates (5.0.2 > 6.0 part 1 > 6.0 part 2).
5. BOOM! Your HTC One E8 now runs Android 6.0.1 Marshmallow.
6. Restore your phone from the stock HTC Backup Software.
7. Done

Unroot and relock bootloader to install ota updates ?

Dear members
I want to update my rooted E6633 running 32.2.A.0.376 to 32.4.A.0.160 through the OTA, of course, because my device is already rooted the downloaded update couldn't be installed, the reason behind seeking for this update that I'm not able to make phone call and the phone is not able to detect the SIM cards and showing pop up error message android.phone.com has stopped repeatedly whenever I press ok and phone app crashes.
what I have done so far is through superus app I chose full unroot and the phone rebooted successfully and I have checked it with the root checker showing that the root is not installed properly
I launched the flashtool and booted the device on flashmood and selected the bootloader relock option
flashtool said that bootloader finished relocking the device, but the device is not able to boot to the normal mood whenever I push the power on button the device only vibrate or boots to flashmood when the cable is connected but when unlocking the bootloader, the device boots normally.
How to update my device without losing my current data and to fix phone application and SIMs recognition?
Do I have to fastboot the original Sony kernel and where can I find it? because I didn't make any backup
I don't mind losing root I just want to make the OTA update installed without flashing my phone and starting from the beginning.
Thank you
Notes: when the device is rooted again and when opening luckyputcher the error messages disappear and SIMs cards work fine and phone app opens normally

I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)

Dna10 said:
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Click to expand...
Click to collapse
Thanks for your reply, not limited bandwidth but slow connection that one of the reasons, if I could extract the kernel from the firmware and flashing it without losing the data and allowing ota to be installed this will be great. Hopefully this way fixes the system errors and keeping the data and settings as it is.
Thanks again I will start following these guidelines if something went wrong surely I will sue you :laugh:

Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?

kingskull said:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
Click to expand...
Click to collapse
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::

Dna10 said:
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Click to expand...
Click to collapse
I was not sure about flashing the whole ftf, I was worried if I flashed the the new 160 would cause the system to break down, so I decided to unroot and to keep my self on the safe side by unrooting, relocking bootloader and installing the stock kernel so that I will be able to update to the .160 fw through OTA
I will follow your instruction about flashing the .367 fw. I was thinking about it but I wasn't sure which options that should I select without losing the data. Should I select the whole options except the wipe section?
Thanks for your help

Don't select anything! It should look like in the screenshot I uploaded

Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Hmmm yesterday before posting my last reply I flashed the firmware I only selected the kernel and nothing happened, no changes happened to the firmware except the ota size was reduced from 485mb to 187mb !?
Oh dear according to the screenshot you uploaded the ftf I downloaded is for middle east and I'm from Saudi Arabia never thought there is custom firmware for Saudi Arabia do you think that the reasone behind this boot failure is because of the difference between the installed firmware and the downloaded one?

It shouldn't pose any problems at all. Any problem arising might be of your doing. What you could do is make a Titanium Backup of your user apps and go for clean install if your problems persist.

Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Ok that's great, after flashing the ftf the device boot normally but the bloody ass error still persist I can't make or receive phone calls the phone app is crashing, of course, since the root is not available luckypatcher will not solve the problem and to be honest I don't know what is the relation between this error and luckypatcher.
The funny thing after the process succeed the phone showing that the software is up to date man !!
more than that when checking software update settings app crashes
I really want to thank you for helping me, I really appreciate it :good:
my last option is downloading 160 fw and flashing it

Have you tried a different dialier app?

First Lock Bootloader Then Flash FTF File.

Need help with Odin, cannot return to stock :(

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try

GODSPD said:
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Click to expand...
Click to collapse
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk

Droidriven said:
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...

GODSPD said:
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
Click to expand...
Click to collapse
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk

Droidriven said:
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
Thanks for the feedback.
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...

GODSPD said:
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
Click to expand...
Click to collapse
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
more than you can imagine, every possible wipe and combination has been done with no luck at all

GODSPD said:
more than you can imagine, every possible wipe and combination has been done with no luck at all
Click to expand...
Click to collapse
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That definitely makes sense that i cannot downgrade but i am flashing either the same firmware or slightly newer staying on the same bootloader version.

Recover data from a J700M blocked by FAP Lock

Hi, my phone has get the message "Custom binary blocked by FAP Lock"
And before flashing the firmware, I want to recover so much important files that I have in the device.
There's a method for recover the files in Download Mode or something?
Please, that happened six days ago and I really need this data.
Thanks so much.

LucasCordoba said:
Hi, my phone has get the message "Custom binary blocked by FAP Lock"
And before flashing the firmware, I want to recover so much important files that I have in the device.
There's a method for recover the files in Download Mode or something?
Please, that happened six days ago and I really need this data.
Thanks so much.
Click to expand...
Click to collapse
No, you can not recover the data via download mode, download mode can only be used to flash the device.
You need to download the full stock firmware for your model number and flash it via Odin but when you flash it, if there are two different CSC files that can be used when you flash it, use the one that does not wipe user data during flashing then you will have access to your data once the device boots properly.
If you know or can find out what the build number is for the stock firmware that was on the device before you tried to modify it, you need to flash that exact build number.
If you flash something that is newer than the stock firmware that was already on the device, it might have an upgraded bootloader which means it would wipe your data when you flash that firmware.
If you are very careful in choosing the exact same firmware that you already had on the device and if you use the CSC file that does not wipe the user data, you can achieve what you are trying to do, but if you choose the wrong firmware, you will probably lose your data.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
No, you can not recover the data via download mode, downloaded mode can only be used to flash the device.
You need to download the full stock firmware for your model number and flash it via Odin but when you flash it, if there are two different CSC files that can be used when you flash it, use the one that does not wipe user data during flashing then you will have access to your data once the device boots properly.
If you know or can find out what the build number is for the stock firmware that was on the device before you tried to modify it, you need to flash that exact build number.
If you flash something that is newer than the stock firmware that was already on the device, it might have an upgraded bootloader which means it would wipe your data when you flash that firmware.
If you are very careful in choosing the exact same firmware that you already had on the device and if you use the CSC file that does not wipe the user data, you can achieve what you are trying to do, but if you choose the wrong firmware, you will probably lose your data.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you so much for your help!

Combination Firmware - A10 A105FNXXU2ASF4

Hi All,
I have a A10 work phone that was returned by a employee and didnt remove the accounts etc before leaving. its been wiped but has the FRP issue.
I'm trying to find a working combination file to wipe the device via ODIN and then reinstall the stock firmware. The combination files ived tried all fail with re-partition failed.
When i go into the recovery menu the firmware is A105FNXXU2ASF4
Could anyone help with the correct combination file or anything else I'm missing.
Cheers

aIecxs said:
flashing combination ROM all newer Samsung devices will run into error "Please get the approval to use factory binary". you need to buy Etoken via Halabtech or bypass with similar service
Click to expand...
Click to collapse