Development [RECOVERY] [12] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27) - OnePlus 9R

{
"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"
}
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.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.

Reserved For me

Reserved For me

@Siddhant221 Nice to see you here! Good work, and keep it up!

Twrp Lemonades skirrrrrrrrrrah nice job ...

Oho

Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx

javi2246 said:
Hi, could this recovery be tested on a oneplus 9 (LE2115)? fastboot boot or flash.
thx
Click to expand...
Click to collapse
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp

Siddhant221 said:
It won't work as oneplus 9 is a gki device which requires other work over on recovery trees you can check on twrp.me for further to check if you device is available or not for twrp
Click to expand...
Click to collapse
thanks for the reply. I'm following the project in zulip to see if there is any news for op9

Hi, i have installed the latest 1.5 twrp on my 8T phone.
used the flash recovery, recovery is booting! but screen in not responding to any touch.
I can use only the power key and then recovery show lock, and ask to swipe to unlock, but screen is not responding.
I have OOS ROM 12 official.
with rooted kernel.
Unlocked.
Please fix, thank you for recovery!

Thanks! It works fine.
If I have OOS12 I can update it by TWRP? Incremental updates are allowed?
If I flash ROM (update, full rom) I must do it at slot A and after that change slot to B and do it again?

Any possibility to support 9 pro?

Any updates for A11?

As TWRP can sometimes take a long time to load, I modified the ramdisk to show a very dark, black splash screen to avoid the risk of burn-in.

Hey, where do I get the image file? Nothing shows up under the link for the release.

I see by the link provided in this topic's header a new version of TWRP based on OOS13 is available for download:
TWRP_V3.7.0_V1
Download:​https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases​​* Did someone test this version of TWRP already?

Siddhant221 said:
View attachment 5671251View attachment 5671257View attachment 5671259
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.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup(except data partition)/restore
ADB/MTP
Flashing Rom
stock rom flashing
fastbootd and adb sideload
Etc. Cuz I don't remember What else I fixed and What was working
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 12 firmware On both slots before flashing rom based on OOS 12 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
Click to expand...
Click to collapse
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?

Gogi_M said:
Hello Siddhant221
* Does this verison (TWRP_V3.7.0_V1) works with Lineageos 20?
Click to expand...
Click to collapse
Yep try it

Related

[TOUCHCOVERY] ORIGINAL | 4EXT Recovery Touch v1.0.0.5 RC6 with SmartFlash for s-on

Proudly presenting:
4EXT Recovery Touch
{
"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"
}
brand new user interface: "4EXT UI"
touchscreen only
extremely fast
much more useful features than the already feature-packed 4EXT Recovery Classic v2.2.7 RC5 (see 2nd post)
4EXT SmartFlash for s-on devices
optionally save space by configuring recovery to exclude /cache from backups
you can configure recovery to save even more space by excluding dalvik-cache from backups
calculates real space needed to complete a backup to save you from troubles
detects your local time zone
-> correct time is used for backups you start from within recovery
allows you to change md5sum check behaviour
displays and updates your current battery level in real time
scrollable texthistory (drag down the statusbar)
built-in interactivity (yes/no questions) for updater-scripts
built-in screenshot functionality
extensive theming capabilities!
nearly ALL YOU SEE is changeable.
"worker bar": create your own custom animations, there are (nearly) no limits! Use any shapes/sizes/animations et.c.
extra low cpu needed for that: absolutely no negative impact on backup/restore speed.
async UI rendering for optimal performance for the "heavy tasks" like backup/restore
backups even faster than with usual recoveries.
.. explore the new interface to see more
includes all features of 4EXT Recovery Classic
​
About 4EXT SmartFlash ​
This is a new feature that allows recovery to flash your boot partition just like as if you were s-off.
Credits and thanks to Team Win and Dees_Troy for their commitment to the community, for their amazing idea with the Dumlock and for extra contacting me only to offer that I may use it.
You guys really rock!
SmartFlash is a different approach to Team Win's HTC Dumlock
Just use your recovery like you would if your device were s-off
No preparations needed, other than telling the recovery that your device is actually s-on
This is done when you install recovery and answer the question that you are s-on with "yes"
You can also change that setting later on via RecoveryControl -> Recovery settings, or by editing 4ext.prop manually
Recovery will autodetect any changes done to "boot" and only attempt to flash your boot partition if it was really changed
This even reduces unnecessary writes to "boot" when for example a new rom uses the same kernel as your previous one
Before updating your boot partition, recovery will always backup your boot partition to your sdcard just for the case something goes wrong
Only the 4 latest boot images are stored, older ones will be removed automatically to prevent taking up too much space.
In case you want to enable or disable that feature temporarily, you can use a switch inside the tools menu in recovery
​
How it works:
Recovery will detect any requested changes for your boot partition
When you reboot out of recovery, it will prepare updating your boot partition on next rom start
This means that your boot partition will be updated when you see the HTC Splash screen, followed by 1 reboot
So basically the only visible difference to when you are s-off is one additional reboot, which takes only a few seconds.
Recovery is NOT flashed to boot and boot is also only flashed once/update
Recovery will only attempt to flash your boot partition if it was really changed
Limitations:
Radio and firmware:
Usually those are flashed via bootloader flashable zips or fastboot even on devices that are s-off.
But in case you wondered: this does not enable you to flash new firmwares or radio images via recovery.
SmartFlash needs a working kernel to be able to upgrade your boot partition.
It cannot work in case your current kernel is incompatible with your device/hboot or has been wiped outside of recovery.
For example you cannot erase boot via fastboot and then start up recovery to update your kernel.
However you don't need a working rom to use it.
The only requirement is that your current kernel is able to start (this happens before you see the boot animation) and that your system partition is mountable.
​​
INFO: ​
For App and Rom devs:​
Make use of the Recovery Interface Api provided by the (free and paid) 4EXT Recovery Apps to push updates/mods/addons for auto installation.
Very easy to use and to integrate into Apps or even shell scripts.
Please check 3rd post.​
Info regarding 4EXT Recovery Touch and its yesno feature, or any interactive installer scripts you might already use, please see 3rd post.​
​
Themes for 4EXT Recovery Touch:
Official 4EXT Recovery Themes Index & Discussion Thread
​
Download​
All downloads are available through 4EXT Recovery Updater.
It's free, no ads, no tracking, no nothing, don't worry
..and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
When you install or download a recovery via the app it makes sure that your recovery config is correctly set up.
It allows to automatically setup your time zone for recovery.
You can use it to get notified about updates regarding your recovery version
You can configure it to get notified in case any critical bugs have been discovered of the recovery version you currently have installed.
It allows me to update known issues/changelogs immediately and to quickly pull a newly released version if there were reports about critical bugs
You can also use it to just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
​
By default the app also saves the recovery.img you flash on your sdcard,
so you can use it to flash the recovery via fastboot in case you need to do that one day.
4EXT Recovery Control
Free version: Recovery Updater
Fully featured: Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Very easy to use, but also includes an extensive set of features available via "advanced mode"
Comfortable configure all settings of recovery
Calculate the space needed to create a new full or advanced backup
So you can make sure the backup will succeed before even rebooting into recovery.
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.​
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
When you restore a backup, the app does the md5sum check instead of the recovery
This ensures that you know whether the restore process will succeed before even rebooting into recovery​
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:
If md5sums don't match but you really need that backup badly, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup​
As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.​
Much, much more! See www.4ext.net
Big thanks to craacK for a lot of great icons!
​
Thanks:​
Big thanks to DolphiCom for all the graphics, the worker bar and a whole lot of great ideas and to the many great testers who spent all day/night testing, reporting bugs, making suggestions, helping with decisions:
Jotha, craacK, Patrics83, Euphorie, Mike1986, Whiskey103, ptr_hamilton, Lizard, TheUntouchable
Big thanks to Jotha and Whiskey103 for testing the themes features creating and their first themes for 4EXT Recovery Touch.
Special thanks to Dees_Troy who joined #4ext several times, just to tell me about important things he assumed I didn't know (and he was right! )
Also Big thanks to all the donators to 4EXT Recovery and everyone who has bought 4EXT Recovery Control! Without you I wouldn't be able to spend as much time with the project:
SO A HUGE THANK YOU!​
FRANKIE-BOY, BENJAMINNZIS, DESPERANTO86, SYRAKUS, VRC8883, FISHA21, ZJXPOT, ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, HAWST, ANIT77, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
Of course BIG THANKS to KOUSH for ClockworkModRecovery!
Without him, 4EXT Recovery wouldn't exist!​
Thanks a lot to the following users for initial testing for specific devices :
SPEEDYCARV, PTR_HAMILTON, JAMESCLINTON, SNOWBOARDKID503, MJESSE81, SEBASTIAAN15, THEUNTOUCHABLE, BMONSTER, ANDREIGHERGHE, PRESTON74, MADKAI, YASIR, PLAYPETEPP
IPERZAMPEM0, THESHAWTY, JBBANDOS, TAZMAN1963, GREGFERNS and INCREDULOUS
Special thanks to Invasion2 and Stlouie65 for spending at least 10 hours of their time helping me debug a really nasty issue on the myTouch 4G!
Also thanks for obtaining calibration values for the touchscreen:
Mjesse81,
Speedycarv,
Wolfepakt
Jaibar
Jayallen1980
Stlouie65
Invasion2
PacerguyDon
Ben_Pyett
Dargocitfer
Darknessrise1234
Lizard
Azazel71
​
Features of 4EXT Recovery Classic:
(Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!)
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.​
You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!​
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.
-> but you can change that​
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu​
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"​
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB​
Switch haptic feedback on/off
Button backlights
​
Recovery Interface Api for Apps and Scripts​
Both: free and paid 4EXT apps now provide a very easy to use interface you can use to access 4EXT Recovery from within your shell scripts or apps.
Features:
wipe cache
wipe dalvik
wipe data / factory reset
install multiple zips at once
backup
If you are interested, please download this zip file with examples​
How to make use of 4EXT Recovery Touch from within updater-scripts:​
Since Beta 1.0.0.3 Beta 4 you can do the following:
identify whether the user is running 4EXT Recovery Touch or not (to use or not to use the following commands)
make use of the native yes/no dialogue (confirm / cancel buttons)
prevent recovery from redrawing the screen ( in case you need to use your own 3rd party interactive binary )
​
To identify 4EXT Recovery Touch:
Code:
if getprop("ext.edition") == "ng" then
<your code>
endif;
To use the native confirm dialogues:
Code:
ui_print("4ext: show_yesno"); # <-- recovery will pause your script and display "yes / no" buttons.
run_program("/sbin/sleep", "2"); # <-- for safety since the above is executed asynchronous
#check the return value by calling:
if getprop("ext.confirm") == "yes" then
<yourcode>
endif;
To prevent recovery from redrawing the screen ( if you want to use an external binary that needs to occupy the screen and get the focus )
Code:
ui_print("4ext: disable_scrn_update");
# don't forget to enable it again after your yesno binary or graphical installer is finished, by calling:
ui_print("4ext: enable_scrn_update"); #otherwise the recovery will appear to be frozen as it won't update the screen anymore.
Oh yeah I have been waiting for this!!
Thanks alot!!
1st post ;D
best app
Yeah after a long time
Hi,
Any links to the themes?
thanks
4D3 said:
Hi,
Any links to the themes?
thanks
Click to expand...
Click to collapse
In my signature and inside the app in the themes menu
And also somewhere inside the post
it looks very nice, good job
Does the new touch 4ext recovery have the phone-off charging bug?
rahditzz said:
Does the new touch 4ext recovery have the phone-off charging bug?
Click to expand...
Click to collapse
it will charge your device to death
jk, no, charging works inside and outside recovery.
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Awsome.. Loving it already.. hehe..
madmaxx82 said:
In my signature and inside the app in the themes menu
And also somewhere inside the post
Click to expand...
Click to collapse
I guess i can use any for the sensation?
thanks
Formhault said:
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Click to expand...
Click to collapse
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Let's see how Build Nr. 2 of RC3 will behave.
madmaxx82 said:
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Click to expand...
Click to collapse
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Formhault said:
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Click to expand...
Click to collapse
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Formhault said:
I just flashed it (latest beta, RC4).
Click to expand...
Click to collapse
Where did u get RC4? I can only get RC3..:S
rahditzz said:
Where did u get RC4? I can only get RC3..:S
Click to expand...
Click to collapse
4EXT Recovery app... That's how I got it. There's no other way you can possibly get it, anyway .
Hmm.. RC4 isnt showing up for me..:S
madmaxx82 said:
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Click to expand...
Click to collapse
Then perhaps my memory was failing on me . I'll see tomorrow what version it is on my gf's DS and update it (I only use it once every few months, anyway). I no longer own the DHD, btw.
Thanks again for bringing the 3VO into your supported-phones line
@those not being able to see RC4... Perhaps you should update the 4EXT Recovery Control app... Latest is v2.3.1
Sent from my LeeDrOiD-loaded 3VO

[TOUCHCOVERY] ORIGINAL | 4EXT Recovery Touch v1.0.0.6 RC2 with SmartFlash for s-on

Proudly presenting:
4EXT Recovery Touch
{
"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"
}
brand new user interface: "4EXT UI"
touchscreen only
extremely fast
much more useful features than the already feature-packed 4EXT Recovery Classic v2.2.7 RC5 (see 2nd post)
4EXT SmartFlash for s-on devices
optionally save space by configuring recovery to exclude /cache from backups
you can configure recovery to save even more space by excluding dalvik-cache from backups
calculates real space needed to complete a backup to save you from troubles
detects your local time zone
-> correct time is used for backups you start from within recovery
allows you to change md5sum check behaviour
displays and updates your current battery level in real time
scrollable texthistory (drag down the statusbar)
built-in interactivity (yes/no questions) for updater-scripts
built-in screenshot functionality
extensive theming capabilities!
nearly ALL YOU SEE is changeable.
"worker bar": create your own custom animations, there are (nearly) no limits! Use any shapes/sizes/animations et.c.
extra low cpu needed for that: absolutely no negative impact on backup/restore speed.
async UI rendering for optimal performance for the "heavy tasks" like backup/restore
backups even faster than with usual recoveries.
.. explore the new interface to see more
includes all features of 4EXT Recovery Classic
​
About 4EXT SmartFlash ​
This is a new feature that allows recovery to flash your boot partition just like as if you were s-off.
Credits and thanks to Team Win and Dees_Troy for their commitment to the community, for their amazing idea with the Dumlock and for extra contacting me only to offer that I may use it.
You guys really rock!
SmartFlash is a different approach to Team Win's HTC Dumlock
Just use your recovery like you would if your device were s-off
No preparations needed, other than telling the recovery that your device is actually s-on
This is done when you install recovery and answer the question that you are s-on with "yes"
You can also change that setting later on via RecoveryControl -> Recovery settings, or by editing 4ext.prop manually
Recovery will autodetect any changes done to "boot" and only attempt to flash your boot partition if it was really changed
This even reduces unnecessary writes to "boot" when for example a new rom uses the same kernel as your previous one
Before updating your boot partition, recovery will always backup your boot partition to your sdcard just for the case something goes wrong
Only the 4 latest boot images are stored, older ones will be removed automatically to prevent taking up too much space.
In case you want to enable or disable that feature temporarily, you can use a switch inside the tools menu in recovery
​
How it works:
Recovery will detect any requested changes for your boot partition
When you reboot out of recovery, it will prepare updating your boot partition on next rom start
This means that your boot partition will be updated when you see the HTC Splash screen, followed by 1 reboot
So basically the only visible difference to when you are s-off is one additional reboot, which takes only a few seconds.
Recovery is NOT flashed to boot and boot is also only flashed once/update
Recovery will only attempt to flash your boot partition if it was really changed
Limitations:
Radio and firmware:
Usually those are flashed via bootloader flashable zips or fastboot even on devices that are s-off.
But in case you wondered: this does not enable you to flash new firmwares or radio images via recovery.
SmartFlash needs a working kernel to be able to upgrade your boot partition.
It cannot work in case your current kernel is incompatible with your device/hboot or has been wiped outside of recovery.
For example you cannot erase boot via fastboot and then start up recovery to update your kernel.
However you don't need a working rom to use it.
The only requirement is that your current kernel is able to start (this happens before you see the boot animation) and that your system partition is mountable.
​​
INFO: ​
For App and Rom devs:​
Make use of the Recovery Interface Api provided by the (free and paid) 4EXT Recovery Apps to push updates/mods/addons for auto installation.
Very easy to use and to integrate into Apps or even shell scripts.
Please check 3rd post.​
Info regarding 4EXT Recovery Touch and its yesno feature, or any interactive installer scripts you might already use, please see 3rd post.​
​
Themes for 4EXT Recovery Touch:
Official 4EXT Recovery Themes Index & Discussion Thread
​
Download​
All downloads are available through 4EXT Recovery Updater.
It's free, no ads, no tracking, no nothing, don't worry
..and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
When you install or download a recovery via the app it makes sure that your recovery config is correctly set up.
Configure 4EXT Recovery comfortably without the need to modify config files.
It allows to automatically setup your time zone for recovery.
You can use it to get notified about updates regarding your recovery version
You can configure it to get notified in case any critical bugs have been discovered of the recovery version you currently have installed.
It allows me to update known issues/changelogs immediately and to quickly pull a newly released version if there were reports about critical bugs
You can also use it to just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
​
By default the app also saves the recovery.img you flash on your sdcard,
so you can use it to flash the recovery via fastboot in case you need to do that one day.
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
[/SIZE]
4EXT Recovery Control
Free version: Recovery Updater
Fully featured: Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Very easy to use, but also includes an extensive set of features available via "advanced mode"
Comfortable configure all settings of recovery
Calculate the space needed to create a new full or advanced backup
So you can make sure the backup will succeed before even rebooting into recovery.
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.​
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
When you restore a backup, the app does the md5sum check instead of the recovery
This ensures that you know whether the restore process will succeed before even rebooting into recovery​
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:
If md5sums don't match but you really need that backup badly, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup​
As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.​
Much, much more! See www.4ext.net
Big thanks to craacK for a lot of great icons!
​
Thanks:​
Big thanks to DolphiCom for all the graphics, the worker bar and a whole lot of great ideas and to the many great testers who spent all day/night testing, reporting bugs, making suggestions, helping with decisions:
Jotha, craacK, Patrics83, Euphorie, Mike1986, Whiskey103, ptr_hamilton, Lizard, TheUntouchable
Big thanks to Jotha and Whiskey103 for testing the themes features creating and their first themes for 4EXT Recovery Touch.
Special thanks to Dees_Troy who joined #4ext several times, just to tell me about important things he assumed I didn't know (and he was right! )
Also Big thanks to all the donators to 4EXT Recovery and everyone who has bought 4EXT Recovery Control! Without you I wouldn't be able to spend as much time with the project:
SO A HUGE THANK YOU!​
FRANKIE-BOY, BENJAMINNZIS, DESPERANTO86, SYRAKUS, VRC8883, FISHA21, ZJXPOT, ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, HAWST, ANIT77, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
Of course BIG THANKS to KOUSH for ClockworkModRecovery!
Without him, 4EXT Recovery wouldn't exist!​
Thanks a lot to the following users for initial testing for specific devices :
SPEEDYCARV, PTR_HAMILTON, JAMESCLINTON, SNOWBOARDKID503, MJESSE81, SEBASTIAAN15, THEUNTOUCHABLE, BMONSTER, ANDREIGHERGHE, PRESTON74, MADKAI, YASIR, PLAYPETEPP
IPERZAMPEM0, THESHAWTY, JBBANDOS, TAZMAN1963, GREGFERNS and INCREDULOUS
Special thanks to Invasion2 and Stlouie65 for spending at least 10 hours of their time helping me debug a really nasty issue on the myTouch 4G!
Also thanks for obtaining calibration values for the touchscreen:
Mjesse81,
Speedycarv,
Wolfepakt
Jaibar
Jayallen1980
Stlouie65
Invasion2
PacerguyDon
Ben_Pyett
Dargocitfer
Darknessrise1234
Lizard
Azazel71
​
Features of 4EXT Recovery Classic:
(Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!)
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.​
You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!​
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.
-> but you can change that​
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu​
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"​
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB​
Switch haptic feedback on/off
Button backlights
​
Recovery Interface Api for Apps and Scripts​
Both: free and paid 4EXT apps now provide a very easy to use interface you can use to access 4EXT Recovery from within your shell scripts or apps.
Features:
wipe cache
wipe dalvik
wipe data / factory reset
install multiple zips at once
backup
If you are interested, please download this zip file with examples​
How to make use of 4EXT Recovery Touch from within updater-scripts:​
Since Beta 1.0.0.3 Beta 4 you can do the following:
identify whether the user is running 4EXT Recovery Touch or not (to use or not to use the following commands)
make use of the native yes/no dialogue (confirm / cancel buttons)
prevent recovery from redrawing the screen ( in case you need to use your own 3rd party interactive binary )
​
To identify 4EXT Recovery Touch:
Code:
if getprop("ext.edition") == "ng" then
<your code>
endif;
To use the native confirm dialogues:
Code:
ui_print("4ext: show_yesno"); # <-- recovery will pause your script and display "yes / no" buttons.
run_program("/sbin/sleep", "2"); # <-- for safety since the above is executed asynchronous
#check the return value by calling:
if getprop("ext.confirm") == "yes" then
<yourcode>
endif;
To prevent recovery from redrawing the screen ( if you want to use an external binary that needs to occupy the screen and get the focus )
Code:
ui_print("4ext: disable_scrn_update");
# don't forget to enable it again after your yesno binary or graphical installer is finished, by calling:
ui_print("4ext: enable_scrn_update"); #otherwise the recovery will appear to be frozen as it won't update the screen anymore.
reserved...
So this is for cmda
Sent from my PG86100 using XDA
looks dope.. but im on cdma to.... can we flash this recovery???
looks promising. I'm gonna keep an eye on this. I'm a little nervous about trying a new recovery after my adventures with this phone today...just want stability for a few more hours lol.
EDIT: just to clarify, im not in any way knocking the stability of this recovery, especially since I haven't tried it yet, I was merely saying I'm looking for stability for now since i was surprised to find myself unbricking my phone earlier.
Looks great. I'll give it a shot
Sent from my PG86100 using Tapatalk
Of course it is for the CDMA!
I'm mad, but not that mad
Also the app will detect your device as cdma and let you confirm!
This works awesome so far! Even got it themed! Haven't tried any flashes or backups yet, but I'm sure it works just fine!
Thanks!
-Tee Jay
noice noice
Thank you!
Before someone asks:
You can drag down the statusbar to get to the text output history.
For taking screenshots:
Press the search button.
When you are finished taking screens, don't forget to copy them to your sdcard using the tools menu.
Yes, the font is small, there will be something... else.. soon
Themes: all themes for the Sensation, or better 960x540 work perfectly on the Evo 3D
wow someone rated 1 star. no respect -_-
Joey_UFC said:
wow someone rated 1 star. no respect -_-
Click to expand...
Click to collapse
Fixed that now its 4 stars
well i did a backup.. then wiped data wiped cash wiped dalvik cash.. then i flashed team nocturals wipe and after it was done the phone rebooted but it went back into recovery??? was it supposed to do that?????
Trying this out right now, i've heard good things about it!! Thanks!
This look amazing! I too could use some stability (3 bricks in 2 days) but hell, cant resist!
Hehe I'm sorry that I cannot give you RC2 which is extremely stable.
But it has no support for wimax backup/restore.
RC3 is meant to fix the 1-2 cosmetic bugs from rc2, but I had to change a little bit more regarding backup/restore of wimax.
And any version I release, will first get a "testing" flag..
This is utterly fantastic. Thank you so much!
its all gOOd just figured id let u kno it rebooted..

[Recovery][6633][twrp] Unofficial TWRP 3.0.2 for Z3 Dual D6633

{
"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"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:​
Team Win Recovery Project or twrp2 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
Decryption of /data
Easy selection of internal/external storage
And much more...
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 cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:​
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):​
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you ​
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0

[RECOVERY[G610] TWRP 3.1 for Galaxy J7 Prime

TWRP RECOVERY FOR GALAXY J7 PRIME
{
"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 is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOADS:
twrp3.1.0-0
Use Odin to flash.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot to if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery. If you choose to 'Allow' then SuperSU needs to be flashed to disable dm-verity.
To Root:
Flash the latest SuperSU:
http://www.supersu.com/download#zip
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
(Note this MUST be flashed before SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install modded kernel from below.
5. Reboot
Modded Kernel:
https://mega.nz/#!tJ5XVa4I!_kMCzV7kOMvEdvJwB3ZUDPZjGUNIuuzK6RSLHMiZG4M (Thanks to maxx35000)
NOTE: NO NEED TO FLASH MODDED KERNEL IF YOU ARE USING ANY CUSTOM ROM
HIT THANKS IF I HELPED YOU:good:
is this oficial ?
Mounting internal is working?
Not work on last update from samsung, with update AQC4 recovery not incompatible
Janeslejade said:
Mounting internal is working?
Click to expand...
Click to collapse
Yes. Read the thread on how to do this.
hoangphuc057 said:
Not work on last update from samsung, with update AQC4 recovery not incompatible
Click to expand...
Click to collapse
It's working. I'm on AQC4
Not working on G610Y.
---------- Post added at 09:23 AM ---------- Previous post was at 09:11 AM ----------
Guys, i want to go back to stock recovery, questions.... Is it safe to flash this stock recovery??
SM-G610F/M_stock_recovery
My unit is G610Y.
Up... Please help, i need the SM-G610Y_stock_recovery... Please someone help or advise if SM-G610F/M_stock_recovery is okay to flash on G610Y??
Help guys! I tried to root my phone but no success. It says need adb 1.3 or newer. What should i do?
External sd mounting?
Thanks for the update, working on G610M
4. Install modded kernel from below.
Click to expand...
Click to collapse
how to do this?
Ephesis said:
how to do this?
Click to expand...
Click to collapse
Flash through odin in AP
Siddhant NAik said:
Flash through odin in AP
Click to expand...
Click to collapse
how about rooting? flash via odin too?
---------- Post added at 09:52 AM ---------- Previous post was at 09:40 AM ----------
Flash through odin in AP
Click to expand...
Click to collapse
Odin wont read it since its a zip file not a tor file.
inamie said:
External sd mounting?
Click to expand...
Click to collapse
This is the essential question!
thank
trinaldi said:
This is the essential question!
Click to expand...
Click to collapse
not working.
Anyone tried this on G6100 ?
Please update aqc4 mod kernel
Thank you bro. Haha :d :d

[MOD][ OCT 16 ][Sanders] MultiROM v33 || no-kexec workaround

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto G5S Plus. It can boot any Android ROM, besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action in general.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. But it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_sanders_YYYYMMDD-xx.img) - download the IMG file from second post and use fastboot or Normal TWRP recovery if you have or any other third party image installers from Google Playstore.
MultiROM (multirom-YYYYMMDD-v33e-UNOFFICIAL-sanders.zip) - download the ZIP file from second post and flash it in recovery.
2. Via MultiROM Manager app
We do not have Official Support, an unofficial APP can be downloaded from second post)
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/MR-op3/multirom (branch mr-7.1)
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery (branch mr-7.1)
Device Tree - https://github.com/MR-op3/device_motorola_sanders (branch mr)​
Credits
nkk71 (For no-kexec workaround)
XDA:DevDB Information
[MOD][OCT 16][Sanders] MultiROM v33 || no-kexec workaround, Tool/Utility for the Moto G5S Plus
Contributors
premaca, syed sajid, GeneticEnginer
Version Information
Status: Beta
Current Beta Version: v33
Beta Release Date: 2017-10-16
Created 2017-10-17
Last Updated 2017-10-31
Changelog and Downloads
If you have come across with WRONG-PIN on Primary after the installation of secondary, flash the following Lock Fix.
Lockfix.zip
20171114
multirom-20171114-v33e- UNOFFICIAL-sanders
TWRP-multirom_sanders_20171114-01.img
20171016
multirom-20171016-v33e-UNOFFICIAL-sanders.zip
TWRP_multirom_sanders_20171016-02.img
- Initial Release
Flash this ZIP file multirom_uninstaller.zipto remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Multirom manager APP: Will be uploaded Soon.
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
Will Motorola Stock works as Primary or Secondary ROM?
Yes, Motorola Stock version works with Multirom as Primary ROM, It is not advised to install stock as Secondary, use only as Primary ROM. You can then install other Android ROMs as secondaries.​
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.​
Enabling no-kexec workaround
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Reserved
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
nkk71 said:
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
Click to expand...
Click to collapse
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
premaca said:
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
Click to expand...
Click to collapse
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
nkk71 said:
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
Click to expand...
Click to collapse
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
winpooh said:
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
Click to expand...
Click to collapse
Yes ,it can work after reset only, you have to do a backup first.
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
abhinav2hd said:
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
Click to expand...
Click to collapse
Be careful and do read the instructions also.
syed sajid said:
Be careful and do read the instructions also.
Click to expand...
Click to collapse
I've used multirom before.. i know how it works ?
abhinav2hd said:
I've used multirom before.. i know how it works ?
Click to expand...
Click to collapse
That's good, I'm not talking about how to use multirom?
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
[URL="https://androidfilehost.com/?fid=889964283620765983]https://androidfilehost.com/?fid=889964283620765983[/URL]
Do I have to wipe data again after updating?
gaurav.saroya said:
Do I have to wipe data again after updating?
Click to expand...
Click to collapse
Nope, just flash it as normal..
syed sajid said:
Nope, just flash it as normal..
Click to expand...
Click to collapse
Okay thanks
syed sajid said:
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
https://androidfilehost.com/?fid=889964283620765983
Click to expand...
Click to collapse
Second link not working
gaurav.saroya said:
Second link not working
Click to expand...
Click to collapse
Working ...afh too slow wait till open..
syed sajid said:
Working ...afh too slow wait till open..
Click to expand...
Click to collapse
It's working now

Categories

Resources