Fastboot on X10 - XPERIA X10 Android Development

Hello people. This thread is mainly for devs.. and I want to share a little finding with you.
I hope you are familiar with fastboot mode on android devices. (If not, check this) And all sony and semc devices not older than 2011 year of release has this feature. By default, X10 doesn't have this. We have only one recovery mode - it's bootloader mode, when you swich off the phone, longpressing BACK-key you connect it to USB cable. Now we're able to get into fasboot mode.
Please note that I didn't created this thing, I only discoverd how this works, tested and made little zip to make use of it. Works on any bootloader, but only on stock kernel.
So, to benefit from whole this thing you need:
- The .zip from attachment
- Stock x10 kernel (UB users, look here)
- ADB/Fastboot drivers on your PC
- ADB/Fastboot tools (check this or this)
- USB cable and working USB port
- Knowledge of what you do and why you do
To install fastboot:
> Download .zip from attachment
> If you have Unlocked Bootloader, flash .ftf from this thread.
> Boot into any recovery and mount system partition
> Flash .zip and reboot.
After Sony Ericsson logo you will see an alert on your screen, saying that it is in fastboot mode. Done. Just connect to USB and use it. But note that if you don't use fastboot in 10 seconds it will automatically reboot, so move faster . To remove fastboot, just flash remove_fastboot.zip in recovery.
Q: Why the f**k I need this?
A: You can benefit from all fastboot features, its an alternative to recovery. For example you can boot any bootable kernel in .img format without flashing it by command:
Code:
fastboot boot your_boot.img
Proof is at photo attached below.
- Well, thanks bro.
- Feed me :good:

@FeraVolt Can this not be implemented anyhow on your latest GB ROM release and kernel?
I would love to see that!

Related

[Q] problem with ROOT FOR SK17i BASED ON 4.0.2.A.0.62 FIRMWARE

i did like this thread
[b KERNELS] WITH CWM AND ROOT FOR SK17i-ST15i-WT19i BASED ON 4.0.2.A.0.62 FIRMWARE
NEEDS UNLOCKED BOOTLOADER
Nothing extra in these kernels.Stability is not compromised.Just the absolutely necessary.CWM recovery (5.0.2.7), root privileges and all the goodies of a debuggable kernel (like init.d support)
INSTALLATION INSTRUCTIONS:
Run cmd in the folder that contains fastboot.exe.Unzip boot.zip in the same folder.Connect your sk17i-st15i-wt19i in fastboot mode(shutdown your device,hold volume up and connect your device to your pc via usb (blue led lights up)at least this is the way for sk17i).
Type:fastboot flash boot boot.img
Disconnect the usb cable.
Reboot.
ENJOY!
To enter CWM press the power on-off key once or twice as soon as the text se logo gets brighter.
Download links:
SK17i:
i have fastboot.exe
and boot.img
in a folder and the cmd it says in every time i try to root my phone < waiting for device >
my phone is in the fast mode (with blue light) connecting to my PC
so whats wrong what did i miss ??
any help will be much appreciated
thanks in advance
Make sure usb driver is installed. Check device manager make sure there are no problems (while phone is connected in fastboot).
wrt54gs7 said:
Make sure usb driver is installed. Check device manager make sure there are no problems (while phone is connected in fastboot).
Click to expand...
Click to collapse
i did check device manager and the usb driver every thing was working good, but the problem still happen all the times the cmd says waiting for device any help
I suggest you install flashtool and check its log while you dis/connect your phone.

Stuck with Doomlords bootloops

Hi, i think i have a problem with the wrong kernel installed.
I have a SXSwith ICS and since a couple of days i tried to unlock the bootloader, put Doomlords CWM on it an root it, because i like to try another ROM.
I Unrooted it via the official way wich worked out good, the only thing strange was that i restarted and it seemed the whole phone was resetted.
Than i wanted to root and i had to put the phone in recovery mode, and i choose the doomlord CWM and flashed it using this guide
.
Xperia S
1.Download the Doomlord CWM Recovery image (download link here) and the Wi Fi Module for Doom Kernel (download link here) and place the same to the computer.
2.Go and rename the “S-DooMKernel-v01_kernel.elf” file into “kernel.elf”.
3.Copy the file renamed on the same folder with ADB / fastboot.
4.Take your phone and its USB cord and by using both connect it with the computer.
5.Copy-paste the “S-DooMKernel-v01-Modules.zip” file from the PC to the Xperia S SD card.
6.Disconnect the smartphone from the computer.
7.Reboot it by entering in fastboot; press the Volume Up button while connecting the phone with the PC.
8.On the computer open command prompt (Start -> run -> cmd) and enter the command: fastboot flash boot kernel.elf. If this isn’t working try with: fastboot -i 0x0fce flash boot kernel.elf.
9.The handset should reboot.
10.When you see the light turn blue hold the Voluem Up button. The Xperia S will enter in recovery mode.
11.In the recovery menu select “install zip from sd card” and pick the file copied there on step 3.
12.The installation procedure should begin. Don’t press anything as the process might take up to 10 minutes to complete.
13.In the end, from the recovery mode menu select “reboot system now” and you are done.
There you have it; that was the easiest and fastest way in which you can learn how to install Doomlord’s ClockworkMod Recovery on your Xperia S smartphone. Do tell us if there were problems on your way, of if you had issues in understanding one of my directions. Now you can go and update your Xperia S with the lasts ROMs available. Take a look and see if the
Everything seemed to be working but the phone is stuck in Doomlords bootloops.
If i hold the volume up than i can enter CWM but the phone doesn,t start anymore.
The phone was running on a stock ICS ROM (i believe the Swiss one)
I flashed this kernel, 2.6.35.11/Doomkernel.nr1 and SDoomkernel v01 Modules.zip
Who can help me out since i,m stuck here.
doomlord kernel is for GB since youre on ICS try KA Kernel, XSX Kernel, and the Advanced stock ICS. look in the development section. you can flash it in CWM since youve flash doomlord kernel or try to flash via fastboot.
Thanks for your quick response, how can i put the kernel on the internal sd?
the phone doesn't start, so it wont be recognised by windows, i tried to mount in CWM but windows doesn't see it.
If i flash in fastboot mode, do i have to change the name again and wich name if i take the KA kernel for example.
Thanks
koossmatrooz said:
Thanks for your quick response, how can i put the kernel on the internal sd?
the phone doesn't start, so it wont be recognised by windows, i tried to mount in CWM but windows doesn't see it.
If i flash in fastboot mode, do i have to change the name again and wich name if i take the KA kernel for example.
Thanks
Click to expand...
Click to collapse
Just downlaod the advanced stock kernel (the fastboot link) and flash it in fastboot
It will boot :good:
just download any of the 3 but u need the .elf file and then flash via fastboot you dont need to change the name just used the name youve downloaded to flash.
for example : ics14.elf
used fastboot or adb
fastboot flash boot ics14.elf
you can also used the flashtool, flash via fastmode then choose the ics firmware you have then flash only the kernel. uncheck everything except the kernel.
but the easy way to do is flash via fastboot mode.
I just tried using flashtool, everything goes fine exept it doesnt flash.
Downloaded the Stock "Swiss" ROM and tried to flash with flashtool, it recognised the device, because it says device connected, then it askes to unplug en plug in the device, which i've done then the pop up that tells to disconnect/connect the device stays on and nothing happens.
I'm getting a little worried now...
Thanks for your replie
hey you have working fastboot right or adb? flash a kernel like what ive said above using fastboot,
or you can try this, dont connect your phone to pc yet, make sure it is turn off (hold power button +power up wait till it vibrates 3 times.)
1. open flashtool
2. choose your firmware.
3. when it says unplugged your phone,connect your phone to pc then hold power button +volume up wait till it vibrates 3 times, then hold power button + volume down then release it will flash.
Thanks for all the replies, i got it working.
Seems that i turned my phone one in fastboot mode and not the flashmode...oops
Flashed the original Swiss ROM again and it works again, thankgod!
But i dont want the original anymore, can i just flash another available rom on the android dev section or do i need to root? Sorry for beeing such a noob.
yes you can just flash any custom kernel it will give you auto root, then u can start flashing rom via cwm. just follow the instructions in every rom.
I am having the same problem as I am stuck with DoomLord's boot loop. I tried to flash ICS stock rom but cant get to flash it. I tried holding the power button + volume up key(until i get the three vibration) and then hold power button + volume up key and release, I get the same DoomLord's boot loop again. I am using X10 Flashing Tool Version 0.8.0.0 Somebody please help me. The device can fast boot.
download the latest flashtool, then download ICS stock firmware of your choice on the general section, then flash it via flashmode. (power+volume down)

Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without apk

Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without apk
!!!!!!THIS IS NOW ALL FIXED AND PROPERLY WORKING BY THESE INSTRUCTIONS HOPE THIS HELPS YOU ALL!!!!!!
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without
Q apk.
this is a guide I compiled from the following devs that are credited and thanked
below.
Apparently Google did not like that we are using our Q's again and have killed
the servers that host our Nexus Q apk, if you are currently logged into your Q
you will not notice it. If you try logging into another Q or relog into your Q for
the first time. It will not work any more.
I have 3 of these and want to keep the Q community alive, I needed to figure out
as many of you how to access your Q through adb if the app is dead to enable usb
debugging so you can load cheap cast and continue to use your Q.
This will get adb debugging back so you can load a custom recovery and get
cheapcast back running through CyanogenMod.
!!!!You will need a otg cable powered is a good idea these are $10.00 here ->
-------------------------------------------------------------------------------
To fastboot unlock your device / Credit and thanks to -> fiveipads
-------------------------------------------------------------------------------
1. cmd to platform-tools
2. Reboot to the bootloader -> cover your Q with your hand -> power on nexus Q as
soon as you see red remove your hand -> (will go solid red and you are in
bootloader)
3. Unlock your device* (with fastboot tool) (type) -> fastboot oem unlock
(immediately copy and paste this into tool and hit enter you have only 5 secs) ->
fastboot oem unlock_accept
4.Q will reboot and turn purple etc.
5.Unplug Q and restart in bootloader see #2. (type) -> fastboot getvar unlocked
(this verifies you unlocked your Q->should reply->unlocked:yes)IF NOT DO NOT
PROCEED TILL IT DOES.
-------------------------------------------------------------------------------
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/attachment.php?attachmentid=1563302&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.Flash the image -> (type in fastboot) -> fastboot flash boot boot-root.img
(image will write should say ok and writing boot etc.)
5.Pull the power on your q and restart the Q
-------------------------------------------------------------------------------
Load Clockwork Mod Recovery / Credit and thanks to -> Koush
-------------------------------------------------------------------------------
1.Download koush's ClockworkMod Recovery.
koush's ClockworkMod Recovery ->
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.1-steelhead.img
md5: dec2a809a20e8cb236ae092e71d8d5fe
2.Connect the Nexus Q to the computer via USB.
3.Make sure the fastboot binary is in your PATH or that you place the downloaded
image in the same directory as fastboot. (rename the downloaded recovery file
recovery-clockwork-6.0.3.1-steelhead.img to -> recoveryq.img to make it easy to
type)
4.Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader or by using the hardward -> cover your Q with your hand ->
power on nexus Q as soon as you see red remove your hand -> (will go solid red
and you are in bootloader)
5.Once the device is in fastboot mode, verify your PC sees the device by typing
-> fastboot devices
***If you don't see your device serial number, and instead see "<waiting for
device>", fastboot is not configured properly on your machine. See fastboot
documentation for more info.
6.FLASH ClockworkMod Recovery onto your device (type) -> fastboot flash recovery
recoveryq.img
(should confirm by okay if not do it again till it does)
7.(type) -> fastboot reboot (this will reboot your device to the factory startup
screen) -> (type) adb devices (make sure your device shows up) -> (type) -> adb
reboot recovery (you should be in clockworkMod recovery)
--------------------------------------------------------------------------------
Install Cyanogenmod to your Q through adb on Clockwork Mod / Credit and thanks to Cyanogen mod crew and hharte for amplifier support and Anthony Hopf for updated working zip file.
--------------------------------------------------------------------------------
1.Download the prebuilt release of CyanogenMod you wish to install.
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited. *****IF YOU CAN MIRROR THESE LINKS CONTACT ME WITH THE LINK*****
TAS5713 (Audio Amplifier):
Download: https://www.dropbox.com/s/vk77uq7dmpazzpz/cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: http://www.magicandroidapps.com/download/cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build. found here ->http://get.cm/?device=steelhead
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
2.Rename your cm10 file to -> cm10.zip (this will make it easier to type later)
3.Move your cm10.zip to your platform-tools folder again like you did the recoveryq.img file
4.To install boot into recovery mode (type) -> fastboot boot recovery.img (or if you are still at recovery ignore this)
5.When Q has reached recovery mode, push the cm10.zip to /sdcard using adb, (type) -> adb push cm10.zip /sdcard/
6.To push gapps (if desired download here -> http://goo.im/gapps/gapps-jb-20130301-signed.zip md5SUM: b7e53e96e1c8b1a1c4865bf29418c8e0 and rename to gapps.zip and move to platform-tools folder)(type) -> adb push gapps.zip /sdcard/
7.From within recovery, "install zip from sdcard" and browse to cm10.zip file After this has installed, it is a good idea to wipe data and cache.
8.Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps.zip file.
9.If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
10.Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu
OR YOU CAN INSTALL THIS ICS BASED ROM BASED ON THE STOCK IMAGE HERE->
http://api.viglink.com/api/click?fo...=Download it&jsonp=vglnk_jsonp_13777850981938
YOU MUST USE ICS BASED GAPPS.
--------------------------------------------------------------------------------
Install Cheapcast to q with auto boot option / credit and thanks to -> Sebastian Mauer and other devs involved (YOU NOW NEED THE OTG CABLE AND A MOUSE)
--------------------------------------------------------------------------------
1.Start your q get the otg cable plug it in wait for the Q to boot all the way the plug the mouse into the otg cable it should work.
2.+Sebastian Mauer's CheapCast allows an Android device to act as a target for #chromecast enabled applications. Android device == Nexus Q; chromecast enabled application == +Google Play Music.
3.Go to the asop brower on the Q and go to this link -> http://www.androidfilehost.com/?fid=23060877489999380
4.Download the apk do not use the store version at this time it is broken.
5.Using a file explorer find and open the apk it will be in the downloads folder. (you may need to authorize installing 3rd party apps in the security menu) once installed open cheapcast tick enable on startup and start sevices button. Now reboot your Q using a reboot button apk from the store.
6.Now your Q will be recognized as a target for any Chromecast enabled app upon startup, like Google Play Music it will also work on youtube as I have verified this, however if using the steelhead internal amp zip it will not output sound except to the internal amp. Use your device (I'm using my S4 GPE) to start and enjoy!
7.If for some reason the apk stops working on boot you may need to reinstall it and restart it for on boot starting. Your Q will now be on all day long so unplug it when not using it. until someoen makes a remote turn off apk or something.
Edit: All the XDA folks who put up a bounty? Please donate to Sebastian - grab the CheapCast app and hit the donate button!
______________________________________________________________________________
(If your Q boots up and the resolution looks wrong you will need to use a different tv or monitor ot happened to me)
I hope this help anyone like me who thought everything on this forums was way to hard to find and put together, this is all tested and is done how I typed it in.
If you mess it up DO NOT COME TO ME CRYING!
If I helped you, click my thanks button and send your donations to all the devs mentioned above, also donate to cheap cast to make it stay around.
Obviously Google does not want us to keep using our Q balls so make sure we keep devs working for us here by posting and showing interest.
Thanks- Ian
OTG cable
At what point did you need an OTG cable? Looks like you did all this via PC? Thanks so much!!!! I have two of them, both had USB debugging enabled until I did factory resets on them this morning. <sigh> The folks at Google were very nice and excruciatingly unhelpful when I called them about it this afternoon. But... apparently a "Nexus Q expert" will get back to me very soon, and I'm sure the response will be the standard Google canned response regarding the Q.
Still trying to figure out how to authorize adb debugging with only 1 usb port please someone explain
Figured it out
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
unknownkwita said:
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
Click to expand...
Click to collapse
I will try that later and report back if it works for me
This is now all fixed and working correctly!
im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing
Could someone please post a video on youtube of how to do this?
dts924s said:
Could someone please post a video on youtube of how to do this?
Click to expand...
Click to collapse
Seriously....read man....... its laid out exactly how to do it.
If you need a video you do not need to be hacking your Q
ianandamy said:
This is now all fixed and working correctly!
Click to expand...
Click to collapse
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
kario said:
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
Click to expand...
Click to collapse
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
Should be: fastboot flash boot boot-root.img
ianandamy said:
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
Click to expand...
Click to collapse
Once this rom is installed how does one get past the nexus q welcome screen?
I still can't believe that CM didn't integrate the amp functionally in their ROM..
watso4183 said:
Once this rom is installed how does one get past the nexus q welcome screen?
Click to expand...
Click to collapse
Hit the "home" key on your KB.
Lokifish Marz said:
Hit the "home" key on your KB.
Click to expand...
Click to collapse
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
ianandamy said:
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
Click to expand...
Click to collapse
Remove or rename AtHomeThemeService.apk, HubBroker.apk and Visualizer.apk from v1.0.2 and flash it. This will remove the stock Q services/frontend without breaking the audio output.
Thanks for the great guide, I just bought my Q a few days ago. I will definitely try this out. It is good to know, that the community is still alive.
Sent from my Nexus S using Tapatalk 4
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/atta...2&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.This is to test it first before you permanatly install it -> (type in fastboot)
-> fastboot boot boot-root.img (If the device reboots and the mute light goes
from red to off then you've successfully booted! Run `adb devices` to ensure it's
showing up and that you can connect to it. If all goes well (which it should)
then you can flash the boot image)
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
(image will write should say ok and writing boot etc.)
6.Pull the power on your q and restart the Q
-------------------------------
you have fastboot flash boot-root.img
its supposed to be-- fastboot "flash boot" boot-root.img

[GUIDE] Redmi K20 Pro - Unlock & Root Information, Links, Tools and Instructions

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)

Question How to fix bootloop?

I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful

Categories

Resources