{
"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...
Related
Because there are too many people ask about "how to decrypt data" and "how to re-encrypt data",
I write a guide to tell you how to decrypt/re-encrypt data partition.
[Change log for V2:]
1. Update script to no-verity-opt-encrypt-6.0.zip
2. Decryption support for Android Oreo and Android Nougat
[Why we need decrypt data partion?]
1. Install MultiRom/MultiBoot
2. Some Roms only work on decrypted device
3. For better performance
[Disadvantage]
1. Low security (Cracker can access your file, and remove lock screen pin from TWRP)
2. It need to wipe your data/internal storage to decrypt data partition.
Decrypt data partition with magisk:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer Rom and no_verity_op5_v2.zip to the device over MTP
3. Go to “Install” section, select ROM, and swipe to confirm the flash
4. Go to “Install” section, select magisk.zip, and swipe to confirm the flash
5. Go to “Install” section, select no_verity_op5_v2.zip, and swipe to confirm the flash
6. Reboot
PS. you should format data before flashing no_verity_op5.zip.
Re-Encrypt data partition:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer stock Oxygen Rom to the device over MTP
3. Go to “Install” section, select the Oxygen rom, and swipe to confirm the flash
4. Reboot
[Proof]
No magic here. What you see is real.
[How it work?]
OnePlus 5 uses FBE(File-Based Encryption) to encrypt data partition.
The latest no-verity-opt-encrypt zip ( https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ ) only replace "forceencrypt" to "encryptable".
It didn't replace "fileencryption", so your data partition is still encrypted.
In order to decrypt data partition, I modified the no-verity-opt-encrypt.zip by myself.
The no_verity_op5_v2.zip will replace "fileencryption" to "encryptable".
boot.img/ramdis/fstab.qcom
{
"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"
}
Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..
aneeshmbabu said:
Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..
Click to expand...
Click to collapse
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.
snowwolf725 said:
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.
Click to expand...
Click to collapse
Hi thanks for the replay , presently i flashed twrp and magisk also I'm in Franco custom kernel , so can i possible to decrypt data,
I'm very new in one plus 5 , coming from Motorola phones , so kindly give me a step wise process for a beginner .. thanks in advance ..
Does no_verity_op5.zip still work after system update?
sinnbro said:
Does no_verity_op5.zip still work after system update?
Click to expand...
Click to collapse
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
snowwolf725 said:
[Why we need decrypt data partion?]
4. For better performance
Click to expand...
Click to collapse
Does someone know what "better performances" means ?
I decrypted my OP3 but honestly I didn't noticed any change in performances (except opening TWRP)...
According to this process, can I also decrypt the stock rom?
snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Thanks
snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Or worse, the device will boot fine and proceed to encrypt your drive...
Why is magisk required?
ChavitoArg said:
Why is magisk required?
Click to expand...
Click to collapse
You don't need to flash magisk, if you don't want it.
Fif_ said:
Or worse, the device will boot fine and proceed to encrypt your drive...
Click to expand...
Click to collapse
Yes, you are right.
It will also encrypt your device.
So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.
ChavitoArg said:
So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.
Click to expand...
Click to collapse
Yes, you have to flash it every time you write the boot partition: flash a ROM or OTA.
Note that if you use Magisk, Magisk by default automatically turns off DM Verity and force encrypt, so there's no need to flash both no_verity_op5.zip and Magisk, just Magisk is fine.
snowwolf725 said:
[Why we need decrypt data partion?]
...
4. For better performance
Click to expand...
Click to collapse
Really ?
I have a few questions for the sake of clarity, as an experience I had makes me question if Magisk handles this. Blu_spark kernel will not boot when flashed with Magisk on my decrypted, stock OOS device - I believe status of encrypted/decrypted and FBE are two separate things based on the reply from eng.stk. it seems to use that kernel while decrypted, I still need to flash no-verity zip, even with Magisk.
This thread states both that you don't need to flash this if using Magisk, but that you need to flash this anytime you modify boot IMG - ROM flash, OTA, etc. I'm trying to nail down when I need this zip and when I don't - very curious if there's some solid info on when to use this in flashing and when not to. Guide is great as is for decrypting - just wanna stay that way.
@wrongway213
Hi,
maybe this will help you: https://forum.xda-developers.com/showpost.php?p=73311252&postcount=114
is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs
HonPig said:
is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
No, new version of xposed supports encrypted data partition.
Which twrp is recommended for decrypt device?
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).
{
"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"
}
NOTE: Decrypting data is not currently working. This is my initial release and i'm planning to fix as many bugs i can. When it's stable enough , only then i will push to official
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* I am not responsible for bricked devices,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Sources: https://github.com/TeamWin
Device tree: https://github.com/Suicide-Squirrel/android_device_huawei_charlotte
Download
Flashing:
Code:
fastboot flash recovery_ramdisk recovery.img
Special thanks to @Dees_Troy for the Huawei Blanc device tree, which this is based on.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL]TWRP:Team Win Recovery Project[P20 PRO], ROM for the Huawei P20 Pro
Contributors
kessaras, steadfasterX
ROM OS Version: 9.x Pie
ROM Firmware Required: v195 or newer
Based On: OMNIROM,TWRP
Version Information
Status: Beta
Created 2019-06-14
Last Updated 2019-06-14
I will use this post to share my work
Sorry for making another TWRP thread, but i've had enough with our current TWRP.
I have enabled logcat and strace.
This is the initial release so keep in mind that it has (probably) currently the same bugs with the official.
The only difference is that you can grab any kind of log and help me improve it and only when it will be stable enough , only then, i will push to the official.
------------------------------------------------------------------------------------------------------
VERSION: recovery-3.3.1-0-b.img | date: 15-06-2019
FIXED:
1. mounts correctly all partitions
2. backup to usb-otg enabled
3. backup all partitions except data (i need to fix decryption)
4. restore fixed.
5. ADB sideload fixed.
6. you can flash a kernel and a recovery .img directly inside TWRP. No more rebooting to bootloader.
NOT TESTED:
1. I don't know about format yet. i haven't tested it because im not ready to format yet.
If anyone is about to format anyway, please after format do:
Code:
adb pull /tmp/recovery.log
and
Code:
adb logcat -b all > logcat.txt
And send me these two logs so that i can fix format and we don't need stock Huawei recovery anymore.
2. Can't flash GAPPS exactly like in the official.
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
FIXED:
1. GAPPS flashing fixed. Same goes for any other flashable package.
2. backup data and wipe data are fixed. (not tested restore yet)
NOT FIXED:
1. Even if wipe data and backup data are fixed, and even though we can restore data ! Sadly there are bugs when we wipe data or perform a restore. Until i fix (if i fix it) decryption, please keep using the stock Huawei recovery to format your data and avoid restoring data.
ISSUE: Data partition is fine and it sais that it's 128gb but apps think that we don't have enough "free space". It may just be an issue in vold too in the rom where i tested it.
VERSION: recovery-3.3.1-0-d + e.img | date: 20-06-2019
FIXED:
- minor bug fixes for stability
- added nvme partition which is needed during the decryption
- adb sideload fixed. No need to push and install
NOT FIXED:
- decryption
- format
It's great news man. Looking forward to your further progress! Fully functional twrp is the juice.
Amazing, hope we can have finally fully functional twrp
Thanks
aoryx said:
Amazing, hope we can have finally fully functional twrp
Thanks
Click to expand...
Click to collapse
adb sideload and gapps flashing are fine too.
Format data needs to be fixed and decryption
Legend.
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
dladz said:
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
Click to expand...
Click to collapse
not yet. gimme some hours. im trying to fix something and then ill share a new build.
i have 2 errors left:
1. linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/sh" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
That problem is in bionic.
in bionic/linker/tests/linker_config_test.cpp or in
bionic/linker/ld.config.format.md. But i can't figure it out yet. That will fix the gapps flashing issue with latest TWRP and mine.
What's strange is that it doesn't happen to everyone. So i'm confused.
Me i can't flash any gapps, when others reported to me that they can.
Click to expand...
Click to collapse
We can finally backup data partition. And we can use MTP. And we can restore data. And everything is ok, BUT
i still can't decrypt the internal storage. it's a work in progress.
Click to expand...
Click to collapse
At least wait for 1. otherwise you may need 3.2 official TWRP to flash gapps and it's boring to flash other TWRP every time.
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
titi66200 said:
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
Click to expand...
Click to collapse
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
kessaras said:
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
Click to expand...
Click to collapse
stop working in RL the PR is waiting for you :laugh:
https://github.com/Suicide-Squirrel/android_device_huawei_charlotte/pull/1
as said: needs testing ofc as I do not own that device
.-
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
Sounds painful, the other twrp does something similar..
Would the chap who made the unofficial one be able to assist?
His threads looked but he's still active .
Feel for you mate, sounds like a massive ballache.
kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Lukas do not wipe data at an encrypted and non-decrypted partition.
When you will boot again to the rom, the system will think that data is clean so it will attempt to encrypt the already encrypted.
At settings you will see that you have 128gb data partition but you will have only a few mb actually.
wipe data does NOT remove encrption, only a format can remove the encryption.
djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Did it actually wipe though? If it didn't the ROM may still boot as it would simply be a dirty flash.
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
pmatj said:
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
Click to expand...
Click to collapse
the only way to know that is to flash it and test it.
what are you afraid of ? if twrp doesn't boot, you can flash back the stock huawei recovery again.
>> the device won't have any issues if twrp is not for that device <<
It should work if it can boot. The only difference is our resolution. So if you see TWRP boot , then it's ok to use it.
* It will probably work because i don't force any specific resolution here.
But if it doesn't , change this to your resolution https://github.com/Suicide-Squirrel...43104c493e172dc469d7838153/BoardConfig.mk#L53
and build TWRP for p20 lite
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
pmatj said:
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
Click to expand...
Click to collapse
If it's a/b try talking to OnePlus 6/6t recovery.
They have a/b there too and if the dev answers to you then you probably have it
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Quote:
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.
Click to expand...
Click to collapse
Features:
amonet-aware
SDCard support
USB-OTG support
Backup/Restore support
Downgrade/Overwrite-protection for LK/PL/TZ
Autorestore of broken boot-patch
Also patches amonet-microloader when flashing images
Supports flashing stock-update bins (rename to .zip, no modification necessary )
NOTE: Your device needs to be unlocked.
NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System" (And "Vendor Image").
Download: twrp-mustang-3.3.1-0.zip
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the Amazon Fire
Contributors
k4y0z, xyz`
Source Code: https://github.com/chaosmaster/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-07-17
Created 2019-07-16
Last Updated 2019-07-17
Changelog
17.07.2019:
Update TWRP to 3.3.1-0
Add vendor and vendor-image to backup
Reserved #2
New build is up, updated to TWRP 3.3.1 and included vendor in backup.
niiiiiice, works well. can do backups now ?
thank you so much! very appreciated
Quick guide on updating from an older version of TWRP for newbies? Thanks!
delgada89 said:
Quick guide on updating from an older version of TWRP for newbies? Thanks!
Click to expand...
Click to collapse
Download the latest version, and flash it from TWRP.
Kctucka said:
Download the latest version, and flash it from TWRP.
Click to expand...
Click to collapse
Cheers worked great.
k4y0z said:
NOTE: Your device needs to be unlocked.
Click to expand...
Click to collapse
To which point do I need to follow the unlocking topic? Is it 13?
Kctucka said:
Download the latest version, and flash it from TWRP.
Click to expand...
Click to collapse
Hi
do I do this like this? I have TWRP 3.2.3.0 now.
adb push TWRP3.3.1.zip /sdcard
boot into TWRP 2.2...
select install
select the TWRP 3.3.1.zip
swipe to flash
Is this how it is done?
garnet2k said:
Hi
do I do this like this? I have TWRP 3.2.3.0 now.
adb push TWRP3.3.1.zip /sdcard
boot into TWRP 2.2...
select install
select the TWRP 3.3.1.zip
swipe to flash
Is this how it is done?
Click to expand...
Click to collapse
Yup that works. You can also download the .zip directly to the tablet.
Kctucka said:
Yup that works. You can also download the .zip directly to the tablet.
Click to expand...
Click to collapse
When I do this how does a runnnign TWRP know where to put the 3.3.1 TWRP?
Worried not to screw the boot up of the tablet.
On another note: How do I back up the tablet with TWRT? Which partitions do I need to back up?
Thanks very much for this !! It is orders of magnitude better than the TWRP from the original.
Now I can actually backup and restore and access all the partitions.
I think I found a bug with twrp-mustang-3.3.1. with a fire 7 2019 and SDcard extended storage. To reproduce.
1. On the fire browser download SOD-fix-test.zip from https://forum.xda-developers.com/sho...&postcount=253
2. Reboot into TWRP
3. Install SOD-fix-test.zip from /sdcard/download
4. Using the file manager, Note the file 12wakelock_for_sod is NOT in /system/etc/init.d
5. Using the file manager, copy /sdcard/download/SOD-fix-test.zip to another location like /tmp
6. Install SOD-fix-test.zip from /tmp
7. Note now the file is correctly installed in /system/etc/init.d
Thanks! Backup and restore worked great! Been missing that for a bit now.
slacka123 said:
download SOD-fix-test.zip from https://forum.xda-developers.com/sho...&postcount=253
Click to expand...
Click to collapse
Don't flash that script, it is useless as described here and here. However I did create an app that holds an actual wakelock and also blocks wifi when the screen is off, vastly increasing stability.
AlwaysLucky said:
Don't flash that scrip
Click to expand...
Click to collapse
Thanks for the warning that my example was an ugly hack/workaround. My point is not the script, the point was to report a bug. You don't have to use that file, it was just an example to highlight the problem with TWRP. If you install stuff to /etc from downloads the install will fail without warning the user.
This worked before, but I don't think I had an SDCARD installed at the time. So I think it's related to that.
Is there an austin build of TWRP?
If so, I cannot find it.
natee22 said:
Is there an austin build of TWRP?
If so, I cannot find it.
Click to expand...
Click to collapse
I think it is the same as the ford. The only real difference between them is the Wifi on austin has 5g. Test run it and see....
fastboot boot twrp******
Here is the thread that installs it. If you are unlocked, run the fastboot.sh
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
how to fix
{
"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"
}
i have problems with this tablet, that dont start nomaly, when power on go directry to recovery....help me please
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features:
* Encrypted build
* Vanilla build (no gapps)
* Selinux enforcing and Safety net passes by default
* More info - Click here
First Time Installation:
* Backup before you begin
* Reboot to provided or TWRP based recovery.
* Format Data , even coming from crDroid 8.x
(otherwise you may not able to boot ROM due to encryption complexities)
* Flash ROM via adb sideload
* Flash Nik Gapps core + Gapps Search addon + Google Device Personalization addon via adb sideload
* Reboot and profit!
Update Installation:
* Backup before you begin
* Ensure you are on provided 12/13 recovery
* Use Updater app to download update and flash
(or download update separately and use Updater app with Local update option)
* No need to flash gapps if already flashed.
Download:
Click Here
Known issues:
* None.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_sm6150-common
Visit official website @ crDroid.net
crDroid sweet/sweetin - crDroid Telegram
Donate to help me in development
crDroid Community Telegram
Donate to help CrDroid team pay server costs
Hello, neobuddy89.
I installed the rom this morning.
I encountered only a "bug" (??).
In developer'options, I choose as usual "File transfer" but it is then automatically set to "No data transfer".
Correction isn't urgent. I can use a USB key.
hi,
i flashed last build and touch issue persists on A13 build
But i still stay on
Nice! Thanks a lot!
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Hellera said:
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I clean flashed it in orange fox recovery, latest version., OrangeFox-R12.1_3. Did I do something wrong? Can you provide a specific recovery something else than default one, please? Thank you.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Hellera said:
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
` Can-dlE ! said:
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Click to expand...
Click to collapse
I faced similar issues on some TWRP builds and OrangeFox, storage, APK and Play Store related stuff. Since then I'm on 'TWRP-3.6.2-sweet-Nebrassy-13-09-22' and never faced such issue again. This one works perfect except for some Pulkit builds, where you need KewL version of TWRP.
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img ...
Click to expand...
Click to collapse
Thank you for your explanation.
I followed the same way to install the rom this wednesday morning (see post 2 of this thread), using also the same twrp.
As workaround to the mtp tranfer problem (awaiting for a quick solution), I simply use a USB key instead of rebooting to twrp.
For having used crDroid 8 for a few months as daily driver, I'm now using crDroid 9 in the place in order to ensure continuity : same environment, same developer.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
Click to expand...
Click to collapse
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
I'm looking forward to flashing A13 once it's more stable. Also, it's the weekend and I don't want to spend the next few days looking at a recovery screen
Hellera said:
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
Click to expand...
Click to collapse
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and
;
you can then work as with MTP File transfer
cocopipou said:
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and View attachment 5758139 ;
you can then work as with MTP File transfer
Click to expand...
Click to collapse
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Hellera said:
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Click to expand...
Click to collapse
I agree with you, but we have to be patient.
Don't forget that we have the chance having a developer who makes a great work.
It's a first release of crDroid 9.
Before installing this rom, I installed various A13 roms.
None of them had the problem of MTP file transfer but other disadvantages like "No advanced restart", ...
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
tomikaka said:
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
Click to expand...
Click to collapse
TWRP version? Magisk Version?
` Can-dlE ! said:
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
Click to expand...
Click to collapse
for me its all working.