Develop Bugs

[RECOVERY][Unofficial][amami] TWRP 3.4.0

Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22

Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release

Reserved

Backup to microSD seems to be working fine (haven't restored anything yet):good:

I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0

115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!

bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).

115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.

bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.

I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:

Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?

Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)

@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.

tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).

115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now

Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?

tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.

115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.

New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.

tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.

[RECOVERY][3.4.0-2][hotdog]Unofficial TWRP recovery for OnePlus 7T Pro Unified(Test)

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:
#include <std_disclaimer.h>
/*
*
* We are 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.
*
*/
Features:
- TWRP boots;
- Fastboot boot is working;
- Decryption is working (except for Oxygen OS);
- System, Vendor and Product partitions mount is not working but it's not a big problem;
- You can flash ROMs;
- Format Data is broken;
- You can flash magisk
Install guide (Reccomended):
Acutally seems oneplus (or directly android 10) re-introduced the recovery partition so you should only flash it in recovery partition or you can try to boot it from fastboot. For now only boot it.
To flash:
Code:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Tips:
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-2 Test by mauronofrio
TWRP 3.4.0-0 Test by mauronofrio
TWRP 3.3.1-43 Test by mauronofrio
TWRP 3.3.1-25 Test by mauronofrio
TWRP 3.3.1-5 Test by mauronofrio
OnePlus 7T Pro Stock Recovery
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_hotdog_unified_TWRP
Kernel source: precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
I want to say a big thanks to the testers @houmles and @ChrisFeiveel84
Created 2019-10-23

Well this completley messed up my phone somehow. First of all, i was not able to install twrp only boot it, but only once, after the first boot i always get an error in fastboot. Secondly i wasnt able to mount /system for example. Cant recommend it right now. @dev Do you have the stock recovery image somewhere and could upload it please?

fritzcola said:
Well this completley messed up my phone somehow. First of all, i was not able to install twrp only boot it, but only once, after the first boot i always get an error in fastboot. Secondly i wasnt able to mount /system for example. Cant recommend it right now. @dev Do you have the stock recovery image somewhere and could upload it please?
Click to expand...
Click to collapse
I'm looking for a stock from where extract it, i think in the night i will be able to extract it

Thanks to Dev for starting work on a TWRP for the OP7T Pro...
Tried the -5 version (only boot from fastboot) and for me it worked fine and also didn't ruin anything on the system.
I had the hope to be able to at least access /data in the filemanager to delete a woesome Magisk extension, but sadly /Data wasn't mounted and also could not be mounted manually. Btw I'm encrypted, but normally I should at least be able to see the folder with garbled names
@dev: should you see a way how I could help in improving TWRP just let me know

Thank you developer for work on this device from this early stage

fastboot boot -> Ok
backup stock boot -> Ok
Patch boot with Magisk Manager -> Ok
Thank

i keep getting this error when trying to do it on my 1+ 7t pro mclaren (remote: Failed to load/authenticate boot image: Load Error)

speedihb2k15 said:
i keep getting this error when trying to do it on my 1+ 7t pro mclaren (remote: Failed to load/authenticate boot image: Load Error)
Click to expand...
Click to collapse
I had the same error. Try to fastboot patched img from here or stock boot img, than try this TWRP after reboot again.

Does the back function working i just want to backup my McLaren edition goodies so i am worried about that

Can mount system partición?
Enviado desde mi GM1913 mediante Tapatalk

liver20 said:
Can mount system partición?
Enviado desde mi GM1913 mediante Tapatalk
Click to expand...
Click to collapse
No. This is also stated in the first post.
Sent from my OnePlus7TPro using XDA Labs

Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.

vtec303 said:
Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.
Click to expand...
Click to collapse
Doesn't matter if decrypted to not, TWRP is not functional on devices launched with Android 10.
Sent from my OnePlus7TPro using XDA Labs

Can i use the boot only option on my 7t pro mclaren(rooted) to flash a new kernel? Or is this only for testing?

Goku1992 said:
Can i use the boot only option on my 7t pro mclaren(rooted) to flash a new kernel? Or is this only for testing?
Click to expand...
Click to collapse
Use ex kernel manger to flash kernels no need for twrp ?

hi this twrp work to flash magisk with the mclaren version?

izimen said:
hi this twrp work to flash magisk with the mclaren version?
Click to expand...
Click to collapse
Search the thread and you'll find your answer.
Hint: 3 posts above yours.
Sent from my OnePlus7TPro using XDA Labs

ok thank you

Hi guys, i'm looking for some testers for the TWRP, if you want to join in the test group write me on telegram, the nickname is the same

vtec303 said:
Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.
Click to expand...
Click to collapse
Hi. How did you manage to decrypt this device? I cannot find a way to do it permanently. Thanks.

[RECOVERY][3.6.2_9][kmini3g] TWRP Recovery

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:
#include <std_disclaimer.h>
/*
*
* We are 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.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn't supported, so don't set the secure boot or put a password at the boot of the device
Download
kmini3g (SM-G800H): https://www.androidfilehost.com/?w=files&flid=319793 - mirror: https://t.me/tab4los
Source code
kmini3g: https://github.com/matteo0026/android_device_samsung_kmini3g
Kernel: https://github.com/matteo0026/android_kernel_samsung_msm8226
Contributors
matteo0026, isbon

Works great, thanks!

New build (-2) is out.
Changelog:
- Minor TWRP source changes (either recovery and device tree)
- Slightly reduced size of the package

New TWRP 3.5.0_9-0 is out.
Changelog:
- All TWRP 3.5.0_9 changes and improvements
- Some changes done in device tree to make it ordered and with less junk
- Persist and firmware (modem) partitions aren't backupable anymore. Firmware partition backup/restore/wipe with vfat partition makes network issues, and with emmc backups are useless since can't be restored successfully, and this "filesystem" isn't wipeable. Persist partition doesn't need any backups/wipes/restores, and if someone has some particular issues, it's always better to go to latest stock firmware, better with pit file too. I don't want to support anymore something that is half working.
- Try to fix time even in backups

Hi guys, new TWRP 3.5.0_9-1 is out!
Changelog:
- Get back persist partition backup, since it can be important to backed up, sometimes.
- Reintroduce su

New TWRP 3.5.1_9-0 is out!
Changelog:
- Changes coming from 3.5.1 version

New TWRP 3.5.2_9-0 is out!
Changelog:
- Changes coming from 3.5.2 version

Hi guys, new builds of TWRP are up. You can find the changelog of the TWRP 3.6.0 here: https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html

TWRP 3.6.2_9-0 for kmini3g is out!
Changelog:
- https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
- https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html

matteo0026 said:
TWRP 3.6.2_9-0 for kmini3g is out!
Click to expand...
Click to collapse
Where is it?

i5510 said:
Where is it?
Click to expand...
Click to collapse
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section

matteo0026 said:
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section
Click to expand...
Click to collapse
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?

i5510 said:
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?
Click to expand...
Click to collapse
Yesterday I've added on rush the link in the first post, and then I just forgot to upload them in AFH. Now they are uploaded on AFH too, hoping that it works fine.

Thank you.

Hi,
How do i know if my device has Encryption with password enabled ? I have a 800F here and would like to flash TWP.
Thanks in advance.

[TREBLE][ROM][GUIDE][10.0] MIUI 12 OneOS Stable for J730X (No Laggy) (Sim working)

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.
I own nothing in these. roms, kernels, gsis. All credits down below.
--------------------------------------
Supported devices:
J730*/J530*/G610*/J710*/J701*
Instructions
Make sure you have latest TWRP or OrangeFox (i recommend OrangeFox)
Download and flash ProjectSpagetX (first flash Create Vendor 2.0, reboot recovery and flash ProjectSpagetX)
Download OneOSMi8Lite-Aonly-10-20201203-nippongsi.img (downloaded file is "gz" you need to extract img file) flash as "system" image.
Download and flash Cronos Kernel 5.0 (cronos kernel more stable in MIUI than other kernels) "i tested it a lot weeks"
Now you can reboot system... but you cant login google services because this is MIUI Global Rom
--------------------------------------
TO FIX CANT LOGIN GOOGLE SERVICES;
Now you opening play store and you clicking Sign in... But nothing happens.. Now
Now first download the Google Play Services
And Gmail. Install two of them.
And reboot now open Gmail and login your account easily!
--------------------------------------
How to Root?;
Flash Magisk canary and reboot system (now system will gets infinite boot)
Make hard reboot (volume down + power)
And enter recovery, Flash magisk canary again, reboot and system seccussfully boots.
--------------------------------------
Bugs;
You cant control brightness
Phone stucks when you use Stock MIUI Camera's mods (use footej for no stuck)
if you found a bug reply down below to let other people know.
Whats working;
You can login Mi account
Rom is smooth
Sim card working
OneOS Settings working
Themes working have good themes by OneOS
Phone not crash (if you using another kernel system will crash's sometimes)
I passed CTS Profile on magisk
--------------------------------------
CREDITS
Project Spaget - Cronos Kernel by @ananjaser1211
MIUI 12 OneOS GSI by nippongsi

My main language is not English sorry for wrong words.

Auto reboot and why have a pattern key..sorry for my bad english

https://sourceforge.net/projects/amber-gsi/files/Nusantara-11/Nusantara_v2.5-11-arm64-ab-Vanilla.img.xz/download

stuck on boot anim at samsung galaxy j7 pro

ilyas UG said:
https://sourceforge.net/projects/amber-gsi/files/Nusantara-11/Nusantara_v2.5-11-arm64-ab-Vanilla.img.xz/download
Click to expand...
Click to collapse
me stuck boot logo

ilyas UG said:
https://sourceforge.net/projects/amber-gsi/files/Nusantara-11/Nusantara_v2.5-11-arm64-ab-Vanilla.img.xz/download
Click to expand...
Click to collapse
A/B GSI's cant work with Project Spaget.

can I use screen lock?

Saitoh Michio said:
can I use screen lock?
Click to expand...
Click to collapse
No, Miui forces to fingerprint lock.

cant flash nippongsi, file too big for the system

leecherleechleech said:
cant flash nippongsi, file too big for the system
Click to expand...
Click to collapse
repartitioner

Türkçe olarak da anlatabilir misin?

hello can i get rom for samsung galaxy J7 Device j7y17lte.

Xander11 said:
hello can i get rom for samsung galaxy J7 Device j7y17lte.
Click to expand...
Click to collapse
Yes

ichbinahmet said:
Yes
Click to expand...
Click to collapse
can i get links pls

Xander11 said:
can i get links pls
Click to expand...
Click to collapse
Links on Instructions panel

ichbinahmet said:
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.
I own nothing in these. roms, kernels, gsis. All credits down below.
--------------------------------------
Supported devices:
J730*/J530*/G610*/J710*/J701*
Instructions
Make sure you have latest TWRP or OrangeFox (i recommend OrangeFox)
Download and flash ProjectSpagetX (first flash Create Vendor 2.0, reboot recovery and flash ProjectSpagetX)
Download OneOSMi8Lite-Aonly-10-20201203-nippongsi.img (downloaded file is "gz" you need to extract img file) flash as "system" image.
Download and flash Cronos Kernel 5.0 (cronos kernel more stable in MIUI than other kernels) "i tested it a lot weeks"
Now you can reboot system... but you cant login google services because this is MIUI Global Rom
--------------------------------------
TO FIX CANT LOGIN GOOGLE SERVICES;
Now you opening play store and you clicking Sign in... But nothing happens.. Now
Now first download the Google Play Services
And Gmail. Install two of them.
And reboot now open Gmail and login your account easily!
--------------------------------------
How to Root?;
Flash Magisk canary and reboot system (now system will gets infinite boot)
Make hard reboot (volume down + power)
And enter recovery, Flash magisk canary again, reboot and system seccussfully boots.
--------------------------------------
Bugs;
You cant control brightness
Phone stucks when you use Stock MIUI Camera's mods (use footej for no stuck)
if you found a bug reply down below to let other people know.
Whats working;
You can login Mi account
Rom is smooth
Sim card working
OneOS Settings working
Themes working have good themes by OneOS
Phone not crash (if you using another kernel system will crash's sometimes)
I passed CTS Profile on magisk
--------------------------------------
CREDITS
Project Spaget - Cronos Kernel by @ananjaser1211
MIUI 12 OneOS GSI by nippongsi
Click to expand...
Click to collapse
I've tried according to the steps above but the result is also a bootloop.
already created vendor, install projectspaget_v3, install OneOSMi8lite-Aonly-.IMG > Install System Image, Install CronosKernel_V5 the result is the same but my bootloop is using j730g/ds.
There is another solution so I can use the rom, what if you do a full backup via twrp OneOSMiLite8-Aonly so we can just restore via twrp.

Melisata said:
I've tried according to the steps above but the result is also a bootloop.
already created vendor, install projectspaget_v3, install OneOSMi8lite-Aonly-.IMG > Install System Image, Install CronosKernel_V5 the result is the same but my bootloop is using j730g/ds.
There is another solution so I can use the rom, what if you do a full backup via twrp OneOSMiLite8-Aonly so we can just restore via twrp.
Click to expand...
Click to collapse
no spaget v3, you should use spaget X

sim not working fo me!

Led light work in j7 prime?

Development [UNOFFICIAL][RECOVERY][12][CAPRIP] OrangeFox Recovery Project

OrangeFox Recovery​
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.
*
*
INSTALLATION:
1. Back up your important data
2. Boot image with "fastboot boot path/to/image"
3. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
4. Install flashable zip
5. Enjoy!
Credits
* TeamWin - for TWRP Recovery
* The OrangeFox Team - for your hard work
* To all testers for their time and patience
* @TheRealDarkness for build OrangeFox
* @ThE_MarD for TWRP sources
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Password, torch, led
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* And many more!
Screenshots: https://telegra.ph/OrangeFox-Recovery-Project--Moto-g30caprip-12-22
Source Code: https://gitlab.com/OrangeFox
Download recovery: https://sourceforge.net/projects/caprip/files/OFOX/
REPORTING BUGS!
* You tell me
* You have to wait 10-20 seconds for the touch to work, (recovery was tested on caprip with ilitek and Novatek touchscreen)

could you enable data decryption for android 12, or it impossible?
even once I disabled screen lock entirely, I can't "decrypt /data" for some reason, which severely limits the entire point of custom recoveries
(running via fastboot boot, not permanent install, but shouldn't make a difference)
otherwise it looks pretty cool!

jan6 said:
could you enable data decryption for android 12, or it impossible?
even once I disabled screen lock entirely, I can't "decrypt /data" for some reason, which severely limits the entire point of custom recoveries
(running via fastboot boot, not permanent install, but shouldn't make a difference)
otherwise it looks pretty cool!
Click to expand...
Click to collapse
did you boot recovery?
I can make a guide on how to decrypt data on this device, it's really easy to do it, in the Moto G³⁰ group in BR we have two methods to do it.
Although since the recovery is based on TWRP 3.7.0-12-0 it should decrypt itself )))

why else would I write here if I didn't boot into this orangefox, lol
I did
Code:
adb reboot bootloader
fastboot boot OrangeFox-R11.1_0-Unofficial-caprip.img
it's the same as with twrp, more or less, /data is locked, and mounting of /data is required for like half the functionality, and nandroid backups are most of the point of a custom recovery
from what I've heard twrp SHOULD be able to decrypt android 11 and 12, idk why it doesn't work for me with neither twrp nor orangefox (which even has a nicer pin entry box for decryption), even if I remove screen lock entirely, it can't do it... (I'm running android 12)

jan6 said:
why else would I write here if I didn't boot into this orangefox, lol
I did
Code:
adb reboot bootloader
fastboot boot OrangeFox-R11.1_0-Unofficial-caprip.img
it's the same as with twrp, more or less, /data is locked, and mounting of /data is required for like half the functionality, and nandroid backups are most of the point of a custom recovery
from what I've heard twrp SHOULD be able to decrypt android 11 and 12, idk why it doesn't work for me with neither twrp nor orangefox (which even has a nicer pin entry box for decryption), even if I remove screen lock entirely, it can't do it... (I'm running android 12)
Click to expand...
Click to collapse
With the attached file you can easily decrypt, just follow these steps:
1° Format data
2° Flash zip attached
3° Format data and reboot
After that the storage should be free of encryption.
Or you can use another method, if you use my rom you will know that all the partitions are in read-write, being able to modify anything, including the vendor. Another exp would be:
With the other attachment "fstab.zip"
You can do the download, then unzip "fstab.zip", it will leave a file called "fstab.qcom", with it you go to the vendor and mount it as RW, then follow the path "/vendor/etc" and copy fstab.qcom, then you do a reboot and the storage would be decrypted.