Related
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without apk
!!!!!!THIS IS NOW ALL FIXED AND PROPERLY WORKING BY THESE INSTRUCTIONS HOPE THIS HELPS YOU ALL!!!!!!
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without
Q apk.
this is a guide I compiled from the following devs that are credited and thanked
below.
Apparently Google did not like that we are using our Q's again and have killed
the servers that host our Nexus Q apk, if you are currently logged into your Q
you will not notice it. If you try logging into another Q or relog into your Q for
the first time. It will not work any more.
I have 3 of these and want to keep the Q community alive, I needed to figure out
as many of you how to access your Q through adb if the app is dead to enable usb
debugging so you can load cheap cast and continue to use your Q.
This will get adb debugging back so you can load a custom recovery and get
cheapcast back running through CyanogenMod.
!!!!You will need a otg cable powered is a good idea these are $10.00 here ->
-------------------------------------------------------------------------------
To fastboot unlock your device / Credit and thanks to -> fiveipads
-------------------------------------------------------------------------------
1. cmd to platform-tools
2. Reboot to the bootloader -> cover your Q with your hand -> power on nexus Q as
soon as you see red remove your hand -> (will go solid red and you are in
bootloader)
3. Unlock your device* (with fastboot tool) (type) -> fastboot oem unlock
(immediately copy and paste this into tool and hit enter you have only 5 secs) ->
fastboot oem unlock_accept
4.Q will reboot and turn purple etc.
5.Unplug Q and restart in bootloader see #2. (type) -> fastboot getvar unlocked
(this verifies you unlocked your Q->should reply->unlocked:yes)IF NOT DO NOT
PROCEED TILL IT DOES.
-------------------------------------------------------------------------------
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/attachment.php?attachmentid=1563302&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.Flash the image -> (type in fastboot) -> fastboot flash boot boot-root.img
(image will write should say ok and writing boot etc.)
5.Pull the power on your q and restart the Q
-------------------------------------------------------------------------------
Load Clockwork Mod Recovery / Credit and thanks to -> Koush
-------------------------------------------------------------------------------
1.Download koush's ClockworkMod Recovery.
koush's ClockworkMod Recovery ->
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.1-steelhead.img
md5: dec2a809a20e8cb236ae092e71d8d5fe
2.Connect the Nexus Q to the computer via USB.
3.Make sure the fastboot binary is in your PATH or that you place the downloaded
image in the same directory as fastboot. (rename the downloaded recovery file
recovery-clockwork-6.0.3.1-steelhead.img to -> recoveryq.img to make it easy to
type)
4.Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader or by using the hardward -> cover your Q with your hand ->
power on nexus Q as soon as you see red remove your hand -> (will go solid red
and you are in bootloader)
5.Once the device is in fastboot mode, verify your PC sees the device by typing
-> fastboot devices
***If you don't see your device serial number, and instead see "<waiting for
device>", fastboot is not configured properly on your machine. See fastboot
documentation for more info.
6.FLASH ClockworkMod Recovery onto your device (type) -> fastboot flash recovery
recoveryq.img
(should confirm by okay if not do it again till it does)
7.(type) -> fastboot reboot (this will reboot your device to the factory startup
screen) -> (type) adb devices (make sure your device shows up) -> (type) -> adb
reboot recovery (you should be in clockworkMod recovery)
--------------------------------------------------------------------------------
Install Cyanogenmod to your Q through adb on Clockwork Mod / Credit and thanks to Cyanogen mod crew and hharte for amplifier support and Anthony Hopf for updated working zip file.
--------------------------------------------------------------------------------
1.Download the prebuilt release of CyanogenMod you wish to install.
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited. *****IF YOU CAN MIRROR THESE LINKS CONTACT ME WITH THE LINK*****
TAS5713 (Audio Amplifier):
Download: https://www.dropbox.com/s/vk77uq7dmpazzpz/cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: http://www.magicandroidapps.com/download/cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build. found here ->http://get.cm/?device=steelhead
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
2.Rename your cm10 file to -> cm10.zip (this will make it easier to type later)
3.Move your cm10.zip to your platform-tools folder again like you did the recoveryq.img file
4.To install boot into recovery mode (type) -> fastboot boot recovery.img (or if you are still at recovery ignore this)
5.When Q has reached recovery mode, push the cm10.zip to /sdcard using adb, (type) -> adb push cm10.zip /sdcard/
6.To push gapps (if desired download here -> http://goo.im/gapps/gapps-jb-20130301-signed.zip md5SUM: b7e53e96e1c8b1a1c4865bf29418c8e0 and rename to gapps.zip and move to platform-tools folder)(type) -> adb push gapps.zip /sdcard/
7.From within recovery, "install zip from sdcard" and browse to cm10.zip file After this has installed, it is a good idea to wipe data and cache.
8.Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps.zip file.
9.If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
10.Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu
OR YOU CAN INSTALL THIS ICS BASED ROM BASED ON THE STOCK IMAGE HERE->
http://api.viglink.com/api/click?fo...=Download it&jsonp=vglnk_jsonp_13777850981938
YOU MUST USE ICS BASED GAPPS.
--------------------------------------------------------------------------------
Install Cheapcast to q with auto boot option / credit and thanks to -> Sebastian Mauer and other devs involved (YOU NOW NEED THE OTG CABLE AND A MOUSE)
--------------------------------------------------------------------------------
1.Start your q get the otg cable plug it in wait for the Q to boot all the way the plug the mouse into the otg cable it should work.
2.+Sebastian Mauer's CheapCast allows an Android device to act as a target for #chromecast enabled applications. Android device == Nexus Q; chromecast enabled application == +Google Play Music.
3.Go to the asop brower on the Q and go to this link -> http://www.androidfilehost.com/?fid=23060877489999380
4.Download the apk do not use the store version at this time it is broken.
5.Using a file explorer find and open the apk it will be in the downloads folder. (you may need to authorize installing 3rd party apps in the security menu) once installed open cheapcast tick enable on startup and start sevices button. Now reboot your Q using a reboot button apk from the store.
6.Now your Q will be recognized as a target for any Chromecast enabled app upon startup, like Google Play Music it will also work on youtube as I have verified this, however if using the steelhead internal amp zip it will not output sound except to the internal amp. Use your device (I'm using my S4 GPE) to start and enjoy!
7.If for some reason the apk stops working on boot you may need to reinstall it and restart it for on boot starting. Your Q will now be on all day long so unplug it when not using it. until someoen makes a remote turn off apk or something.
Edit: All the XDA folks who put up a bounty? Please donate to Sebastian - grab the CheapCast app and hit the donate button!
______________________________________________________________________________
(If your Q boots up and the resolution looks wrong you will need to use a different tv or monitor ot happened to me)
I hope this help anyone like me who thought everything on this forums was way to hard to find and put together, this is all tested and is done how I typed it in.
If you mess it up DO NOT COME TO ME CRYING!
If I helped you, click my thanks button and send your donations to all the devs mentioned above, also donate to cheap cast to make it stay around.
Obviously Google does not want us to keep using our Q balls so make sure we keep devs working for us here by posting and showing interest.
Thanks- Ian
OTG cable
At what point did you need an OTG cable? Looks like you did all this via PC? Thanks so much!!!! I have two of them, both had USB debugging enabled until I did factory resets on them this morning. <sigh> The folks at Google were very nice and excruciatingly unhelpful when I called them about it this afternoon. But... apparently a "Nexus Q expert" will get back to me very soon, and I'm sure the response will be the standard Google canned response regarding the Q.
Still trying to figure out how to authorize adb debugging with only 1 usb port please someone explain
Figured it out
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
unknownkwita said:
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
Click to expand...
Click to collapse
I will try that later and report back if it works for me
This is now all fixed and working correctly!
im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing
Could someone please post a video on youtube of how to do this?
dts924s said:
Could someone please post a video on youtube of how to do this?
Click to expand...
Click to collapse
Seriously....read man....... its laid out exactly how to do it.
If you need a video you do not need to be hacking your Q
ianandamy said:
This is now all fixed and working correctly!
Click to expand...
Click to collapse
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
kario said:
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
Click to expand...
Click to collapse
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
Should be: fastboot flash boot boot-root.img
ianandamy said:
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
Click to expand...
Click to collapse
Once this rom is installed how does one get past the nexus q welcome screen?
I still can't believe that CM didn't integrate the amp functionally in their ROM..
watso4183 said:
Once this rom is installed how does one get past the nexus q welcome screen?
Click to expand...
Click to collapse
Hit the "home" key on your KB.
Lokifish Marz said:
Hit the "home" key on your KB.
Click to expand...
Click to collapse
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
ianandamy said:
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
Click to expand...
Click to collapse
Remove or rename AtHomeThemeService.apk, HubBroker.apk and Visualizer.apk from v1.0.2 and flash it. This will remove the stock Q services/frontend without breaking the audio output.
Thanks for the great guide, I just bought my Q a few days ago. I will definitely try this out. It is good to know, that the community is still alive.
Sent from my Nexus S using Tapatalk 4
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/atta...2&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.This is to test it first before you permanatly install it -> (type in fastboot)
-> fastboot boot boot-root.img (If the device reboots and the mute light goes
from red to off then you've successfully booted! Run `adb devices` to ensure it's
showing up and that you can connect to it. If all goes well (which it should)
then you can flash the boot image)
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
(image will write should say ok and writing boot etc.)
6.Pull the power on your q and restart the Q
-------------------------------
you have fastboot flash boot-root.img
its supposed to be-- fastboot "flash boot" boot-root.img
<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
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Bobenjanneke said:
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
Here
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
Bobenjanneke said:
Must the x829 rooted for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
No.
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
Whenever you going to update official rom manually, you need to rename it 'update.zip'.
X829, x820, x821 etc...all are same device.
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
No, only one time to move from Vendor rom (the one comes with phone ), then you can normally update it OTA or local.
Bobenjanneke said:
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Click to expand...
Click to collapse
I think install TWRP is the easiest way. I bought X829 few weeks ago, installed TWRP and backup the system that come with the phone and can flash any custom rom. I did try flashed Official Indian 5.8.019S, China 5.9.020S,5.9.023S. You can flash any official stock rom with TWRP I tested it worked fine.
I don't find much different between the roms except Chinese rom have some Chinese apps and don't have Google service/Player store but can download and install after rom is installed.
For backup normally there is system image in internal storage maybe it's the system/rom that come with the phone. I have not try to restore this system image though I not sure its only install the rom or wipe internal storage too.
---------- Post added at 05:29 AM ---------- Previous post was at 05:28 AM ----------
Note I installed TWRP 3.0.2 from official website. Try this one if other version don't work.
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Bobenjanneke said:
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Click to expand...
Click to collapse
it is Driver issue, go here and follow the instructions
AhmadSant said:
it is Driver issue, go here and follow the instructions
Click to expand...
Click to collapse
Thank you! That worked!
I only checked the "Google usb driver" , everything else I unchecked...
But when I run ADB usb, $adb_vendor_keys is not set...
ADB reboot bootloader gives same message, both are talking about ADB kill server?
When I command ADB kill server, and run ADB usb, it says
*Daemon not running, starting it etc etc"
I have Daemon tools installed, but is not active on the right bottom in the task bar....
ADB devices gives a number with "unauthorised"...
I think, I know myself the problem...
I only downloaded the software package, unchecked everything ( so also the mainpackage ) and installed only the extras/usb driver...
But know, it is 11pm, to late for me know....
X829 have problem phone not detect under Fastboot mode, Fix is in below link with description:
https://forum.xda-developers.com/showpost.php?p=72154309&postcount=72
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Test TWRP Recovery before flashing internal
Hi,
After you install the drivers and Android Tools all starts to make sense
careful when flashing TWRP into the recovery partition, test with adb and the recovery reboot the file you have, I downloaded by mistake a lower version and all it did was show some lines like it was in a higher screen resolution after a while downloaded the latest and worked, flashed that one into recovery. This makes flashing anything again possible without connecting the phone to the pc other than to copy the file.
In my opinion the stock ROMs are heavy and make the phone work slower but if you want to stick to Official LeEco ROMs than I should advise the Chinese ROM, I've read it doesn't encrypt the Data mount points.
Make a backup of your current installation as mentioned in the link posted earlier, I'm not an expert also and am still learning stuff (forced by the low quality ROMs and the fact that it is an unofficial phone).
Lineage Nougat (new and tested in my phone) and Remix (from what I've heard) are pretty good and make phone light and working fast.
Don't Forget to install Google Apps afterwards (GApps as they call it).
There isn't really the need to rename the file to upgrade.zip just click the zip file and swipe to flash the new ROM.
I haven't rooted my phone, heard that Apps like Home Bank ones don't work so nvm that unless you need it but maybe in a few months you think otherwise, gain some experience first. It's not needed to do any of the things mentioned, only for changing Kernel settings and other stuff... I'm not there yet...
Tried Dolby Atmos from XDA but only one works, test it from the top and see if the app works. Install a Icon builder App to create the icon because it won't show in the settings like in the custom ROM. Other than that improves the sound quality.
Regards,
Pedro
Bobenjanneke said:
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Click to expand...
Click to collapse
Repeat again but skip this one:
-Fastboot OEM device-info
Seems drivers are not loading
Hi,
After you connect the device it should start to work if the drivers are correct, this may take a while at first but I used the info cmd to check if it was working
adb reboot bootloader
(will reboot device into bootloader)
fastboot oem device-info
(should return an ID for you phone)
fastboot boot twrp-3.1.0-0-x2.img
(should start TWRP in the phone)
-- flashing only
fastboot flash recovery twrp-3.1.0-0-x2.img
(Make sure the last command worked correctly before flashing recovery, it doesn't have to be renamed to recovery.zip)
Install Android tools, after that the drivers should start to work. Let us know.
Regards,
Pedro
Thank you all for your help already!
Sorry for my next question, but i am really f*cked up...
Does someone has Skype or Whatsapp for instant help?
I deleted and reinstalling ASDK Manager.
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Bobenjanneke said:
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Click to expand...
Click to collapse
Hi,
Can't remember if the older drivers worked but I can test at home.
The phone should be unlocked already (x829) but you can issue the unlock cmd any time, it will say already unlocked or do it, but the phone needs to connect.
Did you allow USB debugging and did all the other steps they say in the forum? Switch on the phone to media option instead of just charging or it will not allow the connection.
fastboot boot twrp-3.1.0-0-x2.img
-- After the reboot with "adb reboot bootloader" cmd is successful if you issue this it will upload TWRP into the phone using adb and start it, I suggest to use this method at first.
the flash cmd will replace the recovery of the phone with TWRP Recovery, so everytime you enter recovery mode by pressing Vol. Up + Power it will go to TWRP TeamWin instead. Do a backup just in case of the phone using the "fastboot boot twrp-3.1.0-0-x2.img" cmd.
Let us know how it goes...
Regards,
Pedro.
My steps:
-Connected via Media Connection
-Allow USB debugging
-OEM unlocked
-Gave permission on phone screen
Installed ASDK from the guide R24.4.1 ( installed all checked boxes )
ADB start-server
ADB USB
ADB DEVICES
ADB REBOOT BOOTLOADER
and then it hang both on OEM DEVICE-INFO & OEM UNLOCK...
-------------------------
I am installing Universal ADB drivers, maybe that workx....
BTW, I am working with Windows7 64Bit Ultimate...
What was yours both OS?
Thank you very much!
I searched myself on Google, and tried some solutions, but nothing worked...
Installing the Universal ADB driver didn't bring any solution....
I read that after ADB REBOOT BOOTLOADER or FASTBOOT OEM UNLOCK, I have to press the volume up? I didn't read that in the guide ( and it didn't work even )...
I have an old laptop, which I can down/upgrade with XP SP3 or W10...
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)
Here was a Guide. Someone said people don't care about Me or My Work so...
This was posted 18-Jan? I was just looking around to buy this phone. I'm assuming this works with the recent updates to the phone (update the fixes the heating issue).
vman00 said:
This was posted 18-Jan? I was just looking around to buy this phone. I'm assuming this works with the recent updates to the phone (update the fixes the heating issue).
Click to expand...
Click to collapse
Sorry i was late. But Sure, Updates doesnt really Play a Role!
You can Always unlock If Your Device allows it.
Have fun!
Miustone said:
Sorry i was late. But Sure, Updates doesnt really Play a Role!
You can Always unlock If Your Device allows it.
Have fun!
Click to expand...
Click to collapse
Thank you for the quick response. And no worries, I always hold off from getting new phones for a root guide.
Thread / Guide updated
Miustone said:
Thread / Guide updated
Click to expand...
Click to collapse
Has anyone installed a GSI ROM on this device? I'd love to know how the cameras performed.
thatguy222 said:
Has anyone installed a GSI ROM on this device? I'd love to know how the cameras performed.
Click to expand...
Click to collapse
A General System Image does not touch any of the Drivers or the Kernel since its an System Image non related to this Things. So it's the same as on Stock... (Except You would flash AOSP Vendors and Kernels as Base)
After i got a Xperia 1 III gifted by a Supporter i have checked how actual Android work. I have updated the Guides and fixed the issues for everyone hopefully... Enjoy!
Hi there I am coming from another phone where I was flashing AIO images for my updates. How does updating work with an Xperia Pro I once it has been rooted?
Also I am getting a 'no' on the bootloader unlock. What options do I have?
Miustone said:
Introducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
That helped? Leave a Thanks! <3
Donations are actually also really welcome!
Pay Marius Kopp using PayPal.Me
Go to paypal.me/miustone and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com
BTC: 3A93fjg2KxZJEHUpBExs7rVgivfAUumQoJ
ETH&ERC20-USDT: 0xD27860248B7E51720DDf9CA5a1f861CA1029c14A
ERC20: 0xD27860248B7E51720DDf9CA5a1f861CA1029c14A
Click to expand...
Click to collapse
Thanks for this information. I was just wondering if you know of anyone who has actually opened the bootloader on a Pro-I. When I go to the Sony website provided in your guide and tap Service info > Configuration > Rooting, Status, it returns "no" and that's as far as I get. Any suggestion will be appreciated.
When I do adb reboot bootloader I get no prompts but get thrown to fastboot (a black screen and blue LED).
After that any interaction will not work - after some digging it seems that my drivers work for ADB but not for fastboot. Device manager shows a device "other > android" which apparently means that the fastboot drivers are not working. I have tried disabling driver signatures and then installing them again with the phone connected in fastboot mode but that didin't help - am I trying to install the right drivers? I got the OEM drivers from Sony, a 2019 driver which installs from "sa0200adb.inf" that I got from https://developer.sony.com/file/download/xperia-pro-i-driver/
Kind of stuck here, but I've managed to solve a few roadblocks already so maybe I'll crack this one too, later...
Any help will be appreciated. ^^
(edit - figured out some basic stuff I got wrong, did more research and updated my issue acccordingly)
Tsuchimursu said:
When I do adb reboot bootloader I get no prompts but get thrown to fastboot (a black screen and blue LED).
After that any interaction will not work - after some digging it seems that my drivers work for ADB but not for fastboot. Device manager shows a device "other > android" which apparently means that the fastboot drivers are not working. I have tried disabling driver signatures and then installing them again with the phone connected in fastboot mode but that didin't help - am I trying to install the right drivers? I got the OEM drivers from Sony, a 2019 driver which installs from "sa0200adb.inf" that I got from https://developer.sony.com/file/download/xperia-pro-i-driver/
Kind of stuck here, but I've managed to solve a few roadblocks already so maybe I'll crack this one too, later...
Any help will be appreciated. ^^
(edit - figured out some basic stuff I got wrong, did more research and updated my issue acccordingly)
Click to expand...
Click to collapse
just didn't read my fastboot driver installation instructions carefully enough. Banged my head against a wal lfor a long while because I clicked the wrong thing in this step... Stupid newbie mistake but dropping my solution here anyway incase someone searches for this stuff with similar symptoms.
{
"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"
}
Garech said:
Thanks for this information. I was just wondering if you know of anyone who has actually opened the bootloader on a Pro-I. When I go to the Sony website provided in your guide and tap Service info > Configuration > Rooting, Status, it returns "no" and that's as far as I get. Any suggestion will be appreciated.
Click to expand...
Click to collapse
I have succesfully unlocked and installed magisk root on my Pro-I. Should work unless you have some weird version or haven't updated to latest firmware?
Try entering *#*#7378423*#*# in the dialer and it should state whether bootloader unlocking is allowed (and if it is currently unlocked).
Tsuchimursu said:
I have succesfully unlocked and installed magisk root on my Pro-I. Should work unless you have some weird version or haven't updated to latest firmware?
Try entering *#*#7378423*#*# in the dialer and it should state whether bootloader unlocking is allowed (and if it is currently unlocked).
Click to expand...
Click to collapse
Nothing weird - just a regular US model XQ-BE62. This is great news! You are the only person I have heard of that has rooted this phone. I may have mentioned this, but I am not into custom mods just for fun. In fact I'm kind of nervous about rooting, but I am beta testing an experimental app made for filming RAW video. Some other brands of phone are working, but the Pro-I throws a lot of dropped frames and has some restrictions on filming speed that I know the phone can handle. The devs say the issue is caused by Sony's restrictions on third party video apps and the Pro-I should function properly if rooted. Magisk appeals to me because (I think) I can unroot if I want to. I'll follow in your footsteps and see if I can do it.
Thanks very much.
Garech said:
Nothing weird - just a regular US model XQ-BE62. This is great news! You are the only person I have heard of that has rooted this phone. I may have mentioned this, but I am not into custom mods just for fun. In fact I'm kind of nervous about rooting, but I am beta testing an experimental app made for filming RAW video. Some other brands of phone are working, but the Pro-I throws a lot of dropped frames and has some restrictions on filming speed that I know the phone can handle. The devs say the issue is caused by Sony's restrictions on third party video apps and the Pro-I should function properly if rooted. Magisk appeals to me because (I think) I can unroot if I want to. I'll follow in your footsteps and see if I can do it.
Thanks very much.
Click to expand...
Click to collapse
I have a UK/EU model so we do have a difference, however it went easily for me except for own stupidity in fastboot driver installation.
I haven't done much yet beside root with magisk and purge facebook and google off my phone, but plan on playing some more in the future.
Tsuchimursu said:
just didn't read my fastboot driver installation instructions carefully enough. Banged my head against a wal lfor a long while because I clicked the wrong thing in this step... Stupid newbie mistake but dropping my solution here anyway incase someone searches for this stuff with similar symptoms.View attachment 5708441
Click to expand...
Click to collapse
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
What did you do next?
Garech said:
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
View attachment 5709903
What did you do next?
Click to expand...
Click to collapse
Oh, I just googled some guides on fastboot drivers... but you click "have disk" and then browse for google the USB driver .inf file
Garech said:
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
View attachment 5709903
What did you do next?
Click to expand...
Click to collapse
by the way I'm a total noob so don't trust me blindly xD
One other thing that came to mind was that wipe from fastboot fails at metadata partition due to lack of permissions, and you'll get a loopboot and be thrown to recovery and there you can do a factory wipe and it will succesfully wipe the rest. That's what happened to me anyway.
Tsuchimursu said:
by the way I'm a total noob so don't trust me blindly xD
One other thing that came to mind was that wipe from fastboot fails at metadata partition due to lack of permissions, and you'll get a loopboot and be thrown to recovery and there you can do a factory wipe and it will succesfully wipe the rest. That's what happened to me anyway.
Click to expand...
Click to collapse
That's good to know. And I'm a noob too. I have rooted three phones over a period of time years ago and my heart was pounding the whole time. It is comforting to know that someone else has rooted this phone. As I said I am a beta tester for an experimental video app (MotionCam Pro - it's on the Play Store.). There's a small group of us who have the Pro-I and I have stupidly volunteered to try to root. One guy has already given up and returned his phone. I want to find out how this app can work with my phone. Filming in RAW (without dropped frames and lens errors) would be epic. I also DON'T WANT TO BRICK MY PHONE! Thanks for any help you can offer.
One question. I assume that Sony web site that tells me my phone can't be rooted is irrelevant if I have a working bootloader code, right?
Garech said:
That's good to know. And I'm a noob too. I have rooted three phones over a period of time years ago and my heart was pounding the whole time. It is comforting to know that someone else has rooted this phone. As I said I am a beta tester for an experimental video app (MotionCam Pro - it's on the Play Store.). There's a small group of us who have the Pro-I and I have stupidly volunteered to try to root. One guy has already given up and returned his phone. I want to find out how this app can work with my phone. Filming in RAW (without dropped frames and lens errors) would be epic. I also DON'T WANT TO BRICK MY PHONE! Thanks for any help you can offer.
One question. I assume that Sony web site that tells me my phone can't be rooted is irrelevant if I have a working bootloader code, right?
Click to expand...
Click to collapse
yeah it's scary, especially with low volume devices.
I'll have to look into that app, I'm a hobbyist photographer (surprise, given my choice of phone...)
I am a bit confused what page says your can't root a Sony pro-I, but their website will give you an unlock code with an imei of a pro-I and it sure worked for me...
You checked your service menu and your phone stated itself that the bootloader can be unlocked, right?
Also if you can't tick the oem unlocking toggle in dev options after updating firmware but not doing anything else yet, your device might need a factory reset.
I assume you've also backed up all your data and settings etc, you'll be wiping your phone while rooting.