Database Develop

[GUIDE][ALE-L21][ALE-L02] Debrand, upgrade, downgrade and/or convert to dualsim

----------------------------------------------------
I'm kinda busy at my life and won't be able to answer your questions...you can still ask here and hope someone else will reply, or post at the other similar thread - MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed
----------------------------------------------------
Debranding is easy once you find infos how to do it...sadly there's nothing in english. I used a combination of Google Translate + some spanish/italian/polish sites and howto's for other Huawei models to convert my branded single sim ALE-L21 from C150B130 to dual sim C432B188.
Here's how i did it...proceed at your own risk. Don't forget to make a backup because you'll lose your data. Also, your warranty will be void.
Please look at the Q&A section at end of the post; feel free to ask me if something isn't answered, but be prepared for an answer like "flash it again" because that's my first Huawei phone and i own it just for a week...i'm more of a Google Nexus guy.
----------------------------------------------------
Part 1: Unlocking bootloader
Stuff you'll need:
- Model number inside "Settings > About phone"
- Serial number inside "Settings > About phone > Status"
- IMEI inside "Settings > About phone > Status" (write down the first one if you have two of them)
- Product ID by opening dialer and typing *#*#1357946#*#*
- "Updated Step by Step guide to Root P8 lite.pdf" file - http://forum.xda-developers.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616
- Minimal ADB and Fastboot from unlocking bootloader pdf
First you'll need to get your bootloader unlocking code:
1. Go to http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=list and click "Unlock Bootloader"
2. Register a Huawei ID account, repeat step 1, login and click "Unlock Bootloader" again; accept the terms and click Next
3. Enter your phone data and Press Submit; wait a little for the code to show up and save it somewhere safe in case you'll need it someday
Then you'll need to unlock your bootloader:
1. Open "Updated Step by Step guide to Root P8 lite.pdf" and do just step B
Like i said many times in replies/pm's - if you didn't do anything of this, your bootloader is still locked. Doesn't matter if it says unlocked.
-----------------------------------------
Want to go back from 6.0 to 5.01? Read Q&A first, there's a special procedure for that. If you do it directly, you'll lose your imei!
Part 2: Flashing the unbranded firmware
Stuff you'll need:
- Minimal ADB and Fastboot from last part
- C432B132 Europe dual sim firmware - http://carbontesla.com/2015/09/download-huawei-p8-lite-b132-firmware-dual-sim
- Huawei Update Extractor - http://forum.xda-developers.com/showthread.php?t=2433454
First we need to get img files out of Huawei's update.app:
1. Extract the firmware; you should have a folder with dload and CUSTOM
2. Open Huawei Update Extractor as administrator (otherwise you won't be able to extract directly into adb folder), browse (button with two dots) to dload folder from step 1 and open UPDATE.APP
3. Hold Ctrl and select BOOT.IMG, CUST.IMG, RECOVERY.IMG and SYSTEM.IMG; release Ctrl, right click on any marked file, click "Extract Selected" and find your ADB folder (should be "C:\Program Files (x86)\Minimal ADB and Fastboot" or "C:\Program Files\Minimal ADB and Fastboot")
Now the most fun and...ehm...most "dangerous" thing - flashing the files:
1. Do B 2, 3, 4, 5, 6 and 7 from unlocking bootloader pdf file (to boot your phone into fastboot mode and get a cmd window with the right starting location)
2. Type:
Code:
fastboot flash system system.img
press enter and wait until finish...it will take some time
Code:
fastboot flash recovery recovery.img
press enter and wait
Code:
fastboot flash boot boot.img
enter and wait again
Code:
fastboot flash cust cust.img
enter and wait
Code:
fastboot reboot
and enter to reboot your phone
You may think that's the end...let me tell you - it's not. Your phone booted into an ugly version of EMUI with funny icons and "Settings > About phone" Build number says BalongC**B*** instead of the flashed ALE-L21C432B132. Let's fix that.
Fixing balong "bug" - this will cause a factory reset...i hope you made a backup:
1. Remember CUSTOM folder from extracted firmware? Copy it on your phone's internal storage or sdcard
2. Rename CUSTOM to dload
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots
4. Go to "Settings > About phone" and check if it says the right build number (should be ALE-L21C432B132); if it's not, repeat the img file flashing process
-----------------------------------------
DON'T OTA if you're rooted!
Part 3: Getting the latest firmware update (B200) via OTA and (optionally) manually updating to MM B560
a. Getting the latest firmware:
1. Open Updater app, tap Check for updates and install it
2. Repeat step 1 until it says No updates; now you should be on B200
b. Update to MM (6.0):
1. Download C432B560
2. Extract it and copy the dload folder on your phone's internal memory or sd card.
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots.
4. Go to "Settings > About phone" and check if it says the right build number (ALE-L21C432B560)
----------------------------------------------------
Q&A:
Q: I have a ALE-L04 or something else. Can i still do what you wrote?
A: Don't even try because you'll brick your phone. ALE-L04 for example got a totally different chipset (Qualcomm Snapdragon 615) than ALE-L21 (HiSilicon Kirin 620).
Q: What's the difference between ALE-L21 and ALE-L02? Will there be any benefits or disadvantages after changing from L02 to L21?
A: L02 doesn't support some LTE frequencies and NFC; detailed specs: ALE-L02, ALE-L21. There will be no benefits or disadvantages after flashing a L21 rom; everything will be the same, except a different model and build number.
Q: Are there any other uses for this, except for debranding and converting to dual sim?
A: Yes, you can basically use it for everything from upgrading and downgrading firmwares, fixing your bricked phone (if you still can access Fastboot mode) and more.
Q: I don't want dual sim. Why should i flash it?
A: Because why not? You get a bonus functionality and you won't lose anything even if you never intend to use it - you can still use just one sim and a sdcard without any problems. Huawei also planned P8lite to be a dual sim phone, so it's possible you'll get updates faster than people with the single sim variant.
Q: I don't live in Europe. Why should i flash that firmware?
A: Well, you can always find an appropriate firmware on carbontesla website, but be prepared you won't be able to fix the balong bug. Only a few firmware packs include the vendor patch (CUSTOM folder).
Q: Huawei Update Extractor gives me errors why i try to extract img's. What should i do?
A: You didn't listen and didn't run it as administrator. One workaround would be extracting the img's somewhere else (for example new folder on desktop) and then copy/paste them into adb folder. Do as you wish.
Q: I get errors when i type "fastboot flash xxxxx xxxxx.img". What should i do?
A: First look if you typed it correctly, then check if you have the right files - BOOT.IMG, CUST.IMG, SYSTEM.IMG and RECOVERY.IMG (there are multiple RECOVERY files, make sure you get the one without any numbers in it's name) and repeat the command. The last resort would be running "fastboot reboot-bootloader" and retrying the command that gives you errors. By the way - if you can't run fastboot at all, then try opening cmd as administrator. If you used KingRoot, read the next question too.
Q: I unlocked the bootloader via KingRoot and i can't flash anything, help?
A: No, you didn't. Do everything from part 1 and you will be able to flash.
Q: I don't like 6.0, how can i go back to 5.01?
A: Read this. After doing everything it said, repeat part 2 and 3a of this guide to get back on B200.
Q: You broke my phone, i will beat/curse/sue you!
A: Ok, that's not a question. Anyways, not my fault, i said you proceed at your own risk.

Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo

pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Fixing balong "bug":
fixed or no ? please answer

Fixed.
Sent from my ALE-L21 using XDA Free mobile app

please Possible steps to resolve the problem balong "bug"

1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help

pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Thanks for your input. I'll put it into first post...better to be safe than sorry.

darklove0 said:
1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help
Click to expand...
Click to collapse
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).

dennyn said:
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).
Click to expand...
Click to collapse
thnx answer
i dawnload Huawei_P8_Lite_ALE-L21_V100R001C432B170_Europe but not folder (CUSTOM or vendor)
i have update for this 6.0
http://forum.xda-developers.com/p8li...allow-t3305550

Can I flash using fastboot a zip containing the dolby atmos app?

rareshutzu said:
Can I flash using fastboot a zip containing the dolby atmos app?
Click to expand...
Click to collapse
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.

dennyn said:
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.
Click to expand...
Click to collapse
I was afraid of that. Thank you for your answer.

Great threads (and for the p8 lite this thread's was the only one )with real instructions, good and easy to understand.
Thanks for the explanation and for the time you have past for sharing this with the p8 comunity .

after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?

ken218 said:
after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?
Click to expand...
Click to collapse
It (always) shows just one imei after converting from single to dualsim. There shouldn't be any problems while using both sims because the phone is "dualsim standby".

Hello, just for help, I have downgrade my two p8 lite from 6.0 to the latest version B190 5.0.1, and I have full wipe and format all (dalvik, cache, system, data, internal storage) with twrp before and like this no need to flash any fix for balong. just B052, B170 and B190 without any trouble.

I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???

bjkhami said:
I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???
Click to expand...
Click to collapse
Sim1 or sim2? Anyways, try repeating part 2 with B170 (link is inside Q&A section) and then OTA to B188 because sometimes you lose your baseband when flashing older firmwares and OTA usually fixes it.

FAILED (remote: Command not allowed)
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.

pelukin said:
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.
Click to expand...
Click to collapse
Did you run cmd as administrator? Try relocking and unlocking bootloader again, also try a factory reset.
That error usually appears if you try to flash any locked partition...it shouldnt happen with system, recovery, boot and cust. Let's hope you don't have any hardware problems.

[Tutorial] Convert Honor 6+ Chinese in European (only PE-TL10)

Today I bring new tutorial to completely convert the Honor 6 Plus Chinese in European. (It's only applicable for the model PE-TL10).
So we must have unlocked bootloader and root. If we meet these requirements, we can proceed with the conversion.
1. Download the latest European version (B571)
2. Create a folder called dload in the micro sd and introduce there the update.app
3. Download the European oeminfo here, unzip and move the oeminfo.img to internal memory.
4. Install the app termux or terminal emulator
5. Open the app and write "su" to get root permissions.
6. Later, write "dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo" and when it finished, turn off the Smartphone.
7. Press Vol-+ and Power to install the European update.app and we will have turned the PE-TL10 Chinese in European.
Neither me or XDA we are not responsible for any misuse of the tutorial. I want to thank @foncubiert to try it
Original: http://www.htcmania.com/showthread.php?t=1228181

I was looking at it for 1 year, thank you very much. now google hello.

Is there "oeminfo.img" necessary to do the reverse of this process for install twrp old backup?
*** I need "oeminfo" file in China stock rom of China brand Honor 6 Plus Pe-TL10.
This file can be accessed "Srktool backup" or in "dev/block/platform/hi-mci.0/by-name/" . Thank you.

Is there a way to do this for the PE-UL00?
Inviato dal mio PE-UL00 utilizzando Tapatalk

Anyone tried it on PE-UL00 ?
Maybe there's a way to do the same.

Nice guide

Thanks juanro49 for the guide & the file.
The oeminfo works on PE-UL00 (tested myself- finally all google functions and no more strange chin. Stuff)

100 % working, I converted my Chinese PE-TL10 to EU one. Thanks for sharing it!

does anyone know how to convert to C636 ??

RK0lb3 said:
Thanks juanro49 for the guide & the file.
The oeminfo works on PE-UL00 (tested myself- finally all google functions and no more strange chin. Stuff)
Click to expand...
Click to collapse
I did not understand well. It works on pe-ul00?
The b571 can be installed?
thank you

roger_50 said:
I did not understand well. It works on pe-ul00?
The b571 can be installed?
thank you
Click to expand...
Click to collapse
news?

juanro49 said:
Today I bring new tutorial to completely convert the Honor 6 Plus Chinese in European. (It's only applicable for the model PE-TL10).
So we must have unlocked bootloader and root. If we meet these requirements, we can proceed with the conversion.
1. Download the latest European version (B571)
2. Create a folder called dload in the micro sd and introduce there the update.app
3. Download the European oeminfo here, unzip and move the oeminfo.img to internal memory.
4. Install the app termux or terminal emulator
5. Open the app and write "su" to get root permissions.
6. Later, write "dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo" and when it finished, turn off the Smartphone.
7. Press Vol-+ and Power to install the European update.app and we will have turned the PE-TL10 Chinese in European.
Neither me or XDA we are not responsible for any misuse of the tutorial. I want to thank @foncubiert to try it
Original: http://www.htcmania.com/showthread.php?t=1228181
Click to expand...
Click to collapse
I will have succeeded in turning my smartphone PE-UL00 to PE-TL10.
https://forum.xda-developers.com/honor-6/general/pe-ul00-naw-pe-tl10-experience-t3570052 here, my experience.

RK0lb3 said:
Thanks juanro49 for the guide & the file.
The oeminfo works on PE-UL00 (tested myself- finally all google functions and no more strange chin. Stuff)
Click to expand...
Click to collapse
Thanks, my PE-UL00 was converted to TL10 (VIA TWRP if u got any error, just facory reset and reboot and wait
edit.
how to make this phone work wwith dual sim ? i got only 1 sim and only 2g

Has someone tried to install it over PE-TL10V100R001CHNC00B260 build. Or it doesn't matter what is the previous version in the phone?

jhettler said:
Has someone tried to install it over PE-TL10V100R001CHNC00B260 build. Or it doesn't matter what is the previous version in the phone?
Click to expand...
Click to collapse
Hi guys,
self reply. I got through it. It was not completely without troubles, but finally I have Android 6.0 with EMUI 4.0.1 (build PE-TL10C432B571) in my PE-TL10 (originally on Android 4.4.2, EMUI 3.0, build PE-TL10V100R001CHNC00B260). I don't need a ROOT and custom recovery now so it is unrooted and stock recovery now.
First, I have never rooted Honor 6 PLUS and as it is not the newest device and it is not fully supported anymore by Honor MultiTool you have to use another way.
Bootloader has to be UNLOCKED - I used the MultiTool - it's fine and without any troubles
Device has to be ROOTED - that was a bit issue, because you have to flash custom recovery to be able to flash SuperSU and root the device. I did it via fastboot.
To enter the bootloader mode (fastboot) just switch off device, then hold Vol- and plug the USB cable - it should enter the bootloader mode - you should see the android robot and "phone UNLOCKED" indication.
Now you can use fastboot commands (you have to have proper drivers installed, you can find instructions on in another threads on XDA).
Or you can enter bootloader mode with command "adb reboot fastboot" - you have to be in the system (running Android) on the phone to run adb commands. It will restart your device and enter the bootloader mode after restarting.
Once you are in the bootloader mode with UNLOCKED bootloader you can flash custom recovery (necessary to flash SuperSU). I had to flash the proper custom recovery which I found here . I tried to flash another TWRP and CWM recoveries, but without success. You can flash the recovery with fastboot command "fastboot flash recovery CWM.img".
Then you can restart the device into the system with "fastboot reboot". Once you are in the system, you can reboot into recovery with command "adb reboot recovery".
In the recovery choose "install ZIP from ..." and choose this file. I had to choose the version BETA-SuperSU-v2.42.zip otherwise it didn't install anything despite the installation process was successful.
After the successful installation of SuperSU, you should have ROOTED device. You can check it for example with Root checker.
Then I mostly followed this tutorial. But with few modifcations.
I couldn't find this /dev/block/platform/hi_mci.0/by-name/oeminfo folder in my phone so I had to change the command for terminal emulator in the phone to dd if=/sdcard/oeminfo.img of=/dev/block/platform/ff1fe000.dwmmc0/by-name/oeminfo. There is another folder in "platform" folder but it doesn't contain "by-name" folder.
Then the tutorial says Press Vol-+ and Power to install the European update.app and we will have turned the PE-TL10 Chinese in European, but the issue is, you can't enter the "download mode" after you installed custom recovery. It simply doesn't enter the "download mode" and it stays on the screen with honor logo.
It was necessary to get into the system to be able to use fastboot command to flash stock recovery. How to solve it. I could't enter the system anymore, but I could enter the CWM. So I wiped the data and cache through CWM (Vol+ and Power button) and I was able to enter the Android system again.
I used again the "fastboot flash recovery B250.img" and flashed this recovery. It didn't correspond with my build version B260, but it helped.
Then I restarted the phone, entered again the system and through "Settings - Updater - Menu - Local update" and choose the "UPDATE.APP" from "dload" folder (it should be automatically detected) and whoila, it should restart the device and load "download mode" and install the UPDATE.APP. You should be able to do this step with Vol+- Power button combination instead of doing it through "Settings menu". And that's all.
I rather added some of used files into the attachment

Hello there I have a Honor 6 plus PE-UL00 that i want to change to European rom from China variant. Its rooted Android 6 Marshmallow with custom recovery TWRP
Firmware PE-UL00C00561. I'm still a beginning t limited knowledge,. I've learnt what I could from the forums. anyhow..
As per the changing rom guide , I downloaded The European rom B571 update.app and placed it in sdcard DLOAD folder as well put the OEM.img on the hard drive and ran termux and entered the command as per the guide and it seemed to work.
The Next step says ton turn the phone off And then press the volume+/- and Power button.. and it will load into the system and install the rom.
As per The post above, i got up to that step and the phone would Just boot to menu then reset.. I was able to get in recovery mode via TWRP and ran my backup.
I've read Post that the PE.UL00 can be converted, but is it following the exact same way as the PE-TL10? Or I may be missing a step.
The above post encountered a similar issue and had success, but his was a PETL10 and had hise his own recovery.img. (250.img to access his system and update the rom. in that scenario would l try to flash my recovery.img to get back into the system and run the local update?
Lastly another person had commented about their success converting a PE-UL00 to European rom. But just mentioned that it was through TWRP. Would that be just a matter of one I've done the OEM.img boot back into recovery and installed the app through TwRp or must I do a full wipe First?
Sorry for rehashing an old thread.. any advice much appreciated.
.

I got it working. After the OEM. IMG update I tried flashing it through TWRP. After some trial and error, my power button isn't responsive sometimes so maybe i wasnt pressing the volume down/up power button combo correctly. As the phone would just biot to Honor screen and reset.
Eventually after a few reboots and tries it went into the emui screen download mode and success.. I think. I did lose root in the process. I'm unsure how, still a novice, but I was able to re root the phone install custom recover via. TWRP and install SuperSU.
Now I don't have to deal with those China apps

roger_50 said:
I did not understand well. It works on pe-ul00?
The b571 can be installed?
thank you
Click to expand...
Click to collapse
I made it on my pe-ul00, it works for 100%.
It was a long time ago but as I remember, I installed b570 and after that update to b571.

semihy said:
I was looking at it for 1 year, thank you very much. now google hello.
Click to expand...
Click to collapse
May I know how did you rooted the chinese version device ?

[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
I'm providing a set of files that allow you to unlock your bootloader or recover from the closest thing you can get to a hard brick.
MiFlash is capable of flashing anything to your phone while it is in Emergency Download mode.
Yes, this is voodoo magic and it works! Recover from any and all bricks! Some might call it necromancy.
However, it can be also be used even if the device is perfectly alright to simplify upgrading procedures and make ROM flashing fairly painless.
This is for A2017U (North America) and A2017 (China) models only! Do not attempt this on A2017G.
INSTRUCTIONS
If you are flashing TWRP on a locked bootloader, you must first enable OEM unlocking on your device.
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
Follow the steps below with the FASTBOOT_UNLOCK package first, then go into fastboot mode and use the
"fastboot oem unlock" command to unlock (and wipe) your device. Download adb and fastboot below.
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Now install MiFlash (download below).
Open MiFlash and use the [select] button to select the A2017U_*_EDL folder package that you wish to flash.
Boot into EDL mode. (hold Volume Up + Volume Down + Power until you're stuck on a black screen)
Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
If you are flashing TWRP, use the [Power] + [Volume Up] key combo to exit EDL mode and enter recovery. Release the keys when you see the ZTE logo.
You must have an unlocked bootloader to enter TWRP!
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
EDL PACKAGES
FASTBOOT_UNLOCK
This will unlock all fastboot operations, including OEM unlock and fastboot boot/flash.
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Click here to download! (ZIP, 195.8 KiB)
B29_TWRP (Marshmallow 6.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B29 boot stack.
Click here to download! (ZIP, 59.4 MiB)
B15-NEW_TWRP (Nougat 7.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B15-NEW boot stack.
Click here to download! (ZIP, 60.6 MiB)
B15-NEW_FULL (Nougat 7.0)
This will install the entirety of the B15-NEW firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
B19-NOUGAT_TWRP (Nougat 7.1.1)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B19-NOUGAT boot stack.
Click here to download! (ZIP, 61.0 MiB)
B19-NOUGAT_FULL (Nougat 7.1.1)
This will install the entirety of the B19-NOUGAT firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
TOOLS
Xiaomi MiFlash Installer
Version: 2016.08.30.0
Click here to download! (MSI, 31.0 MiB)
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click here to download! (ZIP, 2.7 MiB)
ADB & Fastboot
Visit the SDK Platform Tools download page
Using this, you should safely be able to recover from any brick!
Once in TWRP, you can flash a full OTA or restore your backups and be on your way.
It is tested and working on Windows 10 64-bit.
All zips are signed with Android SignApk and can be verified with TWRP. (they won't install, just say it's not a valid zip after verifying)
A2017 (China) can use this to convert their phone to A2017U if they want. DO NOT flash on A2017G.
POSSIBLE ISSUES & SOLUTIONS
OTA update zips may fail in stock recovery even after flashing FULL EDL packages. This is because MiFlash does not erase blocks before writing the system image. You can run this command from TWRP terminal or adb shell to erase system partition before flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144
Once this is done, OTA zips should succeed in stock recovery after flashing a FULL EDL package.
CREDITS
This was based on the A2017 B07 EDL zip provided by @tenfar at this XDA thread.
HISTORY
2017-04-10 - Added B19-NOUGAT FULL and TWRP package
2017-02-11 - Added B15-NEW FULL signed OTA capable package
2017-02-11 - Added fastboot operation unlock package
2017-02-11 - Separated MiFlash, Qualcomm QUSB_BULK Driver, and EDL packages, removed 7z archives
2017-02-09 - Added B15-NEW TWRP package
2017-02-09 - Added B29 TWRP package

Any idea if this will work with Nougat or not?

neo4uo said:
Any idea if this will work with Nougat or not?
Click to expand...
Click to collapse
It will work on Nougat, however, you will end up on B29 bootloader. You'll need to flash B29 full and upgrade again.
I am having some weird issues with Nougat boot stack flashing + TWRP so I'll hold off on posting a B15-NEW version of this for now.
Update: You can now flash the B15-NEW TWRP package instead.

@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.

Situation: A2017U full stock in Nougat no unlocked bootloader, no root
Want to: Install LOS because i HATE this bullsh... called MIFAidonotknowWTF
Can i use this procedure to do that?
Thanks a LOT

So basically, MiFlash just lets you firehose in any file to a QualComm device from EDL mode? That's pretty handy.

I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.

Snaptraks said:
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Click to expand...
Click to collapse
It is softbrickable by adb commands... I have one device in boot loop.

trying to wrap my head around this whole bootstack/fastboot issue we have with the a7.
So in theory one could use this tool and then unlock (or just have working fastboot) directly from b15?
Then download the bootstack from los thread and be good to go? Or would that bork fastboot again...
I think I am currently running b20 bootstack on b15 by flashing draken's unlock zip without issue (that I know of) but am considering flashing the N version from los thread.

This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.

KwesiJnr said:
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
Click to expand...
Click to collapse
Have fun! Nougat images are now up!

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help

Altomugriento said:
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Click to expand...
Click to collapse
step 2.5) reboot to bootloader from recovery
step 4) wipe system in twrp
step 6) use the [Format Data] button on wipe page of twrp (lineageOS may not be compatible with your current encryption, this will wipe all your settings and internal storage)
and yes that's everything, I believe.

Sticky. Nuff said.
Dev is finally taking off on this phone, thanks to literally 4 or 5 key people. I was afraid I'd made a mistake purchasing instead of O+3, but has worked out well.
Thanks for all your help in your free time.

DrakenFX said:
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Click to expand...
Click to collapse
Thanks buddy, that keymaster -> xblbak appears to have been my issue! So illogical.
I compiled applypatch and used that to apply the B29_TO_B15-NEW .p files to my B29 binaries so they should be nice and exact. (sha1 matches from updater-script)
I can provide a full B15-NEW verity/OTA update friendly package if somebody wants. Just let me know.

Flash Done.
But i can't join to TWRP, it just turn it self off.

Eroticus said:
Flash Done.
But i can't join to TWRP, it just turn it self off.
Click to expand...
Click to collapse
If you are not unlocked you now need to go to fastboot mode and unlock before you can enter TWRP.
If you just mean the screen is still black, you have to hold volume + power up after flashing until it starts up, then let go when you see the ZTE logo.

Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock, rooted and fastboot working N B15 build?
Thanks

khangozzy said:
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock and rooted N B15 build?
Thanks
Click to expand...
Click to collapse
Look up a couple posts.

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Because it had been reported that this was impossible, or at least very difficult, I wanted to clarify whether this means people with locked bootloader running N can now unlock and install TWRP?

Unbrick tool for OnePlus 5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some china OP5 user got it from OnePlus staff, and uploaded it to china cloud drive.
[Driver]
Mega:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=889764386195921378
[Oxygen Version Download]
After you use this tool, your OP5 will be restore into stock Oxygen OS.
Mega 1:
https://mega.nz/#!MPBXkJjK!O2uDD7Xx04KPT_cx9coMHnGtaeSK06t9gwNpUR4KDXE
Mega 2:
https://mega.nz/#!gjRFmB4C!-HN00YSS2tUy5ZQTbJbzwEmZ8VU_iv5lLaTlbXin7Ec
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=745425885120760474
[Hydrogen Version Download]
After you use this tool, your OP5 will be restore into stock Hydrogen OS.
Source :
http://www.oneplusbbs.com/thread-3587805-1-1.html
Baidu pan:
http://pan.baidu.com/s/1qYz7hZu
pwd: 0fb4
Mega (corrupted):
https://mega.nz/#!kyJ1XJ7D!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Mega 2:
https://mega.nz/#!RmQnQKTB!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Google Drive:
https://drive.google.com/file/d/0B9vxnq7dlG4pYVJGaGZOYWNuZzA/view?usp=sharing
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?w=files&flid=204903
[Tutorial]
The steps is the same as 1+3T.
Ref:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Great ! I always prefer a fastboot / edl flash.
Sent from my ONEPLUS A5000 using Tapatalk

Isn't it Oxygen OS?

gonsa said:
Isn't it Oxygen OS?
Click to expand...
Click to collapse
Yes,it isn't.
However you can easily install Oxygen OS by yourself.:laugh:
Ref:
https://forum.xda-developers.com/oneplus-5/how-to/guide-installing-oxygenos-chinese-t3647409

Someone should be able to tweak this to fetch OOS files instead of H2OS. Both the firmwares are the same except userdata
Sent from my ONEPLUS A5000 using Tapatalk

Someone should upload this to androidfilehost so there are other places to download incase the original is taken down.

file in mega is corrupted.
please upload in any uploading site

@snowwolf725 ,since I already "came back" from fastboot-ed github/OOS/MSM8998 build, I like to clarify few tips:
-Unbrick via Qualcomm QFIL tools were well documented here and there (Oneplus 1/2/3/3T) ; but Qualcomm never granted free distribution of QualcommQDLoader9008 DRV or QFIL, AND your WindowsPC has to be disabled with integrity checks or antivirus. So it should be considered as the last extreme ultimate rescue.
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.

@oF2pks if I get your process correctly, for a clean flash, Flash all needs to be done 3 times with the stock recovery followed by OEM lock and post that the last step is to fastboot erase boot/system/user data/cache followed by adb sideload of the stock firmware?
Sent from my ONEPLUS A5000 using Tapatalk

On this subject, we need a return to stock guide for the OP5 :good: Fine writeup oF2pks! :highfive:

oF2pks said:
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
Click to expand...
Click to collapse
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!

TwinAdk said:
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
Click to expand...
Click to collapse
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.

File in mega is corrupt please re upload

hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu

Sir link is not visible

Link is not visible

hsareminia said:
file in mega is corrupted.
please upload in any uploading site
Click to expand...
Click to collapse
sanjeevattre said:
File in mega is corrupt please re upload
Click to expand...
Click to collapse
hsareminia said:
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Click to expand...
Click to collapse
I add new mirror links and dirver download link.
Driver:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ

jasonwsc said:
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
I am aware that the process above is HIGHLY complicated - and is often not necessary.
At the time of my post, my phone was in a state where I had been doing crazy things with it (decrypted data, multiple custom ROMs and TWRP versions, including multiboot variants and the chinese one. On top of that I had flashed the am-verity and force decryption patch zip). This is as such not unusual, but my attempts to return to stock had failed (stock ROM zip failed to flash, stock recovery were wierd as well).
Therefore, when the quick layout for COMPLETE STOCK were outlined above, I grabbed them and did the process, while documenting it for future reference for others. Also, I choose to include the oem unlock and lock part - though I am fully and completely aware that it's unnecessary to 99% of the readers, after all this is One Plus phones
I had not been able to find any other sources of the steps outlined, though they may be simple, so I took all the steps how ever overkill they might be, because then there would be a documented process
The steps above would recover a One Plus 5 from a state where only adb works, pretty serious condition indeed....
I'm staying on OOS based custom ROMs as long as the blobs for the camera is undisclosed by One Plus. I haven't had time to reply to this sooner, have a great weekend, and @asonwsc, I agree with you :highfive:
Kind Regards
TwinAdk

jasonwsc said:
...If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.... flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )

oF2pks said:
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
Click to expand...
Click to collapse
But if the device is considered certified on the play store, then it passed SafetyNet without an issue.
Correct me if I'm wrong, but shouldn't SafetyNet pass under the following conditions?
1. Locked bootloader with no root (stock)
2. Unlocked bootloader with Magisk root.
Is it actually possible for a locked bootloader and unrooted phone to fail SafetyNet? You can't root without the unlocking the bootloader, so how would that trigger SafetyNet?

[GUIDE] How to ROOT the HTC Desire 10 Pro

Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome ?

Any chance on doing a full backup before installing TWRP, as I don't have a default recovery of 1.18.400.20 dugl dual sim and still hope for OTA?
I hoped for "fastboot boot recovery" but I think only with nougat firmware was reimplemented.
Thanks

I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?

FireStorm919 said:
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
Click to expand...
Click to collapse
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...

process failed
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.

david_montes said:
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
Click to expand...
Click to collapse
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck

Fain11 said:
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Click to expand...
Click to collapse
I did try to uninstall magisk but it gets stuck in the boot process (only htc logo), the same thing happens with the backup I made with twrp (only htc logo), the best result so far is applying magisk to the boot, then the system starts but keeps asking me to decrypt the storage, the exact message is "The password you have entered is correct, but unfortunately your data is corrupt" I did factory reset but does not solve the problem, it keeps asking for the password.
Also RUU for my OS-2.13.709.20 is not available so I'm currently stuck.
These things get harder and harder every day

Desire 10 Pro recovered
Finally the last option was to fully stock flash with RUU 2.13.709.20, but now I am back to step one.
At least it works
---------- Post added at 04:20 PM ---------- Previous post was at 04:08 PM ----------
Been human means to keep trying, so I tried again, now I did full factory wipe before applying supersu 2.82 (not working) or magisk 15 (works but keeps asking for a password to decrypt storage).
So I can confirm this procedure does not work with OS-2.1.3.709.20.
If any of you is able to root this version I will be glad to try again in the future but by now I'm done with htc 10 pro.
Happy new year everyone!

thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help

thekingomar said:
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
Click to expand...
Click to collapse
It has been confirmed to be working on 1.18.400.20
Please make a backup before u try because this doesnt seem to work on newer ones like 2.13.709.20
Please leave a reply here if u get it working.
?

Fain11 said:
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
Click to expand...
Click to collapse
Sorry for the delay,
I couldn't find that link either so I extracted it from a RUU for variant a56dj_pro_dugl
Here you go
https://drive.google.com/file/d/1FxKDDOXISNTf5uQJT90nlw6tuClJaX9o/view?usp=drivesdk
Hope this helps
???

thanks for the guide again,
after pulling my courage together I decided to do it on my a56dj_pro_dugl software number 1.18.401.20
everything worked fine from the top to step 14 but there is one problem, flashing the SuperSU zip file is failed,
I tried to re-download it and not renaming it but still the same, here is the log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any suggestions ?

never mind
just rooted it using Magisk , apparently SuperSU is not applicable on my device
I used the same method as SuperSU zip
downloaded the latest version of Magisk (v 15.3) zip file and install it using TWRP
and everything is fine ever since
thanks folks for being awsome developers :laugh:

Required Video
Hi Member,
Can you please upload step by step video for root the HTC Desire 10 pro.
waiting

warnning !!! htc desire 10 pro os 2.13.709.23 taiwan
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!

Mykyzo007 said:
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Click to expand...
Click to collapse
Did you manage to unbrick?

yes
dearbasheer said:
Did you manage to unbrick?
Click to expand...
Click to collapse
yes i manage to unbrick, i'am waiting to see the rom .
But i need help

Unable to flash recovery
When unlocking bootloader I selected any other supported since desire 10 pro isn't listed. Process went through but when flashing twrp I'm getting error. Commad not allowed whereas it shows unlocked

FireStorm919 said:
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome
Click to expand...
Click to collapse
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot

Sangam IME
seyyed.april said:
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I havent checked my inbox for quite some time.
I searched around for this Sangam IME everywhere in,
/system/app
/system/priv-app
/data/app
/data/app-private
But I couldnt find it. I even tried using 3rd party apps like you suggested but it simply doesnt seem to exist.
Even a quick Google search didnt give me any leads.
So are you sure the name is correct ?
Or maybe any more ideas on where to look for the apk ?
Sorry I couldnt be of more help