The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.
I've tried again on Chrome,IE and Firefox but still get Decrypt message.
Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit
Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.
fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp
Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.
People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.
MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.
jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.
Hello, this works fine very thx, but you have recent/new mix version?
Related
Please help!
I am currently trying to root my TF701t on Jellybean but I appear to have corrupted my bootloader. I can boot into the bootloader and do a system wipe and boot Andoid, but when I select the RCK option I end up with the Android image on its back.
I have downloaded CWM 6.0.4.6 and tried to apply the recovery.img file via Minimal ADB and Fastboot command prompt only to be greeted with "cannot load "recovery.img" Result too large".
To be clear the system boots normally and fuctions perfectly - this is strictly a bootloader issue which has been unlocked successfully.
Any help would be greatly appreciated and apologies in advance if either the solution to this has been posted elsewhere or I have not given you the information you require to help.
Many thanks,
East
You need to fastboot recovery from the bootloader.
When you reboot into the bootloader do not select RCK. RCK is the recovery, I don't think the default one can do anything, you just get the android on it's back.
So it should be reboot into bootloader and then don't touch your tablet.
Then from your pc fastboot flash recovery recovery.img
Make sure you are also on a 4.3 bootloader before you fastboot flash CWM 6.0.4.6.
The instructions above are correct
To flash a recovery you need to have the fastboot.exe file and cwm recovery.img file in the same folder.
Right click + shift on the folder they are in and choose open command prompt here
Boot into the Bootloader by either booting with the Power and Volume Down Buttons held down until you get the 3 icons or by typing the following into the command prompt.
Code:
adb reboot bootloader
Then type the following commands to flash the recovery image:
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Start the recovery by making sure the RCK icon is highlighted (use volume down to move) and push volume up to select.
sbdags said:
Right click + shift on the folder they are in and choose open command prompt here.
Click to expand...
Click to collapse
In Windows 7 you can just navigate to the folder with explorer and in the address bar type cmd and hit enter
Opens a command prompt in the correct folder
Doh!
Thank You
Well.......this is very embarrassing.
I have rooted and installed custom roms on my last 3 phones including the my new Nexus 5 without any problems at all. I simply followed the instructions posted by the developers. At the same time I used to take the piss out of the other posters who raised queries because they hadn't followed the instructions. What do I do? Exactly that.
Please accept my apologies sbdags as it is your rom I am installing and thank you to You & Sleeepy2 for posting polite and prompt replys without having a go at me for not following your instructions.
Problem solved I am now rooted!
Thank you again.
East
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
When i try to boot into fastboot mode using power key and volume - key, it shows me a blank screen :crying::crying: . there is no bunny with fastboot logo. only black screen.anyone help me please.
Note: I am on pie with march update.
feroz mahmud said:
...there is no bunny with fastboot logo. only black screen....Note: I am on pie with march update.
Click to expand...
Click to collapse
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Aerobatic said:
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Click to expand...
Click to collapse
Will you please tell me the process of flashing splash? And where do i get this file?
feroz mahmud said:
Will you please tell me the process of flashing splash? And where do i get this file?
Click to expand...
Click to collapse
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
So, you will need:
1. Mi A2 with unlocked bootloader and critical partitions (search this forum on how to unlock) in bootloader mode, connected to USB 2.0 port in PC;
2. Working drivers and / ADB / fastboot installation.
3. "splash.img" copied into directory of working ADB / fastboot installation.
To check that requirement (1) and (2) are fulfilled, run CMD shell in directory of working ADB / fastboot installation and type
Code:
fastboot devices
If output list contains the only 1 string with ID of device (same as shown by "ADB devices -l" command in normal MTP file transfer mode), you are ready to type in commands:
Code:
fastboot flash splash .\splash.img
fastboot reboot bootloader
You are supposed to see the 'bunny' after phone reboots to bootloader mode once again. To reboot back to system just use "fastboot reboot"
If above is not helpful, bring phone to service
Aerobatic said:
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
Click to expand...
Click to collapse
thanks for you information. my device is locked. when i try to peform fastboot devices , it shows me a error saying application was unable to start correctly.
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Aerobatic said:
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Click to expand...
Click to collapse
thanks for your information.
My devices is locked(bootloader). and fastboot isn't showing up. now tell me how do i flash spalsh file?
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
Following is what you could have already found in guides I was suggesting to find and study
2. Prepare everything for unlocking in phone:
2.1. Get "developer rights"
2.2 Allow "USB debugging" and "OEM unlocking" in developer options
3. Have you get acquainted with ADB drivers installation and ADB commands and fastboot commands?
Can you see result of "adb devices -l" command in CMD shell when phone is attached to USB-2.0 port with MTP file transfer enabled?
If no, just bring it to service or somebody who knows what to do.
4. Can you see result of "fastboot devices -l" command in CMD shell when phone is attached to USB-2.0 port in what is supposed to be bootloader mode with black screen?
If no, just bring it to service or somebody who knows what to do.
5.. If yes, and device ID is the same as in result of "adb devices -l" command
6. Unlock bootloader and critical (see guides here in Mi A2 threads), it takes 2 commands and 2 reboots
7. Reflash splash.img as stated above in my 1st message
Nobody here can repair your phone, - only you or service. So I won't write more here.
Aerobatic said:
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
.
Click to expand...
Click to collapse
Can you help me with this? my phone is ok, when i run fastboot command it shows me "??????????? fastboot"
Restart pc or update adb and drivers.
as title ... How to make Bank Application work on my unlocked K20 Pro Indian ROM?
it was mi 9t pro and i switched to the Miui 11 Indian ROM.
kindly explain steps and include links if any.
appreciate help.
NaAZoOR said:
as title ... How to make Bank Application work on my unlocked K20 Pro Indian ROM?
it was mi 9t pro and i switched to the Miui 11 Indian ROM.
kindly explain steps and include links if any.
appreciate help.
Click to expand...
Click to collapse
Flash magisk --> magisk hide.
Just watch that guy on YouTube.
https://youtu.be/MapOXLH5Gkg
Kollachi said:
Flash magisk --> magisk hide.
Just watch that guy on YouTube.
https://youtu.be/MapOXLH5Gkg
Click to expand...
Click to collapse
How to flash magisk?
kindly provide steps & links if any
Sent from my Redmi K20 Pro using XDA-Developers Legacy app
NaAZoOR said:
How to flash magisk?
kindly provide steps & links if any
Sent from my Redmi K20 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127
Kollachi said:
https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127
Click to expand...
Click to collapse
the below quote includes steps to flash TWRP & Magisk from the link you provided, my question is:
after rooting via Magisk, am i able to get OTA updates from Xiaomi for the device normally or just like the old days, once rooted no more updates to come?
and is it sure that bank app will work normally after flashing Magisk??
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.
Click to expand...
Click to collapse
NaAZoOR said:
the below quote includes steps to flash TWRP & Magisk from the link you provided, my question is:
after rooting via Magisk, am i able to get OTA updates from Xiaomi for the device normally or just like the old days, once rooted no more updates to come?
and is it sure that bank app will work normally after flashing Magisk??
Click to expand...
Click to collapse
I don't know about OTA. I don't have Miui on my device. And bank apps work for me with magisk hide.
miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)
sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?