Related
Dell Venue 7 BOOT PROBLEM
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
ManXXXX said:
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
Click to expand...
Click to collapse
You need to flash again the stock rom, the factory reset won't work.
You can found it here http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2 and flashing through fastboot
I don't know what frameworks-res.apk you used, but maybe you forgot set the right permissions, or maybe you took the files for other device.
DL VN 7
Is there some tutorial for flash with fastboot??, i never did it, and i don't want destroy some other..
Go here to Dell's opensource site.. http://opensource.dell.com/releases/...loper-edition/
Link
No working link
ManXXXX said:
No working link
Click to expand...
Click to collapse
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
ADB Driver
Isrks said:
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
Click to expand...
Click to collapse
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
ManXXXX said:
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
Click to expand...
Click to collapse
I found this around here, is for windows 8 but maybe useful for Windows 10
https://software.intel.com/en-us/android/articles/how-to-install-intel-usb-driver-for-android-devices-on-windows-8
ADB Driver
Nah nah this, i think ADB driver.
ManXXXX said:
Nah nah this, i think ADB driver.
Click to expand...
Click to collapse
unfortunately i don't have a computer with windows 10 so i can't solve easily.
i found this googling, so with a little of faith :fingers-crossed: , is the same error than yours http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opoit's for the OPO, but is about the same "intalling adb driver", so could work
in a dessesperate attempt, you can use the update usb drivers in "myKit_BATCH" typing "1" after typyng "ACCEPT"
I fixed it with 15 seconds installer!, i gng try to fix tablet
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
ManXXXX said:
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
Click to expand...
Click to collapse
Ahh that's add driver not recognize your tablet, I suppose that you connect in fastboot mode,
Try using the option of update the adb driver in Mykit_BATCH, you don't lose nothing trying.
Other option is trying the dell's method http://opensource.dell.com/releases/Venue_8_3830_CloverTrail_plus/developer-edition/Download the pdf file and read the instructions from page 2 to page 9 if still not working
here is the sdk tools for windows that the pdf wants
I downloaded SDK tools, i installed Google usb driver, because it say not installed, when it was installing it said: Disable adb driver, ineffectual, error code -1, but after install it work good, so i will test with this, when no i will try another way, that u wrote here
Finally, tried method, no work, finally, update ADB no working for me, cuz installation always fail, next one DELL method, working but i found problem, dell wrote update driver via google extra with codes, BUT
My first code: USB\VID_413C&PID_B119&REV_????, ????, i think there is something wrong
My second code: USB\VID_413C&PID_B119, i think this one is alright, but then up
Finally with dell next page i'm in!, but my kit no working, in every command shut down, so i using windows cmd, it working too
Mhm bruh, no i'm in flash system, sending 'system' awesome, but it's more than 2 minutes , when it will work, omg u r awesome
Bruh, yay, i did it, thq u r master <33
ManXXXX said:
Bruh, yay, i did it, thq u r master <33
Click to expand...
Click to collapse
Are you telling that the dell method works?
The good new is that your tablet is back (with some problems in the way but work, ). after all now you know how to flash through fastboot. If anyelse goes wrong again, you know what to do
NOTE: Maybe your want to replace the framework-res again, but only will work if is for your device. So i recomend that you modify your stock framework-res by yourself (you can use images or xmls from other sources to your framework-res, this should be safer) using apktool manually or a program (there are some of them in xda, choose your favorite )
Yay 50% of dell method worked, just 50% because Dell have tutorial for setting up ADB service, after it i used your tut, thanks, and believe me i will not test it NEVER again.
Good day
Permission to post
I was here to seek help on how to fix my sony xperia Z2
I was flashing my Z2 but accidentally I didn't notice that i click the wrong firmware
and my z2 is not booting. it said that failed to update the new system.
please help me I dont know what to do.
damulag1234 said:
Good day
Permission to post
I was here to seek help on how to fix my sony xperia Z2
I was flashing my Z2 but accidentally I didn't notice that i click the wrong firmware
and my z2 is not booting. it said that failed to update the new system.
please help me I dont know what to do.
Click to expand...
Click to collapse
Hi
Do Flash a New Rom of your Phone with Flashtools v 0.9.18.5
sєňţ ғяom тнe ҡıňɢ ♔ Z2
Sajad Askari said:
Hi
Do Flash a New Rom of your Phone with Flashtools v 0.9.18.5
sєňţ ғяom тнe ҡıňɢ ♔ Z2
Click to expand...
Click to collapse
my z2 is turned off and i cant open it to allow usb debugging sir,
what should I do? i think my z2 got brick
damulag1234 said:
my z2 is turned off and i cant open it to allow usb debugging sir,
what should I do? i think my z2 got brick
Click to expand...
Click to collapse
No problem
Just install Flashtools V 0.9.18.5
And install Your Drivers
And Do flash Your Rom
No need usb Debugging
Are You Can Flash Stock ROM?
sєňţ ғяom тнe ҡıňɢ ♔ Z2
Unless you've messed up the TA partition, our phones are pretty hard to brick. If you hold vol_up then plug in USB to your PC, it should boot into flash mode with a blue LED. That means you can use Flashtool to flash an FTF file to the phone, effectively factory program it.
Si_NZ said:
Unless you've messed up the TA partition, our phones are pretty hard to brick. If you hold vol_up then plug in USB to your PC, it should boot into flash mode with a blue LED. That means you can use Flashtool to flash an FTF file to the phone, effectively factory program it.
Click to expand...
Click to collapse
my z2 is turned off and i already flashed but i used a wrong firmware.
my z2 now is not opening or booting and it say The software update failed
what should i do?
damulag1234 said:
Good day
Permission to post
I was here to seek help on how to fix my sony xperia Z2
I was flashing my Z2 but accidentally I didn't notice that i click the wrong firmware
and my z2 is not booting. it said that failed to update the new system.
please help me I dont know what to do.
Click to expand...
Click to collapse
Hey, don't worry if you do these steps exactly then your phone will boot again normally and you can enter the recovery then flash any rom again and recover your phone from this brick
1- Download and install Minimal ADB and Fastboot from this link: https://www.androidfilehost.com/?fid=24521665358595410
2- Download and install Flashtool drivers from this link: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS41LTIwMTQwMzE4
Skip Step 2 if you already installed Flashtool Drivers that install with Flashtool if you have installed it.
3- Download the latest twrp recovery from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img
4- Move the twrp recovery that you have downloaded in step 3 to this Path C:\Program Files\Minimal ADB and Fastboot
5- Download this kernel from this link: https://drive.google.com/file/d/0Bwn7bAJ-USZjZzg0Q2I2RWlWa1U/view?pref=2&pli=1
6- Extract it then you will find boot.img take this file and move it too to this Path C:\Program Files\Minimal ADB and Fastboot
7- put your phone in fastboot mode by this way >> (Power off your phone completely then wait for 10 second then press and hold the volume up then connect your phone to the computer with usb cable while you are pressing and holding the volume up then the led will change it's color to blue.. that is the fastboot mode)
8- Now go to the Minimal ADB and Fastboot folder in that path (C:\Program Files\Minimal ADB and Fastboot) Press shift button from keyboard then press right click form mouse while pressing the shift button you will find an option [Open command window here] Press it.
9- In the command window write this command exactly: fastboot flash recovery twrp-3.0.2-0-sirius.img
10- Then write this command after it: fastboot flash boot boot.img
11- After it flashed successfully reboot your phone by writing this command: fastboot reboot then unplug the usb from the phone
12- when the phone reboot and the sony logo appears keep pressing the volume up and down until the twrp recovery opens
13- Done
Through the recovery flash any custom or stock rom and your phone will boot normally
I wish that i had helped you if you want any thing just ask me and i will answer.
Mostafa Sherif said:
Hey, don't worry if you do these steps exactly then your phone will boot again normally and you can enter the recovery then flash any rom again and recover your phone from this brick
1- Download and install Minimal ADB and Fastboot from this link: https://mega.nz/#!7942XJjI!9gurv7k3P...RTiDPeArhwjXsG XB9c
2- Download and install Flashtool drivers from this link: http://doomlord.xperia-files.com/dow...41LTIwMTQwMzE4
Skip Step 2 if you already installed Flashtool Drivers that install with Flashtool if you have installed it.
3- Download the latest twrp recovery from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img.html
4- Move the twrp recovery that you have downloaded in step 3 to this Path C:\Program Files\Minimal ADB and Fastboot
5- Download this kernel from this link: https://drive.google.com/file/d/0Bwn...ew?usp=sharing
6- Extract it then you will find boot.img take this file and move it too to this Path C:\Program Files\Minimal ADB and Fastboot
7- put your phone in fastboot mode by this way >> (Power off your phone completely then wait for 10 second then press and hold the volume up then connect your phone to the computer with usb cable while you are pressing and holding the volume up then the led will change it's color to blue.. that is the fastboot mode)
8- Now go to the Minimal ADB and Fastboot folder in that path (C:\Program Files\Minimal ADB and Fastboot) Press shift button from keyboard then press right click form mouse while pressing the shift button you will find an option [Open command window here] Press it.
9- In the command window write this command exactly: fastboot flash recovery twrp-3.0.2-0-sirius.img
10- Then write this command after it: fastboot flash boot boot.img
11- After it flashed successfully reboot your phone by writing this command: fastboot reboot then unplug the usb from the phone
12- when the phone reboot and the sony logo appears keep pressing the volume up and down until the twrp recovery opens
13- Done
Through the recovery flash any custom or stock rom and your phone will boot normally
I wish that i had helped you if you want any thing just ask me and i will answer.
Click to expand...
Click to collapse
i need the key to download can you provide it for me?
damulag1234 said:
i need the key to download can you provide it for me?
Click to expand...
Click to collapse
Ok, no problem but for which one?!
Mostafa Sherif said:
Ok, no problem but for which one?!
Click to expand...
Click to collapse
sir can you provide me all the needed files? the download links are not working. and the other needs key to be downloaded
damulag1234 said:
sir can you provide me all the needed files? the download links are not working. and the other needs key to be downloaded
Click to expand...
Click to collapse
Sorry for this problem,, but i have edited my post and provided you with a new alternative link (for Minimal ADB and Fastboot) see it again.
and i will check the other links now and if any another link is unavailable i will change it for you.
Mostafa Sherif said:
Ok, no problem but for which one?!
Click to expand...
Click to collapse
1. download link need key
2. download link is not working
3. downloaded
5.download link is not working
damulag1234 said:
1. download link need key
2. download link is not working
3. downloaded
5.download link is not working
Click to expand...
Click to collapse
Check now all the download links again,, it should works now normally
Tell me if there is any another thing
Sorry for that
Mostafa Sherif said:
Check now all the download links again,, it should works now normally
Tell me if there is any another thing
Sorry for that
Click to expand...
Click to collapse
how to use md5 file? do i just need to paste it?
damulag1234 said:
how to use md5 file? do i just need to paste it?
Click to expand...
Click to collapse
Where do you get these files?? i didn't tell you to use any md5 file. and there is no md5 file to use it and if you have found any md5 file just ignore it and continue doing these steps only.
Do the steps as i write it and your phone will boot again successfully
Mostafa Sherif said:
Where do you get these files?? i didn't tell you to use any md5 file. and there is no md5 file to use it and if you have found any md5 file just ignore it.
Do the steps as i write it and your phone will boot again successfully
Click to expand...
Click to collapse
the twrp file is an md5 file sir
damulag1234 said:
the twrp file is an md5 file sir
Click to expand...
Click to collapse
Download the twrp.img from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img
After you download it you will see it's name is twrp-3.0.2-0-sirius.img
Then continue my steps normally and tell me if there is any problem
Mostafa Sherif said:
Hey, don't worry if you do these steps exactly then your phone will boot again normally and you can enter the recovery then flash any rom again and recover your phone from this brick
1- Download and install Minimal ADB and Fastboot from this link: https://www.androidfilehost.com/?fid=24521665358595410
2- Download and install Flashtool drivers from this link: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS41LTIwMTQwMzE4
Skip Step 2 if you already installed Flashtool Drivers that install with Flashtool if you have installed it.
3- Download the latest twrp recovery from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img
4- Move the twrp recovery that you have downloaded in step 3 to this Path C:\Program Files\Minimal ADB and Fastboot
5- Download this kernel from this link: https://drive.google.com/file/d/0Bwn7bAJ-USZjZzg0Q2I2RWlWa1U/view?pref=2&pli=1
6- Extract it then you will find boot.img take this file and move it too to this Path C:\Program Files\Minimal ADB and Fastboot
7- put your phone in fastboot mode by this way >> (Power off your phone completely then wait for 10 second then press and hold the volume up then connect your phone to the computer with usb cable while you are pressing and holding the volume up then the led will change it's color to blue.. that is the fastboot mode)
8- Now go to the Minimal ADB and Fastboot folder in that path (C:\Program Files\Minimal ADB and Fastboot) Press shift button from keyboard then press right click form mouse while pressing the shift button you will find an option [Open command window here] Press it.
9- In the command window write this command exactly: fastboot flash recovery twrp-3.0.2-0-sirius.img
10- Then write this command after it: fastboot flash boot boot.img
11- After it flashed successfully reboot your phone by writing this command: fastboot reboot then unplug the usb from the phone
12- when the phone reboot and the sony logo appears keep pressing the volume up and down until the twrp recovery opens
13- Done
Through the recovery flash any custom or stock rom and your phone will boot normally
I wish that i had helped you if you want any thing just ask me and i will answer.
Click to expand...
Click to collapse
sir i cant understand the instruction on number 8 and 9
would you mind explaining it to me? thanks a lot
damulag1234 said:
sir i cant understand the instruction on number 8 and 9
would you mind explaining it to me? thanks a lot
Click to expand...
Click to collapse
No problem In step 8 first: Go to the path i told you in the description then press and hold shift button from keyboard and then press right click with mouse at any empty space in the folder,, a menu will pop up then you will find an option named (Open command window here) select it, then a command window will open.
I wish i had descriped it to you exactly and tell me if you successed to make it
If you do step 8 correctly then continue to step 9.. in step 9, you have to write the commands that i give it to you in the command window that have been opened in step 8.
The commands that i had bold it
Mostafa Sherif said:
No problem In step 8 first: Go to the path i told you in the description then press and hold shift button from keyboard and then press right click with mouse at any empty space in the folder,, a menu will pop up then you will find an option named (Open command window here) select it, then a command window will open.
I wish i had descriped it to you exactly and tell me if you successed to make it
If you do step 8 correctly then continue to step 9.. in step 9, you have to write the commands that i give it to you in the command window that have been opened in step 8.
The commands that i had bold it
Click to expand...
Click to collapse
i followed it what about the number 10? should i put it before i enter the command from number 9?
<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)
DISCLAMER!Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content.
Note: This is a GSI (generic system imaging) ROM and the credits go to @eremitein and the link to his thread is below:
[OFFICIAL CAOS GSI]-----------------------------------------------------------------------------------
The download link to the rom is below:
Click here to download the ROM
----------------------------------------------------------
Here are some requirements to install this ROM on your device.
1. You must have a PC
2. The bootloader of your device must be unlocked. (if you don't know how to unlock the bootloader of your device then the instructions are below.)
3. Your phone's battery must be above 50%
4. You must install this ROM with a clean boot.img. (it is recommended to install this ROM with a clean boot.img, installing this ROM with a patched boot.img can often result in bootlooping/bricking the device.)
-----------------------------------------------
Here's how you can unlock the bootloader of your device.
1.Create a Mi account if you already don't have one.
2. Open up your phone and go into the settings and go into "About phone" then tap on the MIUI version 7 times. (you will unlock the developer options)
3. Now go back from about phone to the settings app and scroll down to "Additional settings" scroll down and you will see "developer options"
4. Open the developer options and turn on "OEM unlocking" and then click on "Mi unlock status" and now turn off the WiFi and turn on your mobile data. Now click on "Add account and device"
5. Go back to the developer options and scroll down and enable "USB debugging"
6. Now go onto your PC and head over to this link (https://en.miui.com/unlock/download_en.html) and download and extract the file that has been downloaded.
7. Go to the exctracted folder, locate and open the .exe file named "miflash_unlock"
8. Login with your Mi account.
9. Connect your device to the PC via a USB cable. (the one that comes in the box is recommended)
10. If the drivers are installed and the device is connected properly then you must see a "Unlock now" option click on it and you will get a 7 days waiting time.
11. After 7 days, try again and if nothing goes wrong your device will be unlocked.
---------------------------------------------------------------------------------------------------------------------------
Now onto installing the ROM:
1. First download and extract this file on your computer SDK Platform tools
2. Download this file and extract it on your computer MIUI 12 ROM download the fastboot file and extract it on your computer.
3. Download the custom ROM and extract it. (the download link is above)
4. Copy and paste the file to the SDK Plaltform tools folder rename the custom ROM file to "system"
5. Copy the vbmeta.img from the MIUI 12 RO folder and paste it in the SDK platform tools folder.
6. Head to your device and power it off, once it is powered off, Hold the volume down button and the power button till the fastboot screen shows up.
7. Now connect the device to your computer and on your computer open the SDK Platform tools folder and make sure that those 2 files are there, "system.img" and "vbmeta.img"
8. Right click and press the shift key at the same time and click on "Open powershell window here"
9. Now in the powershell window, type in the following codes:
Code:
.\fastboot.exe reboot fastboot
.\fastboot.exe --disable-verification flash vbmeta .\vbmeta.img
.\fastboot.exe flash system .\system.img
.\fastboot.exe -w
.\fastboot.exe reboot
-------------------------------------------------------------
If you followed the all steps then your device will be booted up with Android 11.
Hello
will it work with Redmi 9 Galahad or in general with all Redmi 9s?Thanx.
-CALIBAN666- said:
Hello
will it work with Redmi 9 Galahad or in general with all Redmi 9s?Thanx.
Click to expand...
Click to collapse
Hello, this thread is made for Redmi Note 9. I don't know why XDA moved it here... but yeah since this is a GSI it will work for Redmi 9 as well. But once again, try at your own risk.
I know what i do,thanx.Another question.
Is all running for you without bugs or something?
What about battery time and performance in general,can we use it as daily driver,thanx and nice evening,Cheers!!!
-CALIBAN666- said:
I know what i do,thanx.Another question.
Is all running for you without bugs or something?
What about battery time and performance in general,can we use it as daily driver,thanx and nice evening,Cheers!!!
Click to expand...
Click to collapse
Its a very good rom, more stable than MIUI