Related
{
"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"
}
translated by Kizsde :highfive:
I would like to ask everbody not to send me PMs with questions about the installation, that is what the forum is here for. Also everbody should do this at their OWN RISK!
If you already have recovery installed, go to step (3) and continue from there.
(1): As a first step, we should "root" our stock 4.3, so later on we can install a recovery tool:
- a: Download the towelroot apk and click on the Lambda icon
- b: On the phone, navigate to Settings > Security and check the Unknown Resources checkbox
- c: Copy the tr.apk to your phone's SD card and install it
- d: Estabilish an active internet connection on your phone
- e: Run the towelroot app and once it loaded, tap on the "make it ra1n" button. This should "root" your phone.
**The reason why the word "root" is between quotation marks, is because the towelroot app doesn't actually root your phone, but allows a superuser application to be installed on it. We don't actually need an SU app, but "root" is needed for the installation of the recovery.
(2): Installing the Recoveries (source: [link])
-a: On the phone, navigate to "Settings > Developer Options" and check the "USB Debugging" checkbox. If you don't have it listed, just tap the "Build Number" within "Settings > About Phone" 4-5 times.
-b: Connect your phone to the PC
-c: Download the recovery pack created by dssmex
-d: Extract the CWM_SP_4.4.1.zip file to your computer and depending on your operating system run the appropriate install***** file (install_mac.sh= MAC OSx; install_linux.sh= Linux; install.bat= Windows) **(On Windows a menu will appear, where you need to choose option "1" and the rest will be done automatically)
-e: If the installation is successful and you see no errors, you can reboot your phone. Otherwise repeat the installation until it is completely error-free
-f: After reboot, the phone indicates with some blinking lights and a slight vibration that you are now able to select from the recoveries (volume rocker down=TWRP recovery; volume rocker up=Philz recovery; camera button=CWM recovery). It is up to you which one you select, as all of them should be able to do the job just fine. Personally I recommend CWM and the guide will follow this method. IMPORTANT: During the recovery selection, the idle time is 2 seconds and if no button is pressed, the phone will boot normally.
(3): Installation of the Slimkat rom:
-a: Download the newest rom from here: [link]
-b: Copy the Slim-4.4.*.build.*.*-2014****-UNOFFICIAL-lbhuashan.zip to your phone, preferrably to the external SD card. (This can be performed during recovery too, but copying to the SD card is significantly slower this way, so before you do that please read section (4))
-c: During recovery selection, choose CWM
(Quick CWM navigation guide: With physical buttons: Volume down=move down; Volume up=move up; On/off button=Enter/select menu option; || With swipe gestures: Swipe down: move down; Swipe up=move up; Swipe right=Enter/select menu option; Swipe left=back)
-d: Make a backup of your current system, by going to "backup and restore" and selecting the "backup to /storage/sdcard1" option. This will create a "clockworkmod" folder on your SD card and the dated backups will be stored here.
-e: Now go to "Wipe data/factory reset" and select the "Yes-Wipe All user data" option. This will erase the /Data /Cache partitions and delete the ".android_secure" folder on the SD card. IMPORTANT: This may take several minutes to complete.
It is advised to do the following when performing a clean install:
It may happen that the installer is unable to format the system, so it needs to be perfomed manually by going to "mount and storage" and selecting the "format /system" option.
-f: Navigate to "install zip->choose zip from /storage/sdcard1" then browse to and select the previously copied Slimkat rom
-g: The Slimkat rom should now be installed. If you don't prefer to install the Gapps pack, then reboot your phone with the "reboot system now" option, otherwise go to step (4)
(4): Installation of the google apps (Gapps):
-a: Download the newest Slimkat Gapps from this list
-b: Copy it to the external SD card
-c: Go to CWM recovery again (camera button)
-d: Navigate to "install zip->choose zip from /storage/sdcard1" and select the Gapps pack you just copied to the SD card
-e: Once installation is done, reboot the phone
What works:
USB Charging : Ok
USB ADB : Ok
USB MTP : Ok
Video : Ok
Audio : Ok
Sensors : Ok
Screen rotation : Ok
WLAN : Ok
WLAN Hotspot : Ok
GPS : Ok
GSM : Ok
GSM Data : Ok
GSM Voice : Ok
GSM SMS : Ok
Bluetooth : Ok
NFC : Ok (After first boot uncheck NFC and reboot the phone, otherwise you will not be able to use it)
Camera : Ok
FM Radio : Ok
Keyboard : Ok
MHL : Ok
OTG : Ok
ART MOD : Ok
What doesn't work:
???
----------------------------------------------------------------------------------------------------------------------
Frequently Asked Questions + Useful info:
- The first boot will always be slow. This is because once you enter your google account details it starts updating the google apps and your personal details, while downloading your own applications as well
- The rom does not include Sony's own services and user interface
- The rom is rooted by default
- You cannot apply any custom kernels as the bootloader is locked
- After first boot, turn off NFC (or at least try to remove the check from the checkbox, it will not be possible due to a bug), then reboot the phone. After this you will be able to turn it on/off as per usual.
- The rom contains CWM and Philz recovery too (camera button=CWM; volume up=Philz)
- Hijack is a script that enables useres to boot not only stock roms on a locked bootloader, but custom ones too like Cyanogenmod, aopk, pa, pac, slimkat, omni etc...
- It is not possible to update a rom OTA, only from recovery. The method of updating the rom is the same as installing it from step (3), the only difference is that the "-d: wipe data/factory reset" part needs to be skipped
ROM: Slim-4.4.4.build.8.14-20141120-UNOFFICIAL-lbhuashan
GAPPS: Slimkat Gapps
Changes:
Slim-4.4.4.build.8.14-20141120-UNOFFICIAL-lbhuashan:
-Slimkat update-source(8.14)
Slim-4.4.4.build.8.10-20141109-UNOFFICIAL-lbhuashan:
-Slimkat update-source(8.10)
-zram dual core use
-HDR support
Slim-4.4.4.build.8.9-20141101-UNOFFICIAL-lbhuashan:
-Slimkat update-source(8.9)
-fm radio poor reception fix
-Fm transmitter support
-FM Transmitter use the default headset antenna (15-50 meters range)
-hijack & ramdisk permission fix
-glove mod permission fix
-zRam support (size: 256MB) (tested)
-add conservative governor
Slim-4.4.4.build.8.8-20141021-UNOFFICIAL-lbhuashan:
-Slimkat update-source(8.8)
-add torch app
-12.1.A.1.207 update vendor blob files
-add native fm radio
-remove internal sd card (data partition fix 5.4GB)
-UMS support
-add new cwm and philz recovery
-more volume on the headset
-eMMC tweak
-add new adreno libs thx MrSteve555
-rare mic fix thx MrSteve555
-fm radio poor reception fix thx mikereidis
Changelog Slim-4.4.2.build.5.4_LBL-UNOFFICIAL-20140527:
-Slimkat update-source(5.4)
- /storage/sdcard0 permission fix
-add lionheart governor
-voip mic fix
-Enable use of FFMPEG codecs for extended formats (Gallery can play these formats:avi,mkv,wmv,mp4)
Changelog PATCH_Slim-4.4.2.build.4.8_LBL-UNOFFICIAL-20140503:
- /storage/sdcard0 permission fix
Changelog Slim-4.4.2.build.4.8_LBL-UNOFFICIAL-20140503:
-Slimkat update-source
-Some games app crash fix
-enabled glove mod
-stability problem fix
-boot up fix
-PhilZ touch system mount fix
-128kbps audio recording, video mode
- ART mode optimization of applications reboot always fixed
- Selinux permissions fixed
- ++ Little kinder surprise
Changelog PATCH_Slim-4.4.2.build.4.8_LBL-UNOFFICIAL-20140429:
-boot up fix
-PhilZ touch system mount fix
----------------------------------------------------------------------------------------------------------------------
Source codes:
Slimkat
Device tree:
android_device_sony_lbhuashan
android_device_sony_lbqcom-common
android_device_sony_lbcommon
android_vendor_lbsony
hijack-ramdisk-huashan
Kernel Source:
android_kernel_sony_lbmsm8960t
Screenshots:
Credits:
-MrSteve555
-neXusPRIME
-dh.harald
-KeiranFTW
-cray_Doze
-davidmarco
-dssmex
-DooMLoRD
-slimroms
CM11
CM 11 is coming soon
Good job! Gotta test ASAP!
Downloaded installed and using.
Calls texting internet all good so far.
Sent from my C5303 using Tapatalk
great job thanks:laugh:
@bagyusz Forgot ask does Art work?
Sent from my C5303 using Tapatalk
Treboeth said:
@bagyusz Forgot ask does Art work?
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Yes it works.
Is HALO and other features like active display are available in this ROM??
bagyusz said:
Yes it works.
Click to expand...
Click to collapse
Apologies missed that on the OP, too excited by your creating SlimKat
Sent from my C5303 using Tapatalk
Thanks for ur work. One question when I flash ur rom like ur how to my phone stay unlock? Thanks
Gesendet von meinem Xperia SP
Tnx, It's my lovely ROM
I got this error:
Symlinks and permissions..
set_metadata_recursive: some changes failed
E:Error in /storage/sdcard1/Slim-4.4.2.build.4.8
(Status 7)
Installation aborted
*Fixed with install .201 kernel and slim 4.3 version android and than isntalled 4.4 and now work perfect.
Slim 4.3 is only for ULB which means I can't install this ROM as my bootloader is locked. Any way around this?
Buleste said:
Slim 4.3 is only for ULB which means I can't install this ROM as my bootloader is locked. Any way around this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2727557
http://d-h.st/Z12
Hey guys, so the edit today for mounting system, etc fixed the error 7 I assume?
:victory:
vwadam said:
http://forum.xda-developers.com/showthread.php?t=2727557
http://d-h.st/Z12
Click to expand...
Click to collapse
:good:
Sorry for my ignorance but what is ART?
ART: https://source.android.com/devices/tech/dalvik/art.html
any idea how to add back energy saving funktion from 4.3?
Ok!
So, now, we can call you LBL MASTER!! ^^
I'm running this awesome Slimkat since this morning, nearly perfect!
No freeze, no lag, no touch problems...
The only problem i encountred is the LTE tile: after disabling it, i'm not able to enable it again.
Anyone got this problem?
TWRP Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this 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. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1440x2560 (Note 4).
Note 4 Canadian
Note 4 Indian N910G
Note 4 Sprint
Note 4 T-Mobile
Note 4 US Cellular
Note 4 Verizon
Note 4 International N910F
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
Note 4 Canadian (trltecan)
Note 4 Indian N910G (trltedt)
Note 4 Sprint (trltespr)
Note 4 T-Mobile (trltetmo)
Note 4 US Cellular (trlteusc)
Note 4 Verizon (trltevzw)
Note 4 International N910F (trltexx)
TWRP Themes & Splashes (Note 4)
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 2.8.7.0:
Initial ground work for software drawn keyboard (_that)
Fix handling of wiping internal storage on datamedia devices (xuefer)
Allow DataManager to set and read values from the system properties (xuefer)
Fix crash when taking screenshots on arm64 devices (xuefer)
Fix error message after an ORS script completes (Dees_Troy)
Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
Add system read only option – more details below (Dees_Troy)
Add resize2fs and GUI option to run resize2fs (Dees_Troy)
Fix crash loop caused by empty lines in AOSP recovery command file (_that)
Prevent duplicate page overlays such as multiple lock screens (mdmower)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.
reserved 2
Give us version for F model.
Ogy77 said:
Give us version for F model.
Click to expand...
Click to collapse
uploading
Update
ogy77 said:
give us version for f model.
Click to expand...
Click to collapse
all download link ready now
uzairabdulmajeed said:
all download link ready now
Click to expand...
Click to collapse
Thank you sir.
I have twrp 2.8.7.0 in my phone now just flash theme right?
Ogy77 said:
Thank you sir.
I have twrp 2.8.7.0 in my phone now just flash theme right?
Click to expand...
Click to collapse
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
all info in #2 post
created separate threads for
T-Mobile
Sprint
Verizon
Aroma is not working for me...giving error
Sent from my SM-N910G using Tapatalk
splash
Did everything as stated in post#2
I don't understand the splash instructions.
Once i have the desired splash.jpg what do i do?
Can i put the jpg on the sdcard and than flash the AIK-Mobile-Installer?
Does anyone have a copy of the AIK splash installer? Its been removed. I want to change the splash to go with my newly themed recovery. Thank u guys.
Or.......tell me how to change it manually. Thanks
Hello sir i am using galaxy note 4 n910g twrp v3.0.2.0 and m unable to use pleas help me
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6.59.0 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
Features:-
* Touch Interface
Click to expand...
Click to collapse
- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, first touch will select only. After one sec of scrolling or on second touch, it will validate immeadiately. This is by design and not a bug. It is there to limit erroneous validation while scrolling
Click to expand...
Click to collapse
Click to expand...
Click to collapse
First to introduce true JB 4.2 migration: toggle between /data/media and /data/media/0
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT + ext4 support in recovery for external sd
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage and exfat partitions
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore,enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
you can cancel any nandroid operation with back button
create custom_rom.zipfrom current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time incremented copies for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
dual USB mount in recovery support and mount external sd over usb for /data/media devices
adb root in recovery: just wait about a minute to activate
detailed build info in About menu
Click to expand...
Click to collapse
Screenshots :-
{
"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"
}
Click to expand...
Click to collapse
Download:-
Download PhilZ Touch 6.59.0 Recovery from Here
Click to expand...
Click to collapse
Credits :-
>> PhilZ (Original Dev Of PhilZ recovery)
>> Yuweng ( For Making Automated MTK Tools )
>> Pascoal Fernandes ( For Testing )
>> At Last Me EndLess (Monty Kumar) Porter Of "PhilZ recovery"
Click to expand...
Click to collapse
:victoryress Thanks Button If u Like My Hard Work :victory:
I've been waiting for this. Great share. :good:
Hi,
Man, I'd love to find a version of PhilZ that would work with my LG V2O (H910) running Nougat! I'm not a TWRP fan.
TTYL
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
For Huawei Mediapad T1 10
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
READ THIS BEFORE DO ANYTHING:
First of all, keep in mind that this recovery is only for the Huawei Mediapad T1 10 variants (T1-A21L and T1-A21W) (codename: hwt1a21l). More details: link..
"How can i know if my device is the right one?":
If you are using EMUI 3.0., go to Settings
About tablet
Check Model number
If your device is T1-A21W (Wi-Fi variant) or T1-A21L (LTE variant) then it's the correct device
So please, if your device is not one of them then this recovery is not for your device.
Click to expand...
Click to collapse
Let me clarify some thing:
Since our device doesn't have any development support (no ROMs, no recoveries, mods, etc) i decided, many months ago, to bring it some development.
You may ask me why i'm posting a completely deprecated custom recovery for our device, and the why is simple:
Since i started trying to bring custom ROMs and recoveries, many months ago, this was one of the successfully ported recoveries i got. The other one, a twrp 2.8.6.0 recovery, it's almost unusable due to problems with the touchscreen response that i couldn't fix. I basically decided after a long time to open a thread for this recovery and share it because my main objetive was to compile a completely TWRP recovery (3.X version) but after a long and unsuccessfull battle i coudn't do it (yet).
So, i decided to share this one while i'm still trying to get the kernel source fully working to port a completely updated TWRP recovery.
Description
"PhilZ Touch 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
It also adds a full touch interface a completely configurable GUI."
Requirements:
-Unlocked bootloader
-One of the devices mentioned before
- A PC+USB cable or compatible aplication+Root to flash the recovery
Changes between the original version
Changed Philz Touch backgound to a more modern and adapted wallpaper.
Features (Careful: Most of them untested)
touch interface:
toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
written from scratch full touch code
basic scroll kinetics for faster scrolling on demand
safe full touch : no wrongly validations while scrolling
when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
adjust scroll sensitivity in a huge palette
adjust menu height in a huge palette
adjust touch accuracy
30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
user custom background png can be selected in addition to 30 solid colors option
show / hide background icon
show / hide bottom virtual buttons
show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
set number of bottom log rows to show
pause on logs mode: no more miss logs during zip installs
auto dim screen after user configurable delay
auto turn off screen after user configurable delay
adjust brightness and turn off screen with a gesture action
show/hide clock and remaining battery %, even during nandroid operations
clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
toggle vibrator on/off on touch
toggle key repeat for volume up/down scrolling when maintained pressed
key repeat also enabled for virtual buttons
set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
capture recovery screen shots with a gesture action (only some devices)
basic theme support
one file to save all settings
backup and restore settings file
backup and restore only GUI settings
reset to default settings option
prompt to restore your settings from a backup when they are wiped by a new ROM install
option to auto restore your settings from a backup without a prompt
all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
toggle menu options are automatically right aligned and menu text left aligned based on device display size
configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
true JB 4.2 migration: toggle between /data/media and /data/media/0
Secure recovery lock with passkey
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
cancel nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors backup/restore in stock clockworkmod or TWRP modes
advanced power options menu
detailed build info in About menu
Click to expand...
Click to collapse
What's working/not working
I have been testing it and all the basic functions (backups, instalations, partitions, brightness, touchscreen, etc) is working without problems as some extra features of the recovery, but i didn't test everything. In summary, is a completely functional recovery.
Instalation instrucctions:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To flash it to the recovery partition:
Code:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
Once finished reboot your device by pressing power and volume up to boot on the recovery.
Download link
Please do not make mirror of the download link, thanks you.
https://www.androidfilehost.com/?fid=745425885120721868
Credits
- eloygomez from HTCMania as the original recovery is from him
- @Koush for having created and maintaining cwm
- CyanogenMod
- @Tallustus from Team Skyfire for his great support over IRC
- @Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- @Chenglu for his unpacking tools and porting i9505
- kbc-developers for the base semi-touch code and much more
- [email protected] for his great job / support
- @sk8erwitskil for his recovery source, a great place to start learning
- @shoe63 for his help from the start across many devices
- @DooMLoRD for his work and help with Sony
- @[NUT] for his ports to Sony
- @wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- @dougiebee for his work on fixing time on many Qualcom devices
- @ausdim for all the support in developing kernels for i9505
- @dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- @Chainfire for his support (stock recovery flash) and all his work for the Android community
- @Phil3759 for the great original thread which is based mine.
- @ThePhantasma for pushing me to open this thread.
Contributors
@mustang_ssc
Created: 04/04/2017
Last update: 04/04/2017
Useful topics:
- Everything Huawei Mediapad T1 10
- How to root our device: Credits to @mann1
Reserved 2
Finally, we have a working recovery for this device! I am glad you share this.
Time to share the good news! :good:
@ThePhantasma for pushing me to open this thread.
Click to expand...
Click to collapse
Thank you.
Thank you for the recovery. Any custom ROMs available??
dilipg98 said:
Thank you for the recovery. Any custom ROMs available??
Click to expand...
Click to collapse
Not yet, i will try to make the stock rom of our device flashable with custom recoveries and after that i may try to port a CM11 or MIUI.
Anyway, that's not my main purpourse, the priority for me is to fix the issues of the kernel source in order to get completely updated recoveries and roms (TWRP 3.X, LineageOS 14.1, Slim7, etc).
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Mo3ta9em93 said:
please could someone give me a way to root huawei T1-A21L Androird 4.4.4 ??
Click to expand...
Click to collapse
Here i put a complete topic for it:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
mann1 said:
Huawei devices are pain in the a$$, i hardly rooted this model t1-a21l, just couple of days ago.
I've tried with most of the models that shares the same CPU and GPU chipset, but no luck till now with TWRP.
I also tried to port the stock recovery of Ascend G7, they share the same Msm8961, but i got the same problem, recovery never starts.
Click to expand...
Click to collapse
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
mustang_ssc said:
Yeah they are quite complicated.
I have tried to port many recoveries from many devices, most of them without luck, but i ported a couple of TWRP 2.8.X recoveries but the problem is that the touchscreen response gets crazy and it's almost unusable.
This recovery and the TWRP one are from the Huawei G620s/cherry, so if you want to try to port some recoveries or roms i would recommend you to try with the ones from that devices because it's the most similar and compatible device i have found for our tablet.
By the way, thanks for the great guide to root our device, i have pinned it to my second post
Click to expand...
Click to collapse
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
mann1 said:
Thank you so much , you've done great too with porting Philz :good:
I've tried a lot to port many twrps, but the most compatible ones were with
Huawei Y550
https://forum.xda-developers.com/android/help/to-root-huawei-y500-t2923318
https://forum.xda-developers.com/android/development/recovery-huawei-ascend-y550-t3294031
porting 2.8.xx gave me the same cranky touch function, but the rest of other functions work when you slowly touch them.
with 3.x.x they start w/o problems but there's no touch function.
the 2.8.xx that i ported is here
===
I guess the problem is in the (device tree blob dtb) file, by unpacking the TWRP y550 img file, i keep the kernel zImage file and i just port stock dtb from the the stock recovery.img of our device to the twrp, to get the cranky touch ported twrp.
===
you have the privilege of being able to compile the twrp from the scratch, so i suggest that you use the y550 source twrp files then readjust the "screen resolution to 800*1280, and reassign the x and y values to be adapted with our device.
===
I've tried to decompile the dtb to readable dts files of both twrp and stock with "device tree compiler" under Linux, but i got error.
===
these were the results of my tries
Click to expand...
Click to collapse
Looks really interesting, i think i never tried to port anything from that device.
It surprise me to see you got a TWRP 3.X to boot, i never got any one to boot. I will try to port some recoveries from that device but i guess to have the same issues that you have because i think i have been doing the same porting procedure you used.
The problems with the touchscreen may be the dtb file but I'm not sure why it happens because in this recovery is working fine, but I'm sure it will be related to incompatible screen resolution and touchscreen parameters (X and Y axis).
Also I've tried to compile many times a completely updated TWRP recovery directly from the source (and also LineageOS 14.1) but the main problem is the kernel source of our device which it gave me a lot of errors. Casually i think the main problem about this is a missing dts file exclusively for our tablet which indicates the screen parameters, and should be located at arch/arm/boot/dts/qcom/huawei_t110p0_a21l of the kernel source folder. Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
I might try what you told me about use the y550 source files to see how it goes. If you want anything feel free to contact me
mustang_ssc said:
Here you have my GitHub with the device tree, vendor blobs and kernel source of our device in case you find it useful: https://github.com/Mustang-ssc
Click to expand...
Click to collapse
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
mann1 said:
Hi,
Now I've downloaded the repo and everything to compile twrp, but I'm a lil confused with the repo command
I need to download "Minimal Sources" to compile twrp 5.1, what's the right "repo init..." command to get the sources for our device?
Click to expand...
Click to collapse
I sent you a PM :good:
mustang_ssc said:
Ok guys look what i've just got
For now there is still some work to do to have it completely functional because for example the wifi and bluetooth are not working.
Also i finally made the stock rom of our device flashable with my recovery, and i kept it lighter and prerooted. I will open new threads of this roms when everything is ready.
Click to expand...
Click to collapse
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
PinkOstrich said:
Good stuff, I was hoping that someone was working on the t10.
What's the current status on this port?
Click to expand...
Click to collapse
For now i have 4 different roms: CarbonROM, Pac-Man, CM11 and MIUI8. Obviously (and unfortunately) all of them based on kit kat as i cannot make the kernel source to work.
Now the main problem is that the camera and flash is not working, and a weird bug with the play store that doesn't allow to use it. This last one i don't find it logical as it shouldn't be a rom bug but i have tried many gapps and always getting the same bug (error rh-01)
The camera bug is not very relevant considering that our device is a tablet but if i can fix the play store issue i will probably upload some of the roms while i keep trying to fix the camera and flash.
wifi issues with rooted Mediapad T1 10 T1-A21L
I have access to quiet a few of these tablets (Mediapad T1 10 T1-A21L) - like more than 100 They have been used for various wifi-based demonstrations.
Recently they have begun showing an error message "Unfortunately IntegratedTest has stopped working", like every 2-5 minutes and their storage is filling up with very large logs files (which I also contribute to the IntegratedTest application). I haven't found anyone else with this issue.
The IntegratedTest application is a system app and cannot be removed without root. So I decided to try and follow the "- How to root our device" guide and root one of the devices and remove the application - which succeed. However now the wifi doesn't work.
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
jpihl_ said:
Is there anyway to "unroot" the device, or get back to the original, while having removed that annoying application? I would very much like to get the wifi back in a working state
The device works fine and I can access recovery mode and the device both responds both via adb and fastboot.
I'm pretty new to rooting and xda in general, so sorry if this is a stupid question or i posted this in the wrong place.
Click to expand...
Click to collapse
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
mann1 said:
It's quite easy task, run SuperSu app, and from settings, you'll find the "Full unroot" option, after that go back to the "how to root our device" you've already downloaded 2 boot images, the rooted and the origin stock one, reflash the origin stock one again.
Finally you have to get the stock recovery back to replace the philz, download the stock one from here
Use the stock ROM to have your system back.
Click to expand...
Click to collapse
Thanks for your response. I tried to follow your instructions - unfortunately without luck.
What I did:
1. "Full unroot" -> Removed SuperSU App (also su command no longer works - as expected) but still can't enable wifi.
2. Ran fastboot flash boot boot.img -> still can't enable wifi
3. Ran fastboot flash recovery recovery.img -> still can't enable wifi
Which leaves me with "still can't enable wifi" :/
{
"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