Develop Bugs

Unofficial TWRP 2.8.7.1

What is better than the standard CM Recovery:
You can flash another firmware (not the CM)
Normal backup data
You can easily flash the Root
{
"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"
}
Unlock the bootloader as on CM Wiki instructions
Puth the phone in bootloader mode
In the folder with fastboot put crackling-t0x1.img
Enter the following command:
Code:
fastboot -i 0x2970 erase recovery
then Enter
Code:
fastboot -i 0x2970 flash recovery crackling-t0x1.img
Disconnect the device from the USB and remove the battery. Then replace the battery and restart the device in recovery mode to verify the installation. To do this, hold down the "Volume Down" and "Power".
You can download crackling-t0x1.img from here
http://www91.zippyshare.com/v/60lfsDiR/file.html
Credits to 4PDA Members and especially to FindYanot for developing and allowing posting here
IT is NOT my Work

I've been using this for a while, working very good!
Great to make backups and test ROMs.

There is a problem - this recovery can not mount f2fs partitions

RaidonChrome said:
There is a problem - this recovery can not mount f2fs partitions
Click to expand...
Click to collapse
for my information : which system firmware can mount f2fs partitions?

Dior DNA said:
for my information : which system firmware can mount f2fs partitions?
Click to expand...
Click to collapse
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine

RaidonChrome said:
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine
Click to expand...
Click to collapse
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.

Dior DNA said:
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.
Click to expand...
Click to collapse
It does not, in fact it is broken even with ext4 currently

PLEASE HELP, something when wrong
RaidonChrome said:
It does not, in fact it is broken even with ext4 currently
Click to expand...
Click to collapse
Is this the reason why i can't install gapp on my wileyfoxswift and an error appear("e: unable to find partition size for '/recovery") every time i use the wipe.
i upgraded from 12.1 to
13.0-20160127-NIGHTLY-crackling and use the same for recovery but did not work so i installed TWRP and this error occurs -see pics
PLEASE HELP

AromaGapp not working in TWRP
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

noob2016 said:
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.

Tamarinde said:
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.
Click to expand...
Click to collapse
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma

Thanks
robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
That is great! i hope i can try i try it but sadly i send it back since the phone was just here for the upgrade. Anyway thanks for the reply here and on my other post.
Much appreciated

robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!

There is a zip file and recovery. IMG file, any reason why?

image45 said:
There is a zip file and recovery. IMG file, any reason why?
Click to expand...
Click to collapse
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not

robin0800 said:
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not
Click to expand...
Click to collapse
Yes i downloaded the zip file, extracted the recovery.img then flashed by fastboot. I am used to using fastboot commands
So the zip file would function as an update file via a non stock recovery, however once installed would replace the non stock recovery with twrp version!

[RECOVERY] TWRP 3.3.1-0 (lilac) [UPDATE: 2019-09-16]

TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"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
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!​
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16

Nice work!

What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?

Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51

4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!

aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.

modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?

4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...

works perferct! thank you :good:

I got an XZ1. Any chance to get TWRP for it (for testing)?

Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img

TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it

modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...

it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally

a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.

modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.

Question just to be clear: do we have to update twrp for evry new securitypatch?

To decrypt the /data partion on a stock ROM, yes you do.

Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham

UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method

[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)

[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)
This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
{
"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 recovery supports FBE decryption of AOSP based ROMs like LineageOS, OmniROM etc. There is no support for Samsung ODE in TWRP yet. If you're interested, help to provide it is welcome.
FEATURES
File-Based Encryption (FBE) support
MTP and ADB support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
KNOWN ISSUES
If you decrypt /data with TWRP, the trustzone thinks this is a failed unlock attempt and will lock the storage for 1d
'adb sideload' doesn't work
DOWNLOAD
Make sure you download the .img.xz and corresponding .asc.txt file (see INTEGRITY)! You can decompress the the recovery image using p7zip or xz.
You can always find the latest version of the recovery under the follwing links:
S10e
S10
S10+
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img.xz and recovery.img.xz.asc.txt file
Rename the recovery.img.xz.asc.txt file to recovery.img.xz.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.xz.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you open your device for malware!​
What a Wurst!
Contributors
modpunk, derf elot
Source Code: https://github.com/whatawurst/android_device_samsung_beyond0lte/tree/twrp-9.0
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-12
Created 2020-03-16
Last Updated 2020-06-12

FAQ
How do boot into the bootloader/download mode?
Here are the steps:
Turn off your phone
Press and hold the volume down and bixby keys
Connect a USB cable attached to your computer
The 'Bixby' button is the button below the volume keys.
How do boot into recovery mode?
Turn off you phone
Press and hold the volume up and bixby and power key
You can also do the above when you reboot the phone, once the screen turn black press the buttons.
How do I reboot my phone?
Press and hold the volume down and power key for at least 7 seconds.
How do I unlock my device?
Not that if you unlock your device, your phone will be factory reset! Make sure to make backups.
To unlock your device:
Go to Settings -> About Phone and find the "Build Number"
Tab the build number several times till it tells you that you unlocked the Deverloper Settings
Go to Settings -> System -> Advanded -> Developer Settings
Enable "OEM Unlock"
Reboot to bootloader mode (see above)
Follow the instruction displayed on screen and unlock your device
How do I flash the recovery?
After you unlocked the bootloader:
Boot into download mode (see above)
Flash recovery.img and vbmeta-disabled.img using Odin or Heimdall.
What is VBMETA?
Your phone has a partition for storing cryptographic hashes to verify the validity of the flashed software to all the partitions on your system. This is called Android Verified Boot.
In order to flash a recovery.img you need to replace the VBMETA image with a custom image to disable the checks. You can find a vbmeta-disabled.img here.

CHANGELOG
2020-07-24
Update to Linux Kernel 4.14.189
Updated to CTF3 blobs
Removed TWRP app
2020-06-09
Update to TWRP 3.4 (Fixes for SAR and multi user decryption)
Update to Linux Kernel 4.14.183
Fixed ADB only mode

Good Job!

ExtremeGrief said:
Good Job!
Click to expand...
Click to collapse
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.

modpunk said:
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.
Click to expand...
Click to collapse
I don't think TWRP supports Samsung FDE.
By the way for S10(+) just change kernel.

Alright so what are the differences between this and the already available twrp by ian?

stefan243546 said:
Alright so what are the differences between this and the already available twrp by ian?
Click to expand...
Click to collapse
See the features list, this recovery has support for FBE decryption on AOSP based ROMs. Also USB is working correctly and not making your phone so hot that you can fry an egg on it.

It should be possible to format /data and use FDE encryption now.

@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.

angela5246 said:
@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
Click to expand...
Click to collapse
Normally, LineageOS sets up FBE by default if the fstab is configured to use FBE. I'm currently working on a LineageOS ROM for the S10e and FBE is working just fine. Normally all you have to to is to format /data. I dunno which ROM you're using and if it has FBE turned on by default.
angela5246 said:
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.
Click to expand...
Click to collapse
Take a look at https://github.com/whatawurst and check the corresponding twrp-9.0 branches (Kernel, platform, device).

I see.
So just for clarification: Do you say FBE should work in theory with LOS or did you try it actually? Let me tell you about my experience.
I came from stock to LOS 17 provided by Ivan. Kept the original fstab which has FBE enabled. Didnt format /data so FBE was kept. After flashing LOS from within TWRP i booted into LOS. All fine. But on the first reboot or shutdown the phone automatically goes to TWRP. And there it stucks at the splash screen. At that point only flashing to stock is helping. So Ianmac's TWRP is not able to handle FBE. Are you sure this is different with yours?

I've added TWRP for more devices.

With the current release MTP isn't working. However I think I have a fix.

Will this twrp work with one ui 2.1?

I dont think so. But the ctc9 sources are up now.

mcgomfer said:
Will this twrp work with one ui 2.1?
Click to expand...
Click to collapse
Why shouldn't it work?

hanspampel said:
I dont think so. But the ctc9 sources are up now.
Click to expand...
Click to collapse
I don't see what the recovery has to do with CTC9 kernel sources at all.

I've uploaded new versions which fixes MTP.

modpunk said:
I've added TWRP for more devices.
Click to expand...
Click to collapse
Can you support Note10+ devices?
Sent from my SM-N975F using Tapatalk

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"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
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp

Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path

kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp

Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!

@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?

You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.

Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?

mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it

end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks

Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well

Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?

Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.

end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!

keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk

how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted

trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...

Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222

Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

Question Is anyone working on building a custom recovery and rom

Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.

gwenmillett said:
Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.
Click to expand...
Click to collapse
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yet
{
"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"
}

JWnSC said:
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yetView attachment 5889613
Click to expand...
Click to collapse
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases

vadizzi said:
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases
Click to expand...
Click to collapse
Tried "fastboot boot twrp.img" blackscreen after logo...
Edit: my mistake it worked

i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse

vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Ohh ok. This phone is a little different from my last one op9p..recovery was inside ramdisk..so usually I would boot twrp.img and flash recovery to ramdisk..
I tried fastboot boot twrp.img..it switched to slot b..so I had to set active back to slot a..my mistake
I'll try your method and report back. Thanks!

vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Yeah it worked! Default language is Chinese

It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.

JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
no i just show it to you. Developer needs i think

vadizzi said:
no i just show it to you. Developer needs i think
Click to expand...
Click to collapse
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?

JWnSC said:
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?
Click to expand...
Click to collapse
I've just been browsing github and don't know any information

JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?

batargin said:
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?
Click to expand...
Click to collapse
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.

JWnSC said:
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.
Click to expand...
Click to collapse
I realized that you are testing, and I just have no one to turn to for help but you. How can I decrypt it? I just got the device today.

6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.

ibestmoder said:
6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.
Click to expand...
Click to collapse
Extract the file to a directory then put your phone in bootloader, connect your phone then go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitions.

[email protected] said:
Extract the file to a directory then put your phone in bootloader, connect your phone the go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitios.
Click to expand...
Click to collapse
I going to buy it from the maker he going do some changing to English with full support

Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)

aaa.bbb111222 said:
Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)
Click to expand...
Click to collapse
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us

ibestmoder said:
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us
Click to expand...
Click to collapse
It's MIUI, there's nothing that could fix that
That's not the point tho. Gonna assume no one yet tried flashing it (so the potential drawbacks not including 30 minutes lifetime are unknown. Should be always possible to remove that from ROM anyway). And we still don't have any way to unbrick, ZTE doesn't want to give us the flash tool for bs reasons.