[RECOVERY] [OFFICIAL] [TREBLE] TWRP for Xiaomi Redmi 3S/Prime/3X [land]
- Thread starter darshan1205
- Start date
How can I execute the command?
Sorry, but I don´t know how execute the command "fastboot flash recovery twrp-3.1.1-0-land.img" in fastboot mode.
Could you tell me?
:crying:
Sorry, but I don´t know how execute the command "fastboot flash recovery twrp-3.1.1-0-land.img" in fastboot mode.
Could you tell me?
:crying:u can flash image via twrp.Sorry, but I don´t know how execute the command "fastboot flash recovery twrp-3.1.1-0-land.img" in fastboot mode.
Could you tell me?
First, you need to download an adb and fastboot package (just google...)Sorry, but I don´t know how execute the command "fastboot flash recovery twrp-3.1.1-0-land.img" in fastboot mode.
Could you tell me?
Then you need to extract it somewhere on your pc.
Then you copy your "twrp-3.1.1-0-land.img" into the same folder where adb.exe and fastboot.exe is located.
Then you rename your "twrp-3.1.1-0-land.img" into "recovery.img".
When you have Windows 10: Hold shift and rightklick somewhere in the white (whithin the adb-folder) -> "open power shell window here"
In Power shell just type "./fastboot flash recovery recovery.img"
If you get "waiting for device" you have to install the google adb driver: download it (google), extract it somewhere and install the driver manually via device manager - when you get to choose the driver, choose "android bootloader device".
Windows 7: Hold shift and rightklick somewhere in the white -> "open command prompt here".
In command prompt: "fastboot flash recovery recovery.img"
If you get "waiting for device" you have to install the google adb driver: download it (google), extract it somewhere and install the driver manually via device manager - when you get to choose the driver, choose "android bootloader device".
And it´s clear: your device has to be in the fastboot mode (pwr + vol-)
Chears!
Last edited:
Anyone else getting extracttarfork error 255 when trying to restore from a backup? (Data, Boot and System).
Edit: Just restored from an older backup (made with an older version of TWRP) and it seemed to have restored fine. Also just made a new backup and immediately restored it. It also went fine. Huh? am I just suuuuuuper unlucky?
Edit: Just restored from an older backup (made with an older version of TWRP) and it seemed to have restored fine. Also just made a new backup and immediately restored it. It also went fine. Huh? am I just suuuuuuper unlucky?
Last edited:
I have got this error both with official twrp or unofficial one..
I backed up miui 9 china dev rom but failed when i tried to restore.
I backed up miui 9 china dev rom but failed when i tried to restore.
Attachments
Not sure if anyone is familiar with this error: extractTarFork() process ended with ERROR: 255. I get this when I try to restore from a backup. Backups made before with an unofficial build of TWRP restore fine. I've tried reverting back to the older TWRP version but it still displays the same error when trying to restore :S. I pulled this from the log:
Error extracting '/sdcard1/TWRP/BACKUPS/a672d4397d53/2017-09-02--02-42-51_land-userdebug_7.1.2_NJH47F_dec3852f39_rele/data.ext4.win002
So somethings wrong with this file? why is it creating bad files? Whats odd is, if i restore a working backup and install a few apps (Chronus, Twrp and a theme) it will backup fine but then produce the error 255 when trying to restore :S
Anyone? I've been messing with this since yesterday, any input would be greatly appreciated!
Edit: So I guess TWRP pulls the time, timezone and date from the Android system? Chronus was doing something to whatever TWRP needs for this and this is why I couldn't restore anything. Removed the app, TWRP's time settings returned to normal and I was able to make and restore backups again. So Chronus = extractTarFork() process ended with ERROR: 255
Error extracting '/sdcard1/TWRP/BACKUPS/a672d4397d53/2017-09-02--02-42-51_land-userdebug_7.1.2_NJH47F_dec3852f39_rele/data.ext4.win002
So somethings wrong with this file? why is it creating bad files? Whats odd is, if i restore a working backup and install a few apps (Chronus, Twrp and a theme) it will backup fine but then produce the error 255 when trying to restore :S
Anyone? I've been messing with this since yesterday, any input would be greatly appreciated!
Edit: So I guess TWRP pulls the time, timezone and date from the Android system? Chronus was doing something to whatever TWRP needs for this and this is why I couldn't restore anything. Removed the app, TWRP's time settings returned to normal and I was able to make and restore backups again. So Chronus = extractTarFork() process ended with ERROR: 255
Last edited:
DARSHAN, can u give the telegram link of team hyper so, i can know about the development of Android O on Redmi 3s
Hello, I faced a weird behaviour recently.
The recovery couldn't detect otg connections.
I've tried another twrp. It was working fine there though. Would I have to post logs for this?
Could you confirm this issue?
Thank you. Fixes it.
I was in too much of a hurry, that i forgot about it.
My current twrp v3.0.2.
I installed official img 3.1.1-0 by rebooting to recovery.
Phone bootloops.
I have to again install twrp 3.0.2 using fastboot-PC method.
Am i doing something wrong?
what is the solution?
I installed official img 3.1.1-0 by rebooting to recovery.
Phone bootloops.
I have to again install twrp 3.0.2 using fastboot-PC method.
Am i doing something wrong?
what is the solution?
Try installing twrp 3.1.1-0 by fastboot method. It worked for me.