Related
<disclaimer> I take no credit for anything in this guide. A BIG Thanks goes out to @tennear, @Unjustified Dev, @DrakenFX and @Starvirus. They are the ones who figured out the process described below and provided the excellent LineageOS 14.1 ROM. I just wrote this all-in-one-guide because I think the information is way too cluttered and spread over these forums.</disclamer>
<disclaimer> If you're not 100% sure what you're about to do, please first scroll down to the bottom of this post to see a list of DON'T's, a few things you SHOULD ABSOLUTELY NOT DO if you want to keep using your device.</disclaimer>
After having had quite some phones (Moto Defy +, Oneplus One, Nexus 5x,...) and having flashed a lot of ROMs on them, I thought I had quite some experience in these matters. Alas. Unlike Oneplus, ZTE would rather not have users fiddling with their devices. There are also three versions of the Axon 7 called the A2017 (China), A2017G (Global) and A2017U (USA), each with some minute differences from the others. This makes unlocking BL, flashing a custom recovery and installing custom ROMs not so easy on this device.
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution. There's always a tiny chance this process bricks your device. By following this guide, you will lose all your data on your internal memory. Please backup before proceeding. The data on your SD card should be safe.
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4UVMBVpYdVwcnlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
15) Type "Fastboot oem unlock" and hit enter
16) Follow the instructions on your phone and use the volume and power buttons to confirm you want to unlock your bootloader
17) Boot into TWRP by holding both power and volume up button
18) Type "Wipe" and choose "Format Data"
NOTE: If you get a permissions denied issue, try doing these steps while your device is in TWRP.
C) Update bootstack, Install LineageOS 14.1 and update your TWRP to latest version
Q: Why do I need Lineage OS 14.1?
A: It's a custom ROM that's a lot smoother than any available stock rom for any of the Axon 7 versions. Aside from an audio bug (the speakers make a rattling noise when the volume is turned higher than 80-90%) it's perfect. You can however find quite some other decent ROMS here.
Q: Why do I need the latest TWRP?
A: Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone. Update it using the steps below.
1) Download the latest unofficial Lineage OS 14.1 ROM from here: https://www.androidfilehost.com/?fid=457095661767134540
2) Download the A2017G Nougat bootstack from here: https://www.androidfilehost.com/?fid=673368273298930583 (A2017U users: your bootstack is here
3) Download the latest TWRP .img from here: https://build.nethunter.com/twrp/zte/twrp-3.0.4-1-ailsa_ii.img
4) Download a Google Apps version from here: http://opengapps.org/?arch=arm64&api=7.1/ .You must use an ARM64 file since that is the type of the CPU in the Axon 7. You must use 7.1 Gapps since that's the android version Lineage OS 14.1. is based on. Which one you choose is up to you, the "smaller" you go the less google apps will be installed as stock. You can always download the ones you miss via the play store after having installed LineageOS
5) Put the bootstack, the LineageOS and the chosen Gapps zips on your MicroSD card. Also put the TWRP.img on there
6) Flash the A2017G Nougat bootstack: Flash -> select the bootstack file on the microSD card
7) Flash LineageOS 14.1, then flash the Gapps zip file (again via TWRP)
8) Update your TWRP recovery by choosing "Install" and then clicking "Install Image" (bottom right) and selecting the TWRP .img file
9) Wipe dalvik, cache and data
10) Reboot
11) Enjoy your phone
In the unlikely case that you're greeted by a screen that asks you for a password because your system is somehow encrypted, reboot to TWRP and format your data partition to ext4 instead of f2fs (wipe -> advanced)
If your phone doesn't pop up as QUSB_BULK in EDL, you probably installed the driver that came with the phone. The device will pop up below Ports (COM & LPT) on Device Manager as Qualcomm something-something USB device. Uninstall that driver and reinstall winUSB drivers through Zadig.
If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver
Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.
If LOS refuses to install and you get the error axon7.verify_trustzone, install the universal bootloader (A2017X_B15_UniversalBootloader) before the N Modem.
So, the steps after you get access to TWRO are: 1) Install univ. BL (A2017X_B15_... .zip); 2) Install A2017G_N_modem.zip; 3) Install LOS14.1 zip; 4) Optionally, install Gapps; 5) Flash TWRP img
DON'T's:
- DO NOT use the signed TWRP (3.0.2) to backup or restore, it might brick your device
- DO NOT use this guide when you're on locked stock nougat, you need to downgrade to Marshmallow first
- DO NOT flash the wrong N bootstack. There's a different version for G and U devices
- DO NOT use this guide if you're on an A2017 (Chinese) device
- DO NOT unplug your cable from your PC or Axon while axon7tool is doing it's magic
- DO NOT make a mistake or typo, it can be fatal
- DO NOT try flashing random zips or files or formatting this and that when your device doesn't act according to the guide, post your issue instead
- DO NOT wipe anything else than Data, Dalvik and Cache in TWRP
ADDITIONAL STEPS:
- You can opt to root your device by flashing the latest SuperSU zip file
- You can opt to upgrade your unofficial LineageOS to the latest official version to receive weekly OTA updates
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
PsyJoe said:
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
Click to expand...
Click to collapse
Both the aboot.img and the TWRP.img come from A2017U versions. For the moment, we do not know if there is any difference in the aboot file between A2017U and A2017G, but it's highly unlikely. @tennear sent me a tool to read the partitions on my A2017G and the result showed the partitions were the same as those in the A2017U model.
For the moment, there's only one TWRP version, made for A2017U, but it seems to work on all models. I quote tennear here:
tennear said:
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
Click to expand...
Click to collapse
I suspect nearly all bricks on A2017G devices happen when A2017G users use tenfar's tool to unlock the BL. There's a lot of margin for error, for example with the whole COM ports shizzle. I advise not to go down that route. I also advise against trying to flash a rooted image through TWRP without unlocking your bootloader. Especially the command "axon7root.exe -p 4 -b -r" (flashing both boot.img and recovery.img at the same time) seems to kill specifically A2017G devices, that seem to have an extra "DFU" mode, which the A2017 and A2017U devices don't seem to have. A2017G devices get stuck in that mode and there's no way to get them out again.
TL;DR I think the risk isn't in flashing TWRP, but in flashing both boot and recovery at the same time, in the axon7root tool and in flashing a rooted stock rom without unlocking BL.
Thank you for this one thread guide. Should make it a lot easier.
Maybe you can add a few words and links to the B03 files that allow a downgrade from higher versions.
You have a typo in step 14), should be adb not ab
Controllerboy said:
30) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
Click to expand...
Click to collapse
Hi,
So, the backup can be restored, even if we cancel the password? Isn't the backup encrypted than?
Also, when we do swipe to agree to modify the system partition, is flashing SuperSU enough to gain root?
I'm not so much interested in installing a custom ROM (yet) but do want a safe way to gain root.
Thanks for your time and efford,
Edit: And all this is safe (step A) when on B08?
Cheers,
/Cacti
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Znuf said:
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Click to expand...
Click to collapse
Hi,
Thanks Znuf, I'll give it a go then.
Cheerz,
/Cacti
Controllerboy said:
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QDL_BULK"
16) In command, type "axon7tool -r gpt" and hit enter
Click to expand...
Click to collapse
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
le_cactus said:
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
Click to expand...
Click to collapse
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Controllerboy said:
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Click to expand...
Click to collapse
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
le_cactus said:
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
Click to expand...
Click to collapse
I give up. Or at least at this computer.
Just to be sure, the QDL_BULK/QUSB__BULK, shoild it be an unknown device, one with a yellow exclamation mark? Or should I install a driver for it, and if so where do i find it? Google didn't help me out today
I'll try another pc, see if that does work.
Cheers,
/Cacti
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Hi,
i unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Thanks in advance
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Killerdog said:
I unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Click to expand...
Click to collapse
Here's the file from DrakenFX: http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Flash bootstack only once, then flash BO6 stock ZIP. In my experience it doesn't replace TWRP with stock recovery, even when you're not rooted.
DeJe63 said:
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Click to expand...
Click to collapse
Thanks for the tricks. I didn't know you could do all three commands at once. I'll update my guide.
Will this work for B08 or should I go all the way back to "B03 (or others)" ??
Tutorial looks good and simple, big thanks!
In general it works.
For some reason I was not able to update from DragenFX B06 to OTA B08. So I flashed stock recovery, stock B06, OTA B08 and just flashed back TWRP with axon7tool...and it worked. But it may be that I make some mistakes on the way to B08.
I was at BL unlock before.
Controllerboy said:
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Click to expand...
Click to collapse
Hi,
That worked flawlessly on my Win7 box, but I have general USB problems on that device. Got timeouts a few times during the axon7tool -r commands, so I don't dare doing a axon7tool -w command on that machine. So I stepped over to my Win10 x64 machine, but that machine it keeps identifying it as a "Qualcomm HS-USB QDLoader 9008 (COM3) device." :crying: axon7tool -r gives my a "Failed to connect"
Thanks for the help though, much appreciated.
Cheers,
/Cacti
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Controllerboy said:
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Click to expand...
Click to collapse
Thanks for the tips. I'll let you know how things work out.
Cheers,
/cacti
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)
Good Evening,
I have an Android Phone REDMI 6A from the licensed distributor in Indonesia.
The warranty for my phone already expired and I'm tried to Root my REDMI 6A.
I'm searching for the step to Root and here what I get:
1. I need to click 7 times in about to open developer option
2. Allow the USB Debugging
3. Do the unlock bootloader with Mi Unlock (I'm already success and when I'm reboot in below screen there is a text "unlocked"). But it's weird when I see another thread that say for the unlock we need permission from Xiaomi that needs xx days to unlocked legally. But in my case I don't need to wait for xx days.
4. The next step for root is I need to flash with Mi Flash Tools and here is the nightmare when I'm follow the steps and in the steps stated not tell to choose "clean all". In my case the choose for Mi Flash is default in "Clean and Lock" that you can see in the right down below from Mi Flash Tools App.
5. That's it. Flash is done with the option "Clean and Lock" the phone is reboot and Ohh my Goshhh..... the Phone is not working and screen display to Mi Recovery with error "MIUI Versions can't be installed in this device"
From what I read in many threads the situation I'm in is :
1. Flash wrong ROM that makes my Phones Bricked and the protection from Xiaomi is on
2. The bootloader that Unlocked now is Locked and that makes the USB Debugging off too
I'm already do this:
1. Used the SP Flash Tools v 5.1924 with information for SP Flash tool:
a. Download Agent : MTK_AllInOne_DA.bin or MTK_AllInOne_DA_4-19_-signed.bin
b. Scatter Loading files : MT6765_Android_scatter.txt from many ROM Fastboot (Global, China and Rusia)
c. auth_sv5.auth
2. Test in SP Flash Tools "Download" and click the download and then I'm hold volume + in my phone (the battery is disconnected) and then connect the phone use USB cable.
When I'm see the device manager Mediatek USB Port is appear but in SP Flash get error BROM error status_brom_cmd_send_da_fail (0xC0060005)
3. Test the "Format" option in SP Flash Tools with option "Manual Format Flash" and change the data needs from the scatter.txt:
a. Begin Address : 0x5588000
b. Format Length : 0x100000
3. Used Minimal ADB and Fastboot and use command:
a. ADB devices : not work --> I think it's because the usb debugging off. Before when I'm try this when my phone still on this command list the
detail of my devices
b. Fastboot devices : It's work when I can go to fastboot screen (it depends on luck when I'm try the SP Flash tools and I will modified it with
Volume - & Power before connect to PC with usb cable)
c. Fastboot oem device-info : not work
d. Fastboot unlock OEM : not work
e. Fastboot reboot : work but still stuck at Mi Recovery
4. Used Mi Phone Assistant (condition in Mi Recovery choose Connect with Mi Phone) and do the flash ROM used Global, China, and Rusia ROM and still not work.
It works for miui_HM6AGlobal_V11.0.7.0.PCBMIXM_755e2b7216_9.0 and in progress to 100 % but after reboot will stuck to Mi Recovery again.
5. Try Mi Unlock but it's not working
6. When I get to Fastboot sceen by luck I try this too:
a. Used Mi Flash 2017.4.25 with option "Clean All" used ROM (Global, China, Rusia) for flash. Click refresh and the devices is appear and when
click Flash (after fill the path ROM) it's error
b. Used ADB to know the status of my devices (locked bootloader, etc) with command fastboot oem device-info but error
I read if the condition is like this, I'm must flash it to original ROM or China Version. But please tell me how I do that?
I'm already searching and download many ROM (fastboot and recovery) but when used in Mi Phone Assistant to flash ROM it's still not working.
Please tell me if there is some way to restore my REDMI 6A to normal condition (no need for root first).
The condition I'm in now:
1. I have a Mi Account
2. Sometimes by luck I can get to Fastboot screen
Kindly appreciate if you can solve this problem.
Looks like you wiped or formatted your entire phone. I've been in this situation before (RIP my Lenovo A7000a). But i have some experience with SP flash tool.
1. Go to options and go to the download section, and enable USB checksum and storage checksum
2. Load the scatter file
3. Give a checkmark on everything from preloader to userdata
4. Format the phone on the format section(optional but recommended)
5. Then click the download button on download section (important: make sure you haven't plugged your phone)
6. Plug your phone to your PC
7. Wait until the flashing process is done
8. After the flashing process is done you're you will prompted with a green checkmark image
9. Done. It should boot and work properly
---------- Post added at 10:38 AM ---------- Previous post was at 10:18 AM ----------
There's a list of SP flash tool errors and how to solve it here. Maybe it will help you https://forum.hovatek.com/thread-439.html
Hello, If your bootloader is Unlocked, You can go to fastboot & type this command
fastboot erase recovery
fastboot flash recovery twrpname.img
Replace twrp name with name of custom recovery.
Now type : fastboot reboot recovery
Now it will boot in twrp , install any custom ROM from there.
PS: Already told, requires a Unlocked BL
I tried the following:
1. Unlock my bootloader by enabling developer options, enabling OEM unlock, power off the device, hold VOL+ and VOL- simultaniously while connecting a USB cable, and enabling the unlock.
A factory reset was triggered as described in various tutorials.
2. I set the A50 (SN-A505FN/DS) up without Google or Samsung Details.
3. I check, wether the OES unlock was still intact, which it was.
4. I enabled USB debugging and made sure my PC was allowed to do send adb commands.
5. I typed: adb reboot [fastboot, download] (tried both on macOS, Windows and Linux, drivers were installed on Windows via Kies, Samsung Switch and the download package)
6. In the download menu I typed: [fastboot, .\fastboot.exe] flash system <various images derived here: https://www.gadgetsay.com/best-custom-roms-for-samsung-a50/>
--> failed, because the only output was < waiting for any device >
7. Powered the phone of and entered the download mode as in 1.
8. Flashed TWRP from here https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a50-a50dd.3916199/ and later here https://forum.xda-developers.com/t/recovery-root-unofficial-twrp-3-4-0-0-for-galaxy-a50.4138313/
9. Tried to flash the GSI images => Boot loop.
10. Follwed these instructions: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A50 => Still boot loop.
What am I doing wrong? Various tutorials and videos like this one:
indicate that it shouldn't be too difficult.
Thanks in advance for any new idea!
Additional Info: In TWRP i had to resize the system partition after flashing lineage os because it was no longer ~5GB large but rather the size of the image. Afterwards I was able to install GAPPS.
Okay, once again, the answer is "don't be stupid" or at least "rtfm". I've read online, that the A50 doesn't have an a/b-slot so I always downloaded the a-only packages. These however don't work. The very first lineage os with a "b" in the filename (as shown in the video) worked.
CatorCanulis said:
I tried the following:
1. Unlock my bootloader by enabling developer options, enabling OEM unlock, power off the device, hold VOL+ and VOL- simultaniously while connecting a USB cable, and enabling the unlock.
A factory reset was triggered as described in various tutorials.
2. I set the A50 (SN-A505FN/DS) up without Google or Samsung Details.
3. I check, wether the OES unlock was still intact, which it was.
4. I enabled USB debugging and made sure my PC was allowed to do send adb commands.
5. I typed: adb reboot [fastboot, download] (tried both on macOS, Windows and Linux, drivers were installed on Windows via Kies, Samsung Switch and the download package)
6. In the download menu I typed: [fastboot, .\fastboot.exe] flash system <various images derived here: https://www.gadgetsay.com/best-custom-roms-for-samsung-a50/>
--> failed, because the only output was < waiting for any device >
7. Powered the phone of and entered the download mode as in 1.
8. Flashed TWRP from here https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a50-a50dd.3916199/ and later here https://forum.xda-developers.com/t/recovery-root-unofficial-twrp-3-4-0-0-for-galaxy-a50.4138313/
9. Tried to flash the GSI images => Boot loop.
10. Follwed these instructions: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A50 => Still boot loop.
What am I doing wrong? Various tutorials and videos like this one:
indicate that it shouldn't be too difficult.
Thanks in advance for any new idea!
Additional Info: In TWRP i had to resize the system partition after flashing lineage os because it was no longer ~5GB large but rather the size of the image. Afterwards I was able to install GAPPS.
Click to expand...
Click to collapse
dont use the twrp 3.4
use the 3.5
Cator Canulis said:
Okay, once again, the answer is "don't be stupid" or at least "rtfm". I've read online, that the A50 doesn't have an a/b-slot so I always downloaded the a-only packages. These however don't work. The very first lineage os with a "b" in the filename (as shown in the video) worked.
Click to expand...
Click to collapse
we should use arm64 ab because we have SaR device
N200 on OOS 12, can't seem to possibly ever enter fastboot mode. Whenever I try I get some screen with the only options as wipe device, reboot, power off and 'fastboot devices' on my computer no longer shows the phone. Also there is no longer an 'advanced reboot' option in OOS12 so I can't go that route either. Please help so I don't have to bin this thing
Looks like you're in recovery mode. Remember that you have to shut down your phone and hold both volume buttons and the power button while it's unplugged to enter fastboot mode. Alternatively, you can use the "adb reboot bootloader" command while your phone's booted up.
Also, you can't install LineageOS from OxygenOS 12 right now. You need to downgrade to the last version of OxygenOS 11 before installing a custom rom.
Hi, thank you for responding! I've dug in further and what's going on is the driver doesn't work in Windows in fastboot mode, only in ADB does the driver work so I am sort of stuck. I downloaded the OOS 11 zip but I can't figure out how to install it now, I don't have a 'System Update' area in settings that will let me apply the local zip. My update screen just says 'you are up to date' and gives no option to apply a local update. Any idea how to get to the local update setting to apply the OOS 11 zip? Thanks again!
EDIT: I've found a couple of applications that restore the 'local update' feature but now it either says verification failed (My Application2 app) or else the local update file is not shown (OPLocalUpdate_For_Android12.apk). I downloaded this file and put it in the root of the internal storage but it's not working:
NordOxygen_14.I.25_OTA_0250_all_2201171943_downgrade_347e133266814951.zip
Is this the right downgrade file? I have an N200 global. Thanks!
Edit 2: I'm now back on OOS 11! Yahoo! I used the guide here:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Back to my original issue though, I seem to be having driver issues with fastboot mode. I've tried a few USB ports & cords to no avail, do you have any thoughts on troubleshooting a fastboot problem? The device shows normally when plugged into Windows but when I do 'adb reboot bootloader' and the handset enters fastboot mode then I lose the driver and instead the device shows up under 'Other devices' as 'Android' with a yellow exclamation point. I tried installing OnePlus_USB_Drivers_Setup.exe but that didn't do anything, do you think I should boot Windows with driver signing disabled and try again?
You can usually force the OnePlus fastboot driver to install. I don't remember the exact steps, but I think that you have to right click on "Android" in Other devices, select Update Driver, select "Browse my computer for driver software", select "Let me pick from a list of device drivers on my computer", select the Android related category, and select Android Bootloader Interface. Accept all warnings.
If that doesn't work, you could also try the universal ADB driver, as that's what LineageOS recommends.
You probably don't need to disable driver signing.
Thank you for the replies, I was able to get the driver installed and I installed lineageOS per the offficial doc. Unfortunately I seem to have bricked the phone as it's stuck in fastboot mode and won't boot into recovery anymore
What I did was from here:
Install LineageOS on dre | LineageOS Wiki
wiki.lineageos.org
a) fastboot oem unlock
b) boot into custom lineageos recovery via fastboot - fastboot flash boot lineage-19.1-20221116-recovery-dre.img
c) sideload in copy-partitions-20220613-signed.zip
d) install lineageos
Any idea how to get recovery working again?
EDIT: I think I should specify this is an UNLOCKED N200 not a T-mobile one so I think the MSM tool doesn't apply
EDIT 2: I got it booted into LineageOS but now Wifi won't turn on, oh what a night of drama!!!
EDIT 3: I fixed that now too, I'm all set! Thank you!!!