I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2018-04-12
ChangeLog
twrp-3.2.1
Device side:
* fixed encryption fully
TWRP side:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Flashing guide(without fastboot)-
Method#1: this guide for whom got TWRP recovery v3.0.1-0 via QFIL using QPST software or who has @_kyo_ 's TWRP installed
1)load this latest TWRP (v3.1.0-0 or updated version) in sdcard or internal storage
2) boot into existing TWRP recovery
3)click on install tab
4)here from bottom left popup menu, select appropriate storage and from bottom right toggle, switch to INSTALL IMAGE mode(see screenshot)
5)flash latest TWRP v3.1.0-0 as recovery(see screenshot)
6)reboot into new TWRP recovery
Methof#2:Another method is using QPST's qfil option. In this method simply add latest version of twrp >put that into same location where stock(288) twrp existed>than apply same method with updated twrp as you did while qfil-ing stock twrp
Great work @FireLord
THEHARI said:
Flashing guide(without fastboot)-
note- this guide for whom got TWRP recovery v3.0.1-0 via QFIL using QPST software or who has @_kyo_ 's TWRP installed
1)load this latest TWRP v3.1.0-0 in sdcard or internal storage
2) boot into existing TWRP recovery
3)click on install tab
4)here from bottom left popup menu, select appropriate storage and from bottom right toggle, switch to INSTALL IMAGE mode(see screenshot)
5)flash latest TWRP v3.1.0-0 as recovery(see screenshot)
6)reboot into new TWRP recovery
Click to expand...
Click to collapse
confirmed working on my lenovo P1a42
upgraded from TWRP recovery v3.0.1-0 by kyo
so backup & restore fixed i guess ??
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
and did you finished your exams ??
mohamed abd elmoaety said:
so backup & restore fixed i guess ??
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
and did you finished your exams ??
Click to expand...
Click to collapse
yea no bugs. no exams still running
FireLord said:
yea no bugs. no exams still running
Click to expand...
Click to collapse
**** exams anyway
"OOPS!
no mirrors found."
Hi,
I'm trying to use your method to get twrp so I can install custom rom, but I stuck here
E:\dev\Android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.973s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.425s
Any idea?
Thanks
flash problem
for flash
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (30576 KB)...
OKAY [ 1.112s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.346s
any idea?
Get the bootloader unlocked first
:d
developerx07 said:
Get the bootloader unlocked first
:d
Click to expand...
Click to collapse
I have same issue and bootloader unlocked. What should I have to look at second?
New 3.1.1 twrp is up. check changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Is flashing via QPST method the same with flashing via fastboot? (Does it have the exact same results?) @FireLord
danthecoolboy said:
Is flashing via QPST method the same with flashing via fastboot? (Does it have the exact same results?) @FireLord
Click to expand...
Click to collapse
Yes, both have same result
Error while flashing recovery
target reported max download size of 268435456 bytes
sending 'recovery' (30594 KB)...
OKAY [ 1.033s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.278s
I have unlocked the bootloader using fastboot oem unlock
Please help
thanks in advance
vibe p1a42
s.kakrecha said:
target reported max download size of 268435456 bytes
sending 'recovery' (30594 KB)...
OKAY [ 1.033s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.278s
I have unlocked the bootloader using fastboot oem unlock
Please help
thanks in advance
Click to expand...
Click to collapse
even I get the exact same error. I have also unlocked the bootloader using fastboot oem unlock-go.
Awesome XDA & Friends.........Thank you
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
I was able to install the latest TWRP and I am on AEX ROM on my Vibe P1a42. Thanks to all of you guys in this thread.:good:
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
Could you please give me TWRP img for Lenovo Vibe P1a42? I could not install TWRP. getting error 'valid signature and data)'
---------- Post added at 11:52 AM ---------- Previous post was at 11:25 AM ----------
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (30576 KB)...
OKAY [ 1.112s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.346s
Related
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.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 Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Updated with 3.1.0.0 (And works for any 4X)
panchovix said:
Updated with 3.1.0.0 (And works for any 4X)
Click to expand...
Click to collapse
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
Weird, che1 or che2?
Enviado desde mi 6045B mediante Tapatalk
G620s-lO1
@andrejicd it is rare since the twrp itself was made to the g620s/che1, but it just worked on che2 too, well thanks for the info then
Yes, FAILED (remote: size too large)
It is 24.5M, really too large???
And the twrp-3.0.2-0-cherry.img has the same problem.
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Kireto00 said:
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Click to expand...
Click to collapse
It will work.
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
raven731 said:
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
Click to expand...
Click to collapse
What exactly u did?
Hi,
I have the exactly same problem. This is what I did.
My phone: Che2-L11
1. unlooked bootloader
2. flashed twrp-3.1.1-0-cherry.img and twrp-3.0.2-0-cherry.img from dl.twrp.me/cherry/
3. power of an boot to recovery ends in stucking with "honor" bootlogo.
thanks for any hints
panchovix said:
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.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 Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Click to expand...
Click to collapse
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Lballarini said:
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Click to expand...
Click to collapse
Yup same with me( che1-l04). In adb it says file is too large.
Hi Guys,
I am trying to push it and install but I have this error below. BTW, the phone is per-unlocked. It already has a warning red sign "PHONE Unlocked"
target reported max download size of 471859200 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.594s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.594s
.
Enviado do meu ALE-L21 através de Tapatalk
size of image is larger than target device.
G620s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
use minimal ADB program for flashing
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Marcyvee said:
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Click to expand...
Click to collapse
The same here
# fastboot flash recovery twrp-3.2.3-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25136 KB)...
OKAY [ 0.796s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.810s
At the end power and vol+ but and stock "Huawei eRecovery" start and not twrp. I'm using Che2-L11_V100R001C432B310.
Hi everyone !
I'm a little stuck now, so i really need your help !
I want to install LineageOS on my Xiaomi redmi note 4. So i followed the installation instructions on official Lineage website.
At the step "Install TWRP recovery" i'm stuck.
Here are the logs :
Code:
> $ fastboot flash recovery twrp-3.1.0-0-mido.img
target reported max download size of 134217728 bytes
sending 'recovery' (26840 KB)...
OKAY [ 1.328s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.331s
So after searching on the web I tried splitting img into chunks with the following command :
Code:
> $ fastboot flash -S 20M recovery twrp-3.1.0-0-mido.img
Invalid sparse file format at header magi
sending sparse 'recovery' (20476 KB)...
OKAY [ 1.015s]
writing 'recovery'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 1.019s
I choosed 20M for my chunks randomly (inferior to recovery image of 26840KB).
Other informations :
I can't boot to origin system
I can access to fastboot
I can use adb but my device is in sideload mode
Please feel free to answer if you have any idea.
You're great! Thanks.
Did you already unlock the bootloader? It seems not yet..
crok.bic said:
Did you already unlock the bootloader? It seems not yet..
Click to expand...
Click to collapse
Yes I did !
Code:
> $ fastboot getvar all
...
(bootloader) unlocked: yes
...
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
crok.bic said:
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
Click to expand...
Click to collapse
I'm not sure if it's Mido or Nikel.
Do you have a link for Nikel ? Because it doesn't appear in twrp list :\
For adb i've downloaded with
Code:
sudo apt-get install android-tools-adb
I've tried with 3.1.1-0-mido and same error than 3.1.0 :\
@crok you really rock !
I've tried with this link of Nikel : https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/
And I'm having the recovery mode!
I continue the tutorial !
Great news. Please mark the thread [solved] just to help people who has the same trouble and seeking for info/solution.
TWRP For Moto G5s Montana
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
Custom Oreo arm64 release????
rssxda said:
Custom Oreo arm64 release????
Click to expand...
Click to collapse
No, first we want a arm32 build.
Can't decrypt/mount my fs with this. Works on Squids TWRP.
Moto G5S XT1794
Can use Treble imagem?
Hello, here is a new version of the twrp arm / arm64.
twrp.fstab file modification
old twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
new twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/vendor ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="Vendor";backup=1;wipeingui
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display="EFS"
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/logo emmc /dev/block/bootdevice/by-name/logo flags=display="logo";backup=1;flashimg=1
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
I'm no longer this model for now because I gave it to my wife, if anyone can try it. But it should work properly
link AFH > https://androidfilehost.com/?fid=746163614322269316
Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.
tafiir said:
Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.
Click to expand...
Click to collapse
whay you whant to backup your stok recovery?
you can flash it on the phone any time with fastboot/mfastboot comand's
just remember wich stok rom you used last time and flash the propper recovery from it!
Thankyou!
Hello New twrp 3.2.2-0 > https://androidfilehost.com/?fid=5862345805528040464
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
PERGUNTA
Essa versao 3.2.2-0 ela e 32/64 bits
kaique teixeira said:
Essa versao 3.2.2-0 ela e 32/64 bits
Click to expand...
Click to collapse
64bit!
teble
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?
tiagoneo said:
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?
Click to expand...
Click to collapse
Of course not. Treble isn't even here yet
Sent from my Moto G5S using XDA Labs
What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?
1ZeeN said:
What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?
Click to expand...
Click to collapse
No encryption support, but installs DU perfectly
will this work for XT1795 model?
going to stock rom instead of twrp
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s
Akshay K yatheendran said:
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s
Click to expand...
Click to collapse
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!
Some random said:
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!
Click to expand...
Click to collapse
It will be shown even on official twrp. You have to disable overwiting recovery by stock system. For example, magisk can handle it
GoldeneyeS2 said:
TWRP For Moto G5s Montana
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
Click to expand...
Click to collapse
I need perfect gapps for motog5s montana please help me??
i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ????
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Install Stock ROM Huawei
-.phone connected USB
-.connected To On TWRP
-.Rename xxxxxx to update_all_hw
-.Rename xxxxxx to update_data_public
-----------------------------------------------------
Install
-.Shift + right click the folder and open command prompt here
-.adb push HuRUpdater_0.3.zip /sdcard
-.adb push update.zip /sdcard
-.adb push update_all_hw.zip /sdcard
-.adb push update_data_public.zip /sdcard
-----------------------------------------------------
install on TWRP
-.install - Press HuRUpdater_0.3.zip
-.Then follow instructions on screen VOLUME DOWN
-.Press back once more -- Select reboot recovery
-.Wipe data/factory reset -- Then reboot system
-.DONE GOODLUCK
JAZZYBUTT999 said:
i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ????
Click to expand...
Click to collapse
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.
thanks for the info
Chisetdel31260 said:
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.
Click to expand...
Click to collapse
i will try asap and after that i will let u know the results.... thumbs up:good::good::good:
Help
Hi I also have my Mate 10 Lite RNE-L21C432 locked. I can only get into fastboot.
These are the results of fast boot:
C:\adb fastboot oem get—product—mode1
(bootloader) RNE-L21
OKAY [ 0.016s]
finished, total tine: 0.031s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished, total tine: 0.016s
C:\adb>fastboot oem get-build-number
(bootloader) :Systen 8.0.0.046(07P2)
OKAY [ 0.031s]
finished, total tine: 0.031s
C:\adb)fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone??
(bootloader) NOT secboot recovery image?
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail? )
finished, total tine: 0.078s
C:\adb)fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :Systen 8.0.0.046(07P2)
OKAY I 0.031s]
finished, total tine: 0.031s
C:\adb>
can someone help me? Thank you
pabbata said:
Hi I also have my Mate 10 Lite RNE-L21C432 locked. I can only get into fastboot.
These are the results of fast boot:
C:\adb fastboot oem get—product—mode1
(bootloader) RNE-L21
OKAY [ 0.016s]
finished, total tine: 0.031s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished, total tine: 0.016s
C:\adb>fastboot oem get-build-number
(bootloader) :Systen 8.0.0.046(07P2)
OKAY [ 0.031s]
finished, total tine: 0.031s
C:\adb)fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone??
(bootloader) NOT secboot recovery image?
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail? )
finished, total tine: 0.078s
C:\adb)fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :Systen 8.0.0.046(07P2)
OKAY I 0.031s]
finished, total tine: 0.031s
C:\adb>
can someone help me? Thank you
Click to expand...
Click to collapse
Hello
do you have TWRP for emui 8.0 that starts?
if so, use HurUpdater 0.3, reinstall rne-l21c432b304.
Chisetdel31260 said:
Hello
do you have TWRP for emui 8.0 that starts?
if so, use HurUpdater 0.3, reinstall rne-l21c432b304.
Click to expand...
Click to collapse
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
pabbata said:
Hello
as I indicated in the previous post, I can only enter fastboot mode. when I try to install Oreo recovery from this message:
C:\Users\Pabbata\Desktop\TWRP oreo Mate 10 lite\TWRP oreo\data>fastboot flash re
covery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9882 KB)...
OKAY [ 0.359s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
It does not let me install any TWRP either Oreo or Nougat. As you can see fastboot says that the operating system 8.0.0.046(07P2) is currently installed.
Click to expand...
Click to collapse
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
Chisetdel31260 said:
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
teste this TWRP https://forum.xda-developers.com/showpost.php?p=76397635&postcount=2 : p
Click to expand...
Click to collapse
Hi I also installed this twrp, this is the result:
{
"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"
}
pabbata said:
Hi I also installed this twrp, this is the result:
Click to expand...
Click to collapse
ME TOO Help Me
---------- Post added at 03:08 PM ---------- Previous post was at 03:00 PM ----------
++++++++++++++++
*Deleted*
tried but failed
Chisetdel31260 said:
ma sauvegarde de rne-l21c432b133 full https://mega.nz/#!ksdhmCQJ!fb5TDWpBEEA_BwXnO4gd86ry33tD6rVaGdXQ3kYy7LU
copy all to your TWRP folder from your SD card.
Use this TWRP because the backup was done with.
* https://mega.nz/#!c1tyRL7Z!r3fhcK5eNHR1aaN_s8OwafD1eQutvpc2cF-lG4guQdk
restart in TWRP.
go to wipe.
check all except oeminfo. and wipe all.
go to wipe, data format, write yes and validate.
go to wipe check data and change to f2f.
now, go to restore, and restore all files one by one, except oeminfo.
once finished, go to install, install the file meta-inf.zip (it's product).
https://mega.nz/#!d5sgDQba!Zntk05RjlDLFi7Wmz7mmVvvr7nc4vp7Kv2SZtcLjB5Q
then restart.
here is.
Click to expand...
Click to collapse
twrp does'nt flash, this happens see pic after flashing
https://lh3.googleusercontent.com/-...G99AIgCJoC/w530-h942-n-rw/AAAAAAAAAAAAAAA.jpg
I used HuRu today, to flash a Firmware Finder stock Oreo ROM as per my build number
I was partially on elemntal 1.1 (oreo) the phone got boot loop, I tried with my stock
oreo backups, it would show error on Venor and System, tried with Mounting unmounting
from TWRP, didnt work, restarted phone Lost TWRP, but the good thing was my Bootloader
and FRP were unlocked (used a file from Elemental rom thread to unlock FRP,
when my bootloader was already unlocked). In TWRP finally I tried to wipe
every thing (not SD Card), then tried to restore my back up again, unchecked vendor then
restarted, after a few bootloop restarts, I got stock recovery and used Format option, then got nothing on phone just the Stock recovery, format would close with ! mark in between.
So at this point, I would repeatedly get following error when installing any of TWRPs for mate 10 lite:
FAILED (remote: Command not allowed)
Was worried thinking I am not going to get any thing from this point, but then just tried the dload method
which worked only once for me in the past, and later always failed @ 5 %
So tried dload with the files for Nougat (RNE-L21C185B142), luckily it worked for me, I am on nougat again
sentavn said:
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Click to expand...
Click to collapse
Forgive me How is the exact procedure for formatting via fastboot Thanks I have the phone in these conditions
Diego1976 said:
Forgive me How is the exact procedure for formatting via fastboot Thanks I have the phone in these conditions
Click to expand...
Click to collapse
I think by running this command fastboot flash system system.img will automatically erase your data.
JAZZYBUTT999 said:
twrp does'nt flash, this happens see pic after flashing
https://lh3.googleusercontent.com/-...G99AIgCJoC/w530-h942-n-rw/AAAAAAAAAAAAAAA.jpg
Click to expand...
Click to collapse
hello did you solve it? the image like you comes out to me too ..
I also tried with hwota but nothing to do!
let me know if you found a solution
thanks in advance
Aniwat12 said:
Install Stock ROM Huawei
-.phone connected USB
-.connected To On TWRP
-.Rename xxxxxx to update_all_hw
-.Rename xxxxxx to update_data_public
-----------------------------------------------------
Install
-.Shift + right click the folder and open command prompt here
-.adb push HuRUpdater_0.3.zip /sdcard
-.adb push update.zip /sdcard
-.adb push update_all_hw.zip /sdcard
-.adb push update_data_public.zip /sdcard
-----------------------------------------------------
install on TWRP
-.install - Press HuRUpdater_0.3.zip
-.Then follow instructions on screen VOLUME DOWN
-.Press back once more -- Select reboot recovery
-.Wipe data/factory reset -- Then reboot system
-.DONE GOODLUCK
Click to expand...
Click to collapse
This Works on Semi-Brick (Start normally and when Android wakes up it reboots in recovery)?
hi, my mate 10 seems bricked. i can't go into fastboot mode neither in recovery. when i charge the phone, the led remain off.
but if i connect the phone to pc, hisuite starts. what can i do?
if i use hwota, the results is
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.529s
Dyzzy Solution
Guys I am now with some dyzzy solution but... with some logic to me, ok I will explain how I have my device alive again.
to be clear, this brick was caused because I want to have my device from ATT Mexico rebranded with dual sim ROM, then I lost oem info and cant go back 4G, so I installed Custom MORFUZ ROM 3.4, but I still without 4G and now with my second simcard deactivated, so... I tried to reflash with HWOTA the RNE-L03 rom single sim and... that was the mistake, after the procedure.. I got the semi-brick (since 2 days ago), ok then I was searching and reading a lot (and using more common sense haha) so, I needed to repair my device partitions because there was a mess triying to flash from another partition so, thats how I ended here, let's start:
*** First of all, prepare an SD card with the files for the HuRUpdater_0.3 mode, (just a tip, I leaved my phone run out of battery because I had the bootloop on the prompt screen that says that "your bootloader is unlocked and device is not trusted" so its easier to have acces to fastboot mode if you do this way)
- Step 1: I did the fastboot manual flashing unpacking my UPDATE.APP with HuaweiUpdateExtractor (see post#2)
once succesfully finished I rebooted my phone and still bricked
- Step 2: I entered fastboot mode and flashed the recovery image from CATUVA21 for Oreo (see post #9)
(IMPORTANT: DO NOT TRY TO ENTER ON TWRP RECOVERY RIGHT NOW OR YOU WILL NEED TO START AGAIN FROM STEP 1)
-Step 3: Connect the phone to energy (charger?, sorry I have very bad english) just 2 percent an unpplug, that's because if you can't go forward from here, you have to wait less to re-enter in fastboot and try another solution
-Steep 4: Here is the magic, press vol+ and plug the phone to your pc (yea, like entering eRecovery Wifi Mode) and Voilá!!! entered TWRP
-Steep 5: Flash HuRUpdater_0.3.zip, leave it finish, reboot device
Now you will be prompted to EMUI black screen with a message that says "partition is several damaged, you need to clean all partitions" you click on "clean all partitions" once finished, click in "Reboot System" be patient, for me was 4-6 minutes and some bootloops untill I heared the bootanimation tune and there is, initial config and now you are in a very dirty ROM but from here you can reflash a full rom, I hope It Help to anyone.
As the title said, i'm having some errors while i try to flash something in fastboot, i'm folowing this steps:
First i open CMD (with administrator rights) or Terminal (root mode) and Type this:
Code:
adb devices
adb reboot-bootloader
My device reboot into bootloader, then i use:
Code:
Fastboot devices
Fastboot flash [partition] [path to file]
In this case: Fastboot flash recovery recovery.img
And here is where the problems begins
Code:
Fastboot flash recovery (path to the recovery.img file)
Sending 'recovery' (42834 KB) Failed (remote: 'not support "-u" option')
Fastboot: error: command failed
I do a little research about "-u" and got something about erasing a overwriting stuff so...
Code:
Fastboot erase recovery
(Everything is ok)
Fastboot flash recovery (path to the recovery file)
Sending 'recovery' (42834 KB) OKAY
Writing 'recovery' FAILED (remote: 'write partition:recovery')
Fastboot: error: Command Failed
I can't even do a Fastboot boot because of the '-U' option error...
I've tried with RKtools (because of my rk3368h chipset) and there i can flash everything succesfuly but when i try enter in recovery mode my device get stuck in the initial boot image (not the CR boot image)
So, i don't know if i'm using a wrong recovery.img or if my device is the problem. I hope someone can help me :laugh:
P.D: My device is a generic (unpopular) Android, so the only useful info that can i bring you is:
Android version is 8.1 (November 2018 security patch)
Device uses a rk3368h chipset
Bootloader is Unlocked
Obviously isn't rooted (that's why i'm trying to flash a CR)
Similar device: Teclast P10 (probably the m3f5)
And i'm trying to flash a ported TWRP (ported by ME )
That's all, thank you for reading my post and trying to help me.