Related
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo "Updated_19.5.2018"
Huawei P10 debrand/rebrand/update GUIDE
This thread will be discontinued, because Huawei refuses to provide unlock codes in the future, because of security reasons.
A shame that after the support end of the device it will be quite useless, cause you don´t get any security updates and have no chance to make secure again, by flashing something else.
I recommend you not buy any Huaweidevices in the future cause of that.
Disclaimer:
Before you do anything (stupid), backup your data!!!! Don´t make me or others responsible, i warned you!!!!!
If you wan´t to go back to your orginial version some day, you have to backup your OEMinfo!!! Best way to that is via TWRP before the rebranding ( see details of STEP 1)
When using the follwing script, take your time and drink a cup of coffee/tea!!!! First rule, don´t panic!!! Don´t do any (unnecessary) extra steps, while using the script!!!
Be aware that the phone sometimes takes longer for a step to finish, or you get stuck on a certain procedure (maybe depending on your branding). Key is to what to do at this point e.g. how to boot manually into fastboot.
If for some reason you must restart the procedure and factory reset appeared for the step, remember to look for the debugsettings and other mandatory settings.
Please use the orginal cable that came with the device for the rebranding and not some cheap aftermarket stuff. Also make sure you USB-Port has enough power (Might be the case on some notebooks)
70% of the posts/questions here are answered, if you read the gude carefully. So do you´re job and read!!!! Yes, i know it´s a lot to read, but details will maybe save your a**
Make sure you removed security pin from the device and also remove the google-account from the device itself, so you are not triggering googlesecuritysystem on nougat or oreo.
If you have a carrier version of the singleSIM P10 (VTR-L09xxxx) and you want rebrand or debrand it, you have to use the firmware for DualSIM (VTR-L29xxxx), or you SIM won´t be recognized anymore!
The good thing is, after that, you´ll be able to use both SIM or SIM and microSD. The provided HWOTA rom is mainly for the L29. If you want the L09 you have to replace the "update_all_hw.zip" in the update folder. If you not sure how to get, take a look in the Huawei-Forums
From Oreo to Oreo:
1. Download: @AndroidFilehost: HWOTA8_P10_B369a (Oreo) (MD5-Hash: fd330a74d22d2ef55a02bfcfdcea33ee )
All important files are inside this package!!
2. The steps for the this procedure are described here:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
From Nougat To Oreo (or Nougat to Nougat, if you use the older files):
STEP 1 (optional steps for the oeminfo backup are cursive)
1. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!)
The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
If you already unlocked your bootloader with installed twrp you can go to step 2. You don´t have to install TWRP in the following miniguide. the script installs it automatically.
But if you want to backup your system or the OEMinfo you have to do this step.
1. Request an unlock code: https://docs.google.com/forms/d/e/1FAIpQLSeGwoQ44zqykuTfjCQrVP07JOHBYnBcAxAbz9SAVxPTFqMh9g/viewform or contact Huawei via live chat on their site.
It may take some time till you get the code. Hopefully they revamp their old unlocksite in the future, cause using a googleform seems to be temporary solutions anyways.
I also found a nice handy tool, but haven´t testet it yet on the p10 and officially it isn´t yet supported (for now only P20): https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 If can prove that it´s working for the P10 just leave a comment in the thread here or in the orginal thread.
2 Download Hisuite and install: HiSuite
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. Install the ADB Minimal Installer or ADB and Fastboot for Mac and then restart if you already have the driver installed then skip this step.
5. Download TWRP for the P10
6. Now go to ADB and Fastboot installation directory open ADB folder and open the command window as an administrator
7. Connect your phone to PC and reboot the device into fastboot mode by typing “adb reboot bootloader”.
8. Type “fastboot devices” in command prompt and hit enter, it gives you serial numbers in return means your phone connected properly.
10. To unlock bootloader, type fastboot oem unlock yourunlockkey. Here replace unlock key with the key you got. For example “fastboot oem unlock 1234567890″.
11. If you want TWRP at this point you have to copy the downloaded twrp.img-file into the adb directory and type fastboot flash recovery twrpimage.img If you already have oreo running on your device, you must use this updatepackage and follow the guide <.--instead of twrpimage.img type in the exact filename you´ve downloaded.
12. To restart the system type “fastboot reboot”
13. Boot into TWRP and make a Backup of the "OEMinfo" and/or the system. You should be able to that without any guide, otherwise it´s a big mistake keep reading and following this guide!!!
STEP 2
1. Depending on your variant (You can check with the app firmwarefinder and imei, if the update is approved) use:
@AndroidFilehost: HWOTA_P10_B369a (Oreo) (MD5-Hash: b935a84180565fb1717a46d7337f2d43 )
@AndroidFilehost: HWOTA_P10_B365 (Oreo) (MD5-Hash: dbcd30e157625fc6d709b26d49421bb6 )
@MegaUpload: HWOTA_P10_B360 (Oreo) (MD5-Hash: E75DCD3950517E517865878DF8F21679 )
Be aware, it takes some modifications to the script if you wan´t to rollback to nougat. You´ll find guides here on xda for that. So really be sure if you want the new oreo version.
Also you bootloader may stay unlocked after using the script to update to oreo. You have to relock it manually. Boot in fastboot mode and use: fastboot relock INSERTYOURUNLOCKKEYHERE. After relocking your device will once again do a factory reset.
@MegaUpload: HWOTA_P10_B180 (Nougat) (MD5-Hash: 7E11EE56E83AB98DA4DE03273A6A7633 )
@MegaUpload: HWOTA_P10_B179 (Nougat) (MD5-Hash: 7D133B7484E7B4AABA84BA1284D148EC )
some older versions of the hwota:
@MegaUpload: HWOTA_P10_B164
@MegaUpload: HWOTA_P10_B130
and extract it on your PC or your device SD Card. I recommend using 7zip.
2. Run the update.bat file from a preopended CMD with adminrights, It will ask you if you copied the files. Press any key to continue.
3. Now connect your device and Reboot into Bootloader mode using “Volume Down + Power” or just use “adb reboot bootloader” then press any key.
4. The above step will install TWRP in your device.
5. Now Disconnect USB Cable and turn off your device and use “Volume Up + Power” to enter TWRP.
6. Once you’re in TWRP mode, plug in the USB cable again and press the Enter key on your computer.
7. If your files are saved in the HWOTA folder on the SD card, type 1 and press ENTER and if files are saved in the HWOTA/Update folder on your PC, type 2 and press ENTER. I recommend using the sdcard, cause you avoid problems with cheap cables, driverproblems, etc. Make sure you sdcard is fully working and has no errors.
8. It’ll ask you the update type, again type 1 and press the Enter button twice.
9 Done! Be patient an let it do it thing.
10. If you have any problems booting, i recommend doing an low-level factory reset after.
11. Run the update.bat file as an administrator, It will ask you if you copied the files. Press any key to continue.
12. Now connect your device and Reboot into Bootloader mode using “Volume Down + Power” or just use “adb reboot bootloader” then press any key.
13. The above step will install TWRP in your device.
14. Now Disconnect USB Cable and turn off your device and use “Volume Up + Power” to enter TWRP.
15. Once you’re in TWRP mode, plug in the USB cable again and press the Enter key on your computer.
16. If your files are saved in the HWOTA folder on the SD card, type 1 and press ENTER and if files are saved in the HWOTA/Update folder on your PC, type 2 and press ENTER. I recommend using the harddrive of the pc
17. It’ll ask you the update type, again type 1 and press the Enter button twice.
18. Done! Be patient an let it do it´s thing.
19. If you have any problems booting, i recommend doing an low-level factory reset after.
20. If you are rebranding your device with this method, you have to do the whole "STEP 2" again in order to flash the new system files correctly. Also sometimes the device gets stuck on installing the new system after pushing the big updatefiles via adb. Wait 10min and if nothings happens you have to longpress the power key in order to complete.
21. After the new firmwarefiles have been pushed the device will make a factory reset, if it fails, restart the device while pressing Power+Volume up and factory reset the device from the orginal recovery. If enter TWRP at this point, something went wrong.
After that, you´ll be able to get updates directly from huawei via systemupdate or use the awesome firmware finder from the playstore.
If you wondering how to use the firmware finder, watch this guide and do it step by step: Firmware Finder Tutorial If you don´t want to rebrand/debrand this maybe enough for you!
STEP 3 (Optional Update Method 1)
If you have already unlocked your bootloader und installed TWRP, you can also use this method to install the new system update (Don´t try it if you are running oreo or wan´t to install it!! There is no stable und fully functioning version of TWRP for Oreo yet!!!):
1. Make a complete backup of your current system via twrp and save the backup to sd or your pc.
2. Download one of the Huawei P10_HWOTA files from above, save it on your device and unzip it
3. Navigate to the update folder in the HWOTA-folder and copy the 3 files to your device (sdcard recommended)
4. Now Boot your device into TWRP
5. In TWRP flash "update.zip" and don´t reboot!!!
6. Flash "update_all_hw.zip" and don´t reboot!!!
7. Flash "update_data_public.zip"
6. Wait until all files are flashed
7. Done! Reboot TWRP
STEP 4 (Optional Update Method 2):
1. download and install Firmware Finder
2. start the app and search for the exact model you want to update for example VTR-L29C432
3. Look for an FullOTA package and check with your IMEI if the device is approved, otherwise it won´t install cause huawei hasn´t signed the update for your device (IMEI) yet.
3. hit the button "inapp proxy" and setup the proxy with localhost and port 8080 in your phone´s wifi settings.
4. check for the update in systemupdate-app from huawei on your phone, start the update and pause it quickly (at 1-3%).
5. delete the proxy in your wifi settings.
6. resume the update
7. After successful download your device will reboot and install the update
If it fails there actually 3 reasons:
1. your Wifi is crap
2. you didn´t do the steps correctly
3. the firmware isn´t approved for your device, so be sure to check with imei before
(Maybe) Useful Links:
Team MT
Team MT Firmware Database for VTR-L29C432
New Huawei Multi Tool from TeamMT (Be sure to check it out, it´ll soon support the P10)
Guide for firmware finder (made by Firicel69)
OEMInfo Collections
My Other P10 Plus Thread
[TOOL] TOOL ALL IN ONE (No P10 Support yet, but you can request it)
Tips:
Pressing Power + Volume Down will launch the Fastboot Mode
Pressing Power + Volume Up will launch the Recovery Mode
Pressing Power + Volume Down with connected USB will launch the Fastboot Mode in forcemode (might useful if you can´t boot to the bootloader)
Pressing Power + Volume Down+Up will launch the forced firmwareupdate if you have the suitable updatefiles on your sdcard in a folder named "dload"
Turning your phone off and then pressing Volume Down while pluging in your USB-Cable will launch the Fastboot Mode
This whole thing was only possible because of the hard work of other heros here on xda!!
Mainly its based on the method from mankindtw [Guide] Mate 9 Flash Update Package and Rebrand
Big THX to mankindtw for the script!! Please send him some money, if you can!
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
sangsaby said:
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
Click to expand...
Click to collapse
I´m not 100% sure, but in my opionion your VTR-AL00 (should be the china version with playstore) has exactly the same hardware as the VTR-L29. Be sure to backup you system or at least only your oeminfo.
In case you rebranding doesn´t function you can revert back to your orginal version via TWRP. Maybe you should try the 636 instead of the 432, depending on your location.
sangsaby said:
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
Click to expand...
Click to collapse
Hi, i would like to rebrand to VTR-AL00, can you please send me the oem info of vtr-AL00?
Thank you
yangsong2000 said:
Hi, i would like to rebrand to VTR-AL00, can you please send me the oem info of vtr-AL00?
Thank you
Click to expand...
Click to collapse
Really sure, think about it twice, most people want rebrand their phone to L09 or L29. I makes no sense to rebrand to VTR-L00, the only advantage i see, is that you get updates earlier, but in fact the other variants get really often updates too.
People with VTR-L00 bought their device cheap in china and want to rebrand because of the missing playstore, or thr missing LTE bands.
Here you can see the differences between the variants:
http://consumer.huawei.com/en/phones/p10/specs/
I´m sorry i can´t provide yoo a oeminfo for the VTR-L00.
LwannaCM said:
Really sure, think about it twice, most people want rebrand their phone to L09 or L29. I makes no sense to rebrand to VTR-L00, the only advantage i see, is that you get updates earlier, but in fact the other variants get really often updates too.
People with VTR-L00 bought their device cheap in china and want to rebrand because of the missing playstore, or thr missing LTE bands.
Here you can see the differences between the variants:
http://consumer.huawei.com/en/phones/p10/specs/
I´m sorry i can´t provide yoo a oeminfo for the VTR-L00.
Click to expand...
Click to collapse
Actually in VTR-AL00 you have more features and the updates are faster. Moreover, you can install play store
By the way in case I don't like it, I can go back to European version. But at the moment I want to try VTR-AL00!
Do you know where I can download it or do you know someone who has it?
Thank you
Good day.. i am using this method.. i have one question..
what is this firmware provided?? HWOTA_P10_B164.zip
is it VTR-L29C432 or C636??
thanks!
francisac3 said:
good day.. I am using this method.. I have one question..
What is this firmware provided?? Hwota_p10_b164.zip
is it vtr-l29c432 or c636??
Thanks!
Click to expand...
Click to collapse
vtr-l29c432
Be sure to stick exactly to the steps! After its finished wait at least 15min.
If the device won´t reboot itself, you have to switch it off and maybe make a low level reset via orginal recovery, if you´re stuck in a boot loop.
Happened to me on 1 of 5 flashes.
yangsong2000 said:
Actually in VTR-AL00 you have more features and the updates are faster. Moreover, you can install play store
By the way in case I don't like it, I can go back to European version. But at the moment I want to try VTR-AL00!
Do you know where I can download it or do you know someone who has it?
Thank you
Click to expand...
Click to collapse
Sorry, i couldn´t find a oeminfo for the VTR-AL00
LwannaCM said:
vtr-l29c432
Be sure to stick exactly to the steps! After its finished wait at least 15min.
If the device won´t reboot itself, you have to switch it off and maybe make a low level reset via orginal recovery, if you´re stuck in a boot loop.
Happened to me on 1 of 5 flashes.
Click to expand...
Click to collapse
thanks.. will try this on my vtr-tl00 chinese version.. downloading the file now
Rebrand p10
Hi I have VTR-L29C738B150. It is brand Polish mobile Polkomtel. I want to change to open Europe software. I try to do this like in this post but nothing happened after I am in TWRP and click enter. Please help me.
what happened to the update.bat?? i cant use this.. when i open the update.bat... it only pops up then immediately close
DiMeteo24 said:
Hi I have VTR-L29C738B150. It is brand Polish mobile Polkomtel. I want to change to open Europe software. I try to do this like in this post but nothing happened after I am in TWRP and click enter. Please help me.
Click to expand...
Click to collapse
Maybe you forgot to unplug the cable. Just repeat the steps to this point. If you however get stuck, try to flash a custom rom for the p10 from this section, at least you get your device working again.
Maybe you find a solution here: [Guide] Mate 9 Flash Update Package and Rebrand it´s the same batch from mankindtw, only with files for the p10.
francisac3 said:
what happened to the update.bat?? i cant use this.. when i open the update.bat... it only pops up then immediately close
Click to expand...
Click to collapse
Maybe the update.bat hates you, just kiddin Open a CMD as admin run the update.bat from there. What you describe is a common problem and relates to a lot of other batchfiles
Rebrand P10
LwannaCM said:
Maybe you forgot to unplug the cable. Just repeat the steps to this point. If you however get stuck, try to flash a custom rom for the p10 from this section, at least you get your device working again.
Maybe you find a solution here: [Guide] Mate 9 Flash Update Package and Rebrand it´s the same batch from mankindtw, only with files for the p10.
Click to expand...
Click to collapse
I do all like You say. But I have a problem (I can't do backup in TWRP and while I install TWRP on the end there is a error). Maybe I shoud set something in developer option?
DiMeteo24 said:
I do all like You say. But I have a problem (I can't do backup in TWRP and while I install TWRP on the end there is a error). Maybe I shoud set something in developer option?
Click to expand...
Click to collapse
Please read again everything in Step 1, there lies your answer how to get your TWRP and what to activate in developersettings. This step has nothing to do with the update.bat and is absolutely crucial and mandatory.
After installing TWRP the official way, make a backup and continue.
Rebrand P10
LwannaCM said:
Please read again everything in Step 1, there lies your answer how to get your TWRP and what to activate in developersettings. This step has nothing to do with the update.bat and is absolutely crucial and mandatory.
After installing TWRP the official way, make a backup and continue.
Click to expand...
Click to collapse
I will show you where is the problem.
when I boot in fastboot I see something like this:
replace recovery to TVRP
target reported........
sending recovery........
OKEY
writing recovery.....
FAILED <remote:Command not allowed>
finished
after this I do all with volume up+power and nothing happened
DiMeteo24 said:
I will show you where is the problem.
when I boot in fastboot I see something like this:
replace recovery to TVRP
target reported........
sending recovery........
OKEY
writing recovery.....
FAILED <remote:Command not allowed>
finished
after this I do all with volume up+power and nothing happened
Click to expand...
Click to collapse
O.K. now i understand, did you set OEM-Unlocking in Developer Options? It seems like you have a locked FRP and your device doesn´t allow flashing the custom recovery.
Someone already had this problem on the Mate 9:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page56
LwannaCM said:
O.K. now i understand, did you set OEM-Unlocking in Developer Options? It seems like you have a locked FRP and your device doesn´t allow flashing the custom recovery.
Someone already had this problem on the Mate 9:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page56
Click to expand...
Click to collapse
I have FRP lock but I cant set OEM unlocking in developer option because it is grey (non active)
DiMeteo24 said:
I have FRP lock but I cant set OEM unlocking in developer option because it is grey (non active)
Click to expand...
Click to collapse
K, now we are talking. Only thing you can do is flash your rom back to stock the semi-official way:
Download the firmware finder from the playstore.
Search for your device (not the one you want rebrand to) and check with IMEI in Firmware Finder just to be sure. Here you have a guide: Firmware Finder Tutorial
If you prefer reading, you can also follow this: https://forum.xda-developers.com/p10/how-to/guide-update-p10-via-firmware-finder-app-t3674477
Then you should be back to normal. When it´s finished you can try again, just be really sure following the steps and do no extra steps!! ....for Instance wiping something after you installed TWRP
You can try the dload method instead, but i recommend doing it via firmwarefinder, simply cause it will work.
This guide should work with any Xiaomi device, including the Redmi K20, Redmi K20 Pro, Xiaomi Mi 9T and Xiaomi Mi 9T Pro.
Install ADB on windows 10
Go to developer.android.com and download SDK Platform-Tools for Windows as ZIP
Unzip and save in a folder on the C drive. Remark: you do not have to install anything or run any program.
Check installation: Shift+right click on an empty area in the folder and select open command prompt here and type adb. The result should be similar to this: Android Debug Bridge version 1.0.39 Revision 3db08f2c6889-android Installed as C:\ADB\platform-tools\adb.exe. If ADB is not correctly installed, you will probably see the following message: ‘adb’ is not recognized as an internal or external command, operable program or batch file.
Unlock bootloader
Backup all your personal documents
Turn off lockscreen security (fingerprint, code, face ID)
Make sure you have sufficient battery.
Make a Mi account: Settings > Mi account
Activate developer options: Settings > about > MIUI version: Tap 5 times
Enable OEM unlocking: Developer options > OEM unlocking
Enter fastboot mode: Hold volume down + power
Connect to PC and install drivers: Use device manager and select manually downloaded drivers
Download unlock tool: Go to en.MIUI/unlock > Unlock now > Sign in > Download Mi Unlock as ZIP
Unlock bootloader: Extract ZIP > Run miflash_unlock.exe > Sign in with your Mi account and follow instructions. The unlock tool will say unlocked successfully and the phone will reboot itself
Install TWRP
Enable USB debugging: Settings > Developer Options > USB Debugging
Download TWRP ZIP: Unzip
Flash TWRP: Boot into bootloader. Connect to PC. Open folder where twrp.img is stored. Shift+right click on an empty area in the folder and select open command prompt here. Type fastboot devices to ensure your phone is recognized. Flash TWRP by typing fastboot flash recovery twrp.img.
Flash custom ROM
Download files: Download the ROM (and other files like Gapps, Magisk) and move it to your internal storage
Backup stock ROM: Select backup. Select system (not system image) & select boot. Select storage where the backup will be saved. Name the backup. Swipe to backup. When the backup is done, press reboot system for your phone to start up normally. Keep a copy of the backup on the internal storage and one on your PC
Wipe old software: Boot into recovery. Select wipe. Select advanced wipe. Select data, cache, dalvik cache and system** and swipe to wipe. When the reset is done, press back (twice) to return to the TWRP homescreen.
Flash ROM: Select install. Select the ROM (and add other files like Gapps, Magisk). Swipe to confirm flash. When flashing is done, press reboot system. The first boot will take a lot longer than usual.
Remarks:
** It is not always necessary to wipe system, since most custom ROMs automatically wipe system. Wiping anyway should not do any harm. Furthermore, formatting data (wipe > format data > type yes) is unnecessary most of the time. It is useful for people who have an encrypted device. If your device is encrypted and TWRP fails to flash, format data to remove encryption. Note that if you disabled all lockscreen security, then encryption is disabled. Encryption is not possible without lockscreen security. To encrypt again after flashing, go to device settings in the new ROM. Be sure to setup lockscreen security first.
Krullendhaar said:
This guide should work with any Xiaomi device, including the Redmi K20, Redmi K20 Pro, Xiaomi Mi 9T and Xiaomi Mi 9T Pro.
Install ADB on windows 10
Go to developer.android.com and download SDK Platform-Tools for Windows as ZIP
Unzip and save in a folder on the C drive
Check installation: Shift+right click on an empty area in the folder and select open command prompt here and type adb. The result should be similar to this: Android Debug Bridge version 1.0.39 Revision 3db08f2c6889-android Installed as C:\ADB\platform-tools\adb.exe
Unlock bootloader
Backup all your personal documents
Turn off lockscreen security (fingerprint, code, face ID)
Make sure you have sufficient battery.
Make a Mi account: Settings > Mi account
Activate developer options: Settings > about > MIUI version: Tap 5 times
Enable OEM unlocking: Developer options > OEM unlocking
Enter fastboot mode: Hold volume down + power
Connect to PC and install drivers: Use device manager and select manually downloaded drivers
Download unlock tool: Go to en.MIUI/unlock > Unlock now > Sign in > Download Mi Unlock as ZIP
Unlock bootloader: Extract ZIP > Run miflash_unlock.exe > Sign in with your Mi account and follow instructions. The unlock tool will say unlocked successfully and the phone will reboot itself
Install TWRP
Enable USB debugging: Settings > Developer Options > USB Debugging
Download TWRP ZIP: Unzip
Flash TWRP: Boot into bootloader. Connect to PC. Open folder where twrp.img is stored. Shift+right click on an empty area in the folder and select open command prompt here. Type fastboot devices to ensure your phone is recognized. Flash TWRP by typing fastboot flash recovery twrp.img.
Flash custom ROM
Download files: Download the ROM (and other files like Gapps, Magisk) and move it to your internal storage
Backup stock ROM: Select backup. Select system (not system image) & select boot. Select storage where the backup will be saved. Name the backup. Swipe to backup. When the backup is done, press reboot system for your phone to start up normally. Keep a copy of the backup on the internal storage and one on your PC
Wipe old software: Boot into recovery. Select wipe. Select advanced wipe. Select data, cache, dalvik cache and system** and swipe to wipe. When the reset is done, press back (twice) to return to the TWRP homescreen.
Flash ROM: Select install. Select the ROM (and add other files like Gapps, Magisk). Swipe to confirm flash. When flashing is done, press reboot system. The first boot will take a lot longer than usual.
Remarks:
** It is not always necessary to wipe system, since most custom ROMs automatically wipe system. Wiping anyway should not do any harm. Furthermore, formatting data (wipe > format data > type yes) is unnecessary most of the time. It is useful for people who have an encrypted device.
Click to expand...
Click to collapse
i am not able to unlock bootloader help pls
Jaskaran21 said:
i am not able to unlock bootloader help pls
Click to expand...
Click to collapse
With respect,
You've given no information for anyone to want to help.
DaveHTC200 said:
With respect,
You've given no information for anyone to want to help.
Click to expand...
Click to collapse
Sorry i am getting 168 hours later error in the mi unlock tool i have tried 3-4 different accounts with different phone numbers but still it is showing the same error. I had even waited for a week but still its the same error
Jaskaran21 said:
Sorry i am getting 168 hours later error in the mi unlock tool i have tried 3-4 different accounts with different phone numbers but still it is showing the same error. I had even waited for a week but still its the same error
Click to expand...
Click to collapse
I'm not sure you can get around the waiting time!
Some people get longer times than others I believe, you just have to continue to use the phone and potentially keep trying.
I may stand corrected though
DaveHTC200 said:
I'm not sure you can get around the waiting time!
Some people get longer times than others I believe, you just have to continue to use the phone and potentially keep trying.
I may stand corrected though
Click to expand...
Click to collapse
It is not possible to get around the waiting time. The waiting time and the requirement for a Mi account is a safety measure to prevent reseller from installing spyware/malware. Just wait.
Krullendhaar said:
It is not possible to get around the waiting time. The waiting time and the requirement for a Mi account is a safety measure to prevent reseller from installing spyware/malware. Just wait.
Click to expand...
Click to collapse
Some mentioned about an older version of MiFlash but I've not required this as yet
DaveHTC200 said:
Some mentioned about an older version of MiFlash but I've not required this as yet
Click to expand...
Click to collapse
I have tried the old unlock tool it gives the same error
Why did you have to use TWRP? I used only MiFlash with the India ROM fastboot and it worked fine.
DontDamnMe said:
Why did you have to use TWRP? I used only MiFlash with the India ROM fastboot and it worked fine.
Click to expand...
Click to collapse
MiFlash only works with MIUI ROMS.
What are the PRO/CONS of rooting this Mi 9T Pro device? what would stop working?
alxtorrentazos said:
What are the PRO/CONS of rooting this Mi 9T Pro device? what would stop working?
Click to expand...
Click to collapse
You can flash EEA, Global and China firmwares on different phones. You can flash custom rom. That's about unlocking bootloader, rooting is another thing which you can do once U unlocked.
For bad things you become able to harm or destroy your device(what happens if you do something very wrong, always double check while flashing from PC, don't lock bootloader on firmware not for your region) and there are security flaws in storage encryption.
dpdp73 said:
You can flash EEA, Global and China firmwares on different phones. You can flash custom rom. That's about unlocking bootloader, rooting is another thing which you can do once U unlocked.
For bad things you become able to harm or destroy your device(what happens if you do something very wrong, always double check while flashing from PC, don't lock bootloader on firmware not for your region) and there are security flaws in storage encryption.
Click to expand...
Click to collapse
Thank you for your reply sir. I was wondering about NFC or Google Pay, things like that maybe stop working after unlocking the bootloader.
Everything perfect except for Magisk. When I try to install Magisk from TWRP, I am always getting Error 1. How can I fix it?
Hi guys,
I'm sorry, but I have tue current problem of many people here : OEM unlocking is impossible.
I tried 3 times, with 168h/7 days intervall each time, but same error.
I allowed OEM unlocking and USB debugging, I tried with several MiFlashUnlockTools.
I can't find why it doesn't work...
caperonjr said:
Hi guys,
I'm sorry, but I have tue current problem of many people here : OEM unlocking is impossible.
I tried 3 times, with 168h/7 days intervall each time, but same error.
I allowed OEM unlocking and USB debugging, I tried with several MiFlashUnlockTools.
I can't find why it doesn't work...
Click to expand...
Click to collapse
What error?
After waiting 7 days and trying to unlock again, what happens?
When you are waiting for the 7 days to finish, do not change the Mi account on the phone, do not go to the Mi Unlock Status setting and press start. Doing anything like this will reset the process and start the timer again.
When the 7 days are finished you should only put the phone in fastboot mode, connect it to the PC and run the Mi Unlock Tool.
Robbo.5000 said:
What error?
After waiting 7 days and trying to unlock again, what happens?
When you are waiting for the 7 days to finish, do not change the Mi account on the phone, do not go to the Mi Unlock Status setting and press start. Doing anything like this will reset the process and start the timer again.
When the 7 days are finished you should only put the phone in fastboot mode, connect it to the PC and run the Mi Unlock Tool.
Click to expand...
Click to collapse
The same error : 168h to wait !
I don't think I do something to reinitialize the process : mi Mi account is not changed, oem unlock and usb debug always allowed...
I have a global rom, can it be the reason ? Or the method is the same for all versions of this phone ?
Hello,
Well, i've made all the steps, but after flashed TWRP, the phone only boots on Fastboot mode...
Can you help me?
Will the "bootloader unlock" cause a factory reset of the phone?
Kicked off the wait timer so 168hrs or 7 days to wait. Box fresh Mi 9T Pro; I'll probably be lurking around these parts of XDA now.
What happened to the old clear gel cases? The included black hard case is super-brittle and cracked as I was putting it on for first use. Ordered a good old gel case; I'd like to actually see the aurora effect :silly:.
Anyone know if running a system update will reset the timer?
Like many, I was overwhelmed with information when trying to unlock, flash, and root my phone. After many failures, I decided to compile the good information all in one place.
I hope this helps. If it does, please consider buying me a beer...
Bitcoin Address: 17p3sW8hG5ndZqAuoDQiUE99iHwBZss6UK
Bitcoin QR Code:
{
"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"
}
________________________________________
MY SPECS
I'm using the Redmi K20 Pro running Android version 9 PKQ1.181121.001 (patched July 1, 2109) and MIUI Global 10.3.5. I am in the United States and I have Verizon as my cellular service provider. On the Redmi K20 Pro in the United States, Verizon is compatible with LTE/GSM (and CDMA, but I learned that Verizon is phasing out CDMA).
BOOTLOADER & UNLOCKING
Let me start by thanking Jumundz who saved my ass when I bricked my phone. More on that below...
"ALL IN ONE" TOOL
The following guide details how to root your phone manually. If you already understand the process, or want to tweak some of the steps, I recommend using:
ALL IN ONE tool. / (mediafire alternative link)
...or...
Xiaomi ADB Fastboot Tools (this is the current version, 2.3.1)
DEVELOPER MODE & USB DEBUGGING
To start, we need to enable Developer Mode.
Go to Settings and then click on About phone.
Then tap "MIUI version" several times (5-7 taps) until a notification reads "You are now a developer."
Go back into the main Settings menu and scroll down until you see Additional settings.
Click on Additional settings and then scroll down until you see Developer options
Click on Developer options. Here you will find a number of options that are not commonly available. If you have not unlocked your device yet, you will notice that OEM unlocking is turned off and also greyed out so that you cannot click on it. Instructions for unlocking your device can be found below.
Scroll down and tap USB debugging.
** Optional ** I also tap Install via USB just in case I want to use that down the road.
After enabling Developer Mode, connect your phone to your computer with a USB cable. (*NOTE* Some USB cables only charge your device. Make sure your USB cable is designed to permit data transfer as well.) A notification will pop up on your phone asking if you would like to allow the connection for USB debugging. Press "YES" so that the computer and phone will recognize each other in the future.
OFFICIAL MIUI UNLOCK
As many of you know, Xiaomi created obstacles for those wishing to unlock the bootloader. Xiaomi claims they created the waiting period to "deter resellers from loading shady firmware into their devices" (LINK). So, I created a Mi Account and then made the unlock request with the official MIUI unlocking tool Mi Unlock. The program that downloaded (at least for me) through the official site was miflash_unlock-en-3.5.719.27.zip
MI ACCOUNT BYPASS TOOLS?
Since unlocking my device through the official pathway, I read that you can bypass this process using other tools. ** Disclaimer ** I have not personally used these tools! XiaoMiTool (version 1) is discussed in this XDA article, but recommends using XiaoMiTool V2(Download link to the latest version of XiaoMiTool V2). XiaomiBuzz suggests using the Mi Account Unlock Tool. Here is a link to the Mi Account Unlock download file (the password required to unpack the .rar file that downloads is ourflashfile.com).
JUST IN CASE: THE MOST IMPORTANT TOOL
** Disclaimer ** You may not need this section, but if you run into problems (like I did) this is your salvation.
After a few failed attempts at rooting my Redmi K20 Pro, I flashed my device and found myself needing to unlock the bootloader (again). However, when I tried, I ran into an error message that read "you must wait 30 days before unlocking another device." Some of you have run into this problem if you accidentally lock your device while using Xiaomi ADB/Fastboot Tools or TOOL ALL IN ONE (discussed later in this guide). Luckily, I found a thread by Jumundz (LINK) that indicated that an older version of MiFlash Unlocker (version 2.2.406.5) would still unlock my device. Thankfully it did!
GET THE STUFF YOU NEED
There are several sites that suggest to offer the best way to root your device. I have tried many of them and very few have worked (it's possible that I messed up the process somewhere). Whatever... this worked for me...
Generally, I followed this guide posted on AndroidInfoTech.com. I am, however, making some recommended changes.
XIAOMI USB DRIVERS
Start by getting the USB drivers. XiaomiBuzz has a pretty comprehensive list of all Xiaomi phones and their respective USB drivers (HERE). But, here is a link to the Xiaomi Redmi K20 Pro USB Driver Package for Windows 7/8/8.1/10 (32/64-bit). Scroll down and select the download link.
Alternatively, you could download the Xiaomi Mi PC Suite through mi.com and install the drivers through that program. The version I used was 2.2.0.7032_2717.
Go ahead and install the Xiaomi USB drivers.
ADB & FASTBOOT
Next you'll need to setup ADB & Fastboot. You must have USB Debugging enabled for either of these platforms to work properly. See above for instructions on USB Debugging. Both ADB and Fastboot are utilized through the command line, so I was confused me for the longest time on when to use each one. In fact, I had trouble getting ADB to work, but Fastboot worked fine. Turns out the reverse is more common (people tend to have problems with Fastboot, but not ADB).
Here's the difference:
ADB: This is the platform that you can use when your phone is turned on normally (booted into the system). So, if you can see your your normal phone screens, then ADB will work.
FASTBOOT: Note that you can still use Fastboot when your phone is turned on normally, BUT you cannot use ADB when your phone is in Fastboot mode.
Get the latest ADB Driver Installer from miui.blog. This will install ADB and Fastboot. The current version of the ADB Driver Installer (for me) was 1.4.3. (Alternative download through Mega.nz).
Alternatively (and I recommend this instead), you can get the Android Platform Tools Pack for Windows which comes with the Google USB drivers, ADB, Fastboot, and the ADB/Fastboot drivers. Download it from miui.blog here, or through Mega.nz here.
Go ahead and install the file package you have chosen. Once installed, ADB and Fastboot should be able to be used universally (from anywhere on your PC). Just know that many installation guides suggest installing ADB into a special folder on your C: drive which is fine too. We will come back to this folder to run some commands later in the guide.
TWRP
You'll need TWRP which is a recovery (or "temp") operating system that will run on your phone when you're attempting to root your device. However, TWRP doesn't have an official version specific to the Redmi K20 Pro. Luckily, XDA Member madsponge26 has a list of TWRP options that will work for the Redmi K20 Pro in this thread. I recommend going with the TWRP Auto Install option. You can also download a compatible TWRP image from androidfilehost.com. Here's a link to version-3.3.1-13-raphael.
Once downloaded, extract the .zip file. It should contain 5 or 6 files. Copy all of the files and paste them into the ADB folder (if you're sticking with my recommendation, it will be the "platform-tools" folder). When you copy-and-paste these files, it may ask you if you want to replace some files with the same names. That's fine (they're the same). Just click "Yes." If you downloaded the TWRP image separately (say, from androidfilehost.com), just copy the twrp.img file into the same folder.
MAGISK
Next download Magisk.zip from the official Magisk github.com page. The latest version (for me) was Magisk v19.4. Don't bother unzipping it. This .zip file will be placed (as a .zip file) onto your phone.
DISABLE FORCE ENCRYPTION TREBLE
Also download Disable-Force-Encryption-Treble.zip. Like Magisk.zip, don't bother unzipping this file because you're going to place it (as a .zip file) onto your phone. Here's a Dropbox link to directly download the file. Otherwise you can download it from Androidfilehost.com.
FLASHING TWRP & ROOTING
Alright, you got all the software tools and now we're ready to proceed with flashing TWRP and Magisk.
With your phone powered on normally, plug your device into your computer with the USB cable.
Pull down on the screen to display the notifications. One of them should read "Android System" and indicate how the phone is interacting with your computer as a connected device. Switch it to "File Transfer." Your phone should now show up as a drive on your computer.
Open the "Redmi K20 Pro" drive on your computer and then open the "Internal shared storage" folder (it should be the only folder).
Drag and drop the Magisk.zip and the Disable-Force-Encryption-Treble.zip into that folder.
**SIDE NOTE: Some guides suggest that you wait until you're in TWRP to transfer these files. That's fine. To do so, wait until you're in the TWRP interface and then select "Mount" and "Enable MTP." Your phone's internal storage should appear as a device on your computer and you can then transfer the .zips.
Once transferred, unplug your phone from the computer and power it off.
Enter into Fastboot mode by pressing and and holding down the Volume Down button and the Power button at the same time. It may take several seconds. It will vibrate and then boot your phone into Fastboot mode.
Next, connect your phone to your computer with the USB cable.
Once you connect your phone to the computer via USB, you should hear the computer recognize the phone but you may not see it show up as a drive. That's okay.
Go to your computer and open a command line interface in the ADB folder (if you're sticking with my recommendation, it will be the "platform-tools" folder).
**NOTE: If you chose the Auto Install option of TWRP, you can simply double-click the file "flash_twrp.bat" and then skip to the next section (TWRP INTERFACE).
**TRICK: Go to the folder where you have the ADB file adb.exe and click in the file pathway (where it says "C:\Users\Username\Downloads\platform-tools_r29.0.4-windows\platform-tools" or whatever). Highlight and delete that file pathway, and instead type "cmd". Hit enter and it will open a terminal window already in the proper directory.
**SIDE NOTE: If you installed ADB/Fastboot universally, you can simply open the command line interface by clicking on Start and typing "cmd" to open a terminal window. Once in the terminal window, you can "cd" or change directory to the one where you have ADB. Also, you can use Powershell, but you may need to preference each Fastboot command with "./."
In that terminal window, make sure you're in the folder with adb.exe and then type this command:
fastboot devices
This command looks to make sure that the Fastboot platform recognizes your device. Next to "Fastboot Devices," you should see a series of numbers and letters. That series of numbers and letters is your phone identifier.. If you do not see any numbers/letters, then Fastboot does not see your phone and you need to troubleshoot the situation.
Next, type in the following command:
fastboot flash recovery twrp.img
What this is doing is identifying what platform to use (fastboot), telling it what you want to do (flash), in which directory you want to perform that action (recovery), and what file to use to flash it (twrp.img). It is important to note that, depending on how you installed TWRP, the .IMG file may be called "recovery.img" or "twrp.img" or some variation of the TWRP version number. You can either rename the file to "twrp.img" or you can type in the entire filename.
Once you hit enter, it will read something like:
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 0.254s]
finished. total time: 1.696s
Once it's finished, enter this command to boot into the temporary TWRP recovery operating system:
fastboot boot twrp.img
Once you hit enter, it will read something like:
downloading 'boot.img'...
OKAY [ 1.428s]
booting...
OKAY [ 0.138s]
finished. total time: 1.566s
TWRP INTERFACE
Unplug your phone from the USB. The screen will go black and you may see the "Redmi" logo come on the screen. After a few seconds, the TWRP title page will appear. Once the TWRP operating system powers on, you may be presented with the option to enter a PIN code (if you previously had one on your phone) or a passcode. Enter the PIN or code to get into the TWRP interface.
Once in TWRP, you will have several options. Click "Install" and scroll to the bottom of the file list to find the magisk.zip that you transferred onto your phone. Go ahead and swipe right to install it. Once the installation is complete, click "Reboot System" to power the phone back on normally.
That's it. Your Redmi K20 Pro should now be rooted.
If there are any problems, start the process over from the Fastboot interface on your computer (where you flashed TWRP onto your phone with "fastboot flash recovery twrp.img"). Go through the same process, but before you install the Magisk.zip, first install the Disable-Force-Encryption-Treble.zip.
If this was helpful, please consider buying me a beer!
Bitcoin Address: 17p3sW8hG5ndZqAuoDQiUE99iHwBZss6UK
Bitcoin QR Code:
________________________________________
ALL TOOLS FROM THE ABOVE GUIDE
ALL IN ONE Tool: ALL IN ONE Tool
Alternate Download: (mediafire alternative link)
Xiaomi ADB Fastboot Tools:Xiaomi ADB Fastboot Tools v2.3.1
Mi Flash Unlock: miflash_unlock-en-3.5.719.27.zip (just the version that I used)
Mi Flash Unlock (latest version): official download site
XiaoMiTool V2 (link to download latest version): (https://www.xiaomitool.com/V2/#download).
Mi Account Unlock Tool: mediafire download (password: ourflashfile.com)
MiFlash Unlocker 2.2.406.5: mediafire download
Alternate Download: androidfiles.host download
XIAOMI USB Drivers: Xiaomi Redmi K20 Pro USB Driver Package for Windows 7/8/8.1/10 (32/64-bit)
For ADB/FASTBOOT get...
Android Platform Tools Pack for Windows: download from miui.blog (includes: Google USB drivers, ADB, Fastboot, and the ADB/Fastboot drivers)
Alternate Download: Mega.nz download link.
TWRP Auto Install (Mega.nz link): TWRP Auto Install
TWRP 3.3.1-13-Rapheal: androidfilehost.com link
Magisk.zip: Magisk v19.4
Magisk.zip (latest version): official download site
Disable-Force-Encryption-Treble.zip: "]Dropbox direct download link
for MI 9T PRO to?
Hi guys,
You know if this guide works with the European rom 10.3.3?
Thanks
Ekil said:
Hi guys,
You know if this guide works with the European rom 10.3.3?
Thanks
Click to expand...
Click to collapse
This should work but realistically all you really need to do is get all the drivers than go ahead and use mi flash tool to go to 10.3.16 fastboot Rom, can be found at mifirm, then go ahead and flash it make sure to select clean all, NOT clean all and Lock. (it's selected by default). Then proceed to install twrp, and flash any Rom you like, there are some modules for getting back nfc and Gpay so look around for them on here and boom you're all set.
Make sure you have an unlocked bootloader first obviously, after that it's relatively simple to install twrp, and after that it's smooth sailing. You just can't flash on stock European firmware as all these ROMs are based on the Chinese or Indian firmwares and vendors, and as a result will brick your phone,if you try to flash on 10.3.3. Trust me I've done it before and it's not fun.
Good luck :fingers-crossed:
fast9000 said:
This should work but realistically all you really need to do is get all the drivers than go ahead and use mi flash tool to go to 10.3.16 fastboot Rom, can be found at mifirm, then go ahead and flash it make sure to select clean all, NOT clean all and Lock. (it's selected by default). Then proceed to install twrp, and flash any Rom you like, there are some modules for getting back nfc and Gpay so look around for them on here and boom you're all set.
Make sure you have an unlocked bootloader first obviously, after that it's relatively simple to install twrp, and after that it's smooth sailing. You just can't flash on stock European firmware as all these ROMs are based on the Chinese or Indian firmwares and vendors, and as a result will brick your phone,if you try to flash on 10.3.3. Trust me I've done it before and it's not fun.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Hi!
Thanks for the detailed answer, I'll try it on the weekend ✌?
Hi, could you please list the exact and only set of tools you used to unlock your phone and install 3rd party ROMs?
Like list them step wise
1.
2.
3.
...
Thanks in advance!
ntmalol said:
Hi, could you please list the exact and only set of tools you used to unlock your phone and install 3rd party ROMs?
Like list them step wise
1.
2.
3.
...
Thanks in advance!
Click to expand...
Click to collapse
Well you should realistically read the forums but this is basically what I did
1. Unlock Bootloader using official mi unlock tool, (make an acc. wait a week or so)
2. Get the mi flash tool preferably latest, download fastboot Rom CN 10.3.16 from mifirm (Google it)
3.Go to fastboot mode in phone plug it in, press refresh for port to be detected, extract the mifirm Rom to desktop select the second folder before images option
4. Flash the fastboot Rom make sure to select clean all, DO NOT FLASH CLEAN ALL AND LOCK. (Will brick your phone and you'll be sticked with a locked bootloader)
5. Flash process takes 5 mins roughly, boot in setup lockscreen pass remember it for twrp setup.
6. Flash twrp via fastboot or adb, use the raphael variant latest found on the forum
7. Boot into twrp and enter screen lock to decrypt phone
8. Download any Rom and GAPPS, flash them and you should boot just fine.
Proceed to install magisk, and any other modules you want (vanced, Gpay, etc)
There is a 10.3.17 version for Chinese fastboot Rom available not sure of its compatibility so don't bother just stick to 10.3.16
Very simple once you have an unlocked bootloader just be careful when using the mi flash tool.
Good luck :good:
fast9000 said:
Well you should realistically read the forums but this is basically what I did
1. Unlock Bootloader using official mi unlock tool, (make an acc. wait a week or so)
2. Get the mi flash tool preferably latest, download fastboot Rom CN 10.3.16 from mifirm (Google it)
3.Go to fastboot mode in phone plug it in, press refresh for port to be detected, extract the mifirm Rom to desktop select the second folder before images option
4. Flash the fastboot Rom make sure to select clean all, DO NOT FLASH CLEAN ALL AND LOCK. (Will brick your phone and you'll be sticked with a locked bootloader)
5. Flash process takes 5 mins roughly, boot in setup lockscreen pass remember it for twrp setup.
6. Flash twrp via fastboot or adb, use the raphael variant latest found on the forum
7. Boot into twrp and enter screen lock to decrypt phone
8. Download any Rom and GAPPS, flash them and you should boot just fine.
Proceed to install magisk, and any other modules you want (vanced, Gpay, etc)
There is a 10.3.17 version for Chinese fastboot Rom available not sure of its compatibility so don't bother just stick to 10.3.16
Very simple once you have an unlocked bootloader just be careful when using the mi flash tool.
Good luck :good:
Click to expand...
Click to collapse
I used CN 10.3.17 version and works fine.
Not working?
Hey, i tried doing this but the phone does not boot into TWRP after i send
fastboot boot "C:\Users\loren\Desktop\Root Mi9T\twrp-3.3.1-13-raphael-mauronofrio.img"
Click to expand...
Click to collapse
Instead, it reboots to system, then when i reboot it again it does a couple of bootloops then enters Mi Recovery; to get it to work again i have to wipe all data.
Any ideas? I'm on MIUI 10.3.2.0 EU
---------- Post added at 06:10 PM ---------- Previous post was at 05:51 PM ----------
Bidishake said:
Hey, i tried doing this but the phone does not boot into TWRP after i send
Instead, it reboots to system, then when i reboot it again it does a couple of bootloops then enters Mi Recovery; to get it to work again i have to wipe all data.
Any ideas? I'm on MIUI 10.3.2.0 EU
Click to expand...
Click to collapse
Nevermind, i fixed it - instead of sending that i sent a simple fastboot reboot while pressing volume up. Booted into TWRP, installed disable-encryption and magisk, cleaned cache, and rebooted like a charm.
Thank you for the guide!
I tried to flash twrp on my mi9 t pro miui 10.3.2 global ( for some reason that's the latest ota i got don't know if its a fake rom ) , but can't get to recovery , i tried some versions of twrp but can't get to it with vol + and power button. I get 1st logo than screen fades to black , 1 time it took me to miui recovery.
By the way the miui version im on don't have the option to manually update ( manually select the update zip ),
Does this make it a fake rom?
Also if i try to install from the latest package from the updarer app can it fix my missing miui recovery or brick my phone?
Don't use XiaomiTools v2, my OS was corrupted and stuck at Mi logo after attempting to unlock bootloader and flash TWRP recovery.
Better to do so using official mi unlock to unlock bootloader and ADB fastoot to flash TWRP
I used xiaomi tool v2 to unlock boolader, install twrp and xiaomi eu beta (9.10.17). The tool did it all for me, no drivers, no adb no commands used, nothing else but the tool (xiaomi mi 9t pro eea, windows 10)
Try this for MIUI 11
Install the ADB-Fastboot USB Driver.
Unlock the bootloader of your phone.
Flash TWRP on Redmi K20 Pro / Mi 9T Pro. You may also use Wzsx150’s TWRP if you want; it’s in Chinese tho.
Download Xiaomi.eu MIUI 11 ROM from the link above.
Reboot your phone to the TWRP Recovery mode.
Choose Wipe > Format Data then type Yes to confirm.
Copy the Xiaomi.eu MIUI 11 Zip file to your phone.
Choose Install > locate the ROM Zip file > Swipe to confirm flash.
Choose Reboot > System.
Set up Google Account and you are good to go.
https://miui.blog/redmi-k20/xiaomi-eu-miui-11-redmi-k20-pro-mi-9t-pro
It would be nice if this worked for me........followed every single step and it will not boot into TWRP, it either gets stuck in a boot loop or it goes to the build in MiRecovery, and to get around this i need to force wipe the phone with MiRecovery, i quite literally am not allowed to install TWRP so i gotta go the other route to install Magisk and root my phone.......on EU version of the K20 pro if anybody else is having this issue or knows a fix.
I can't boot into TWRP.
Bootloader is unlocked.
I tried both TWRP, auto Install and version-3.3.1-13-raphael. Both install with "OK". On any of them when I send fastboot boot twrp.img I get again OK's, the screen goes black and it just stay there... any ideas? thanks!
Edit: yesterday I installed OTA update and then I did the bootloader unlock. I discovered in settings that my USB developer was not enabled (disabled after update/or unlock) - could this be a reason for TWRP not working?
Thanks for the guide. Couldn't install Magisk 20.1 via "TWRP 3.3.1-22 Unofficial by mauronofrio", however, was able to do it through TWRP 3.3.1-21.
K20 Pro India on MIUI 11.0.1.0.
Note: in the command 'fastboot flash recovery twrp.img' I thought 'recovery' was the source (computer) folder, but it was actually specifying the folder in the destination (phone).
scarmage said:
Thanks for the guide. Couldn't install Magisk 20.1 via "TWRP 3.3.1-22 Unofficial by mauronofrio", however, was able to do it through TWRP 3.3.1-21.
K20 Pro India on MIUI 11.0.1.0.
Note: in the command 'fastboot flash recovery twrp.img' I thought 'recovery' was the source (computer) folder, but it was actually specifying the folder in the destination (phone).
Click to expand...
Click to collapse
intersting :what you mean by ##Note: in the command 'fastboot flash recovery twrp.img' I thought 'recovery' was the source (computer) folder, but it was actually specifying the folder in the destination (phone).[/QUOTE]
## i do as always flash the twrp via cmd
1- fastboot devices
2- fast flash recovery " recoveryname.img "
3- fastboot reboot like that
what source you ?
The OP does a great job of explaining what each command does. If you're used to DOS commands, then when you issue a command that has a file name (eg: copy), you would specify a 'source directory' and a 'destination directory'. If the command contains only a single directory, then you won't get to know whether it's supposed to be a source directory or destination, unless it's specified explicitly. That's what I meant. But I guess if you know your way around android adb commands and such, you wouldn't have that confusion. I'm kinda new to this, so it wasn't obvious to me.
Antidote03 said:
intersting :what you mean by ##Note: in the command 'fastboot flash recovery twrp.img' I thought 'recovery' was the source (computer) folder, but it was actually specifying the folder in the destination (phone).
Click to expand...
Click to collapse
Don´t resolved
My phone is also like this, asks the 30 days so I can solve the brick, tried mi unlock 2.2.406.5 but it also did not work. Someone help, I don't want to wait 30 days.When I take the internet cable to try tbm, it says error unknown (-1)
I am trying to unlock an Android phone that has stopped taking the correct password after a auto-restart. I know the PIN, I have not changed it in a long while. The phone stopped accepting the PIN after the sudden auto-restart so I am just clueless what may work. Hard reset is not an option for this device without backing up the data so willing to try anything that may help.
Additional information:
1. The phone does not have USB debugging enabled.
2. It is recognized by ADB only in sideload mode.
3. When I try to get into Recovery mode pressing volume up and power button, it goes directly to the black screen that shows image of a phone and USB cable.
4. I have not been able to get to the stock recovery screen where different options like mounting can be chosen.
Any suggestion or guidance would be hugely appreciated. Thanks a ton for your time.
Thank you.
This is just brainstorming not a tutorial!
i don't know if it works like this, but you can try..
requirements
- stock ROM (in case you brick device)
- magisk manager (in case twrp does not work)
- AIK from osm0sis
- Qualcomm HS-USB QDLoader 9008 Driver
- fastboot_edl.7z
- twrp-3.3.1-0-mido.img (or ZCX TWRP from cofface)
- Appender-v4-rec.zip
- QSaharaServer.exe
- fh_loader.exe
- prog_emmc_firehose_8953_ddr.mbn
- splash.img from xaacnz
steps
- prepare twrp.img (you must patch twrp manually)
- prepare splash.img
- prepare hack_splash.xml (tricky/dangerous)
- prepare twrp.xml (tricky/dangerous)
- install qualcomm drivers
- boot in EDL mode from fastboot
- check com port
- initialize firehose connection with QSaharaServer.exe
- flash splash.img with fh_loader.exe
- flash twrp.img with fh_loader.exe
- reboot into recovery
- check if twrp is able to decrypt userdata
if decryption unsuccessful, you can't backup data. but you could still enable usb-debugging even with root permissions by patching default.prop
- patch boot.img with magisk manager (set advanced - keep force encryption)
- unpack boot.img with AIK
- enable usb-debugging in default.prop
- repack, rename to boot.emmc.win
- restore boot.emmc.win from twrp
- install Appender-v4.zip
- reboot
- adb root
- adb pull /dev/block/dm-0
you might find this confusing, it is! do not try anything above without knowing what you do! i don't own this device. nothing is tested. i can't write tutorial with exact steps, this is your task. You are the one who will figure out solution and write tutorial. we can just assist and answer questions (you can ask any question for each single step, one after one)
after all, there is no guarantee it works for your device. also please note @xaacnz is not available and won't help on this.
there might be easier methods i don't know, please do your own research how to temporary by-pass or unlock bootloader without permission from xiaomi, there are plenty much tutorials for QFIL / EDL mode for other devices, maybe one of this methods works
if you decide to continue, be aware this is last option only and there might no way back to recover your data..
please read
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Bypass bootloader lock of Redmi 5A(riva) without permission from xiaomi
the tricky/dangerous part is to find the right offsets and sizes for partitions. you might get some info from fastboot getvar all
Thank you for your reply! These steps are indeed a overwhelming for me but I can try one step at a time.
I was thinking of a basic solution like using Aroma File Manager to delete lock-information-storing files from the device.
However, when I reboot into recover mode it takes me directly to a screen that looks like this: https://i.ytimg.com/vi/AJICnDxnXEo/maxresdefault.jpg
I cant find a recovery page like this one which may allow me to install Aroma from SD card: https://i.ytimg.com/vi/0zntvnVEIYQ/hqdefault.jpg
I was wondering is flashing an OTA image from adb may solve this. The device is recognized by adb only in sideload mode.
If flashing a new OTA image can take me to recovery menu that allows installing Aroma from SD card perhaps that will work?
Sorry if these questions are too basic for you. I have no real technical knowledge on these stuff. Just trying to learn from scratch to save data on the device.
Thank you so much for your time.
aIecxs said:
This is just brainstorming not a tutorial!
i don't know if it works like this, but you can try..
requirements
- stock ROM (in case you brick device)
- magisk manager (in case twrp does not work)
- AIK from osm0sis
- Qualcomm HS-USB QDLoader 9008 Driver
- fastboot_edl.7z
- twrp-3.3.1-0-mido.img
- Appender-v4-rec.zip
- QSaharaServer.exe
- fh_loader.exe
- prog_emmc_firehose for your device
- splash.img from xaacnz
steps
- prepare twrp.img (you must patch twrp manually)
- prepare hack_splash.xml (tricky/dangerous)
- prepare twrp.xml (tricky/dangerous)
- install qualcomm drivers
- boot in EDL mode from fastboot
- check com port
- initialize firehose connection with QSaharaServer.exe
- flash splash.img with fh_loader.exe
- flash twrp.img with fh_loader.exe
- reboot into recovery
- check if twrp is able to decrypt userdata
if decryption unsuccessful, you can't backup data. but you could still enable usb-debugging even with root permissions by patching default.prop
- patch boot.img with magisk manager (set advanced - keep force encryption)
- unpack boot.img with AIK
- enable usb-debugging in default.prop
- repack, rename to boot.emmc.win
- restore boot.emmc.win from twrp
- install Appender-v4.zip
- reboot
- adb root
- adb pull /dev/block/dm-0
you might find this confusing, it is! do not try anything above without knowing what you do! i don't own this device. nothing is tested. i can't write tutorial with exact steps, this is your task. You are the one who will figure out solution and write tutorial. we can just assist and answer questions (you can ask any question for each single step, one after one)
after all, there is no guarantee it works for your device. also please note @xaacnz is not available and won't help on this.
there might be easier methods i don't know, please do your own research how to temporary by-pass or unlock bootloader without permission from xiaomi, there are plenty much turorials for QFIL / EDL mode for other devices, maybe one of this methods works
if you decide to continue, be aware this is last option only and there might no way back to recover your data..
please read
https://github.com/alephsecurity/firehorse
https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381
the tricky/dangerous part is to find the right offsets and sizes for partitions. you might get some info from fastboot getvar all
Click to expand...
Click to collapse
there is no usual recovery for xiaomi. even if, you can't install aromafm from stock recovery because only oem signed files accepted. you can try via sideload you will see it fails.
i don't think OTA will fix anything, but of course you can try. i will meanwhile prepare xml files for you, but give me time.. i am a newbie to this, too.. maybe on weekend i have time
i am not sure if this method does wipe data (i can not see the "erasing userdata" message on this fastboot screenshot)
@BushraXiaomi
Is your RN4 with Qcom SoC or MTK (mido or nikel)?
Did you enable device encryption (did you have to enter password before the lock screen would appear)?
@Alecxs Thanks a lot again! Let me try out the codes you provided screenshot of. I will give you an update on what I see.
And I tried editing out the original block quotation. The changes are not being saved after repeated attempts. Sorry about that.
@Alecxs Thanks a lot again! Let me try out the codes you provided screenshot of. I will give you an update on what I see.
And I tried editing out the original block quotation. The changes are not being saved after repeated attempts. Sorry about that.
Mine is on QCom. And I did have an old lock screen password. I didn't change it but the phone suddenly stopped taking the correct PIN after an auto-restart.
mirfatif said:
@BushraXiaomi
Is your RN4 with Qcom SoC or MTK (mido or nikel)?
Did you enable device encryption (did you have to enter password before the lock screen would appear)?
Click to expand...
Click to collapse
@Alecxs so based on the discussion here I am guessing unlocking bootloader will result in the data getting erased
link: https://forum.xda-developers.com/moto-x/moto-x-qa/unlocking-bootloader-wipe-data-t2739564
BushraXiaomi said:
Mine is on QCom. And I did have an old lock screen password. I didn't change it but the phone suddenly stopped taking the correct PIN after an auto-restart.
Click to expand...
Click to collapse
Encryption is different than lock screen. I'm asking this because if your device is encrypted and the password is changed/corrupted/not working, it's almost certain that your data is not recoverable, even if you manage somehow to flash TWRP and/or unlock bootloader without wiping data.
---------- Post added at 06:25 PM ---------- Previous post was at 06:17 PM ----------
BushraXiaomi said:
@Alecxs so based on the discussion here I am guessing unlocking bootloader will result in the data getting erased
link: https://forum.xda-developers.com/moto-x/moto-x-qa/unlocking-bootloader-wipe-data-t2739564
Click to expand...
Click to collapse
Data wipe on unlocking bootloader is the expected behavior and Google strongly recommends this behavior to OEMs. However bootloader is not a part of Android (AOSP), so not all OEMs fulfill all requirements. And therefore there are very rare chances that unlocking may not erase data.
Secondly, as mentioned earlier, many Qualcomm devices (including a long list from Xiaomi) have an exploit in Emergency Download mode. EDL is a bootloader mode which operates even below the usually called bootloader (ABOOT; the one which provides "fastboot" protocol). It can be hacked to get a dump of whole storage chip or flash a partition e.g. recovery (TWRP) without going through proper channel of bootloader unlocking. Note that a locked botloader won't boot a custom "boot" or "recovery" partition which is not signed by OEM's private key (like TWRP is). It's part of Chain of Trust on Android devices.
However (somehow achieved) access to "userdata" partition will be of no use if the partition is encrypted as I explained. TWRP won't be able to decrypt it without correct PIN/password (if it was set). However if it wasn't encrypted or "default_password" was used for encryption (and not the one you set), data recovery is very probable.
I hope it clarifies the basic scenario for you.
There are few things that must be known:
1. Which soc? qcom or mtk, if mtk go to service centre and don't waste time here.
2. Do you have permission to unlock bootloader? If you have permission to unlock then you can easily just unlock, note that unlocking itself doesn't wipe data, it is wiped after it. There are some tricks you can do so that data is not wiped after unlock and you must search them on your own.
3. Is your device encrypted? If it is then which encryption FBE or FDE? If it is encrypted then most likely data can't be recovered.
If you have qcom soc, don't have permission to unlock bootloader then you can do this...
From what you said it looks like recovery is corrupted, you could try flashing stock recovery from *edl but stock recoveries are useless but you can still backup your important data maybe, I am not sure because I have not been into recoveries for past 4 years.
The following method is not tested for your device but might work since the bootloader bug might be present in your device too. Improving alecxs answer you can do this:
1. Grab twrp for your device
2. Append 4k blocks using this command on any Linux based distro or termux (Android app) or BusyBox 1.31.
Code:
printf '\x30\x83\x19\x89\x64' | dd of=/path/to/twrp.img ibs=4096 oflag=append conv=sync,notrunc
3. Flash the recovery using edl
4. Directly boot into recovery and see if it boots.
5. If it boots then delete password file of Android and boot into OS.
6. Password should be removed now.
*edl: you must learn to use edl
@mirfatif @saurabh6377 thanks to both of you! I was reading up to understand the steps suggested by @Alecxs
let me try out the different options suggested by you and I will let you know how it goes.
@mirfatif no I did not use any extra encryption apart from setting the regular lock screen
@saurabh6377 1. qcom
2. I dont think I have the permission. Never needed to check it until now and never needed to ask for the permission so guessing I don't have it by default
3. I didn't have any extra layer of encryption apart from the lock screen
so your device is most likely encrypted with FDE and default_password as a lot of older xiaomi devices. lets hope the issue is just with screen lock - however there is not really a good explanation (why unlocking screen fails) other than broken encryption. in such case your data is not recoverable.
please note xiaomi removed the fastboot edl command since oreo 8.1 and there might be downgrade protections, so do not update to later version than 8.0
Please just try to boot your device in EDL mode and report back
Hi all, just wanted to update you that I don't have any result yet. Reading up on each of the steps so I can execute as suggested. I will get back to you when I have some results. Thanks again
follow the link behind fastboot_edl.7z and try to boot into EDL mode with modified fastboot.exe
@Alecxs Just to double check, I am directly following the steps mentioned here: https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Is that ok? Doing this first before anything else?
yes. if it works, you can proceed with installing Qualcomm HS-USB QDLoader 9008 Driver (and tell us the COM port from windows device manager)
if fastboot_edl not working, you must find another way to boot into EDL aka shortcircuiting data pins on usb-connector (deep flash cable) or find a test point on the physical motherboard on youtube
found offsets and sizes for partitions in rawprogram0.xml
i have copied all required files from Xiaomi_Redmi_Note_4_V9.0.5.0.NCFMIEI_20171113.0000.00_Global_7.0_XFT and tried to patch the files. in the modified splash.img string SPLASH!! is replaced with HACKED!! hopefully this works. also i have patched default.prop to make adb insecure in case twrp does not work.
there are differences in files when appending manually or with Appender-v4-rec.zip, so actually i have flashed twrp-3.3.1-0-mido.img to another device (Redmi 5), patched with Appender-v4-rec.zip and created a copy of recovery partition afterwards. the result you can find in twrp-hack.zip (this is the only zip file you need)
for debugging purposes i have uploaded boot-insecure.zip and twrp-3.3.1-0-mido.zip which contains all three files: original, manually patched, patched with appender (you don't need this)
@Alecxs I am trying. Sorry I don't have any result yet This is so out of my depth, league, width etc. etc.
Buttttt I am committed to save the data so I will keep going over the steps you suggested until I feel confident to execute them. Really sorry for how slow I am being about it.
I really, really, really appreciate all your help. THANK YOU SO MUCH!
Hi All,
With the recent launch of LineageOS 18.1 I decided to take the plunge and get it installed on my fully stock Videotron/Freedom H915. Since I had to smash together info from a half dozen other threads, I figured I'd gather it all together here for folks with a Canadian phone trying to make this work.
Since I knew absolutely nothing coming into this, I'm going to go a little more detailed on this write-up. If you've been flashing ROMs since the old days of Cyanogenmod you can probably skim half of this.
Disclaimer : I'm not responsible for any bricked phones or other negative outcomes. This is what worked for me, but I'm far from being an expert. If you continue past this point you agree to take your time, do your reading, be responsible for your own device/actions and not hold me or the forum accountable for anything that might go wrong. You've been warned.
IMPORTANT NOTE #1
If you've picked up an H915 on ebay and you are intending to use it on a network other than the one it's SIM locked on, make sure you do the whole SIM unlock process on the stock ROM either before you get started at all, or once you've reverted to the vulnerable stock ROM after Step 1 below.
I actually use Telus as my provider and I wasted a bunch of time trying to figure out why I couldn't get signal because only the stock ROM will prompt you for a SIM Unlock code. Lineage will just sit there dumbly and not allow you to enable data.
Once you've unlocked the SIM it will stay unlocked from that point forward, just make sure to unlock it and verify your SIM is working with LTE on the stock ROM before you get started.
IMPORTANT NOTE #2
Use LGUP's "DUMP" feature to take a backup of ALL partitions on your phone before you start. If you're reading this thinking "I just bought this phone off ebay, there's nothing on it I care about", take the backup anyway. You never know when you might need a copy of the modem partitions or other things from your phone's original build. It came in super handy for me in troubleshooting the process. So go do a backup!
Current Issues:
If signal is too weak to connect to a tower (or non-existent), the OS tends to crash with a modem error. Still trying to figure this one out.
I think I can get this working without first jumping to US996 but haven't had a chance to verify that. If I do I'll update the thread.
Download Prerequisites
Links working as of 2021-06-29
LGUP with patch
Link
Working adb/fastboot environment
Instructions
Download
Fastboot Drivers
Link
Universal ADB Driver
Link
Videotron/Freedom H915 Android 7 (Nougat) version E - H91510e_00_VTR_CA_OP_1205.kdz
Link
USA General US996 Android 7 (Nougat) version F - US99610f_00_1205.kdz
Link
APK for Terminal Emulator
Link or Alternate Link
LG V20 Root Package Original (v4?)
Link
Old TWRP for Root Package
Link
Videotron/Freedom H915 Modem Partition Image
Link
Lineage Install Zip for H910 (grab the latest, I'm using lineage-18.1-20210506-nightly-h910-signed.zip which is already out of date)
Link
MindTheGapps
Link
(Optional, for rooting) Magisk
Link
Different Boot Modes
For those not familiar with these phones, there are three different "modes" the phone can boot into. Here's a quick reference on how to boot into each one.
Download Mode
This mode is used for pushing KDZ files or individual partition backups using LGUP
Turn Off Phone
Hold the Up-Volume Button
Insert USB-C Cable with other end already plugged into PC
Bootloader (aka Fastboot) Mode
The H915 doesn't come with this mode by default. If you try it, you'll just get battery charging. We'll be temporarily converting the phone to a US996 in order to use the DirtySanta exploit to replace the bootloader partition with a leaked Engineering aboot.
This mode is used with the fastboot tool to load the TWRP utility into the Recovery partition.
Turn Off Phone
Hold the Down-Volume Button
Insert USB-C Cable with other end already plugged into PC
Recovery Mode
The recovery mode on a stock phone is used to perform a factory reset. We will be using the Factory Reset a couple times with the stock ROMs, then replacing the contents of the recovery partition with the TWRP tool that allows us to format partitions, load partition images, and sideload apps and LineageOS itself.
Turn Off Phone
Hold the Down-Volume Button
Press and hold Power-On (rear fingerprint sensor/button). When LG Logo appears, release power button for 1 second then press and hold again
When "Factory Data Reset" appears, release all buttons
Press Volume Down to highlight "Yes" then press power button to select the option
Repeat for the confirmation
Note about flashing KDZ files using LGUP
You can flash KDZ files onto the phone using LGUP from two places - either with the phone in "Download Mode", or with the phone booted into the OS with the USB Options set to "File Transfer" and USB Debugging turned on.
The difference between these two is when it performs the OS compatibility check.
In Download Mode it's the code of the Download Mode partition that does the check. In the OS, it's the OS that does the check before booting to Download Mode and bypassing Download Mode's check.
Why is this important? Because when converting from one phone to another (Say, an H915 to a US996 like we do below), you initially can't flash the KDZ using LGUP's "Upgrade" function. You can only use "Partition DL" to replace the contents of partitions with the contents of the KDZ. This kind of works, but ends up with a phone that will sometimes identify as a H915 (in Download Mode) but sometimes identify as a US996 (in the OS). To clean it up, once you've done the Partition DL method, you can do it again from the OS and use the Upgrade method to get a really clean install.
It works going back the other way as well when you want to return to stock.
If this doesn't make sense, don't worry. You don't need to fully understand it to follow the instructions below, I just found it to be interesting info that didn't seem to appear in other threads.
Process Overview
Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
Enable Dev Options
Dump contents of US996 KDZ partitions over top of existing partitions
Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
Transfer files to the SDCard and install Terminal Emulator
Unlock the Bootloader using the DirtySanta exploit
Boot to old TWRP and install new TWRP
Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
Reboot to LineageOS
Actual Process
1 - Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
We need to be on Nougat for this to work, so if you're on Oreo you have to downgrade to Nougat before we begin. I chose a Nougat ROM for the H915 that's vulnerable to the DirtySanta exploit because I know it works and because I'm hoping in the future to be able to skip converting the phone to a US996 if possible.
Boot phone into Download Mode
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
When finished phone will reboot
1.5 - Do this if Step 1 Failed... Otherwise continue to Step 2
Depending on what's loaded on your phone when you start, it might complain about doing Step 1. This should allow us to bypass the issue and allow Step 1 to work. You can use this step if you've already converted the phone to another model as long as it's not bricked.
Boot phone into download mode
Launch LGIP with Patch
Select "PartitionDL" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK. When done it will reboot.
If it hangs or loops on reboot, boot into "Recovery Mode" (which at this point will Factory Reset the OS)
The phone boots into the OS
Quickly go through setup wizard. Skip as many things as possible.
Go Settings - General - About Phone - Software Info - Make sure it identifies as H91510e
Change the USB Option mode to "File Transfer"
Then repeat Step 1, but from inside the OS instead of in Download Mode
2 - Enable Dev Options and File Transfer Mode
We need these enabled after every time we flash the OS so that our LGUP and adb commands will work. You'll get used to doing these steps a bunch.
Quickly go through setup wizard. Skip as many things as possible.
Unplug USB-C cable
Swipe down from the top and change from USB Charging mode to File Transfer mode
Settings - General - About Phone - Software Info
Tap on Build Number many times until it unlocks Developer Mode
Go back 2 menus and enter the new "Developer Options" menus
Make sure "Enable OEM Unlock" is enabled
Enable "USB Debugging" (will be greyed out if USB-C cable is still attached)
Go back to main screen
Plug USB-C cable back in.
A pop-up will appear asking to Allow USB Debugging. Check the "Always Allow" box and tap OK
3 - Dump contents of US996 KDZ partitions over top of existing partition
The Videotron/Freedom KDZ has no Bootloader/Fastboot mode. If you try to enter bootloader mode you'll just end up charging the battery. So we have to cross-flash the US996 KDZ to get a phone with a bootloader which we can then replace with the engineering version using the DirtySanta exploit.
Boot phone into download mode
Launch LGUP with Patch
Select "PartitionDL" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK
When the phone boots back into the OS, repeat all of Step 2.
Note: If it asks for a password on startup, follow the "Boot to Recovery" steps and since
we don't have anything loaded in the recovery partition it will wipe/erase the phone
and remove the password.
4 - Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
As mentioned in the "Note about flashing KDZ files using LGUP" section above, after you use the PartitionDL method you get a kind of dirty phone image that doesn't always identify as its new model. To clean up, we repeat the process in Upgrade Mode, taking advantage of the fact that at least the OS now identifies as US996 even if Download Mode doesn't. After this, Download Mode will also identify as US996.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
When the phone boots back into the OS, repeat all of Step 2.
5 - Transfer files to the SDCard and install Terminal Emulator
We will need some files on the SDCard in the phone in order to install them, either inside the OS (in the case of Terminal Emulator), or later on from TWRP. The Terminal Emulator will be used for the DirtySanta exploit so we need to get that installed now.
Make sure the USB Connection is set to Data Transfer mode and copy the following files to the SDCard:
APK for Terminal Emulator
twrp-3.5.1_9-0-us996.img
h915freedommobilemodem.img
Enable installing apps from unknown sources by:
Settings - General - Fingerprints and Security - Unknown sources (turn it On)
Install Terminal Emulator:
Tools - File Manager
Choose "Allow" when prompted
Click the up-arrow next to "Internal Storage"
Choose SD Card
Scroll down and tap on jackpal.androidterm-1.0.70-71-minAPI4.apk
Install
6 - Unlock the Bootloader using the DirtySanta exploit
The US996 KDZ has a bootloader but it's locked. In order to unlock it we need to use the DirtySanta exploit to give us permissions to replace the Bootloader/Fastboot with a leaked engineering version.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Settings - General - About Phone - Software Info
Verify that Software Version lists as US99610f
Copy the twrp-3.0.2-1-us996.img file into the folder containing the LG V20 Root Package
Open a command prompt window and change to the folder containing the LG V20 Root Package and run "Step1.bat"
It will push multiple files to the phone and apply some patches/exploits.
This proces will take 5 minutes and put you out at an "elsa:/ $" prompt
At this "elsa:/ $" prompt in your command prompt window type the following:
run-as con
chmod 0777 /storage/emulated/0/*
On the phone, launch Terminal Emulator and run the following:
id
Verify that the string which comes back contains the string "context-u:r:untrusted_app".
If not, run Step1.bat again, else continue forward
Enter the follosing command into Terminal Emulator (be very careful to type it properly):
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If that command came back with an error, close and re-open Terminal Emulator and try again
The command should begin to patch another file. This will take 5 minutes and will return you to the "elsa:/ $" prompt in Terminal Emulator when it has finished
Open another command prompt to the same folder and run "Step2.bat"
This step will download backup copies of the boot and aboot partitions from the phone then boot the phone into bootloader/fastboot mode.
You'll know it worked if the first line at the top of the phone screen appears in red
In the command prompt window, run Step3.bat
It will flash boot1.img and the TWRP Recovery image multiple times then restart the phone
The phone will hang, no matter how long it's left. Wait 5 minutes (at least until the logo re-loads once) then do the following:
Unplug the USB-C cable
Remove the battery from the phone to turn it off
Replace the battery
Boot into Fastboot mode and run the following commands in your command prompt:
fastboot flash boot bootbackup.img
Remove the USB-C cable and battery to turn off the phone. Then replace the battery and enter Recovery Mode
The phone will show a big red exclamation mark saying "Your device is corrupt". This is normal. It will go away after a few seconds then boot into recovery. This error screen is the result of the engineering "aboot" image that was flashed to give us an unlocked bootloader and will always happen on boot.
7 - Boot to old TWRP and install new TWRP
The old version of TWRP recovery will load. Don't ask me why we can't just go straight to new TWRP above, it didn't work well when I tried it.
If it asks for a password to decrypt data, click Cancel
Swipe to allow modifications
Install - Select Storage - MicroSD Card - OK
Install Image - Scroll down and tap the "twrp-3.5.1_9-0-us996.img"
Select the Recovery partition and swipe to confirm flash
Back to main menu
Reboot - Recovery
8 - Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
The new version of TWRP will load:
Check the "Never show this screen during boot again" box
Swipe to allow modifications
Wipe - Format Data - type "yes" to continue
This is likely to fail the first time. Repeat it to properly format the data partition.
Go back to Main Menu - Wipe - Advanced Wipe - Select "Dalvik / ART Cache", "System", and "Cache"
Swipe to wipe
Back to main menu
Advanced - ADB Sideload
Plug in USB-C cable
Swipe to start sideload
In command prompt window on PC type the following:
adb sideload lineage-18.1-20210506-nightly-h910-signed.zip
When complete tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip
If you want to root the phone (completely optional, not necessary for this process), now is the time to do it. Tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload Magisk-v23.zip
Go back to main menu - Install - Install Image - tap the h915freedommobilemodem.img file
Select the Modem partition and swipe to confirm flash
Remove USB-C cable
9. Reboot to LineageOS
Go back to main menu - Reboot - System - Swipe to reboot
References where I got the info to make this tutorial
Official Lineage 18.1 for LG V20 Release Thread
LineageOS Wiki for H910
DirtySanta Bootloader Unlock and Root Guide (Original)
H910 Rooting Thread (Cross-flash H915 then DirtySanta to US996)
H915 Root, TWRP using DirtySanta [WorkingSignals]
Noob Friendly Root TWRP using DirtySanta
General info about Modem Hardware, Firmware, Radio Interface Layer
[Reserved]
thank you so much. i need it
Great job for writing a complete how-to guide!
Thank You, You saved my old V20 H915
hi have you been able to find a better modem?
btw i'm not able to decrypt under twrp, can you?
Just want to confirm, it's only guide wich works for me. But I have issues with modem:
1. When I tried to change mode of modem, "prefered network type", phone stayed in the loop of the kernel panic "modem crash"
2. It were difficult to revert changes back. Finally, safe mode (in order to get it, you need to press volume up and volume down in the same time, during LinageOS booting process) helped me - when I disabled airplan mode, I had 2-10 seconds until next kernel panic. And in ~10 attempts, I were able to finally switch modem's mode to GSM/WDCMA/LTE
3. I used this phone 3 days, and once the kernel panic (because of modem) happened again
Any ideas what to do with modem? Also, the picture "Your phone is corrupt" is not fan Any ideas how to change it?
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Riot54 said:
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Click to expand...
Click to collapse
This is normal. Flash a kernel that's patched for dirty santa OR, cover the proximity sensor on boot and keep it covered until boot is complete.
That worked, thanks.
After multiple attempts going back and forth with step 6, I finally did it! I might switch to Lighthouse or Arros but I wouldn't have gotten this far without your guide.