Related
Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.
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!
Same steps as previous Xiaomi models
1- First officially apply to unlock bl
2 Download and flash twrp as needed
Be cautious when brushing the machine, at your own risk
RECOVERY information:
Name version: Redmi Note 9 Special Edition TWRP Chinese and English modified optimized version
File package name: TWRP-3.4.1B-Redmi Note 9.7z
Introduction:
The author synchronizes the latest source code of TWRP. In the omni environment, the official kernel file is used to write the device code.
Some bugs were fixed by modifying the source code, some functions were added and improved, and finally compiled.
Thanks for the enthusiastic engine oil test.
This RECOVERY is stable and practical, with various functions. The author has measured many times and recommended to use it when flashing. No major bugs have been found.
I haven't tested it comprehensively. I hope that if you find any bugs, please give me feedback in time. Thanks~~~~
Brushing is risky and requires careful operation. Brushing is a personal voluntary act, and the author does not bear any problems caused by brushing into this rec.
important:
1. This rec supports automatic decryption of data partitions, and encrypted data can be used normally under rec without formatting.
Please don't flash the unknown rec randomly, it may cause the data to be unable to be decrypted, and the data will be lost.
The official default is to encrypt the data for the lock screen password, and you need to enter the lock screen password to enter twrp.
2. Theoretically, this rec supports swiping into the official original full amount of cards, but will cover twrp.
3. Bootloader must be unlocked to flash into the third-party rec, please unlock BL.
4. Built-in root system / remove root function, through the root system, you can enable the system to obtain root permissions.
5. Function to prevent being overwritten by official rec (any one is enough): prevent overwriting of TWRP, root system, etc.
6. It is recommended to turn off the avb2.0 verification after the official package of the card is swiped, otherwise it may cause the system to be damaged due to the root boot.
7. If the boot prompt system is damaged due to root, etc., you can flash the boot.img on the fastboot line or flash the closed vbmeta to restore normal.
Please use my own one-click flashing tool to flash in, otherwise, there is a mess, don’t ask me
[Known bugs]:
1. There is a certain probability of entering the first screen of twrp card, forced restart, re-swipe or re-enter twrp should be able to solve.
Update on 2020.06.09:
1. Some optimizations
2. There is a certain probability of entering the first screen of twrp card, forced restart, re-swipe or re-enter twrp should be able to solve.
Content of the first edition of 2020.06.06:
1. Based on the twrp source code, I modified and adapted the Android 10 compilation system and named the version number as [3.4.1b] to show the difference, indicating the unofficial version number
2. Support dynamic partitioning of Android 10 system
3. Support Android 10 system data decryption (password is the lock screen password)
4. Adapt user space fastboot of Android 10 system,
5. Support card swipe official complete package
6. Support the card swipe magisk official card swipe package, you can also use twrp's built-in root system (magisk20.3)
7. Support FBE multi-user decryption, such as mobile phone avatar, application avatar and the like are multiple users. Data can be backed up normally by other users without decryption, solving the problem that some oils cannot be backed up
8. It is recommended to turn off the avb2.0 verification after the official package of the card is swiped, otherwise it may cause the system to be booted due to root and prompt system damage.
9. If the boot prompt system is damaged due to root, etc., you can flash boot.img on the fastboot line or flash vbmeta to turn off the verification to restore normal.
10. There is a certain probability that the first screen of the card will be swiped in after a certain probability, and it will be forced to restart and re-swipe it again.
The download file will be updated on the second floor
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Download link update
[MOD EDIT: URL REMOVED]
If you ROOT, you must turn off avb2.0 verification in TWRP, otherwise it is not the system
Unpacking your file does not work for me, I always get a "not supported compression method" error with 7 zip
MeinsEins said:
Unpacking your file does not work for me, I always get a "not supported compression method" error with 7 zip
Click to expand...
Click to collapse
Your decompression software is too old, I have uploaded a decompression compatible with the old version, please download again
czghzh said:
Your decompression software is too old, I have uploaded a decompression compatible with the old version, please download again
Click to expand...
Click to collapse
Thanks for updating, it worked now, but I don't think that my software was too old as I use the current (19.00) version of 7ip
is this ok to use it in redmi note 9s or pro sd variant series?
jhun3xx said:
is this ok to use it in redmi note 9s or pro sd variant series?
Click to expand...
Click to collapse
Impossible, please do not do this
MI Unlock doesn't see my phone when in fastboot mode.
Doesn't matter if I do it manually (power + vol down) or through "adb reboot fastboot".
Any solution?
Akitake said:
MI Unlock doesn't see my phone when in fastboot mode.
Doesn't matter if I do it manually (power + vol down) or through "adb reboot fastboot".
Any solution?
Click to expand...
Click to collapse
Have you tried to enable OEM unlocking, USB Debugging and add account to Mi Unlock Status on Developer Options?
awahok said:
Have you tried to enable OEM unlocking, USB Debugging and add account to Mi Unlock Status on Developer Options?
Click to expand...
Click to collapse
Yes I do, but I figured it out.
I had an unknown device in my device manager "Other Devices > Android", and it couldn't find drivers because I was using a slimmed down version of Windows 10, which also blocked Windows update & driver updates through windows servers.
Used another device which has stock Windows installed and works fine. I now just need to wait about 150 hours to be able to unlock c:
Thread closed due to GPL non-compliance. When ready to upload kernel source, PM me.
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL