Database Develop

[Recovery] ClockworkMod - TF701T Proxy Thread

{
"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"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot

Video Tutorial
Video Tutorial Thanks @wwjoshdew

Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?

CWM 6.0.4.7
OP Updated

Feb/2 OP updated

Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.

I was on 6.0.4.6 and i used flashify to update. Worked fine.

hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app

@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g

wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!

OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew

recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.

@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?

sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...

I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?

lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.

sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.

lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us

updated.

Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.

[NEW LAYOUT][RECOVERY][3.x] Team Win Recovery Project [22/06/2016]

TWRP 3.x for HTC Incredible S​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface - no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
This is TWRP recovery 3.x compiled for HTC Incredible S. Credits go to Team Win for this awesome recovery.
This specific recovery uses the new layout, meaning that the sdcard is used as the data partition.
How to Install
Download the recovery from the link below
Make sure you have fastboot installed
Open a terminal in Mac or Linux, or Command Prompt in Windows
Go to the directory where the recovery is placed
Then flash using this command:
Code:
fastboot flash recovery path_to_recovery.img
Tip: Type "fastboot flash recovery " and then drag the recovery file into the terminal.
Before installing a ROM, make sure you have switched to the new data layout.
Please scroll down to the third post to find out how to do this.
Download
TWRP 3.x
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the HTC Incredible S
Contributors
rqmok
Source Code: https://github.com/rqmok/android_device_htc_vivo/tree/cm-13.0
Version Information
Status: Stable
Stable Release Date: 2016-06-22
Created 2016-06-22
Last Updated 2016-07-01

Changelog
22/06/2016
- Initial Release

Switching to the new data layout
* Make sure you have backed up everything because everything will be wiped!
- Install the recovery with the new data layout.
- Reboot to recovery.
- Go to "wipe".
- Press "Format Data".
- Type "yes" (without the quotes) then press enter/return on the keyboard.
- Go back to "wipe" and select "Advanced Wipe".
- Select everything in the list.
- Then Swipe to Wipe.
- Go back to the main screen.
- Go to "Reboot" and select "Recovery".
- After rebooting recovery, you are ready to install the ROM.
- Do not forget to attach the phone to your pc and copy over the ROM and GApps.

I have only a black screen

rqmok said:
Switching to the new data layout
Click to expand...
Click to collapse
Installation work properly.
Code:
R:\2011-02_Incredible_S_vivo_S710D\_Recovery\TWRP_by_rqmok\New_Layout>fastboot flash recovery recovery.img
sending 'recovery' (8578 KB)...
OKAY [ 2.257s]
writing 'recovery'...
OKAY [ 1.199s]
finished. total time: 3.457s
R:\2011-02_Incredible_S_vivo_S710D\_Recovery\TWRP_by_rqmok\New_Layout>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
And here we have TWRP 3.0.2.0 on S710D.
{
"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"
}

I can't use, I have reboot after a black screen

help, how do I fix black screen ??

raiden.80 said:
help, how do I fix black screen ??
Click to expand...
Click to collapse
Try using this recovery.

Why do we need to use sdcard as data partition? This will decrease performance even more.

when i try to install the recovery it say "fast boot does not recognize as internal or external command". what should i do?help me pls

rinart73 said:
Why do we need to use sdcard as data partition? This will decrease performance even more.
Click to expand...
Click to collapse
Because there isn't enough place for the rom and gapps in normal layout

how to install it without pc
I mean can i zip it as PG32IMG and copy it to sd-card then flash it

I'm having problems with this recovery: it hangs on the TWRP boot screen so I cannot proceed to wipe in order to use the new format.
I'm unlocked s-on and previously used vivkat with clockwork 5.0.2.0.
Never mind, after removing the sdcard it worked.

my computer can't recognize my phone in fastboot mod , i have alredy installed htc driver , plase heilp me

Majid121b said:
my computer can't recognize my phone in fastboot mod , i have alredy installed htc driver , plase heilp me
Click to expand...
Click to collapse
I have same case with you.
WA ==> keep trying by plug-unplug until PC recognized your phone.
You need to have the fastboot ready with the command, once the phone detected then press ENTER
Good luck

touch screen damage and does not work properly
I have HTC incredible and I install TWRP 3 . my touch screen can not work good and some places in my touch screen can not work properly when I want format all of data and use new layout and I type yes , and want press Enter , it does not work , so I have to choose wipe all . can I use another method for format all data and use new layout?

I have Incredible s and install cyanomdod 5.1 on it and when I want install gapps on it , twrp 3 said you ROM 6.1 and you must install gapps 6.1 and can not install it.
twrp detect my OS is 6.1, but my OS is 5.1. I use gapps nano for install it.

Link down
Hello!
Can anyone post a mirror for this recovery? The original link is down.
Thanks!

Soft BRICKED A2 (bootloop)

I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE

Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully

try fastboot flashing unlock_critical

munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"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"
}

Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot

munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please

Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img

What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.

Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.

Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585

I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.

HELP: Bricked P20 Pro - "Getting package info failed"

Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this
{
"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"
}
.
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
My Model : CLT-L29C432
Please help..
I have placed down here some more info from fastboot which may could help,,
*****************
PS C:\adb> fastboot oem get-product-model
(bootloader) CLT-L29
OKAY [ 0.004s]
Finished. Total time: 0.005s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.004s
PS C:\adb> fastboot oem get-build-number
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.004s]
Finished. Total time: 0.004s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.020s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.005s]
Finished. Total time: 0.006s
PS C:\adb>
*******************

I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)

Anutter226 said:
I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)
Click to expand...
Click to collapse
ATt least your TWRP is working, .. even it is useless.. looking forward for solution..

alfrqan said:
Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this .
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
Please help..
Click to expand...
Click to collapse
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.

You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches

After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)

I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn

KennyDumah said:
I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn
Click to expand...
Click to collapse
So you should just flash stock boot.img to be able to boot to os again....

Anutter226 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.

side_flip15 said:
You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches
Click to expand...
Click to collapse
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
Sounds interesting. will give it a try.

side_flip15 said:
So you should just flash stock boot.img to be able to boot to os again....
Click to expand...
Click to collapse
I download several update.zips and up pack them and so far i could not find this file in :boot.img:

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
can i know which TWRP you have used here?

YellowSnowman23 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I have tried this without success. I used to flash imgs by "fastboot flash system xxx.img"

alfrqan said:
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..
Click to expand...
Click to collapse
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.

side_flip15 said:
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.
Click to expand...
Click to collapse
I tried a lot of them.. but still not able to boot into TWRP

alfrqan said:
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.
Click to expand...
Click to collapse
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]

alfrqan said:
can i know which TWRP you have used here?
Click to expand...
Click to collapse
Always unofficial, it's the most functional

Update>>
I have visited Huawei service center in Madrid and they said "there is no way to repair it, you have to change the motherboard". This is ridicules and I dont believe that.

YellowSnowman23 said:
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]
Click to expand...
Click to collapse
hey,
I have downloaded and extracted many official and found the following files unzip file (update.zip):
for system: SYSTEM.img
command: fastboot flash system SYSTEM.img
Result: error: cannot load 'SYSTEM.img'
For RECOVERY_RAMDISK: RAMDISK.img
command:
Result:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16384 KB)...
OKAY [ 0.369s]
writing 'recovery_ramdisk'...
OKAY [ 0.140s]
finished. total time: 0.509s
conc. still not booting only fastboot commands,,,,,,

General 📌 [Shared] TWRP by skkk

A12/A13
-----------------------
{
"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"
}
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
or
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
--------------------------------------------------------------------------------------------------------
REC VERSION
Install with TWRP or fastboot***
flash recovery_ab twrp.img(cmd)
or
./flash recovery_ab twrp.img(Power Shell)
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
---------------------------------------------------------------------------------------------------------
DOWNLOAD
REC VERSION
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/zeus/
__________________________________________________________________________________
Boot version A13
https://mega.nz/folder/7g0EUAxK#HYD-Wl65HCYKa8PiwSsLKQ
Spoiler: Change the language.

woohooo!

hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.

alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
me to

alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
bootloader must be unlocked
What command did you use?

NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
i unlocked bl, and i even had magisk installed, maybe magisk's the reason?
command i use:
fastboot flash recovery twrp-3.6.2_12-v3.8.2_A12-zeus-skkk.img

NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
flash recovery twrp.img
Bootloader Open

ttistvn said:
flash recovery twrp.img
Bootloader Open
Click to expand...
Click to collapse
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/

NOSS8 said:
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/
Click to expand...
Click to collapse
worked like charm. i was being noob. thx

Working on the a partition
Command :
fastboot flash boot_a twrp.img

Thank you very much
NOSS8​. He works

Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?

karkiankit said:
Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?
Click to expand...
Click to collapse
Normally yes

updated today

dont flash TWRP.
TWRP A12 flashing instructions:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.

Very nice.....waiting for updated zip rom....

updated today

new update...very nice working..

new update 3.6.2_12-v3.9 working fine no issues as of now

trinadhchinna7 said:
new update 3.6.2_12-v3.9 working fine no issues as of now
Click to expand...
Click to collapse
Me too