Database Develop

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.

alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery

Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.

But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.

Can someone else confirm that it always reboot to recovery even after re-installing a rom?

Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium

no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally

Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?

Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.

Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.

First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.

Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom

Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?

Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .

not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery

Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.

You di not ask the right question:
Does this work for someone , anyone please confirm.

[Recovery] [V3.0-006] Red Wolf 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"
}
/* Your warranty is now void! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the flashlight 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 me for messing up your device, I will laugh at you. */
Click to expand...
Click to collapse
Introduction
Red Wolf Recovery is alternatovní recovery based on the source code TWRP.
The main objective of the Red Wolf Recovery is to provide the features that were for some reasonrefusedto add to the official source code Winu Team (besides the maximum utilization of hardware options that device ...).
Hence Recovery supports password protection, since Team Win rejected this method of security because users generally do not read any kind of warning, then it was just a mistake on the part of Team Winu that somebody got into the facility despite a recovery password protected.
For this reason, therefore, I warn that the red wolf is secured in such a way that nobody could get into recovery without the user's password, but no recovery willnot safeguardagainst reinstall the device via Flash or Mi fastboot. So please take a note!
Acknowledgments:
Ray Li: For his help in modifying the source code TWRP.
osm0sis: In the video below scripts which also runs most of the functions recovery.
z31s1g: For the base material. theme.
And all the other developers of the various scripts and installation files as Chanfire,topjohnwu,cofface,etc
Features recovery:
- Brightness can be reduced to a minimum fair value. (TWRP only supports a minimum of 10% Brightness).
- Support for more than 50 sections (including "subsections").
- Possibility of installation of paintings in section Modem and Boot Logos.
- Adjusted ADB - for security reasons already does not start automatically at boot recovery, but now it turns in the recovery
- Recovery allows you to set and remove a password
- Torch phone is now going to turn right in Recovery
- Automatically Block stock recovery
- Recovery contains settings regarding Governor where recovery is currently running. If, therefore, not in a hurry, so just switch to performance and processes such as backup, restore or installation will be up almost 20% faster.
- When you confirm the installation file on the screen appears and warnings checkbox for the finished installation. This recovery will automatically notify the completed installation using the notification LED.
- For safety reasons deactivated TWRP theme engine.
- Official TWRP application was replaced for Snap Camera HDR.
- Access to the folder with zálohama and setting recovery is blocked. Access to these files is only possible from the recovery. (This is only an internal storage)
- The first recovery that is built on OMNI ROM code purely for Kate.
- Folder screenshotama of recovery has been moved to /sdcard/WOLF.res to already screenshots of recovery are not confused with the other screenshotama ..
- Updated Czech translation - Slovak translation can be translated from the strings provided below.
- new terminal supports three commands: unpackbootimg, mkbootimg and zipper (so they may also be retrieved from the script, of course).
- Recovery supports Tap To Wake Engine (dt2w is not supported yet ...)
- Support for "night mode".
- Built AromaFM supports Czech language.
- User can set custom name for the folder backup & ID at the ADB.
- Create backup can also be erased at once (not therefore been deleted one by one as it is in ofiko TWRP).
- Recovery is assembled on AOSP 7.1.2 / TWRP 3.1.1-0 / Omni 7.1.2.
Built-in installation files:
Supers
Magisk
Nitrogen UNROOT
substrates Rescue
Deactivation dm-verity
substrates Rescue Legacy
- Built-in scripts community:
Fix-fp-scanner (script to fix the fingerprint reader if the ROM reports "hardware can not be found")
ramdisk- cleaner (the script automatically cleans content boot from custom kernels and thus need not be renewed when switching to a different kernel stock kernel. However, the script still only supports ElementalX kernel, Radon kernel and Franco kernel.Warning: After cleaning the content boot must just to flash a new kernel - certainly attempt to restart the device to the system !!)
rm-pass(script to remove security currently installed ROM.)
NOS-before-flash-other-kernel(script recently found on 4PDA - deactivates the post-script Nitrogen boot ROM and thus allows better compatibility custom kernel).
Community scripts can thus be understandable added community. If you have your script / tip on a script about it here let me know.

Known Bugs
- The search engine of the camera HDR Snap is momentary assembly inoperable. TWRP still finds the application and if the application is installed TWRP and even prevents installation Snap CAMERA HDR.
The problem is mainly that I do not have complete access to that search engine - probably even if I somehow repaired and recovery will still prefer ofiko TWRP search application. So it probably could not be correct function ofiko TWRP applications not installed. However, definitely I do something in the next builds I make.

Link to download
latest build released: official
https://www.androidfilehost.com/?fid=889764386195913594
Update Changes
Update!
RedWolf-V3.0_006-Kate_Kenzo
Major changes;
- After clicking on the main menu icon coffee displays a new button "folder backups." Here you can now rename your current folder & zálohama or even set a new ID instead of the serial number at the ADB.
- Clicking on the Main Menu button to restore the icon appears at the top "bones". Using this button you can now delete all backups currently displayed. Therefore no longer need to delete one by one separately.
Current info
Version recovery: V3.0
Current build: 006
Number of community scripts: 4
Number of installation files: 6
Date of latest released build: 05-7-2017

Strings of recovery can be download here:
Strings for any translation AromaFM:
Extra Links
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
https://github.com/TeamWin
All Credit to ATG Droid
Source

Ss pls

not in a hurry but will have to remind you that source is not updated.... please add
~peace

AxeCORE said:
Ss pls
Click to expand...
Click to collapse
here!

adithyan25 said:
not in a hurry but will have to remind you that source is not updated.... please add
~peace
Click to expand...
Click to collapse
Visit our Forum - https://androidforum.cz
měj hezký den

Can i flash any rom on this type of recovery ?

xN00Bx said:
here!
Click to expand...
Click to collapse
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution

cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
+1

filipino guy said:
Can i flash any rom on this type of recovery ?
Click to expand...
Click to collapse
Yes you can flash it on any roms
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!

xN00Bx said:
Yes you can flash it on any roms
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
Click to expand...
Click to collapse
Yaa now working don't know why it didn't worked at first he he he thank you bro

I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system

anandumohan said:
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
Click to expand...
Click to collapse
Same thing

Recovery was withdrawn because its not yet ready to run on the variant Kenzo fully,
only kate is completely functional!
we will back to you when it's gets fixed
~thanks

Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

Development [RECOVERY] [11] [star/mars] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 Pro/Ultra
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_star
https://github.com/TeamWin/android_device_xiaomi_mars
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download:
star: https://twrp.me/xiaomi/xiaomimi11ultra.html
mars: https://twrp.me/xiaomi/xiaomimi11pro.html

Wow
Finally, official TWRP for our device, thanks alot to dev

when i flash it ,i can`t mount my /data
my device is mi 11 star

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
Are you on android 12?

Nebrassy said:
Are you on android 12?
Click to expand...
Click to collapse
yes

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
on android 11 the same......

Edlar said:
on android 11 the same......
Click to expand...
Click to collapse
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt

Nebrassy said:
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
did you try if its connected by typing fastboot devices?

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
Try going to mount menu, disable mtp and enable it, then check id adb is recognized

Nebrassy said:
Try going to mount menu, disable mtp and enable it, then check id adb is recognized
Click to expand...
Click to collapse
Worked, here are the logs
Thx !
Edit : That's strange, when i try to attach files, they upload and then disappear when i save
so, recovery :
recovery.log - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
logcat part1 : https://pastebin.com/ZPenY56E
part 2 : https://pastebin.com/6MYkJs5R

marcel112 said:
did you try if its connected by typing fastboot devices?
Click to expand...
Click to collapse
Tried and no problem
But, solved, thank you nonetheless

Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?

datadelrey said:
Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?
Click to expand...
Click to collapse
did you remove password or pin?

Great news!
I am wondering if there is a roadmap when TWRP will be available for A12?

{
"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"
}
Everything is fine, a log file appeared after I backed up the boot, I hope it's useful

please make a clear tutorial on how to fix the unable to mount/data
i removed the pin and password before fastboot boot twrp.img, go to advanced flash current twrp, and when i restart the device it goes to fastboot again.

Nebrassy said:
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Click to expand...
Click to collapse
How to update if we are currently use a different TWRP? I mean not "official".

Mi 11 Ultra / star
Using EU 12.5.20 and twrp 3.5.1
Update to 3.6.0 via Install Zip in 3.5.1
Reflash EU rom after update twrp and booted normally now.
Working fine. Thank you.

@hacker738 and now check, which version of TWRP is installed
if 3.6.0 then I'll really congratulate you

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S8 Series (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 Tab S8 X906B, X906C, X906N, X900, X806B, X806C, X806N, X800
Download & Guide:
1. Unlock your bootloader.
2. Downloads for Tab S8: gts8u twrp, gts8p twrp , gts8 twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
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.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
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
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree: gts8u, gts8p

Changelog:
GitHub History Tab S8
GitHub History Tab S8+
GitHub History Tab S8 Ultra

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section

You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?

SavXL said:
You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?
Click to expand...
Click to collapse
Yes its.
Also if anyone have the regular Tab S8 send me recovery.img here or on telegram

Sure, this is for X700XXU1AVCD/X700OXM1AVCD/X700XXU1AVCD (Tab S8 Wi-Fi Middle East).
I used this to root but it may be corrupt so you might wanna check.
Download

Hello ,
Is it possible with this twrp version to use the sd card also ? Thank you for your answer .

I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?

Techguy777 said:
I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?
Click to expand...
Click to collapse
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.

Finally awake. Gonna go ahead and flash TWRP on my Tab S8+ and share my results!

SavXL said:
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.
Click to expand...
Click to collapse
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet

Techguy777 said:
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet
Click to expand...
Click to collapse
Then don't spam every thread with tab s6 topics

I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.

SavXL said:
I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.
Click to expand...
Click to collapse
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.

afaneh92 said:
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.
Click to expand...
Click to collapse
How do I do that? Is it a command I can run in adb?

SavXL said:
How do I do that? Is it a command I can run in adb?
Click to expand...
Click to collapse
Use root explorer, zip the folder and upload it

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, will do once I get back into android.

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz

SavXL said:
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Wow, I asked for firmware folder from vendor not the whole vendor.

afaneh92 said:
Wow, I asked for firmware folder from vendor not the whole vendor.
Click to expand...
Click to collapse
Ohhhhhhhhhh, I'm sorry LOL. When you said vendor/firmware I assumed you said to upload the vendor folder OR the firmware folder. I'll remember that for next time. XD

Development [ROM][Unofficial][pdx225][13] Lineage 20 For SONY XPERIA 10IV

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_pdx225
https://github.com/XperiaBrickers-10IV/vendor_sony_murray
https://github.com/XperiaBrickers-10IV/hardware_sony
Current Bugs:
None
Many thanks to:
@clfbbn
@loipuru
@WindowsDev0
@dylanneve1
@Sakuu
Special thanks to
Sony
@jerpelea
For sending me the device

If some moderator could make us a device forum that would be lovely

King081 said:
View attachment 5856369
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
http://GDrive
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
Device Trees will be public soon
Current Bugs:
Sound does not work
screen flickers black
vibration does not work
USB doesn't work in recovery
takes about 3 buttton presses to get out of deep sleep
ENG build so you will get a red border
Many thanks to:
@clfbbn
@lolipuru
@WindowsDev0
@dylanneve1
Click to expand...
Click to collapse
What device is this ROM for?

TheWorldYT said:
What device is this ROM for?
Click to expand...
Click to collapse
pdx225 Xperia 10IV

Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.

litelinux said:
Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.
Click to expand...
Click to collapse
It's not sodp based, it's stock based

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yeah, don't worry it's my development device, so don't need testers, this is for those that like Trying stuff and mainly to get a forum

Join my telegram group for now https://t.me/Xperia007

King081 said:
It's not sodp based, it's stock based
Click to expand...
Click to collapse
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid

litelinux said:
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid
Click to expand...
Click to collapse
SODP tries to open source all the blobs, while stock based doesn't, due to the difficulty sodp is not really stable compared to stock base

Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yup, it's the closest thing to my previous phone (xz5c) I can fond on the market! Even the outer frame feels similar.

Could Be Anyone said:
I miss the xperia compacts.
Got small hands and the compacts were perfect.
10 IV is all right but I wish the width was smaller, 65mm would be amazing.
I guess I should be thankful it's just 67mm and not 77mm like the newer google pixels
Click to expand...
Click to collapse
Lol me with the Google Pixel 7

Update available
Changelog:
Sound and Mic now working
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR

Update available
Changelog:
Vibration and SDM work so screen does not flicker anymore and does not take 3 button presses to wake display
Current Bugs:
camera
ENG build
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR
it is now a usable device,
device trees will be public today

Device Tree are now public link available on first post

Could Be Anyone said:
Thanks so much.
Will install and provide feedback.
Is there lineageos recovery? I couldn't find one.
Click to expand...
Click to collapse
You'd have to extract the payload.bin file and flash boot vendor_boot and dtbo in fastbootD then reboot to recovery and flash rom.zip

Could Be Anyone said:
Keep getting an error.
E:Signature verification failed
E:error: 21
Install from SD card completed with status 2
Installation aborted
Click to expand...
Click to collapse
That's weird never happened to me before

Could Be Anyone said:
Well that's weird since I followed your instructions to a T.
Could you port lineageos recovery as well? It'll fix this problem since the stock recovery doesn't have the option to bypass signature verification.
Click to expand...
Click to collapse
You didn't listen then, extract ROM zip extract payload.bin, then flash vendor_boot boot and dtbo then reboot to recovery (Los one) then flash rom zip

Could Be Anyone said:
I couldn't find the los recovery on the first page.
Click to expand...
Click to collapse
I just said to extract it

Could Be Anyone said:
Ah, I my bad, I thought it was just a normal zip you meant to install, sorry about that.
Click to expand...
Click to collapse
No worries lol