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.
{
"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"
}
Installation
To temporarily boot this recovery:
fastboot boot twrprolakv5.img
To permanently install it:
fastboot flash recovery twrprolakv5.img
Download
SourceForge
Troubleshooting
1.: Permanently install show error.
R.: You need to boot recovery and install the Image by Recovery to Recovery
2.: Recovery missing afeter install and boot into stock (OEM) system.
R.: Stock (OEM) system clear 64 bits recovery by defaut, so you need to install the TWRP 64bits install a Custom ROM right away.
Code:
Changelog:
2021-09-02
- First release
2021-12-08
- Tried to fix OTG test it!!!
2022-03-31
- Fixed format "auto" when format External SD-CARD
- Bump to version 3.6.1*
2022-07-09
- Changed vfat to exfat on SD format options.
- Bump to version 3.6.2
2022-10-15
-Update kernel prebuilt source to match with last kernel sources
- Bump to version 3.7.0
XDAevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@jeangraff30
@brunogroa
Version Information
Status: Stable
Kernel: 3.18.140-Stable
TWRP: Source
Device: Source
Created 2021-09-02
Last Updated 2021-12-08
Thank you so much for the hard work mate! ✌
One question:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Also, I just flashed latest version and it says it's 3.6.1, not 3.6.2. Is that right?
rambomhtri said:
One question:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Also, I just flashed latest version and it says it's 3.6.1, not 3.6.2. Is that right?
Click to expand...
Click to collapse
ohh sorry for this, is 3.6.1 i just writed wrong XD
brunogroa said:
ohh sorry for this, is 3.6.1 i just writed wrong XD
Click to expand...
Click to collapse
Ok, thanks!
What about this question?
rambomhtri said:
Is the FW of Moto G6 (Ali) upgradable?
Or it comes included with the ROM zip?
Click to expand...
Click to collapse
rambomhtri said:
Ok, thanks!
What about this question?
Click to expand...
Click to collapse
FW you just need to flash most recently STOCK ROM for your region... just it, this never changes in rom flash
brunogroa said:
FW you just need to flash most recently STOCK ROM for your region... just it, this never changes in rom flash
Click to expand...
Click to collapse
How can we check the FW version?
The baseband maybe?
I'm pretty sure I updated 2 years ago or more, I don't remember, to the latest official stock ROM via OTA. I wanted to check the numbers, just that.
rambomhtri said:
How can we check the FW version?
The baseband maybe?
I'm pretty sure I updated 2 years ago or more, I don't remember, to the latest official stock ROM via OTA. I wanted to check the numbers, just that.
Click to expand...
Click to collapse
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
pocky-stick said:
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
Click to expand...
Click to collapse
Yeah, I have the exact same baseband version. Is that enough to guarantee we have the same version and the latest?
rambomhtri said:
Yeah, I have the exact same baseband version. Is that enough to guarantee we have the same version and the latest?
Click to expand...
Click to collapse
It can be tricky with Motorola devices because sometimes elements like the baseband aren't updated each version, see if you notice discrepancies in the other values.
You can always grab the stock PPS29.118-15-11-16 from lolinet and flash it. If you're running a custom ROM, I suggest backing up your data, flashing the entire image, then reinstalling the custom ROM. Attempting to update the radio/bootloader over a custom software has given me a few blankflash-level bricks before.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
brunogroa 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.
View attachment 5400275View attachment 5400287
Installation
To temporarily boot this recovery:
fastboot boot twrprolakv5.img
To permanently install it:
fastboot flash recovery twrprolakv5.img
Download
SourceForge
Troubleshooting
1.: Permanently install show error.
R.: You need to boot recovery and install the Image by Recovery to Recovery
2.: Recovery missing afeter install and boot into stock (OEM) system.
R.: Stock (OEM) system clear 64 bits recovery by defaut, so you need to install the TWRP 64bits install a Custom ROM right away.
Code:
Changelog:
2021-09-02
- First release
2021-12-08
- Tried to fix OTG test it!!!
2022-03-31
- Fixed format "auto" when format External SD-CARD
- Bump to version 3.6.1*
2022-07-09
- Changed vfat to exfat on SD format options.
- Bump to version 3.6.2
2022-10-15
-Update kernel prebuilt source to match with last kernel sources
- Bump to version 3.7.0
XDAevDB Information
TWRP for Moto G6, Tool/Utility for the Moto G6
Contributors
@jeangraff30
@brunogroa
Version Information
Status: Stable
Kernel: 3.18.140-Stable
TWRP: Source
Device: Source
Created 2021-09-02
Last Updated 2021-12-08
Click to expand...
Click to collapse
Hi Guys,
I'm getting this when attempting to flash the TWRP image. Any suggestions?
sternz said:
Hi Guys,
I'm getting this when attempting to flash the TWRP image. Any suggestions?
Click to expand...
Click to collapse
your bootloader is not unlocked ¬¬
brunogroa said:
your bootloader is not unlocked ¬¬
Click to expand...
Click to collapse
I see! Is that the process of getting an unlock code from Motorola as shown at the beginning of the 5 minutes mark in this video
sternz said:
I see! Is that the process of getting an unlock code from Motorola as shown at the beginning of the 5 minutes mark in this video
Click to expand...
Click to collapse
is same in all motorola, turn on unlock on dev options on stock, go to bl an get the code, insert on site, pick the unlock code and unlock (and it will clean all your data on phone), so yes
brunogroa said:
is same in all motorola, turn on unlock on dev options on stock, go to bl an get the code, insert on site, pick the unlock code and unlock (and it will clean all your data on phone), so yes
Click to expand...
Click to collapse
Got it! Thank you for the response and helping a total n00b!
Whats the difference to official twrp for ali?
zitronenmelissa said:
Whats the difference to official twrp for ali?
Click to expand...
Click to collapse
official dont allow to install custom roms cos is only 32 bits.... the uno one is 32/64
Can't imagine the hours in this- thanks!
My error when installing twrprolakv5.img
"Image not signed or corrupt"
Confession- attempted install of twrprolakv5.img with twrp v3.2.3 already installed.
Any brief flashes of wisdom?
brunogroa said:
official dont allow to install custom roms cos is only 32 bits.... the uno one is 32/64
Click to expand...
Click to collapse
Does that still applies to the lastest official version (3.7.0_9-0)?
pocky-stick said:
Running 'fasboot getvar all' is a good way to check and compare values. My US Retail G6 was updated through OTA to the final official update PPS29.118-15-11-16. Bootloader version 'MBM-2.1-ali_retail-a49aaf13a93-200423', baseband 'M450_23.31.10.89R ALI_NA_CUST' and release key '3afd9'.
Click to expand...
Click to collapse
thanks! Double checked and mine is this!
Related
It's enough, don't hide TWRP inside a ROM thread!
Built from source inside cm-13.0 source tree, always sync to upstream TWRP
Trusted, completely open (recovery changes, device tree, kernel, etc)
Currently use the new default TWRP theme
Qualcomm encryption support (untested, have no plan to encrypt my device)
Properly run AROMA Filemanager 2.00b7
Compatible to both old KitKat and new Lollipop bootloader (since 20160201 build, use updated kernel source but CM known not boot with the new bootloader)
Download Links:
AFH: twrp-3.0.2-0-wt88047-20160513.img
Source Code:
Device tree: https://github.com/kumajaya/android_device_wingtech_wt88047/tree/cm-13.0-twrp
TWRP source: https://github.com/omnirom/android_bootable_recovery/tree/android-6.0
Kernel source: https://github.com/CyanogenMod/android_kernel_wingtech_msm8916/tree/cm-13.0
{
"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"
}
Which version is this?
You sr. Allow me to translate it for my people language and post it as an addition?
(No theming works included for now)
Lennoard said:
Which version is this?
You sr. Allow me to translate it for my people language and post it as an addition?
(No theming works included for now)
Click to expand...
Click to collapse
As latest upstream version, 2.8.7.0 android-6.0 branch.
Good for all room sir ? I use cm 12.1 never try cm 13 coz have a bug camera
wow good work dude... you are the hero here.. lol
@ketut.kumajaya
Code:
TW_EXCLUDE_MTP := true
I need MTP. Is it because MTP is broken you disable or what?
nick37332001 said:
@ketut.kumajaya
Code:
TW_EXCLUDE_MTP := true
I need MTP. Is it because MTP is broken you disable or what?
Click to expand...
Click to collapse
Previously broken but get compiled now.
ketut.kumajaya said:
Previously broken but get compiled now.
Click to expand...
Click to collapse
So I guess can remove it since its fixed?
nick37332001 said:
So I guess can remove it since its fixed?
Click to expand...
Click to collapse
Yes, I'll revert it.
Build 20160101 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Re-enable MTP and confirmed works
- Updated kernel source
@Kuma, Is there any reason that the new twrp is not working when pressing Vol UP+Vol Down+Power. I tried many times. I always flash through fashboot. And how can i permanently flash new twrp based on CM 13. I tired from adb folder, but recovery from phone is not working. Only one recovery working perfectly from phone is TWRP2.8.7.1. But you are saying use the proper recovery for better experience.
My device is Redmi 2 (2014818).
rkpg said:
@Kuma, Is there any reason that the new twrp is not working when pressing Vol UP+Vol Down+Power. I tried many times. I always flash through fashboot. And how can i permanently flash new twrp based on CM 13. I tired from adb folder, but recovery from phone is not working. Only one recovery working perfectly from phone is TWRP2.8.7.1. But you are saying use the proper recovery for better experience.
My device is Redmi 2 (2014818).
Click to expand...
Click to collapse
Working for me. After the Tux logo, still no idea why TWRP splash screen not appear but blank screen and then main TWRP menu shown. You can flash recovery via fastboot using "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img" command.
<noob> Sorry, I'm new to Redmi 2 </noob>
Now the question: I am not able to permanently flash the recovery using fastboot, though the phone can hotboot one ("tethered"). Whenever I flash a recovery and reboot to it, only stock MiRecovery comes in.
Does anybody know solution?
Vynikal said:
<noob> Sorry, I'm new to Redmi 2 </noob>
Now the question: I am not able to permanently flash the recovery using fastboot, though the phone can hotboot one ("tethered"). Whenever I flash a recovery and reboot to it, only stock MiRecovery comes in.
Does anybody know solution?
Click to expand...
Click to collapse
Use the command "fastboot boot twrp-2.8.7.0-wt88047-20160101.img" next to "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img"
zhtengw said:
Use the command "fastboot boot twrp-2.8.7.0-wt88047-20160101.img" next to "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img"
Click to expand...
Click to collapse
So which one should I use? As I said, I want to FLASH the recovery, not to boot it.
Vynikal said:
So which one should I use? As I said, I want to FLASH the recovery, not to boot it.
Click to expand...
Click to collapse
Pay attention to the phrase "next to".
I mean use the commands both.
First, fastboot flash recovery ***.img, it will flash your recovery partition;
then, fastboot boot ***.img, it will override your boot partition, and your MiRecovery will be replaced.
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
ketut.kumajaya said:
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
Click to expand...
Click to collapse
Hi om kuma, is the TWRP Possible to read primary storage at ur cm13? Cuz I format my external storage as primary storage but its not detected anywhere in TWRP, so its need a little trick to flash ur update etc. From recovery with limited...
ketut.kumajaya said:
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
Click to expand...
Click to collapse
Can I use it for Oneplus One (bacon) CM13?
This is a working recovery + kernel for the newer oneplus x devices. (E1003_15)
TWRP 3.1.0 : https://drive.google.com/open?id=0B4M7PGD9hwRdbXBmekJpNkQyaHc
Arsenic Kernel : https://drive.google.com/open?id=0B4M7PGD9hwRdc1RzWkVRRlFHMDA
- Android 6.x and 7.x compatible.
- It only works with AOSP/CM roms based on the new bootloader.
Instructions :
- Update to OOS 3.x if you haven't already
- Unlock your bootloader if your on OOS
- Boot into bootloader
- fastboot oem unlock (if you haven't unlocked your bootloader already)
- fastboot flash recovery twrp-3.1.0.0-onyx-E1003_15_161107.img
- fastboot reboot (and hold the volume down key to get into the recovery)
- Make a backup!
- Wipe system/data/cache/dalvik cache
- Flash your favorite rom
- Flash the Arsenic kernel
Credits to :
@CheckYourScreen for his kernel
The whole TWRP team.
Tested on : cosmic os , RR and LOS.
Note: This is merely a temporary solution until everything gets released officially.
edit: Official version of lineage-14.1-20170316-nightly-onyx-signed.zip now works without flashing a custom kernel.
What's different here than official twrp and arsenic r32?
There's no point of releasing a new one unless it has some more fixes.
Fyi I'm already working on twrp, aroma is almost fixed, only some graphical glitches are remaining(which doesnt appear in screenshots), will release as soon as its fixed.
{
"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"
}
nikhilsnigam said:
What's different here than official twrp and arsenic r32?
Click to expand...
Click to collapse
It actually works on the new revision of the oneplus X.
Alot of people had trouble getting a working twrp to flash a custom rom on a E1003_15 oneplus X . Since almost no roms came with a kernel that supported the E1003_15 , i figured i'd patch arsenic's kernel since it supports both AOSP/CM roms.
This is by no means a replacement for any official release and merely a temporary solution until everything gets released officially.
CheckYourScreen said:
There's no point of releasing a new one unless it has some more fixes.
Fyi I'm already working on twrp, aroma is almost fixed, only some graphical glitches are remaining(which doesnt appear in screenshots), will release as soon as its fixed.
Click to expand...
Click to collapse
It only has the fix for the e1003_15 devices. It's merely a temporary solution and i do suggest people use the official Twrp/Arsenic kernel once it's released.
Ps: Nice to see aroma installer will be available to us soon. Any repo where i can find these changes? I don't mind testing it
ChzeRub said:
It only has the fix for the e1003_15 devices. It's merely a temporary solution and i do suggest people use the official Twrp/Arsenic kernel once it's released.
Ps: Nice to see aroma installer will be available to us soon. Any repo where i can find these changes? I don't mind testing it
Click to expand...
Click to collapse
We have a telegram group, PM me if you're interested
ChzeRub said:
This is a working recovery + kernel for the newer oneplus x devices. (E1003_15)
TWRP 3.1.0 : https://drive.google.com/open?id=0B4M7PGD9hwRdbXBmekJpNkQyaHc
Arsenic Kernel : https://drive.google.com/open?id=0B4M7PGD9hwRdc1RzWkVRRlFHMDA
- Android 6.x and 7.x compatible.
- It only works with AOSP/CM roms based on the new bootloader.
Instructions :
- Update to OOS 3.x if you haven't already
- Boot into bootloader
- fastboot flash recovery twrp-3.1.0.0-onyx-E1003_15_161107.img
- Boot into recovery
- Flash your favorite rom
- Flash the Arsenic kernel
Credits to :
@CheckYourScreen for his kernel
The whole TWRP team.
Tested on : cosmic os , RR and LOS.
Note: This is merely a temporary solution until everything gets released officially.
edit: Official version of lineage-14.1-20170316-nightly-onyx-signed.zip now works without flashing a custom kernel.
Click to expand...
Click to collapse
Woow.. it's perfect cosmic rom... great working now on my opx... thank you ChzeRub...
Hello highest respect to owner of arsenic kernel and twrp maintainer or developer i dont know the precise name for tht im sorry just want to ask, if i flash official twrp 3.1.00 from twrp app is if the same as on this thread
Wanakmalarief said:
Hello highest respect to owner of arsenic kernel and twrp maintainer or developer i dont know the precise name for tht im sorry just want to ask, if i flash official twrp 3.1.00 from twrp app is if the same as on this thread
Click to expand...
Click to collapse
This version is for the newer oneplus x devices. Currently the official version doesn't support them yet.
ChzeRub said:
This version is for the newer oneplus x devices. Currently the official version doesn't support them yet.
Click to expand...
Click to collapse
@ChzeRub, Is it possible for this patched TWRP version to mount USB-OTG so that I can install Arsenic kernel from there.
I only copied RR Rom and gapps to internal storage, flashed them, flash boot.img, now I am stuck in RR booting animation.
Tried to push kernel from ADB with no result. Device not found error.
Or could you make the boot.img version of arsenic, so at least my opx pass RR booting animation.
Qniichan said:
@ChzeRub, Is it possible for this patched TWRP version to mount USB-OTG so that I can install Arsenic kernel from there.
I only copied RR Rom and gapps to internal storage, flashed them, flash boot.img, now I am stuck in RR booting animation.
Tried to push kernel from ADB with no result. Device not found error.
Or could you make the boot.img version of arsenic, so at least my opx pass RR booting animation.
Click to expand...
Click to collapse
You can boot into recovery , connect it to your computer and copy the files onto the sdcard.
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
FEATURES
Click for feature list
Always have a full functional backup. Just in case of unforeseen circumstances!
DOWNLOAD
DOWNLOAD LASTED BUILD
GAPPS
First time installing crDroid to your Moto G4play, or coming from another ROM:
** Make sure you're running the latest TWRP Recovery
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
MAINTAINER @SrPh00_00
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
SOURCES
ROM
KERNEL
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked Bootloader & TWRP Recovery
Based On: Lineage OS
Version Information
Status: Stable
Build Date: 12/01/2019
Created 12/01/2019
Last Updated 31/01/2019
The rom is stable, and everything is working perfectly!
Pedro_01 said:
The rom is stable, and everything is working perfectly!
Click to expand...
Click to collapse
Thanks bro
Reserved! I will install later!
Pedro_01 said:
The rom is stable, and everything is working perfectly!
Click to expand...
Click to collapse
allanph said:
Thanks bro
Click to expand...
Click to collapse
Thanks Bro
ROM very stable! Everything works, no lags, batery drain alsome! A lot of customizations avaliable! Thx bro
Does anyone knows how can I unlock XT1609 bootloader and install twrp? I wanna try this rom on my G4
Sent from my XT1609 using Tapatalk
Gabe. F said:
ROM very stable! Everything works, no lags, batery drain alsome! A lot of customizations avaliable! Thx bro
Click to expand...
Click to collapse
Thanks bro
zohaibkhan143 said:
Does anyone knows how can I unlock XT1609 bootloader and install twrp? I wanna try this rom on my G4
Click to expand...
Click to collapse
G4 athene ?
Im on Sprint Harpia version however it states during zip install that I dont have the correct harpia retail version. Is this not for the Sprint G4 Play?
allanph said:
G4 athene ?
Click to expand...
Click to collapse
Moto G4 (verizon)
Sent from my XT1609 using Tapatalk
taemta3 said:
Im on Sprint Harpia version however it states during zip install that I dont have the correct harpia retail version. Is this not for the Sprint G4 Play?
Click to expand...
Click to collapse
Send me the complete error, please.
zohaibkhan143 said:
Moto G4 (verizon)
Click to expand...
Click to collapse
just follow the description and get, install
allanph said:
just follow the description and get, install
Click to expand...
Click to collapse
But my bootloader is locked and have no twrp. How can I flash this rom?
Sent from my XT1609 using Tapatalk
zohaibkhan143 said:
But my bootloader is locked and have no twrp. How can I flash this rom?
Click to expand...
Click to collapse
Unlocking the bootloader and installing the TWRP
Volte working bro?
xt 1607 using the crDroidAndroid-9.0-20190113-harpia, clean wipe of system data cache. Will not install, I have installed several other custom roms on this phone via the latest TWRP. Gives the following error
Warning: no file contexts
E3004: This package is for device: harpia.harpia_retail: this device is .
Updater process ended with ERROR: 7
Error installing zip file /external_sd/crDroidAndroid-9.0-20190113-harpia-v5.0.zip
I reflashed the HARPIA_NPOS26.48-43-2.zip stock to make sure the device was stock as possible (minus unlocked bootloader and TWRP) error still occurred.
I redownloaded the zip file to make sure it was not corrupt, error still occurs.
Desperately wanted to try Pie on my Harpia with this ROM. Please help!
taemta3 said:
xt 1607 using the crDroidAndroid-9.0-20190113-harpia, clean wipe of system data cache. Will not install, I have installed several other custom roms on this phone via the latest TWRP. Gives the following error
Warning: no file contexts
E3004: This package is for device: harpia.harpia_retail: this device is .
Updater process ended with ERROR: 7
Error installing zip file /external_sd/crDroidAndroid-9.0-20190113-harpia-v5.0.zip
I reflashed the HARPIA_NPOS26.48-43-2.zip stock to make sure the device was stock as possible (minus unlocked bootloader and TWRP) error still occurred.
I redownloaded the zip file to make sure it was not corrupt, error still occurs.
Desperately wanted to try Pie on my Harpia with this ROM. Please help!
Click to expand...
Click to collapse
You have to be with Twrp Updated!!!
please refresh and try again please contact me after this if you continue the error
AgentVoid said:
Volte working bro?
Click to expand...
Click to collapse
I did not try it, my operator has volte not enabled it.
Switch to Latest TWRP3.2.1
allanph said:
You have to be with Twrp Updated!!!
please refresh and try again please contact me after this if you continue the error
Click to expand...
Click to collapse
No the upgrade to the latest TWRP worked like a champ. ROM is booted and working great. Only issue I had was some irregularity with the camera but a restart seems to have cured the error.
Loving PIE
{
"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"
}
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
NOTE:
Decryption of data works when fastboot booting TWRP AND when permanently installing TWRP
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[b]build-version[/b]-lake.img
To permanently install it:
Temporarily boot twrp
Place the twrp-installer zip on your internal/external storage, or push to /sdcard or /external_sd using adb:
Code:
adb push twrp-installer-[b]build-version[/b]-lake.zip /sdcard (or /external_sd)
Tap Install -> Navigate to /sdcard or /external_sd and select the twrp-installer -> Swipe to install
Reboot recovery. NOTE: if you had Magisk installed previously, be sure to flash again before rebooting to System
NOTE: you can flash the twrp-installer zip directly in Magisk Manager as a module to install and/or update TWRP!
NOTE: Currently, there is no official twrp-installer zip, but there will be for the next official update. However, you can use the "unofficial" twrp-installer for the time being as it is built using the same sources
Downloads
• TWRP (Official) || https://twrp.me/motorola/motorolamotog7plus.html
• TWRP (Unofficial) || twrp-3.3.1-lake-Q-v1.img
• INSTALLER || twrp-installer-3.3.1-lake-Q-v1.zip
NOTE: The unofficial twrp.img and twrp-installer.zip have been updated for Stock Q and Q based custom ROM's. They may also work on all Pie ROM's (is anyone still using Pie?) as well but is untested
XDA:DevDB Information
TeamWin Recovery Project 3.3.1, Tool/Utility for the Moto G7 Plus
Contributors
Jleeblanch
Source Code: https://github.com/TeamWin/android_device_motorola_lake
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-23
Current Beta Version: 3.3.1
Beta Release Date: 2019-05-11
Created 2019-05-14
Last Updated 2020-04-03
Reserved
Treble support ?
Laercio_lalau said:
Treble support ?
Click to expand...
Click to collapse
Yes, of course. The device comes fully treble enabled, so it wouldn't make sense to build TWRP without supporting it. I'm sure it'll need some tweaks here and there and I gotta add in decryption support. It's not that it's broken, I just haven't implemented it yet. I wanted to get a working build up for at least flashing Magisk and GSI's.
Jleeblanch said:
Yes, of course. The device comes fully treble enabled, so it wouldn't make sense to build TWRP without supporting it. I'm sure it'll need some tweaks here and there and I gotta add in decryption support. It's not that it's broken, I just haven't implemented it yet. I wanted to get a working build up for at least flashing Magisk and GSI's.
Click to expand...
Click to collapse
so does it support GSI? It would be good news Bro
Laercio_lalau said:
so does it support GSI? It would be good news Bro
Click to expand...
Click to collapse
Yes, absolutely. I do need to update the twrp fstab a little for our device but it does support flashing system and vendor images. GSI's only contain a system.img, so you're good to go!
Again tho, until I implement decryption support, backups of /data and /sdcard (internal storage) aren't possible.
Hey guys,
I've not installed TWRP for a long time, I've been using the same phone (Nextbit Robin) almost two years.
Do I follow this guide to install this? https://www.xda-developers.com/how-to-install-twrp/
Using the instructions above?
Tomato_Jam said:
Hey guys,
I've not installed TWRP for a long time, I've been using the same phone (Nextbit Robin) almost two years.
Do I follow this guide to install this? https://www.xda-developers.com/how-to-install-twrp/
Using the instructions above?
Click to expand...
Click to collapse
The important thing NOT to follow at that link (which otherwise seems to have good info) is DON'T 'fastboot flash recovery twrp.img' but instead do 'fastboot boot twrp.img' to only boot it initially (notice the words 'flash' and 'recovery' aren't in there), after which there is a new way within TWRP to fully install it. The reason is because there is no longer a recovery partition in the newer A/B-slotted devices including G7+, so if you fastboot flash the old way it could brick your device. So just follow the instructions in OP of this thread once you get to the 'Install via ADB' section.
Edit: another thing is that touch isn't working in current version after installing twrp in latest firmware versions (but does work when booted), also as pointed out in OP decryption still isn't added so can't do full nandroid backups or work with internal storage.
Okay, thanks.
Going to give it a go shortly.
will it make its way to the 'official' download page? https://twrp.me/Devices/Motorola/
I must be doing something wrong, I have a couple of ideas but I'm afraid to try any of them in case I brick it.
I am getting FAILED (remote failure)
C:\G7Plus>adb reboot bootloader
C:\G7Plus>fastboot boot twrp-3.3.0-lake.img
downloading 'boot.img'...
OKAY [ 1.576s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.607s
Click to expand...
Click to collapse
Model
moto g7 plus XT1965-3
Build number
PPW29.98-28
Tomato_Jam said:
I must be doing something wrong, I have a couple of ideas but I'm afraid to try any of them in case I brick it.
I am getting FAILED (remote failure)
Model
moto g7 plus XT1965-3
Build number
PPW29.98-28
Click to expand...
Click to collapse
Did you unlock the bootloader?
washoq said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
No, I did not
It has been a while since I have rooted a phone. And even then i think I have only done it 2-3 times altogether.
Thanks.
Tomato_Jam said:
No, I did not
It has been a while since I have rooted a phone. And even then i think I have only done it 2-3 times altogether.
Thanks.
Click to expand...
Click to collapse
If you need the link where to unlock bootloader on Motorola phones:
https://support.motorola.com/us/en/bootloader
Dahenjo said:
If you need the link where to unlock bootloader on Motorola phones:
https://support.motorola.com/us/en/bootloader
Click to expand...
Click to collapse
Thanks
so pointless until touch support i am guessing
supergear said:
so pointless until touch support i am guessing
Click to expand...
Click to collapse
Not pointless, and besides touch was working fine up until PPWS29.98-66-2 was released. I've since fixed touch in the latest firmware.
AFH Download -> twrp-3.3.1-v3-lake-jlb.img
md5sum = 008d4434ada4b6b68034dd19b2d199b3
I'll update the OP accordingly this evening.
Decryption is planned to get implemented in TWRP? Is it (easily) possible to run the device without encryption, while keeping the possibility to do OTA updates?
Edit: Hey, since when does Motorola stop delivering OTA updates to unlocked devices? That's not what I know from Moto G2, Moto X Play, Moto Z Play. All of them did receive and install OTA updates fine having unlocked bootloader, but the Moto G7 plus shows that it would not receive OTA updates anymore!
Edit2: Maybe they just put that warning in place but don't mean it. They wrote it would still be possible as usual:
https://support.motorola.com/us/en/products/bootloader-unlock/documents/MS91999
Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola. Upgrade packages to new versions of Android will be pushed to all eligible devices, regardless of their bootloader locking status.
Click to expand...
Click to collapse
Hallo ,
Have the same experiance , no April Update for Moto 7Plus over OTA reteu2 channel, nothing.... have flash self ... on my phone only open bootloader and later Magisk for root... not more...
Hope TWRP come the next time with encryption...thanks on this way for the dev's
tag68 said:
Decryption is planned to get implemented in TWRP? Is it (easily) possible to run the device without encryption, while keeping the possibility to do OTA updates?
Edit: Hey, since when does Motorola stop delivering OTA updates to unlocked devices? That's not what I know from Moto G2, Moto X Play, Moto Z Play. All of them did receive and install OTA updates fine having unlocked bootloader, but the Moto G7 plus shows that it would not receive OTA updates anymore!
Edit2: Maybe they just put that warning in place but don't mean it. They wrote it would still be possible as usual:
https://support.motorola.com/us/en/products/bootloader-unlock/documents/MS91999
Click to expand...
Click to collapse
Same here... "System integrity compromised" and I only unlocked the bootloader, nothing else
{
"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"
}
Proudly Presenting RisingOS for OnePlus Nord N200 5G [Dre] !!!
What is RisingOS?
RisingOS is a Open Source Aftermarket Android Operating System that aims to deliver unique and refreshing android experience.
Based on Android 13 | Tiramisu QPR2 | with LineageOS
Screenshots
Device specific changes
Based on OOS 12 C.23 Firmware, Flashing OOS 12 firmware is a must before installing
Known Issues:
Same as LineageOS 20
Credits
@andr01dfr3ak - for Device Tree, Kernel, Vendor tree, and sooooo much ground work for supporting the sm4350 platform.
Tattoorepairman (aka Howie Feltersnatch on Telegram) for letting me use his dev rig for this project.
Notes
Download Link: https://androidfilehost.com/?w=files&flid=338327
Installation Guide
Sideload
1. fastboot flash the 4 recovery image from download link under the "Recovery_Files" directory
2. Reboot device into recovery mode
3. Enter ADB sideload mode
4. adb sideload ROM.zip
5.Wipe data/cache/dalvik-cache
6. Sideload preferred zip files (magisk, etc.)
7. Reboot to system
Android OS version: 13.0.0_r43
Security patch level: May 2023
Build author/Device Maintainer: Travisholt92
Kernel source code: https://github.com/LineageOS/android_kernel_oneplus_sm4350
Firmware source code: https://github.com/risingTechOSS
Firmware created by: The risingOS Team & ME
Based on OOS 12 C.23 Firmware
Telegram group: https://t.me/YeetROMs
Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/
Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the difference because I have the core version but there’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?
can you use the same method as lineage upgrade os method to sideload this from los 19.1?
talejandroamazom said:
can you use the same method as lineage upgrade os method to sideload this from los 19.1?
Click to expand...
Click to collapse
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.
Curiously said:
Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the differencek because I have the core verbutpj butpj thKeepere’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?
Click to expand...
Click to collapse
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.
zm55 said:
Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/
Click to expand...
Click to collapse
I'm running these builds TMO C.21 firmware. C.23 specifically is not required, though that is what the vendor blobs are based on.
Travisholt92 said:
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.
Click to expand...
Click to collapse
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this
talejandroamazom said:
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this
Click to expand...
Click to collapse
Which stock firmware version are you running?
Travisholt92 said:
Which stock firmware version are you running?
Click to expand...
Click to collapse
c.23 de2117
talejandroamazom said:
c.23 de2117
Click to expand...
Click to collapse
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?
Travisholt92 said:
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?
Click to expand...
Click to collapse
yes i did
talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Can you get a logcat and email it to me @ [email protected]
USB debugging should still work on first boot without enabling it in dev options.
talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM
Travisholt92 said:
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.
Click to expand...
Click to collapse
Can I convert to the gapps version from the core? Or do I have to factory reset?
Curiously said:
Can I convert to the gapps version from the core? Or do I have to factory reset?
Click to expand...
Click to collapse
You can dirty flash
Travisholt92 said:
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM
Click to expand...
Click to collapse
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete
talejandroamazom said:
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete
Click to expand...
Click to collapse
Glad to hear you got it working
If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.
famewolf said:
If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.
Click to expand...
Click to collapse
can i participate in this as a tester