{
"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"
}
ONLY FOR NOUGAT FIRMWARE
Working:
ADB
If can possible make a mount / backup or restore any partition, included DATA, restore, backup, flashing...
The settings are saved on CUSTOM partition, and BACKUP's on external storage
MTP
Dont working:
Tell me
Changelog:
RC2 16-03-2017:
Updated UI
New logo and splash screen
Fixed errors on Backup/Restore
Optimized the code
RC1 11-03-2017:
Updated to TWRP base 3.0.3
Data in whole recovery, mount, unmount, backup, restore, flashing .zip files... NO MORE NEEDED DOWNGRADE TO MM
ADB Now can send command and receive
Optimizations...
b9 15-12-2016:
MTP and ADB works at init thanks to: @LastStandingDroid
ADB Keys working thanks to: @LastStandingDroid
Deleted unneded stuff
b8 14-12-2016:
Reworked MTP
Reworked with kernel B336
Updated banner with correct version of recovery
b7 13-12-2016:
Reworked MTP
Removed unnecesary files
Removed DM-Verity v2
b6 08-12-2016:
New Init logo and banner
Deleted parameters for MOUNTING DATA
Deleted splash2
Reworked init.rc and fstab
b2 03-12-2016:
ADB works but no "auth"
MTP works
Backup & Restore of all patitions working (no DATA backup)
Settings of TWRP saved on CUSTOM partition
b1 02-12-2016:
First version working on Nougat
Images
Attached in bottom of the post.
Download:
For install in Android MM (if dont are now in Android N) or for install in Recovery Nougat b*: https://mega.nz/#!tE1XXIaK!ICq1NO1DpLedfdgB0j5DzH4xtEN6jcz2Di8UXfcqSBE
recovery.img for install with Fastboot: https://mega.nz/#!gU91XJjI!V3RcPQ0tDeFNBJAu04cI1gxMqDypEdxs6TQHGF3h0_o
Regards
BadWolfYe said:
Working:
All dont listed in "Dont Working"
Dont working:
ADB
USB MTP
Mount and manage DATA
Download:
For install in FASTBOOT: https://mega.nz/#!JcNCADDA!f4EvXvIJYEPkALmUrG5WDhB-u7pRpcDZ5DvQpQpxlD8
For install in Android MM (if dont are now in Android N):
Im working in fix the error listed up, when i fix all, i work in Revolution Recovery for NOUGAT
Regards
Click to expand...
Click to collapse
Is for VNS-L21 ? Or not?
Why is this called Android Nougat?
The named its called for only work on Android Nougat Firmware....
Adb/mtp fixed...
Working on data partición fix
Oh god i hope you get it sorted, your my last hope with my brick ..... **** me
WTF?
This is no a job, dont need a review for employer's HAHAHAHAHAHA
News:
Data partition still no working...
In this moment recovery save the settings in CUST partition
Backup of all listed partitions CORRECT (tested)
Only can backup to external sd
ADB no work "unathorized" but MTP yes, for activate, go to mount and disable mtp, after, reenable mtp... an boila!
Installation fails at 7 status error (in this moment caused by data partition)
im deleting all unusued stuff on recovery, and upload in the next hours... BETA 2 xd
OP updated
I do not mean to be rude and I appreciate your work, but how is this different from the regular TWRP and from TWRP by Meticulus? I mean there are two rock-solid versions of TWRP, what is the added value of flashing this one?
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
BadWolfYe said:
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
Click to expand...
Click to collapse
My apologies, I feel super stupid now. Thanks for your contribution!
Thanks for your work
Thread cleaned of stupidity. Next time we'll talk privately. :good:
Cheers,
Darth
Senior Moderator
TWRP not picking up internal storage, please help.
Recovery updated and reworked...
Hello
I do not understand, I can not manage to make it work.
He shows me cust 177mb
Internal storage 0mb
Micro sdcard 0mb
And I get to nothing. thank you
I understood
BadWolfYe said:
Recovery updated and reworked...
Click to expand...
Click to collapse
Now can i flash directly on the reworked twrp? Like if im going to reflash the b329 + data files? And also the camera fix?
Is there somewhere already a supersu file for root
Then you could root it and then downgrade with toolkit because the twrp he has fixed and thus you could zip the zip yes
Thank you for your great work
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
ExodosPL said:
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
Click to expand...
Click to collapse
It must be "fastboot flash recovery RevRecNP9Lite.img"
Thank You, it works
Related
{
"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"
}
TWRP Recovery for Xiaomi Mi 6 (sagit)
Hi guys,
I made the TWRP from TeamWin official sources for our Xiaomi Mi6 (sagit). You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot Mi6 into fastboot mode
Flash using
Code:
fastboot flash recovery twrp-3.1.1.0-sagit-v2.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery, ADB and MTP
Let me know if there are others
Source code:
ValoXTech's Github
The data partition cannot be decrypt. All the names of folders and files are messy characters.
Nice. all works
gh2923 said:
The data partition cannot be decrypt. All the names of folders and files are messy characters.
Click to expand...
Click to collapse
You have to wipe -> format data to decrypt your device. I'm working on a fix for the encrypted side.
Do i have to flash the *no-verity-opt-encrypt-5.1.zip after flashing the rom with your TWRP? And do i have to wipe system to or only data?
ValoXis said:
You have to wipe -> format data to decrypt your device. I'm working on a fix for the encrypted side.
Click to expand...
Click to collapse
Yeah, I knew that, just don't want to backup & format... Thanks a lot!
Waiting for repair encryption, otherwise I will not use third party recovery
thanks for your great work，and wait for you to fix the encrypted side.
Is it the official version?
TWRP v2 for sagit released!
Changelog:
Fix MTP and ADB
Download:
AndroidFileHost
Great news @ValoXis great to find mi5 guys come to mi6 too
I hope it will soon be fixed I never enables encryption where can I see if it is enabled? I too have the strange characters in recovery file manager
I twrp on MI6 does not stay installed and it's all encrypted !?
yakie996 said:
I hope it will soon be fixed I never enables encryption where can I see if it is enabled? I too have the strange characters in recovery file manager
Click to expand...
Click to collapse
gaggione78 said:
I twrp on MI6 does not stay installed and it's all encrypted !?
Click to expand...
Click to collapse
"Strange characters" means that you have the device encrypted. To decrypt you have to wipe -> format data. NOTE: You will loose all your data in data and userdata partition.
By unlocking the bootloader I have done a factory reset why isnt it gone? isn't it possible to have encryption and twrp running together without this problem?
yakie996 said:
By unlocking the bootloader I have done a factory reset why isnt it gone? isn't it possible to have encryption and twrp running together without this problem?
Click to expand...
Click to collapse
mi unlock tool only wipes data partition and keeps internal storage as such with no wipe
Then wipe data?For twpr that does not stay installed?
yakie996 said:
By unlocking the bootloader I have done a factory reset why isnt it gone? isn't it possible to have encryption and twrp running together without this problem?
Click to expand...
Click to collapse
gaggione78 said:
Then wipe data?For twpr that does not stay installed?
Click to expand...
Click to collapse
It is possible, but Xiaomi for Mi6 uses FBE encryption. Actually a few devices have it. I'm working on a fix that will be released soon.
For now you have to "wipe"-> press "format data" button to use internal storage from recovery, so data and sdcard will be decrypted (and wiped).
Then look ....... thank you a thousand you are a myth !!!!
When i wipe format data how to install a custom rom?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only for Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25
Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices
Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks
adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs
I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.
Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks
New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards
Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers
Would this work on the Chinese V9 variant?
smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?
adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...
TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"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"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03
I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.
Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.
3.1.2_r18 version released. Check download link in OP
hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?
fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok
rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.
Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?
Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.
I make a full backup, so can I restore that backup file after LineageOS?
This works when go command fastboot boot .... ?
I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...
Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).
Freshly built for cepheus twrp 3.3.0
Now working with standard builds of opengapps no need for the custom build.
Known issues:
Global FW only unless you flash matching dtbo and boot.img
Does not support encryption
Instructions: unzip and flash the image via fastboot.
Changelog:
v11 hope this fixes backup/restore issues some were having
TWRP v12 Download:
https://www.androidfilehost.com/?fid=6006931924117882399
Kernel source
https://github.com/randomblame/android_kernel_xiaomi_sm8150/tree/twrp
serious things start ! Keep it up
stuck at logo screen..then bootloop. flashed recovery-mi9-3.2.3.img right away and i'm back to recovery.
impressive gapps arm64 compatibility with all recoveries collected:
recovery-mi9-3.2.3.img - nope
twrp-3.2.3-6-cepheus-mauronofrio.img - nope
twrp-3.2.3-10-cepheus-mauronofrio.img - nope
Twrp_3.3.0_Cepheus.img - nope
twrp_cepheus.img - nope
twrp_en.img -nope
doggydog2 said:
stuck at logo screen..then bootloop. flashed recovery-mi9-3.2.3.img right away and i'm back to recovery.
impressive gapps arm64 compatibility with all recoveries collected:
recovery-mi9-3.2.3.img - nope
twrp-3.2.3-6-cepheus-mauronofrio.img - nope
twrp-3.2.3-10-cepheus-mauronofrio.img - nope
Twrp_3.3.0_Cepheus.img - nope
twrp_cepheus.img - nope
twrp_en.img -nope
Click to expand...
Click to collapse
I'll throw the stock kernel in and that should fix it. This one seems to have an issue with some devices that I haven't figured out
randomblame said:
I'll throw the stock kernel in and that should fix it. This one seems to have an issue with some devices that I haven't figured out
Click to expand...
Click to collapse
thanks. the upstream kernel you published also bootlooped. is it the one you will push in it?
doggydog2 said:
thanks. the upstream kernel you published also bootlooped. is it the one you will push in it?
Click to expand...
Click to collapse
New build is up with the stock kernel. Should be more compatible. I still have people running off revos who say it will not boot. I believe there is a partition layout difference. This has been tested to work with GLOBAL firmware and gsi's on top
randomblame said:
New build is up with the stock kernel. Should be more compatible. I still have people running off revos who say it will not boot. I believe there is a partition layout difference. This has been tested to work with GLOBAL firmware and gsi's on top
Click to expand...
Click to collapse
v2twrp is not booting with revos, stucking at bootlogo, will go back to previous twrp
portfolio said:
v2twrp is not booting with revos, stucking at bootlogo, will go back to previous twrp
Click to expand...
Click to collapse
Revos and anything based on the china firmware kills it dead. I'm gonna try to pull the kernel out of the china fw next and see if that is compatible with both global and china firmware layouts
Please be sure encryption has been disabled before testing otherwise it's not going to load
Backup works?
Hi @randomblame for the decryption/encryption problems, if it doesn't work just disable it in compilation process hiding TW_INCLUDE_CRYPTO := true and others crypto flags.
For the clock you can see this commit: https://github.com/mauronofrio/andr...mmit/3647d514f905764e2d095a54213e4d52085d28da
Maybe you will need to set it to 84 more or less.
For adb, you should build the twrp with -eng and not with -userdebug, userdebug build is not more used since android 8.1
I didn't find a device tree source so i decided to write here.
Hope this will help you fix your problems
Thank you so much, finally a recovery with working gapps installation WOHOO!
Tested with https://treble.andro.plus/ FolokoROM with newest opengapps mini package
EDIT: Sorry its not working, the gapps package was flashed successfully, but after a reboot there were no gapps installed. ?
MindtheGapps works but there is no faceunlock
Is Nandroid working on this one?
mauronofrio said:
Hi @randomblame for the decryption/encryption problems, if it doesn't work just disable it in compilation process hiding TW_INCLUDE_CRYPTO := true and others crypto flags.
For the clock you can see this commit: https://github.com/mauronofrio/andr...mmit/3647d514f905764e2d095a54213e4d52085d28da
Maybe you will need to set it to 84 more or less.
For adb, you should build the twrp with -eng and not with -userdebug, userdebug build is not more used since android 8.1
I didn't find a device tree source so i decided to write here.
Hope this will help you fix your problems
Click to expand...
Click to collapse
Hey thanks for the tips clock needed an offset of 80, adb is fixed and hopefully encrypted devices will not fail to boot and allow /data to be formatted. Backup seems to be working.
The problem with the opengapps packages is that it is not set up for system as root I'm pulling down their git and I'll build one to host as well
v4 test:
MTP: working (auto mount)
ADB sideloading: working
OTG: no (( -> only one time setup via sdcard or PC sideloading
Encryption: no
OpenGapps64: yes (after resize thou)
Backup: not tested
Reboot to fastboot: ok
Reboot to recovery: ok (not with fastboot thou, don't know why this is common)
Advanced functions={Copy log,ADB sideload,Terminal,File Manager,Reload Theme,Fix Contents}
Partitions mountable={System,Vendor,Data,Cache,persists,cust,metadata,sdcard}
The problem with the open_gapps package is here:
https://github.com/opengapps/opengapps/commit/82538ba5b07e3093a11d583463b07a848a4a32b9#diff-4b4d756dd3b2a232970b47588e486edd
The device is not detected as system as root or a/b I'm gonna try to put together a package for us.
if [ -n "$(cat /proc/cmdline | grep slot_suffix)" ];
then
ui_print "- AB DEVICE DETECTED";
device_abpartition=true
SYSTEM=/system/system
VENDOR=/vendor/vendor
elif [ -f /system/system/build.prop ];
then
ui_print "- SYSTEM_AS_ROOT DEVICE DETECTED";
device_abpartition=true
SYSTEM=/system/system
VENDOR=/vendor/vendor
else
device_abpartition=false
SYSTEM=/system
VENDOR=/vendor
fi
this should work
*edit ok toolbox is not properly linked in twrp so these changes will do nothing for now. I did compile a version of opengapps that DOES install through this recovery and will link it in the OP I also modified it so that it should pass the architecture test that it fails in the china twrp if anyone prefers that one. It is only micro but if there is demand maybe I can make a couple options but I would prefer to find a better fix.
The working version of gapps is here: https://www.androidfilehost.com/?fid=1395089523397955923
also started working on this for fun
{
"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"
}
v4 still not booting into recovery with ROS
portfolio said:
v4 still not booting into recovery with ROS
Click to expand...
Click to collapse
ok, I have to correct, it is working with ROS, this time I flashed v4 over fastboot and it boots into recovery (1st I flashed v4 in my previous TWRP, so one has to use fastboot command to flash this TWRP).
Also this TWRP is really nice to understand and to handle, Thx for that, I'll try corrected gapps later, also no problem to mount system and seeing gapps have to install into /system/system
:good::good::good:
anyway strange: booting into recovery only succeeds when usb-connected to a PC over adb command/vol up+pwr/on-off menu,
when not usb-connected, no way to boot into recovery, always boots into system after a short waiting time showing the mi logo
???
also: other TWRPs show the partition /system/system as /system_root/system and /vendor/vendor just as /vendor and I suppose
the downloadable opengapp-version will only work with v4 twrp and not with other twrps mounting partitions in a different way
randomblame said:
also started working on this for fun
Click to expand...
Click to collapse
Can't wait to test, thanks for working on it!
TWRP for OnePlus 8 and 8 Pro
{
"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"
}
TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers, and zulip-chat.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM".
Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.
Code:
#include
/*
*
* Yea, though I walk through the valleys of c++ and java, of the shadow of death on these forums,
* I will fear no evil and i will develop and code restless: for thou art with me and my keyboard;
* thy rod and thy staff they comfort me, and my mouse..
*
*/
A13 support is still a WIP, but most things are working, A13 is all new, keep that in mind.
WORKING:
Decryption
ADB Sideload
Format Data
Flashing zips (kernels and ROM's)
Backup/Restore
MTP is working
adb is working
OTG
more...
NOT WORKING
tell me
Download
Beta 3
Flashable zips:
https://devuploads.com/h6omb3dsxg5n -> twrp_op8_ext4-3.7.0-b3.zip - 34.8 MB
https://devuploads.com/d6j8gpbyfbzf -> twrp_op8_erofs-3.7.0-b3.zip - 34.8 MB
Flashable imgs
https://devuploads.com/gxv3t5onoapm -> twrp_op8_ext4-3.7.0-b3.img - 100.0 MB
https://devuploads.com/vg662syh8j7j -> twrp_op8_erofs-3.7.0-b3.img - 100.0 MB
(Please disable any adblockers downloading from my links)
Instructions
Windows
Install oneplus usb driver, after disabling driver signature enforcement
Download and install platform tools, unzip and add the folder to Windows path,
"Settings > Advanced System Settings > Environment Variables > New"
Example -> http:///imgur.com/a/x8XOofQ
open command prompt, or powershell, and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
Linux
Download and add to path (.bashrc) platform-tools:
export PATH=$HOME"/platform-tools:$PATH"
dont forget udev rules if you're using ubuntu based distro:
https://github.com/M0Rf30/android-udev-rules
open a terminal and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
that's all.
Telegram Group:
Telegram: Contact @infected_unofficial_stuff_group
t.me
Feel free to join!
Source Code:
GitHub - infectedmushi/twrp_device_oneplus_instantnoodle
Contribute to infectedmushi/twrp_device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
https://github.com/infectedmushi/android_bootable_recovery
https://github.com/bigbiff/android_device_oneplus_instantnoodle
https://github.com/TeamWin/android_bootable_recovery
https://github.com/systemad/android_device_oneplus_instantnoodle
Credits:
@bigbiff
@Lossyx
@Captain_Throwback for original tree
@mauronofrio for original tree
TWRP team
HOW TO BACKUP && RESTORE ON TWRP CORRECTLY
theincognito said:
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Remove any password/pin/pattern before doing this
Backup
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
In TWRP
If you skip this step you will not be able to successfully start the system after restoring data
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Reboot system
Note:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen or a toast message saying "com.android.phone keeps stopping."
Tap "Close app", hold the Power button down to be presented with the option to (Lockdown), Power off, or Restart. Select Restart
It may take a couple of restarts
If you want to backup and restore fingerprints too, follow the guide in the attached file
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ect-8t-kebab-2021-09-04.4302449/post-85292199
thanks @BillGoss && @theincognito
This is awesome! Thanks for opening a new thread!
Sweeet tnx
Thank you very much, beta 2 is working good
uploaded beta 3.
changelog:
https://gerrit.twrp.me/c/android_bootable_recovery/+/4411
* zip install: unmap any dynamic partitions before installing
https://gerrit.twrp.me/c/android_bootable_recovery/+/4401
* version: don't show as error if we cannot write the version string
https://gerrit.twrp.me/c/android_bootable_recovery/+/4386
* relink recovery modules correctly - Added ziptool as unzip deprecated in a11
regards.
Why do we need to install new drivers with no signature?
Whats the problem with normal platform tools?
Can anyone confirm if could restore a backup successfully and what is the right order to restore every partition?
xtcislove said:
Why do we need to install new drivers with no signature?
Whats the problem with normal platform tools?
Click to expand...
Click to collapse
you don't need to do anything if you already got fastboot and adb working.
Thank you to all the people involved.
Finally the hard work gave fruits!
Noce to see this become official finally
Successful restore anyone?
vibration does not work :3
Do we have to use MSM Tool to format before installing? Also, did anyone successfully restore a nandroid backup?
progress on MTP issue..
Revenant Ghost said:
Do we have to use MSM Tool to format before installing? Also, did anyone successfully restore a nandroid backup?
Click to expand...
Click to collapse
If you run MSM you'll completely wipe your phone and relock the bootloader.
anyone can test MTP on Windows, and data restore?
https://drive.google.com/open?id=1b...JmIBVr&[email protected]&usp=drive_fs
@infected_ for me mtp work on beta 2 and 3. On oneplus 8 pro with latest oos.
Noob9496 said:
@infected_ for me mtp work on beta 2 and 3. On oneplus 8 pro with latest oos.
Click to expand...
Click to collapse
nice. can you test /data restore? and see if doesn't gives error 255?
infected_ said:
nice. can you test /data restore? and see if doesn't gives error 255?
Click to expand...
Click to collapse
Unfortunately, I will not do it at the moment because I do not have time. And in case of problems with the system, I will have to reinstall everything and upload files.