Develop Bugs

[OFFICIAL][RECOVERY]OrangeFox Recovery Project [R10.1]

OrangeFox Recovery Project
{
"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:
/*
* 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 recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE​
Supports Treble, Miui, Custom Roms
Downloads:
1. OrangeFox download site: https://files.orangefox.tech/OrangeFox-Stable/dipper/
2. SourceForge: https://sourceforge.net/projects/orangefox/files/dipper/
Release Notes:
1. See README.md here: https://sourceforge.net/projects/orangefox/files/dipper/
2. Read very carefully the contents of post #2 below.
Documentation and Frequently Asked Questions: https://wiki.orangefox.tech/en/guides
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Download the OrangeFox zip file to your device
2. Reboot to your current OrangeFox or custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
Frequently Asked Questions; Installation from stock recovery; MIUI OTA; Troubleshooting; Sundry Information:
* See https://wiki.orangefox.tech/en/guides
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots
see https://files.orangefox.tech/Screenshots/R10/
Other useful information - see below
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Mi 8
Contributors
DarthJabba9, MrYacha
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Stable Version: R10.1
Stable Release Date: 2020-04-08
Created 2020-01-23
Last Updated 2020-04-08

R10.0_1_001 Beta released
I have released OrangeFox R10.1 Beta 001.
Downloads:
OrangeFox download site: https://files.orangefox.tech/OrangeFox-Beta/dipper/
Sourceforge: https://sourceforge.net/projects/orangefox/files/dipper/
Changelog (General for R10.1): https://wiki.orangefox.tech/en/changelog#orangefox-r101
Device-specific changes:
- Fixed language translations
- Updated the initd addon to use Anykernel3 (better support for system-as-root devices)
FAQ and Guides: https://wiki.orangefox.tech/en/guides
Backup and restore
Read this post for detailed advice. Do not try to backup/restore anything without first reading it.
Incremental MIUI OTA:
Due to recent changes in stock MIUI, you must not disable DM-Verity when flashing a stock MIUI ROM that is based on either Android Pie, or Android 10 (the relevant option in OrangeFox is now unticked by default). If you disable DM-Verity, incremental MIUI OTA updates will definitely not work.

Reserved

Thank you. Does it allow you to bakcup and restore the persist partition?

Boiisxu said:
Thank you. Does it allow you to bakcup and restore the persist partition?
Click to expand...
Click to collapse
Yes.

DarthJabba9 said:
Yes.
Click to expand...
Click to collapse
I'll try it, thank you.

Nice work mate. But can it flash persist.img directly from the menu? Thanks!

JonathanFreeze said:
Nice work mate. But can it flash persist.img directly from the menu? Thanks!
Click to expand...
Click to collapse
Should be fine.

I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.

Xiaomi063 said:
I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.
Click to expand...
Click to collapse
How did you flash from fastboot? You extracted the image file from the zip?

Xiaomi063 said:
I have Orangefox R10.0-3, and I cannot install R10.0-4 or the new beta R10.1. I tried both flashing from bootloader with fastboot commands (recovery.img) and installing the R10.1 beta zip from Orangefox R10.0-3. Phone won't boot to recovery and will just reboot to android. I have install.log but have less than 10 posts and have no idea how to attach files. I'll PM you with the log.
Click to expand...
Click to collapse
The log that you sent to me by PM looks perfectly fine, and everything should work.
Judging from what you said in the other thread where you first explained your problems, I think that something is seriously broken in your device. It may be that your bootloader has been modified by something you flashed before. In the previous thread, you describe the current situation. But what you have not told us is exactly how you got here in the first place. Without that information, one can only speculate. And my speculation is that the recoveries (whether flashed in fastboot or recovery mode) install correctly. However, something in the modified bootloader is ignoring them (or perhaps your partition sizes are borked). If this speculation is correct, then I think you might have to flash a full fastboot MIUI ROM (of whatever ROM came with the phone in the first place) and let it wipe everything (just don't accidentally lock your bootloader again). This should reset the partitions and also replace the recovery partition with stock MIUI recovery. Then you can start all over again by flashing an OrangeFox img with fastboot.
But unless you can retrace all your steps to identify what you originally flashed that started all these problems (and avoid it in the future) you might well end up in the same situation again.

DarthJabba9 said:
The log that you sent to me by PM looks perfectly fine, and everything should work.
Judging from what you said in the other thread where you first explained your problems, I think that something is seriously broken in your device. It may be that your bootloader has been modified by something you flashed before. In the previous thread, you describe the current situation. But what you have not told us is exactly how you got here in the first place. Without that information, one can only speculate. And my speculation is that the recoveries (whether flashed in fastboot or recovery mode) install correctly. However, something in the modified bootloader is ignoring them (or perhaps your partition sizes are borked). If this speculation is correct, then I think you might have to flash a full fastboot MIUI ROM (of whatever ROM came with the phone in the first place) and let it wipe everything (just don't accidentally lock your bootloader again). This should reset the partitions and also replace the recovery partition with stock MIUI recovery. Then you can start all over again by flashing an OrangeFox img with fastboot.
But unless you can retrace all your steps to identify what you originally flashed that started all these problems (and avoid it in the future) you might well end up in the same situation again.
Click to expand...
Click to collapse
I bought this phone second hand, it already had bootloader unlocked and came with TWRP wzsx150 installed. It had MIUI 11 global, not sure the exact version (11.0.1, 11.0.2...) but it was android 9, and the same day I got it I installed the latest xiaomi.eu beta rom on it, before trying to install other custom roms or installing another recovery.
I already tried flashing full fastboot MIUI Global rom using fastboot with MiFlash software, tried two versions: 11.0.6.0 and 10.1.2.0. When doing that the same happens, MIUI works correctly and I can install xiaomi.eu roms but not any other custom rom and only a reduced number of recovery versions.
Is there anything more I should check? like partition format or partition size? should I format all partitions?
I used MiFlash 20180528, not the latest version, don't know if this could affect the flashing process...

Xiaomi063 said:
I bought this phone second hand, it already had bootloader unlocked and came with TWRP wzsx150 installed. It had MIUI 11 global, not sure the exact version (11.0.1, 11.0.2...) but it was android 9, and the same day I got it I installed the latest xiaomi.eu beta rom on it, before trying to install other custom roms or installing another recovery....
Click to expand...
Click to collapse
Flashing a full fastboot ROM with the Mi Flash tool should have sorted out any problems. That is normally a last resort, and it should work. If it didn't work, then I am out of ideas. This might well be some sort of ARB issue - but I have no experience at all with ARB, so I can't tell. Perhaps it was already broken before it was sold to you. Who knows?
I know of no reason why the device should be happy with some recoveries, and not with others. There is no logic to it, that I can see.
Unfortunately, this discussion is now off-topic, as this is not a recovery issue (I thought it might have been - but it is obvious that it isn't). I guess you might have to cut your losses and stick with whatever recoveries and ROMs work with your device - and perhaps return to wzsx150 and the most recent MIUI Global (which would avoid ARD issues). Good luck!

I flashed the last stable version and it works flawlessly. I love that it flashes dfe automatically.
However, I don't know If I can use my old backups made by the twrp i was using, can I?
Thanks you!

Boiisxu said:
.... However, I don't know If I can use my old backups made by the twrp i was using, can I?
Click to expand...
Click to collapse
You can always try - but I wouldn't hold out much hope. It all depends on whether the partition tables are compatible. Also, OrangeFox expects its backups to be in /Fox/BACKUPS/ whereas twrp looks somewhere else - so there has to be some renamings of directories if OrangeFox is to be able to locate the backups.

Does the latest beta support encryption?
I am using xiaomi.eu ROM

Irish_Dude said:
Does the latest beta support encryption?...
Click to expand...
Click to collapse
Yes.

Many thanks for keeping OF for Mi8 dude
This is the best recovery so far imho

Adriano-A3 said:
Many thanks for keeping OF for Mi8 dude
This is the best recovery so far imho
Click to expand...
Click to collapse
Yeah it takes so much headache out of flashing that is unparalleled

arifqur said:
Yeah it takes so much headache out of flashing that is unparalleled
Click to expand...
Click to collapse
Thanks (also to @Adriano-A3).
The question now is whether the last beta is robust enough to turn it into a "Stable" release ...

[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.

PBRP [Joyeuse][v2.9.1]

{
"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.
Based on TWRP version: 3.4.0
PitchBlack version: 2.9.1
For device: Redmi Note 9 Pro
Maintainer/Authors build: https://forum.xda-developers.com/member.php?u=8529431
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel Source: https://github.com/Joyeuse-Indonesia-Project/kernel_xiaomi_sm6250
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
Code:
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Fix Dynamic Partition
- Improper mount of /data partition
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/uc?id=1HiPbEimxTiZlAXmjgVzf69bB_knn4H1E&export=dow nload

GREAT JOB!

Works on curtana? thanks

zenez said:
Works on curtana? thanks
Click to expand...
Click to collapse
onlye Joyeuse, in curtana you already have twrp and others.

All right, will try later. ?

Yuluga said:
onlye Joyeuse, in curtana you already have twrp and others.
Click to expand...
Click to collapse
Yes but this one is said dealing with dynamic partition. A must have.
Is it planned to have a release devoted to Curtana.
Thanks
EDIT:
I've just tested it on Curtana in order to test file copy/modify in system via file explorer.
Unsuccessful trial. System is still kept at read only state.
Anyway a real nice interface design. Thanks to devs.

any one test it? any bug?

hoang_phuong84 said:
any one test it? any bug?
Click to expand...
Click to collapse
It is working from what I can do on a Curtana. It cann't install because digest is not in accordance but should be working well on Joyeuse and at any point better than LR modded fix release available at T.me.
Just boot it on your phone and try it like that.

Recoveries struggle to get stable on this device/system it seems (what is the status of PBRP: alpha, beta, stable?). I saw something about a Android 10 Boot Partition causing the problems but would like to understand better if and how Recovery will work nicely with this device and Custom ROMs. Can someone point me to a explanation/thread why on RN9P, Android 10 it is so difficult to get a working Recovery for Custom ROM Install/Updates?

hello,
bravo for this excellent work, since the time we hoped functional custom recovery. Are all backup and restore functions functional, micro sd recognition, etc? ... Thank you

the right commend for Flash the recovery.img is "fastboot flash recovery recovery.img"
second, i get decrypt data after i reboot to recovery.

I have curtana twrp on joyeuse phone. Can ı flash via curtana twrp?
Edit 1: I tried install via curtana twrp. Error 1 fail...

Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.

fathroen said:
Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.
Click to expand...
Click to collapse
I've tried too but the same result.
"Fixed it" with fastboot first time installation of v11.0.4 and will wait for fastboot package v11.0.5.

After flashing recovery, and entering to PBRP is asking for password for decrypt data, i do not have password, my phone is not encrypted

fathroen said:
Anybody try to flash latest Redmi Note 9 Pro EU ROM (v11.0.5.0) with this recovery? I tried dirty flash it from 11.0.4 and got error message. After flashing, It stay and boot on 11.0.4 but lost wifi mac address.
Click to expand...
Click to collapse
Are you referring to the xiaomi.eu rom v11.0.5? If so, there's alot of people reporting problems booting after flashing that version. You're probably not referring to the stock rom, as I don't think there are any recovery flashable zips for that available.
In regard to fixing your wifi problem, in reading through the GSI rom thread, there are many reports of wifi being lost after flashing the boot.img from a different version of the stock rom than that which users were originally on without updating the other partitions. If the v11.0.5 boot.img was flashed to your phone, but some other partitions failed to flash, that may explain things. You could try downloading/extracting the v11.0.4 boot.img, either from the stock or xiaomi.eu rom package depending on which you are using, and flashing that again from fastboot using "fastboot flash boot boot.img".
Otherwise if that fails, reflashing v11.0.4 in its entirety should hopefully get your wifi working again.

mariob098 said:
After flashing recovery, and entering to PBRP is asking for password for decrypt data, i do not have password, my phone is not encrypted
Click to expand...
Click to collapse
Same issue here

You'll have to use the password/pass number you used to unlocked your device when waking it up.

blowy666 said:
You'll have to use the password/pass number you used to unlocked your device when waking it up.
Click to expand...
Click to collapse
But i do not have lock screen pin/password

thanks
Sent from my Redmi Note 9 Pro using Tapatalk

[RECOVERY][TREBLE][UNOFFICIAL] TWRP 3.5.2 for NB1

{
"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:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a full 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.
TWRP built for the Nokia 8. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
Installation
If you are installing TWRP for the first time, then you need to flash it from fastboot:
Code:
fastboot flash:raw boot <twrp.img>
Otherwise you can install the latest release by flashing the appropriate .zip file
Downloads
Treble: Releases · resident-nokia/android_device_nokia_A1N-TWRP (github.com)
Stock: Releases · resident-nokia/android_device_nokia_NB1-TWRP (github.com)
Contributors
THMSP, emufan4568
Sources:
Treble: https://github.com/GPUCode/twrp resident-nokia/android_device_nokia_A1N-TWRP: TWRP tree for Nokia 8 Sirocco / Treble (github.com)
Stock: resident-nokia/android_device_nokia_NB1-TWRP: TWRP tree for Nokia 8 Stock (github.com)
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-11-07
Last Updated 2021-04-10

New build is up!
* TWRP is based on the twrp-10.0 branch now
* Decyption blobs have been updated to android 10
* Decryption works with and without screen lock (pattern, pin. password)

New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing

emufan4568 said:
New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing
Click to expand...
Click to collapse
Treble, and ota updates? Enlighten me here.
Back to stock, that's a huge fix. But oh, we can't install it on stock. So... What's going on?!

Arashone said:
Treble, and ota updates? Enlighten me here.
Back to stock, that's a huge fix. But oh, we can't install it on stock. So... What's going on?!
Click to expand...
Click to collapse
By OTA updates I mean my crDroid releases. In the past, flashing the .zip from TWRP would fail at step 2. Now you do not have to wipe data and reflash T-Virus every time you need to update to any new crDroid release

emufan4568 said:
By OTA updates I mean my crDroid releases. In the past, flashing the .zip from TWRP would fail at step 2. Now you do not have to wipe data and reflash T-Virus every time you need to update to any new crDroid release
Click to expand...
Click to collapse
Great
Is it possible for stock version too?

Arashone said:
Great
Is it possible for stock version too?
Click to expand...
Click to collapse
Yes it is. I just need to replace the kernel with a non-treble one and remove the vendor partition references. But why would you need a stock version anyway? There are no custom ROMs for stock to flash

emufan4568 said:
Yes it is. I just need to replace the kernel with a non-treble one and remove the vendor partition references. But why would you need a stock version anyway? There are no custom ROMs for stock to flash
Click to expand...
Click to collapse
There are ota updates for stock official ROM. Many people have let's say 488b and want to stick to latest version of oreo. TWRP 3.3.1 can't do that, and fails at stage 2 of flashing offline ota.
Btw, this new xda is God fast... Kisses to the Prophets!

Arashone said:
There are ota updates for stock official ROM. Many people have let's say 488b and want to stick to latest version of oreo. TWRP 3.3.1 can't do that, and fails at stage 2 of flashing offline ota.
Btw, this new xda is God fast... Kisses to the Prophets!
Click to expand...
Click to collapse
Stock TWRP has this issue too. It is caused by listing non-existant partitions in gpt-utils https://github.com/resident-nokia/t...d3df561fb6/recovery/gpt-utils/gpt-utils.h#L82 When installing an OTA TWRP tries to switch slot but it fails because it is not possible to switch slot on a partition that does not exist. This issue was fixed by this commit https://github.com/GPUCode/android_...mmit/179c5de56987455ca10e424ab1eaa00dd882228d and now it lists all the correct partitions and TWRP no longer fails when installing updates. I agree, XDA feels more like modern website rather than a 2005 forum

emufan4568 said:
Stock TWRP has this issue too. It is caused by listing non-existant partitions in gpt-utils https://github.com/resident-nokia/t...d3df561fb6/recovery/gpt-utils/gpt-utils.h#L82 When installing an OTA TWRP tries to switch slot but it fails because it is not possible to switch slot on a partition that does not exist. This issue was fixed by this commit https://github.com/GPUCode/android_...mmit/179c5de56987455ca10e424ab1eaa00dd882228d and now it lists all the correct partitions and TWRP no longer fails when installing updates. I agree, XDA feels more like modern website rather than a 2005 forum
Click to expand...
Click to collapse
Is this issue fixed in TWRP 3.3.1 too (which is used for stock firmwares)? That was my question. 'cause the last (recent) time I used it, no such change was apparent. Also, restoring bku was impossible, although I'm not sure about it.
The change here, paves the way of using Q on our lady.

New build is up! Download from here: https://github.com/resident-nokia/android_device_nokia_A1N-TWRP/releases/tag/v3.5.2
Updated TWRP to version 3.5.2
Up-to-date umbrella kernel
Updated decryption blobs to Q
Use common FBE TWRP decryption strategy (should fix most issues with decryption)

emufan4568 said:
New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1_TWRP/releases/tag/twrp-3.4.0-0-2-2
* Allow wiping of System partition
* Fixed OTA updates failing at Step 2 of flashing
Click to expand...
Click to collapse
now phone stuck at teamwin logo

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or 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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* 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.
Supported Models:
Galaxy S10 G9730, G973U, G973U1 and G973W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10: beyond1qlte.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
31.12.2020 - Update TWRP to 3.5.0
14.11.2020 - Initial Release

Seems to be working properly! Thank you!

wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!

robocopvn said:
wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!
Click to expand...
Click to collapse
It isn't free, but yes. Mine is and rooted. Verizon variant here.

abranson said:
It isn't free, but yes. Mine is and rooted. Verizon variant here.
Click to expand...
Click to collapse
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.

superturtlr19 said:
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.
Click to expand...
Click to collapse
I had to pay and had it done remotely. Sampwnd. . Google it

abranson said:
I had to pay and had it done remotely. Sampwnd. . Google it
Click to expand...
Click to collapse
Oh wow, these are pricey. Well thank you for your time.

Deleted

afaneh92 said:
Note: download link is down, will make new build tomorrow then will fix the link. Please do not share older builds.
Edit: new builds are up, US devices are not supported anymore, only devices already unlocked before 9 November are.
Click to expand...
Click to collapse
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it

illspiritX said:
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it
Click to expand...
Click to collapse
Read notes on OP

afaneh92 said:
Read notes on OP
Click to expand...
Click to collapse
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?

abranson said:
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?
Click to expand...
Click to collapse
Will contact you on telegram

Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?

fabiokino said:
Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?
Click to expand...
Click to collapse
To encrypted the the data partition again need to do factory reset from stock recovery.

afaneh92 said:
To encrypted the the data partition again need to do factory reset from stock recovery.
Click to expand...
Click to collapse
Thank you for the answer. My idea was to make a TWRP image once I completely personalized the system and then encrypt the device, but I understand that it's not possible...
So the alternative solution is to find a way yo make an image of the encrypted device after the personalization...
Is there a way to make an image of the encrypted data partition apart from using dd? Since it is encrypted with fbe I was wondering if there's a method which doesn't require to save the whole partition but only the actual (encrypted) files.

Changelog:
16.02.2021 - Initial R build for Android 11

Does anyone with a SM-G9730 wanna try a US rom I made for it?

how to disable AVB in s10 9730?

jrkruse said:
Does anyone with a SM-G9730 wanna try a US rom I made for it?
Click to expand...
Click to collapse
9730 module can flash us version? I wanna try