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.
Related
hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Thanks Flippy for sharing the steps with us.
can i downgrade from Nougat to Marshmallow？
microbai said:
can i downgrade from Nougat to Marshmallow？
Click to expand...
Click to collapse
sorry for the delay, yes you can, just follow the steps.
ayad said:
hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Click to expand...
Click to collapse
I followed all of the steps and it says "Flash Failed (Fastboot) PLEASE HELP
Edit: I fixed the problem by simply rebooting it. I didn't think it would be that easy.
SameSame, but L-Version ... cannot find Stock ROM ...
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
pwallenb said:
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
Click to expand...
Click to collapse
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Could someone please help me with downgrading my YB1-X90L, it just refuses to boot at all after my nephews messed with it, I found the stock rom but I can't get some of the needed programs and drivers,
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Hello
I made this all and my Yoga-Book runs on Android 6.0.1 . But is there a possibility to get an Android Build 7.1.1? Because I can't restore my Backup it seams it is corrupt and if I try to update im configuration-app its does anything but at the end its allways on 6.0.1.
It would be great if someone can helb me.
Best regards
Peter
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
phsma said:
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
Click to expand...
Click to collapse
looks like the original link is down, so i searched for the file name YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip and this came up:
YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip | Easy Firmware
easy-firmware.com
ive no idea if this is working or safe to use but its a start.
good luck
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
galumph said:
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
Click to expand...
Click to collapse
I'm in the same boat. I acquired a YB1-X90F but all it does is show the orange Lenovo splash screen, then a black screen.
So here I am reading threads. But I'm already at my first hurdle...since I can't boot into the OS and go into Developer Options to start the boot loader unlock process.
YB1-X90F No OS(?) - Flashing Help
TL;DR: Noob needs to stock flash a device that won't boot into OS. Here's how the recovery looks (without and interaction): Boot loader: Splash screen: I have acquired a YB1-X90F that just shows the orange Lenovo splash screen and or a...
forum.xda-developers.com
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Brent.M said:
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Click to expand...
Click to collapse
any ideea why my yoga book is not visible in fastboot?
i installed drivers and platform lite indicated in drive location.
currently my yoga sbows bootloader error 05 during booting
Thank you @Brent.M I have a booting Yoga Book again
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
The link is not work anymore, could you please share you firmware for x90L model ? thanks
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
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)
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Edit: thanks for the answers, when I buy this phone an root it I can let you know how it went.
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
there is no problem to root xiaomi device,because it can unlock BL
lWanderingl said:
Hello everyone, this is my first post here, I'm planning on buying a phone with high specs, good camera and the possibility to access root so my attention went to Xiaomi 12T Pro.
I've seen a two-weeks old post on reddit where some guy with this same phone asked for help and ultimately managed to root it using magisk, however the 12T pro has a snapdragon chipset and from my last experience (about 6 years ago) snapdragon devices can't be rooted? Maybe that guy had the normal 12 pro and got confused with the name?
Anyway I have a laptop so if there's a possibility/potential in the future to root this phone I might as well buy it.
If you want I can also link the reddit post so you can give it a look.
Thanks everyone.
Click to expand...
Click to collapse
Hello , You can unlock bootloader then root your device easily with magisk , xiaomi devices are root friendly if you need any help lemme know i will do as much as i can
I would love a step-by-step, hold my hand type of tutorial. If some of you have spare time to do something good for the less capable brothers here, it will be great.
Yeah step by step Link would bei very helpful
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "fastboot devices" your phone should appear
Method 1 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 booting in TWRP (not recommended on this device, may cause bootloop)
pros: original recovery wont be replaced
cons: loads temporary recovery, once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
GoldenWarriorM said:
Here is step-by-step tutorial
Step 1 Unlock bootloader (it will erase ALL YOUR DATA)
1) create and login in Mi account
2) go to settings>My device>All specs> click MIUI version several times
3) go to settings>additional settings>developer options> here enable OEM unlocking, usb debugging and link your Mi accont to phone
4) download latest MI unlock tool from official site https://en.miui.com/unlock/download_en.html and unzip the archive into a folder
5) download qualcomm usb drivers or launch driver_install_64.exe in downloaded MI unlock tool folder
6) launch miflash_unlock.exe and login in your MI account, hold power and volume down for 5-7 sec to boot in fastboot mode, connect phone to pc
7) try to unlock (it will say to wait 1-7 days and try again)
8) Voila, your phone unlocked and wiped
Step 2 flashing or booting TWRP
1) go to settings>additional settings>developer options> here enable usb debugging
2) download platform-tools https://developer.android.com/studio/releases/platform-tools
3) download TWRP https://mega.nz/file/USUjQR4D#g8_rCCouOcJLK4DrryIyHbE99dwP4Hj-T-XSBtoSx6Q
3) unzip the archive into a folder
4) put twrp-3.6.2_A12-diting-skkk.img in the same folder
4) run cmd (win+r and type "cmd")
5) type "cd path/to/folder" (if folder not on C drive run "DriveLetter:" for example "D:"
6) boot in fastboot and connect phone to pc
7) type "adb devices" your phone should appear
Method 1 booting in TWRP
pros: original recovery wont be replaced
cons: loads temp recovery once you booted system or disabled device TWRP will be erased
8) type "fastboot boot twrp-3.6.2_A12-diting-skkk.img"
9) install magisk (flash downloaded magisk.apk or zip in recovery)
Method 2 flashing TWRP (recomended)
pros: easily accesible (just hold power and volume up for 5-7 sec)
cons: replaces original recovery)
8) type "fastboot flash recovery twrp-3.6.2_A12-diting-skkk.img"
9) fastboot reboot
10) hold power and volume up for 5-7 sec)
11) install magisk (flash downloaded magisk.apk or zip in recovery)
Click to expand...
Click to collapse
Just confirming: in the TWRP page, the 12T Pro is not listed as a compatible device (https://twrp.me/Devices/Xiaomi/).
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Just did as instructed and it works. Only bummer is that twrp is in Chinese. I did google a youtube video and followed instructions to change language. So far all good.
Do OTA updates still work after rooting? Or what is the process to upgrading once rooted?
GoldenWarriorM said:
7) type "adb devices" your phone should appear
Click to expand...
Click to collapse
You mean "fastboot devices", as it is already in fastboot
booting to recovery ended in error for me " FAILED (Status read failed (Too many links))" which led to bootloop.
I reflashed original ROM and I will try flashing.
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
HValenti said:
flashing the recovery went as sharp as possible.
I do not recommend to boot into recovery before flashing it.
Click to expand...
Click to collapse
I didn't tried to boot without installing, I think there is a problem with A/B slots. On devices without B slot booting in TWRP should work as intended.
JF_Derzi said:
Will the provided version of the TWRP work? I would like to avoid boot loops or even a hard brick.
And, would Orange Fox work too? Could you point us the correct version?
TIA.
Click to expand...
Click to collapse
Provided version works on my device (Mi 12T Pro, Global ROM). Hardbrick is impossible if flashing TWRP in recovery partition.
I didn't found compatible Orangefox recovery
There are 3 versions of TWRP:
BOOT:
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
REC:
Update with existing TWRP.
gold
CMD
fastboot flash recovery_ab twrp.img***
powershell
./fastboot flash recovery_ab twrp.img***
BOOT REC:
Both methods
On this thread the proposed version is REC.
***Remove lock screen security and reboot to decrypt data then install TWRP.
Reboot with the buttons combination and not with a fastboot command
Update REC
twrp-3.7.0_12-v6.5_A12-diting-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Spoiler: Change languages
{
"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"
}
Then reboot TWRP
No need TWRP for Rooting
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Xiaomi 12T Pro
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
Pass SafetyNet without Magisk Hide Props Config and
How to Hide Root from Apps via Magisk DenyList [Android 13]
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Try island app on Google play
HValenti said:
I would like to inform any new thinker for root possibility in this device that I was not able to hide the root by Google Pay/Wallet in this phone (ROM: 13.0.11.0 - SLFEUXM), by executing the casual procedures:
https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/#METHOD_2_Pass_SafetyNet_without_Magisk_Hide_Props_Config_NEW and
https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
All other bank apps I use have no clue that I am rooted, and work flawlessly.
If you know something more I can try, I will be happy to get any help on the matter.
Click to expand...
Click to collapse
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
NOSS8 said:
Maybe you have already tried this (your links don't work):
magisk/settings/hide Magisk, renaming it..
Zygisk enable/enforce exclusion list enable.
Configure exclusion list / display system apps / check those related to your problem.
Reboot.
Click to expand...
Click to collapse
Yes I have done all of this. Links have been fixed.
tavocabe said:
Try island app on Google play
Click to expand...
Click to collapse
I don't think I can isolate Google Pay/Wallet, but I will try it.