Bootloader and root for ASUS_Z01GS version (OPR1.170623.032.WW_Phone-15.0410.1803.51) - Asus ZenFone 4 Pro Questions & Answers

I just bought a new Zenfone 4 Pro (much cheaper than the 5Z and better than the other 5s).
It's an ASUS_Z01GS, not an ASUS_Z01DS, which is strange, since all the support sites have firmware with Z01DG in the filenames.
Its firmware version is OPR1.170623.032.WW_Phone-15.0410.1803.51 (that's the one it came with) and there are no OTA updates.
Its Android version is 8.0.0.
I have tried using ASUS's official unlock tool to enable bootloader (v 9.1.0.0 and 9.1.0.3), however, both failed.
I've tried various rooting utils (TunesGo, KingRoot, KingoRoot), however, these failed too.
Is there anyway to root this phone (the GS model with the firmware I have).
Thanks.

Related

Can you flash a cheap tablet w/ custom firmware to an official android firmware?

I got a cheap Dragon x10 2017. Its stock with Android 7 however it runs a custom firmware and that's created an issue with NordVPN and its kill switch. It does not have a locked boot loader so flashing it should be easy enough. However i'm new to flashing and i'm not sure if you can even get official firmware builds that will work on an off brand tablet. Thoughts?

Unlock bootloader confusion

Hey Guys,
I have been googling for a while now and I seem to constantly come across conflicting and at times worrying posts which has very much left me stuck right were I am. I just recently purchased a Mate 9 in the hope I would be able to, like all my previous mobiles install a custom rom and tweak it to my specific needs. This however hasn't been the case.
Firmware:
System 8.0.0.046
Dataver MHA-L09 8.0.0.371(C34)
Things that have been tried:
1. No I didn't get a boot unlocker code from the Huawei
2. Yes I have contacted them personally via two different channels and both returned with a we are happy to give it to you, that's not an issue, but this code doesn't exist anymore.
3. DC-Unlock tool didn't detect my mobile in manufacture mode, in which I found another forum post stating to use HCU 3.22 client instead which worked to the point of detecting my mobile, but told me that the current security patch not supported.
4. Contacting DC-Unlock, told me there is no ETA on getting this patch level to work
5. I have read people downgrading to a previous version, unlocking and then installed the custom rom via HiSuite, this doesn't give me that option.
6. I have read people downgrading to a previous version, unlocking and then installed the custom rom via firmware finder.
6.1 Issues with this is that I seen someone claim to upgrade to version 8.0.0.3.75, which is higher then mine, which enabled the rollback feature, is this correct?
6.2 Issues with this is that I have read that gpu turbo has been enabled and many have warned that rolling back to a pre-gpu turbo enabled firmware will brick you mobile and would result in a motherboard needing to be replaced for nearly the cost of the mobile itself.
I am tempted to try another site which I can't remember the name of, which if you pay considerably more then DC-Unlock. at least if they can't get the code, would be refunded. but I think that site is down now as I feel they were playing on people who didn't know how to have done it for free via the Huawei site back in 2018.
So I want to know is there a safe way to unlock my bootloader I think my only option is option 6 but just want more details from others who have done it this way before, or have I pretty much exhausted all my option and just bite the bullet and upgrade to 9.0.1.187 and possibly further through the OTA update process and just enjoy the mobile for what it is and it's limitations?
Thanks again.
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
mucski said:
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
Click to expand...
Click to collapse
Thanks for that, I can already upgrade to 9, my system updates app is just waiting for me to accept. The issue is that I don't want to go forward. I really want to go backwards, so I can unlock my bootloader first. I'm already at the stage where I have tried most if not all the safe ways to unlocking my bootloader, but with my currently installed android version I can't. The only way forward for me it seems is the firmware finder app and SD force flash back to EMUI 5 aka Android 7 to use DC-Unlocker to unlock it first, then that gives me the freedom of installing the official Android 9 or openkirin.
I just worried as some people have stated that if you attempt a downgrade after a specific point, something about GPU turbo being enabled in later firmwares, which will brick your mobile.
I just want to hear from others who have done this successfully or if it's not possible in my case.

[Resolved] #Solved# Any Possible Solution to Downgrade Back to Nougat?

Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk

[Help] Flash Stock Rom HONOR 6X

Hello guys, can somebody help me?
I own a Honor 6x (BLN-TL10)
When I bought at 2017, I flashed my firmware to a different one cause I didn't wanted to use the chinese version, so I upgraded or downgraded to that firmware (BLN-C900B131) since that change, my device always recognize as hi6250, and when I try to install the original firmware on my device, It fails, on the update proccess appear that message, "Software install failed! Incompatibility with current version." cause I want to upgrade to 8.0 oreo, my phone right now is at android 6.0 emui 4.1.
Can you send the link of update file that you have used? And a screenshot of build number?
I'll attach 3 screenshoots, one of my EMUI and Android at the moment and the firmware's that I tried to install
The BLN-TL10 firmware that was the same that came with my phone when I bought
I've tried to unlock the bootloader, but Huawei phones bought on china doesn't have OEM unlock option enabled ;(
Idk if have some way to unlock bootloader without that option

Ok Guys, I need you. Downgrade Emui or Modify all android.

Hello guys !!
How are you today? because im ultra fine like all the days.
Well, i want to ask you if you can help me with this problem;
I Have a Smartphone Huawei, model "Mate 9 (MHA-09)", with Bootloader Locked, system Emui 9.1 = Android 9, FRP Unlocked.
For me, my 2 solutions are:
" Downgrade Emui 9.1 to Emui 9.0, then, to Emui 8, and finally, to unlock bootloader whit DC-Unlocker"
" Or change all the system with root, like the launcher, the notification panel, menu, etc"
I read about:
° HuRupdater
° Upgrade / Downgrade by SD Card With Dload
° Downgrade With Hi Suite 9.0 or 5.0 with FunkyHuawei
° Install TWRP whit NoChek
° Firmware Finder
° DC- Unlocker
° Xloader
° Update With SD 16Gb and not 32Gb
and i try, and i try.
and thats why i am here, i still can´t find those solutions, and i need help.
Can you help me please?
PatadaVoladora! said:
Hello guys !!
How are you today? because im ultra fine like all the days.
Well, i want to ask you if you can help me with this problem;
I Have a Smartphone Huawei, model "Mate 9 (MHA-09)", with Bootloader Locked, system Emui 9.1 = Android 9, FRP Unlocked.
For me, my 2 solutions are:
" Downgrade Emui 9.1 to Emui 9.0, then, to Emui 8, and finally, to unlock bootloader whit DC-Unlocker"
" Or change all the system with root, like the launcher, the notification panel, menu, etc"
I read about:
° HuRupdater
° Upgrade / Downgrade by SD Card With Dload
° Downgrade With Hi Suite 9.0 or 5.0 with FunkyHuawei
° Install TWRP whit NoChek
° Firmware Finder
° DC- Unlocker
° Xloader
° Update With SD 16Gb and not 32Gb
and i try, and i try.
and thats why i am here, i still can´t find those solutions, and i need help.
Can you help me please?
Click to expand...
Click to collapse
You can downgrade simply by HiSuite, see discussion (check also the earlier posts):
https://forum.xda-developers.com/showpost.php?p=80889343&postcount=3
That way you can go down to EMUI 8 but not earlier than to the firmwares with Security patch 07/2018 or later
And you cannot (and must not - people hardly bricked various Huawei phones, not just Mate 9) roll-back further because at that time Huawei changed the Bootloader
It actually means that you cannot go back to be 'able' to use old/good DC Unlocker - instead of DC Unlocker you will have bricked device that can only be repaired by Testpoints method
Also, only by Testpoints method you can rollback to Oreo, Security patch 06/2018 or earlier, that you can then unlock by DC Unlocker.
It was discussed in one of the threads here for Mate 9, about two months ago - please search
It was also asked and answered in another Mate 9 thread (during the last month or so - please search, you will find) about the available options to unlock Bootloader - but all goes down to the Testpoints, and some costs (to Halabtech, HCU or a particular Telegram group) that are about 30 Euros or more
Only those who never upgraded over Oreo firmwares with Security patch 06/2018 (that is, who still have the older Bootloader) can simply unlock the Bootloader with DC Unlocker for about 4 Euros ;-(
zgfg said:
You can downgrade simply by HiSuite, see discussion (check also the earlier posts):
https://forum.xda-developers.com/showpost.php?p=80889343&postcount=3
That way you can go down to EMUI 8 but not earlier than to the firmwares with Security patch 07/2018 or later
And you cannot (and must not - people hardly bricked various Huawei phones, not just Mate 9) roll-back further because at that time Huawei changed the Bootloader
It actually means that you cannot go back to be 'able' to use old/good DC Unlocker - instead of DC Unlocker you will have bricked device that can only be repaired by Testpoints method
Also, only by Testpoints method you can rollback to Oreo, Security patch 06/2018 or earlier, that you can then unlock by DC Unlocker.
It was discussed in one of the threads here for Mate 9, about two months ago - please search
It was also asked and answered in another Mate 9 thread (during the last month or so - please search, you will find) about the available options to unlock Bootloader - but all goes down to the Testpoints, and some costs (to Halabtech, HCU or a particular Telegram group) that are about 30 Euros or more
Only those who never upgraded over Oreo firmwares with Security patch 06/2018 (that is, who still have the older Bootloader) can simply unlock the Bootloader with DC Unlocker for about 4 Euros ;-(
Click to expand...
Click to collapse
Hello mate.
I had tried before posting, but it didn't work.
So far the temporary solution I found (which I also tried for Dload and Hi suite, and it did not work, maybe I am wrong) is to perform a Downgrade from Emui 9.1 to 9.0, then you can perform a Downgrade to Emui 8.0. (but it is not possible to do it directly from 9.1 to 8.0)
I have an information puzzle, I still can't get to Emui 8, I keep reading, trying, buy 4 credits in DC, and surprise, they can't unlock it, and I already tried so hard, for so long that I'm seeing if I already sell Huawei, and I add it to my friends list "Never Buy again"
as ise with LG, Samsung, Xiaomi.
It is frustrating, he became a dictator huawei with his Sisteman "Emui" with which I can not even clean my quiet ass without bothering with his updates
PatadaVoladora! said:
Hello mate.
I had tried before posting, but it didn't work.
So far the temporary solution I found (which I also tried for Dload and Hi suite, and it did not work, maybe I am wrong) is to perform a Downgrade from Emui 9.1 to 9.0, then you can perform a Downgrade to Emui 8.0. (but it is not possible to do it directly from 9.1 to 8.0)
I have an information puzzle, I still can't get to Emui 8, I keep reading, trying, buy 4 credits in DC, and surprise, they can't unlock it, and I already tried so hard, for so long that I'm seeing if I already sell Huawei, and I add it to my friends list "Never Buy again"
as ise with LG, Samsung, Xiaomi.
It is frustrating, he became a dictator huawei with his Sisteman "Emui" with which I can not even clean my quiet ass without bothering with his updates
Click to expand...
Click to collapse
Yes, exactly as in my post you cited. You downgraded from 9.1 to 9.0, then from 9.0 to 8.0, but you are still with the newer 8.0 sharing the same new Bootloader as 9.0 or 9.1 - the same new Bootloader that cannot be unlocked for 4 EUR.
You would have to downgrade further, to the older 8.0 firmwares (before GPU Turbo and/or earlier than Security Patch 06/2018 - they usually correspond to the jump from the old xloader to the new one).
But such downgrading is not possible by e.g. HiSuite, and if you enforce it by DLOAD, you would jump to the band wagon with several other users of various Huawei devices who similarly wanted to 'cheat' - but instead of unlocking Bootloaders for the cheap 4 EUR, they hard-bricked their phones.
There is only one method to downgrade to that old xloader.img - TestPoints: it requires to open the phone, to shorten pins on the TestPoints at motherboard and then to use a special loader and driver by Huawei to flash the board image. You may have problems to restore IMEI(s).
If you are interested about, search on XDA and outside, you will find the guides.
Actually, there were even instructions here (not very detailed - requiring further research for resources), under the Mate 9, Q/A or Guides section (e.g., I remember that I have asked for how-to at late Aug or early Sep, got a short answer but I never pursued to try it on my own)
E.g., attached is a photo of TestPoints pins for Mate 9
finally, I have the solution
zgfg said:
Yes, exactly as in my post you cited. You downgraded from 9.1 to 9.0, then from 9.0 to 8.0, but you are still with the newer 8.0 sharing the same new Bootloader as 9.0 or 9.1 - the same new Bootloader that cannot be unlocked for 4 EUR.
You would have to downgrade further, to the older 8.0 firmwares (before GPU Turbo and/or earlier than Security Patch 06/2018 - they usually correspond to the jump from the old xloader to the new one).
But such downgrading is not possible by e.g. HiSuite, and if you enforce it by DLOAD, you would jump to the band wagon with several other users of various Huawei devices who similarly wanted to 'cheat' - but instead of unlocking Bootloaders for the cheap 4 EUR, they hard-bricked their phones.
There is only one method to downgrade to that old xloader.img - TestPoints: it requires to open the phone, to shorten pins on the TestPoints at motherboard and then to use a special loader and driver by Huawei to flash the board image. You may have problems to restore IMEI(s).
If you are interested about, search on XDA and outside, you will find the guides.
Actually, there were even instructions here (not very detailed - requiring further research for resources), under the Mate 9, Q/A or Guides section (e.g., I remember that I have asked for how-to at late Aug or early Sep, got a short answer but I never pursued to try it on my own)
E.g., attached is a photo of TestPoints pins for Mate 9
Click to expand...
Click to collapse
Men, thanks for the answer, and sharing your time.
Well,
Finally, I found the solution that I wanted to apply a long time ago.
Which one?
simple; Take the cell phone, sell it and send the **** to Huawei.

Categories

Resources