Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Unlocked bootloader is required.
Installation
To temporarily boot this recovery:
Code:
fastboot boot mali.img
To permanently install it:
fastboot flash recovery mali.img
Done!
Download
Mega
XDA:DevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@Electimon
@dejello
Version Information
Status: Beta
Created 2019-04-27
Last Updated 2019-04-27
It's of no use now that there are no 64 bit roms.
Chirag91 said:
It's of no use now that there are no 64 bit roms.
Click to expand...
Click to collapse
We already have an Android 10 X64 Rom in testing, and also an X64 version of Orange Fox Recovery.
Wvanderlei21 said:
We already have an Android 10 X64 Rom in testing, and also an X64 version of Orange Fox Recovery.
Click to expand...
Click to collapse
That's wonderful is radio, bluetooth working?
Chirag91 said:
That's wonderful is radio, bluetooth working?
Click to expand...
Click to collapse
Practically everything works, the developer is only correcting some small bugs ...
Electimon said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Unlocked bootloader is required.
Installation
To temporarily boot this recovery:
Code:
fastboot boot mali.img
To permanently install it:
fastboot flash recovery mali.img
Done!
Download
Mega
XDA:DevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@Electimon
@dejello
Version Information
Status: Beta
Created 2019-04-27
Last Updated 2019-04-27
Click to expand...
Click to collapse
Can you upload it to another site? My transfer quota is exceeded in mega...
Someone knows how to downgrade this recovery?
Decryption doesn't work just like dejellos TWRP.
Source
Where is the source for this recovery?
it says image is corrupt but when i booted it it worked
sans1131 said:
it says image is corrupt but when i booted it it worked
Click to expand...
Click to collapse
The bootloader is expecting the stock recovery.img; not mali.img. it is also expecting a certain hash and other identifying features.
To the bootloader the image is corrupted. To us, it`s a modern miracle.
sans1131 said:
it says image is corrupt but when i booted it it worked
Click to expand...
Click to collapse
not OEM = corrupt
in combination with a unlocked bootloader = every image is corrupt, even OEM ones
is it normal, that when Im restoring a backup of a rom it is like fresh installing the rom? None of my installed apps are restored, all app data is gone... Did I something wrong or is this custom recovery not working correctly. I mean why should I do a 9gigabyte backup and restore it to get the same result as I could have when simply flashing the 600MB ROM zip
externus said:
is it normal, that when Im restoring a backup of a rom it is like fresh installing the rom? None of my installed apps are restored, all app data is gone... Did I something wrong or is this custom recovery not working correctly. I mean why should I do a 9gigabyte backup and restore it to get the same result as I could have when simply flashing the 600MB ROM zip
Click to expand...
Click to collapse
Did you backup /data??
WoKoschekk said:
Did you backup /data??
Click to expand...
Click to collapse
I backed up everything that was available. I think for Data was something like "no ext." mentioned.
Did I had to Mount something before backup/restore?
Its some years ago that I used a custom recovery because of that I was curious about my problem.
externus said:
I backed up everything that was available. I think for Data was something like "no ext." mentioned.
Did I had to Mount something before backup/restore?
Its some years ago that I used a custom recovery because of that I was curious about my problem.
Click to expand...
Click to collapse
No, it's not necessary to mount any partition.
Maybe decryption issues?
Ever since installing this, rebooting always goes into the bootloader. From the bootloader, I can boot into system or recovery without a problem, but... well, there must be a way to fix this. I know that others have the same problem, but has anyone found a fix?
Cheers
fastboot flash recovery mali.img
target reported max download size of 534773760 bytes
sending 'recovery' (21620 KB)...
OKAY [ 0.505s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.355s]
finished. total time: 0.860s
--> when booting into recovery: "no command". ---> there a fix? Using the "boot" command it is working perfectly, but I'd like to flash so I can install Official RR ROM
fabit00 said:
fastboot flash recovery mali.img
target reported max download size of 534773760 bytes
sending 'recovery' (21620 KB)...
OKAY [ 0.505s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.355s]
finished. total time: 0.860s
--> when booting into recovery: "no command". ---> there a fix? Using the "boot" command it is working perfectly, but I'd like to flash so I can install Official RR ROM
Click to expand...
Click to collapse
Flash TWRP and boot directly into recovery by using Vol-/+ and Power. Do not boot the device into system!
WoKoschekk said:
Flash TWRP and boot directly into recovery by using Vol-/+ and Power. Do not boot the device into system!
Click to expand...
Click to collapse
Okay, so:
1. security settings to lock option "password" instead of "pattern" (why you will see in step 7 & 8.)
2. power off
3. power button + volume down --> bootloader
4. in powershell putting "fastboot flash recovery mali.img" command with the output of post #18
5. via volume down button selecting "boot into recovery"
6. TWRP shows up with the "decription"
7. I enter the password which I set in the OS in step 1
8. "decription error" --> okay, so I cancel, then going to
9. "Install" in TWRP ---> /sdcard nothing there, altough there should be my zips (RR and magisk)
Thanks!
Edit:
Model XT1925-5 with latest Stock ROM (PPSS29.55-337-7-10) installed and bootloader unlocked (of course)
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Features:
All function in a normal TWRP
Support F2FS file system!
Battery capacity display works well!
Supported device:
C8817D
C8817E
G621-TL00
G620S-UL00
G620S-L01
Che1-CL20
Che1-CL10
Che1-L04
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Run "fastboot flash recovery twrp2.8.7.0_cherry_en_f2fs.img" in command line
4. Reboot and enjoy it
Download:
https://s.basketbuild.com/filedl/devs?dev=dianlujitao&dl=dianlujitao/cherry/twrp2.8.7.0_cherry_en_f2fs.img
XDA:DevDB Information
TWRP, Tool/Utility for all devices (see above for details)
Contributors
dianlujitao
Source Code: https://github.com/dianlujitao/android_device_huawei_cherry/tree/twrp
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-09-12
Created 2015-09-12
Last Updated 2015-09-17
Hi, thank you for your good work...
i would like to mention i made a back up of stock rom with your twrp for 620s-L01...
When i restore that back up, i don't have ril connection, i am not asked for my code pin
I am unable to flash recovery . It is showing success in fastboot but stock recovery is booted even after flashing this recovery. I am able to boot into recovery by connecting to pc. (fastboot boot twrp2.8.7.0_cherry_en_f2fs.img). What to do?
Madhunath said:
I am unable to flash recovery . It is showing success in fastboot but stock recovery is booted even after flashing this recovery. I am able to boot into recovery by connecting to pc. (fastboot boot twrp2.8.7.0_cherry_en_f2fs.img). What to do?
Click to expand...
Click to collapse
do " sudo fastboot boot twrp2.8.7.0_cherry_en_f2fs.img"
Madhunath said:
I am unable to flash recovery . It is showing success in fastboot but stock recovery is booted even after flashing this recovery. I am able to boot into recovery by connecting to pc. (fastboot boot twrp2.8.7.0_cherry_en_f2fs.img). What to do?
Click to expand...
Click to collapse
You should flash the latest official release.
I met the same issue and solved it by this.
It seems that the very very old bootloader will restore official recovery and boot automatically.
desalesouche said:
Hi, thank you for your good work...
i would like to mention i made a back up of stock rom with your twrp for 620s-L01...
When i restore that back up, i don't have ril connection, i am not asked for my code pin
Click to expand...
Click to collapse
When backup a AOSP-based build, select system,data,boot partition is OK.
I don't use emui, but I backup and restore a cm, it's okey
Any mirror on this? Basketbuild is not working with me...
jerryhou85 said:
Any mirror on this? Basketbuild is not working with me...
Click to expand...
Click to collapse
http://bbs.zhiyoo.com/thread-9673037-1-1.html
Please, dear friend now for Perth che2-l11
PleasePleasePleasePlease
Hi Sir will you try to compile M twrp?
desalesouche said:
Hi Sir will you try to compile M twrp?
Click to expand...
Click to collapse
Tried on nubia z9 max, nothing different
Hi Guys,
I attempted to install the twrp recovery and fastboot seemed to install it ok, but I can't get into it via vol-up & power. when i try to boot the recovery using fastboot (under windows) i get the following :
C:\ADB>fastboot boot twrp2.8.7.0_cherry_en_f2fs.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.343s
The phone is running the new che2-l11 lollipop 5.1 build ... could this be the problem? The phone IS unlocked.
Just tried it again on a different pc. and the phone is sitting on the honor boot screen with vol-up & power.
martzweb said:
Hi Guys,
I attempted to install the twrp recovery and fastboot seemed to install it ok, but I can't get into it via vol-up & power. when i try to boot the recovery using fastboot (under windows) i get the following :
C:\ADB>fastboot boot twrp2.8.7.0_cherry_en_f2fs.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.343s
The phone is running the new che2-l11 lollipop 5.1 build ... could this be the problem? The phone IS unlocked.
Just tried it again on a different pc. and the phone is sitting on the honor boot screen with vol-up & power.
Click to expand...
Click to collapse
This recovery is for Qualcomm 410 varient
may i ask you to update twrp for cm12.1? it seems to be broken due to cm12.1 update?
i would like to add some more device .
What the hell does Cherry have to do with anything? This is a Cherry recovery?
Honor 4x model Che2-L11 custom recovery
hi
I installed twrp for Honor 4x model Che2-L11 and worked perfect
1-install ADB Fastboot
copy TWRP_2.8.7.x_P8Lite_kirin_v2.img ADB Fastboot installation folder
hold shift key and write click on ADB Fastboot installation folder choose "open command window here"
2-run adb reboot bootloader
3- run fastboot.exe flash recovery "TWRP_2.8.7.x_P8Lite_kirin_v2.img"
note phone must be unlocked and aslo installphone driver
HiSuite (install it driver included)
note:
to check phone is connected
run
adb devices
fastboot device
twrp2.8.7.0_cherry_en_f2fs.img not worke for me(Honor 4x model Che2-L11)
download img:
http://forum.xda-developers.com/showpost.php?p=62598513&postcount=156
help
hi please help me, how can i install cynogen mod in honor 4x,
please hlep me step by step
i have che1-L04
Is twrp3 coming?
Can I use this twrp recovery for my Che2-UL00 please?
Never mind, just being dumb... I fixed it myself
Okay guys, I'm in full panic mode. I was just getting ready to reinstall my X with Lineage OS. I had CM 13.0 up until now. I've backuped everything, then powered off my phone (simple, normal power down).
After that I was trying to get into TWRP (I had 2.x.x.x installed), but VolDown+Power got me in a boot loop. The OnePlus Logo flashes, phone vibrates short then reset and it flashes/vibrates again. I tried booting normally, that doesn't work either.
The only thing I can do is get into fastboot, but I can't flash anything! The phone says it's locked (though I unlocked it before I put CM 13.0 on it)
Code:
c:\Android>fastboot flash recovery twrp-3.1.1-1-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (16002 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.509s
c:\Android>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
c:\Android>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
Help! I can't boot my phone and I can't flash anything either. Is there anything I can do or missed?
After 2 hours of trying everything I found I'm now at a point where I could install the original (?) recovery via the MSM DownloadTool 2.0.2. Now I have a recovery which looks like stock... I can "Install from local" and "Install from USB". Tried the latter and I get the "adb sideload" mode. Tried to upload the latest Lineage OS Nightly through this sideload, but it fails after 47%.
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
intoxicated.mad said:
If possible Flashing oos 3 might help or there's unbricking guide for opx you might want to see
Click to expand...
Click to collapse
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Anyway you got out of trouble ??
I have the exact same problem, only I am running Sultan's ROM. Unfortunately, my phone is not backed up, because I wasn't going to install a new rom or anything. Is there any way to restore my phone without losing data. I downloaded the MsmDownloadTool V2.0, and am wondering if I could replace the stock recovery.img in there with the one for my ROM, or would this not work?
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
drunken_m said:
Thanks! That was actually the solution: the stock recovery can only flash OOS, it seems. I flashed OOS 3.1.4, then enabled oem unlock, flashed TWRP and Lineage.
Still no idea why my phone wouldn't boot after powering it off or why my bootloader was locked in the first place.
Click to expand...
Click to collapse
I also faced that issue too and it happens when you have installed custom rom or recovery without first unlocking the bootloader. Do It Now If you haven't
Actually the bootloader was already unlocked (I needed that to install CM in the first place), but I think I accidentally re-locked it when I tried to remove root (to install a banking app).
As I wrote I already fixed the issue by installing the original bootloader/recovery and OOS over a serial link, then unlocked the bootloader again and installed the latest TWRP And Lineage. So all is fine now.
adamantiumXT said:
Ok, so I tried replacing the recovery.img, and it didn't work, so I used the original one from the tool and dirty flashed OOS 3.1.4. All my original files and apps are still there, but none of them will open, except for google apps, which I assume came in the OOS ROM (Google Play works but says 'download pending' if I try to download an app). Unfortunately, this mix of software doesn't let me enable developer options in the settings (when I tap the build number nothing happens) so I can't use ADB to make a backup. I think the only way to get things working is to do a clean install OxygenOS, which would lose all my files. I'll think I'll try to use a file manager to copy the contents of the internal storage to a USB device, then do a full clean install.
Also, in this weird state of software, only the back button works, the home and recent apps keys don't, so if I do something in Chrome, I need to restart the phone to do something else
Click to expand...
Click to collapse
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
drunken_m said:
Rule #1 of flashing: always have a backup ready.
If you have TWRP installed and can get into recovery you can pull your files via ADB. After that I'd also recommend a clean install (full wipe).
Click to expand...
Click to collapse
I have to agree, but I wasn't flashing when the phone decided to brick itself , so I didn't have a recent backup. In the bricked state I could only access fastboot mode, not recovery . I ended up copying what I could from the internal storage partition (which basically had everything I needed anyway), then clean installing a new ROM, and restoring my files.
For anyone else who gets into the same situation, I recommend that you make sure to not turn on WiFi or mobile data after you dirty flash OxygenOS, and remove your Google account. This will mean that Google's backup of your phone and apps (if you turned that feature on) will be of your working setup. As I tried to use Google Play in the messed up system, Google decided to replace my backup with the bad config so I couldn't restore in the new ROM - although looking at the Google Drive app now, the good setup is backed up, only I have no way to restore it
Maybe I have the same problem, not sure. I can't boot the phone. Holding vol down + power only makes the phone reboot over and over until I let go. It turns off afterwards, never enters recovery mode. I can access fastboot mode, but my bootloader is locked so I can't flash anything. Any suggestions?
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
- Touch works
Download:
TWRP 3.4.0-15 Unofficial by mauronofrio
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_surya
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-23
Tyvm
Ok men
this gets hot
Thanks
Wow! The first one
I am still waiting for my bootloader to be unlocked but then I will give it a try for sure
not working fastboot? what impact does that have? Fastboot not working? Thank you
Thanks for your work
Not working : image flash (system-vendor-product)
Click to expand...
Click to collapse
Doest it mean that when flashing a rom from recovery, theses partitions won't be updated ?
adrenochrome25 said:
Thanks for your work
Doest it mean that when flashing a rom from recovery, theses partitions won't be updated ?
Click to expand...
Click to collapse
means you cant flash .img yet (like for gsi roms). zip roms will work fine
My phone is not here yet.
Can you backup persist.img partition using dd command from twrp terminal?
do you need to unlock recovery to flash twrp? unlocking will cause data erase, right? is it possible to do it without data loss?
Yes! It came earlier than expected, didn't even receive my phone yet, very good news!
crazyjuliano said:
do you need to unlock recovery to flash twrp? unlocking will cause data erase, right? is it possible to do it without data loss?
Click to expand...
Click to collapse
Yes for first two questions . No for the 3rd One.
LUNARIO said:
Yes for first two questions . No for the 3rd One.
Click to expand...
Click to collapse
Thank you, one more question though, once we have twrp ready does it also mean we have possibility to root device as well?
Hi
I have a little problem...
I have done:
fastboot flash recovery twrp-3.4.0-12-surya-mauronofrio.img
and fastboot says:
Sending 'recovery' (131072 KB) FAILED (remote: 'Requested download size is more than max allowed
')
Finished. Total time: 0.004s
How could I fix?
crazyjuliano said:
Thank you, one more question though, once we have twrp ready does it also mean we have possibility to root device as well?
Click to expand...
Click to collapse
Yes it it will be possible to Root
---------- Post added at 11:55 AM ---------- Previous post was at 11:31 AM ----------
Phoenix_Alx said:
Hi
I have a little problem...
I have done:
fastboot flash recovery twrp-3.4.0-12-surya-mauronofrio.img
and fastboot says:
Sending 'recovery' (131072 KB) FAILED (remote: 'Requested download size is more than max allowed
')
Finished. Total time: 0.004s
How could I fix?
Click to expand...
Click to collapse
Fastboot by default wont work with USB 3 ports. Connect to USB 2 or you need to install Windows 7 drivers
LUNARIO said:
Yes it it will be possible to Root
---------- Post added at 11:55 AM ---------- Previous post was at 11:31 AM ----------
Fastboot by default wont work with USB 3 ports. Connect to USB 2 or you need to install Windows 7 drivers
Click to expand...
Click to collapse
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
O, fixed.
I have flashed the rom from xiaomi.eu https://forum.xda-developers.com/xiaomi-poco-x3-nfc/how-to/rom-xiaomi-eu-rom-poco-x3-nfc-t4165247
and boot with its boot.img. Miui has started fine and then I have restarted in recovery mode. it's working fine now
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
Are you in stock or xiaomi.eu?
Very happy to see this thread. Thank you for your work
piranime said:
Are you in stock or xiaomi.eu?
Click to expand...
Click to collapse
before, with the problem in stock. Now in xiaomi.eu
Phoenix_Alx said:
upps sorry I didn't say. It is connected in USB2 and linux.
Anyway. After of many reboots in bootloader I have flash recovery but...
now, whe phone enter in twrp doesn't working touch in screen and show a screen with the title: mount and it ask a password.
very strange
Click to expand...
Click to collapse
I've managed the same, I guess it's because I forgot to remove any fingerprint / password before flashing
So now phone always boots into twrp and is stuck at the Mount / Decrypt Data screen where it's asking for a password
I've downloaded stock ROM xxx://bigota.d.miui.com/V12.0.2.0.QJGEUXM/miui_SURYAEEAGlobal_V12.0.2.0.QJGEUXM_c68aede605_10.0.zip and am wondering how to get working system back
Would this be the correct steps?
1) extract boot.img from the ROM
2) flashing the boot.img through command fastboot flash boot boot.img
Any other step necessary to get my phone to boot back to stock?
Thanks for your help
Hello, owner of the RN 5 here
After the command fastboot boot twrp.img my device do not enter the twrp, but displays the mi logo and "unlocked" status.
The same happens when I use orange fox recovery.
What might have caused that?
The device is unlocked (the official way) .
Connection (cable, drivers, etc) seems to be ok (anyhow I did unlocked the BL)
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot devices
ec976afd fastboot
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot boot C:\redmi-unlock\twrp-3.3.1-0-vince.img
Sending 'boot.img' (36784 KB) OKAY [ 0.778s]
Booting OKAY [ 0.143s]
Finished. Total time: 0.964s
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>
Please, advice
tman_pl said:
Hello, owner of the RN 5 here
After the command fastboot boot twrp.img my device do not enter the twrp, but displays the mi logo and "unlocked" status.
The same happens when I use orange fox recovery.
What might have caused that?
The device is unlocked (the official way) .
Connection (cable, drivers, etc) seems to be ok (anyhow I did unlocked the BL)
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot devices
ec976afd fastboot
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot boot C:\redmi-unlock\twrp-3.3.1-0-vince.img
Sending 'boot.img' (36784 KB) OKAY [ 0.778s]
Booting OKAY [ 0.143s]
Finished. Total time: 0.964s
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>
Please, advice
Click to expand...
Click to collapse
Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
Reboot into OrangeFox by pressing the power + volume up keys, until you see the OrangeFox splash screen (the keys may be may vary on your device)
From here
Installing OrangeFox Recovery
wiki.orangefox.tech
Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
Or read this
Android Tip: Boot into twrp or cwm recovery without flashing
Yes, that’s true. You can boot into any recovery of your choice on your Android phone by following this guide. No need to flash and replace the stock bootloader. Though I have tested this met…
aubykhan-wordpress-com.cdn.ampproject.org
joke19 said:
Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
Or read this
Click to expand...
Click to collapse
Well, that didnt work - copying both twrp and orange recovery changed nothing (still MI logo and "unlocked" status after the command fastboot boot image_file.img).
joke19 said:
Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
Reboot into OrangeFox by pressing the power + volume up keys, until you see the OrangeFox splash screen (the keys may be may vary on your device)
From here
Installing OrangeFox Recovery
wiki.orangefox.tech
Click to expand...
Click to collapse
Well, I am not an expert - I am just affraid of doing that while fastboot boot file.img didnt work. Is it safe?
I guess I have onlu one chance to try.. Will you help me in case I dont succeed?
tman_pl said:
Well, I am not an expert - I am just affraid of doing that while fastboot boot file.img didnt work. Is it safe?
I guess I have onlu one chance to try.. Will you help me in case I dont succeed?
Click to expand...
Click to collapse
When you download the right recovery it will work
Or ask here
[Official][Recovery][TWRP]TWRP For Xiaomi Redmi 5 Plus/Redmi Note 5
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Maybe this can be a problem
Maximum Path Length Limitation - Win32 apps
Maximum path length limitation.
docs.microsoft.com
OMG, I am soooo lame.
I just installed android app "Device ID" and it turned out I AM ON WHYRED codename (not venice). I was pretty sure whyred = RN5 Pro, while regular RN5 - vince...
Well, Mi forum https://c.mi.com/thread-1911812-1-1.html confirms what I thought, but...
soooo ashamed.
Now I have to read again and check everything again..