First thanks to drgravy who compiled this TWRP build for the LG G Pad 8.3 GPE (V510); device name Palman, a link to the official TWRP download page will be posted once the appropriate section for (Palman) has been created.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help
Download:
TWRP 2.6.3.1 V510 Palman
How to flash:
Since this is a GPE Tab simply boot your device into fastboot. Easiest way is to do adb reboot bootloader.
Once booted into the bootloader simply issue this command:
fastboot flash recovery palman.img
Once done reboot into recovery and you should be greeted with TWRP.
CREDITS:
@Dees_Troy and team win for this wonderful recovery
Confirmed working on GPE version.
Unlocok bootloader and flash recovery or you can just do "fastboot boot palman.img" and it will boot in recovery without flashing it (so you get to keep stock recovery in case you need to run an OTA later).
Hi
I get the message "Waiting for the device", so how get the device in fastboot mode?
Thanks
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Ver3go said:
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Sorry for the dumb question, but where do I get the drivers for the GPE? I used Dalingrin's easy root script for the LGE, but "adb shell" doesn't work with that minimal adb, so I'm assuming I need to grab a different driver?
UPDATE: Still looking for the drivers. I downloaded the latest ADT and had it install the Google USB Driver, but still neither "adb shell" nor "fastboot devices" works properly. Just to answer the obvious question, yes, I've enabled USB Debugging in Developer Options. Any thoughts on how I can get past this hurdle so that I can get to a point where I can root a GPE device?
UPDATE 2: Okay, I figured it out and have GPE all nice and rooted now! Basically just follow the instructions to root a Nexus 5 but use the recovery image on this thread and you should be golden!
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
This package is for "palman" devices; this is a "v 500".
Click to expand...
Click to collapse
Is there any easy way to fix that?
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I might have an easy answer for you, give me a few minutes to try it out first.
---------- Post added at 04:32 PM ---------- Previous post was at 04:06 PM ----------
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I think you can do this two ways, flash back to the stock recovery, or just run the stock recovery once from the bootloader. Flashing back to the stock recovery is probably the safest option, however I have an idea if you don't want to have to go back and forth.
Disclaimer, I'm an NOT expert with this so it may not work.....
Ok, for either option you'll need the stock recovery. You can download it from HERE (Stolen from AutoPrime's post).
I recommend putting the update ZIP and recovery image file in a folder of your root path (for me "C:\android\")
Here's my idea, have fastboot just boot the stock recovery once.
Make sure ADB debugging is enabled in "Developer Options"
Connect your USB cable and run
Code:
adb reboot bootloader
Your tablet should reboot and your should see the bootloader screen, once you see the screen run
Code:
fastboot boot C:\android\17-recovery.img
fastboot should show you progress indicator and once it is finished your tablet should see a red exclamation mark. press the power button and then the vol. up button. This should show options 1. Reboot System 2. ADB Sideload, use the volume keys to select adb sideload then press the power key to select.
then
Code:
adb sideload C:\android\a0bd45922b5958a38acef76f577f527268ef90db.signed-KRT16O.L004_user-KOT49H.L004_user_update.zip
I think it will work, not sure if it will keep TWRP or overwrite it. Like I said earlier, I'm not an expert.
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
OTA updates are not working with a custom recovery like twrp. Either flash back to stock or wait for the developers to compile and release the updates as zip packages that you can flash from the custom recovery menu. Look what a developer said about this here http://forum.xda-developers.com/showpost.php?p=48150524&postcount=31
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Archon810 said:
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Click to expand...
Click to collapse
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
djkinetic said:
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
Click to expand...
Click to collapse
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Archon810 said:
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Click to expand...
Click to collapse
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
The problem is /sdcard/TWRP/ is completely empty. There are no files in there. I even checked using shell and ls -al.
And yeah, I didn't let it reboot after unlocking.
I actually have a replacement en route from Google to address a yellow tinted display. I think I'll wait until that gets here, let it update to 4.4.2, and then go through this process on that device.
sorry, how do you open the recovery?
djkinetic said:
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
Click to expand...
Click to collapse
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
I'm probably earlier in the process than you @Archon810. I have similar issues have a decreasing feeling that I will solve this any time soon. At this point, if I fastboot boot the recovery palman.img and try to install the noroot V510 zip image provided, I get the binary link error which was present on my Nexus 7 on twrp for awhile. I backleleveled the twrp to 2.6.3.0 on the Nexus 7 and this stopped that problem. More seriously, after all the stuff I've done to fix things, I fear I have probably borked things more than fixed them.
Now after any attempt at flashing anything in recovery whether I install the recovery or just boot from it, the result is binary file error.
Going to try restoring the default image and doing things again.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Any way we can get a CWM build for V510 so that we can avoid the binary error from TWRP?
djkinetic said:
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
Yeah, as per the other thread, this did the trick.
Related
Unofficial release -TWRP recovery for the Galaxy Tab S2 - SM-T713/719/813/819, Qualcomm MSM8976
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
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
Mar 11, 2017
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.
Update 1/4/2017
TWRP 3.1.0-1 MM/NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from source
System image backup
F2FS support >> To be added
Twrp app support
Bugs:
Reboot to recovery loop when using reboot utilities. Use hardkeys combo only to boot to recovery POWER + HOME + VOL UP
If you get stuck in a recovery loop reflash TWRP with auto-reboot enabled.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 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.
DOWNLOAD:
TWRP 3.1.0-1 - Nougat
twrp_3.1.0-1_sm-t713_14417n
twrp_3.1.0-1_sm-t719_13417n
twrp_3.1.0-1_sm-t813_14417n
twrp_3.1.0-1_sm-t819_14417n
TWRP 3.1.0-1 - Lollipop/Marshmallow
twrp_3.1.0-1_sm-t713_1417
twrp_3.1.0-1_sm-t719_1417
twrp_3.1.0-1_sm-t813_1417
twrp_3.1.0-1_sm-t819_1417
TWRP 3.0.2-1
SM-T713/719
twrp_3.0.2-1_sm-t713
SM-T813
twrp_3.0.2-1_sm-t813
SM-T819
twrp_3.0.2-1_sm-t819_31816
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after 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 SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Does rooting require a permissive kernel?
DeeXii said:
Does rooting require a permissive kernel?
Click to expand...
Click to collapse
Rooting doesn't, custom recovery might.
I don't know yet until someone reports.
I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.
dalingrin said:
I was not able to mount /data in TWRP however.
Click to expand...
Click to collapse
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted
dalingrin said:
I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.
Click to expand...
Click to collapse
York2k16 said:
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted
Click to expand...
Click to collapse
Thanks for testing and posting the logs. @York2k16 Correct the error mounting data is because of encryption. Twrp is unable to find the encryption key.
It's true Android 6 devices are encrypted by default, but don't need to be.
Work around for now would be not to use encryption until I find the solution.
The issue with adb is because of Samsungs stock kernel.
I need to recompile it with root protection removed.
Unfortunately no sources are available as yet.
Well at least we have a working recovery and a root solution.
Can you confirm a few things:
UI orientation, portrait or landscape?
UI colour?
All other options and features working correctly?
Thanks, well done for probably being the first in the world to have a rooted S2 VE 8.0
ashyx said:
Work around for now would be not to use encryption until I find the solution.
Click to expand...
Click to collapse
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?
TWRP does not work properly on T813. I am unable to use it because can not click on buttons
York2k16 said:
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?
Click to expand...
Click to collapse
you need to format the data partition in TWRP to remove encryption.
whynottoday said:
TWRP does not work properly on T813. I am unable to use it because can not click on buttons
Click to expand...
Click to collapse
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?
@dalingrin
Does this at least ask for the encryption password?
https://www.androidfilehost.com/?fid=24572330218881914
Also whilst in the android OS could you post me the output of
ls -l /dev/block/bootdevice/by-name/
Thanks.
ashyx said:
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?
Click to expand...
Click to collapse
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app
whynottoday said:
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.
ashyx said:
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.
Click to expand...
Click to collapse
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app
whynottoday said:
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Mount issue, you mean data?
Can you post the recovery.log.
You will find it under Advanced in twrp.
ashyx said:
mount issue, you mean data?
Can you post the recovery.log.
You will find it under advanced in twrp.
Click to expand...
Click to collapse
here attached
whynottoday said:
here attached
Click to expand...
Click to collapse
try this, could you post the log too please.
https://www.androidfilehost.com/?fid=24572330218881937
I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?
DeeXii said:
I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?
Click to expand...
Click to collapse
Can you test the link in post #11.
Can you mount data?
ashyx said:
Can you test the link in post #17.
Can you mount data?
Click to expand...
Click to collapse
Give me a few...
I'm finishing up some work things and uploading stock to AFH.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
ashyx said:
Can you test the link in post #11.
Can you mount data?
Click to expand...
Click to collapse
Post #17 says its for T813; Does that matter?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[kagura] TWRP 3.1.1-0 touch recovery, Tool/Utility for the Sony Xperia XZ
Contributors
AndroPlus
Source Code: https://github.com/TeamWin/android_device_sony_kagura
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2017-08-28
Now it's official!
Make a material version?
Sent from my F8332 using Tapatalk
Can someone post a detailed instruction please? I followed the TWRP instructions but kept getting stuck on "waiting for devices" on fastboot. I tried several different drivers suggested in other threads but none worked for me
@AndroPlus Do we need an unlocked bootloader for this?
Yes we do.
@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
edit: problem solved I installed your kernel with: sudo fastboot flash boot boot.img
and now I can boot into TWRP and LED during boot shows light. Seems to be a really great kernel.
paulle said:
@AndroPlus, please maybe you can give some hint. I unlocked the bootloader (worked), when I installed TWRP with fastboot and the installation seemed to be sucessful, but I cant boot into TWRP. During boot I'm pressing vol+, but nothing happens. Even the LED shows no light during boot. What I did wrong or what can I do to boot into TWRP?
Click to expand...
Click to collapse
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).
AndroPlus said:
1. Turn your device off.
2. At the same time, press the Power button and Volume down until your device vibrates.
3. Quickly release the Power button, but keep pressing Volume down (5 sec or more).
Click to expand...
Click to collapse
Thank you, this method worked too.
@AndroPlus will that work with the dual Sim version F8332 also?
hanaheeno said:
@AndroPlus will that work with the dual Sim version F8332 also?
Click to expand...
Click to collapse
yes
Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?
hanaheeno said:
Thanks a lot for your great amazing efforts @AndroPlus, is there any need to unlock the bootloader prior to rooting or flashing TWRP? And if yes, is it simply booting into fastboot and running the command "fastboot oem unlock" or enabling it from the Developer Options?
Click to expand...
Click to collapse
You have to enable oem unlock in developer options and run "fastboot oem unlock", then flash my custom kernel.
Because of strict security, we have to edit kernel to disable sony_ric and dm-verity to root if you want to custom /system.
If you can use system-less SuperSU you don't need to flash custom kernel.
Restore bug?
I just restored my backup and IMEI was gone. So the backup as such works fine besides the IMEI. Consequently I couldn't connect to the mobile network. I had to flashtool the original rom and restart the whole process.
Anyone else experienced such a problem?
I've repacked the 250 stock kernel with everything (except twrp, indeed). I use your recovery, and it works fine so far. But from system, I can't boot into twrp directly (e. g. from Titanium Backup or NeoPowerMenu).
For any help thanks in advance!
Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks
drakegao said:
Hi, I flashed the twrp.img, but when I tried wipe or install rom to xperia XZ, I got can't unmount system, 'device or resource busy' error. Any ideas how to fix it? Thanks
Click to expand...
Click to collapse
See post #13 (3 posts above yours) - doing this does the trick
Klaus N. said:
See post #13 (3 posts above yours) - doing this does the trick
Click to expand...
Click to collapse
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool
drakegao said:
Thanks give a try. Will this twrp work on UK-customized rom? I flashed that rom using flash tool
Click to expand...
Click to collapse
Yes, indeed.
No boot in recovery
Problem: Unlock done and OK, flashed TWRP and OK. But I cannot boot in TWRP. Not with buttons, not with adb. I see only the message, that my device is unlocked.... The LED ist dark.
Today I flashed the kernel v4 and Ok, flashed TWRP again and ok, same result. No boot in recovery. Only the f***in message that my device is unlocked, Firmware is..... . 260 and a German xz single Sim.
Any Idea? Sorry for my poor English.
Team Win Recovery Project 3.1.1-0
This is for the A2017, A2017U, and A2017G.
WARNING: The ZTE Axon 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/zteaxon7.html
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
UNLOCKING YOUR BOOTLOADER
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
A2017U or A2017 users can simply unlock from EDL mode using MiFlash here.
I do not have a method for A2017G, there may be other threads on XDA to guide you through the process.
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Unlock your bootloader! See above!
{
"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"
}
Download TWRP for the ZTE Axon 7.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] button while your device reboots or boots from power off.
Once you're in fastboot with your bootloader unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with Magisk:
Download the latest Magisk stable by topjohnwu.
Without exiting TWRP, transfer the Magisk zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.1.1-0 (twrp.me) - See release details here!
v3.1.0-0 (twrp.me) - See release details here!
v3.0.4-1 (build.nethunter.com) - Fix crash on selecting reboot with an empty data partition, add Data backup warnings
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-1 (twrp.me) - Use crypto libraries from ROM (Nougat support). Fix USB OTG and Fast Charging. Reduce boot times.
v3.0.3-0 (twrp.me) - Renamed to ailsa_ii, Persist merged with EFS, Modem no longer mounted, Backup/Restore/Flash Bluetooth/System Image added. LA.HB.1.3.1.c1-19500-8x96.0 + Linux 3.18.45.
v3.0.2-0 (twrp.me) - Initial release.
FEATURES
MTP support
USB OTG storage support
Legacy USB Mass Storage mode support - use your phone like an SDCard reader or flash drive!
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows ZTE full OTA flashing (only for A2017U firmware)
KNOWN ISSUES
F2FS takes a long time to boot, see below.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_zte_ailsa_ii (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the ZTE Axon 7, Tool/Utility for the ZTE Axon 7
Contributors
jcadduono, Team Win
Source Code: https://github.com/TeamWin/android_device_zte_ailsa_ii
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-02-08
Created 2016-12-09
Last Updated 2017-11-25
Link does not work is there a typo?
lokissmile said:
Link does not work is there a typo?
Click to expand...
Click to collapse
Nope, bigbiff is just taking long time to hit the go button on jenkins to build the device and rebuild twrp.me lol
I think he fell asleep
You can use this for now: https://build.nethunter.com/test-builds/twrp/zte/twrp-3.0.2-0-a2017u.img
Downloaded and installed although not sure how this differs from the one in the unlock thread. Made a backup everything seems OK. Thanks!
lafester said:
Downloaded and installed although not sure how this differs from the one in the unlock thread. Made a backup everything seems OK. Thanks!
Click to expand...
Click to collapse
It shouldn't be any different, or any differences there are should be minimal.
One (and maybe only) notable difference might be that it uses ZTE's USB configuration rather than Google's.
It also supports legacy mass storage. (accessing sdcard like a flash drive, instead of MTP)
I should also add that it's pretty much 1/3 of the size too lol.
UnjustifiedDev's unofficial TWRP is 3.0.2-2. I recall people were having issues with restoring some partitions (mostly EFS), so he backported the bugfix from the 7.0 TWRP code, which seemed to have fixed the issues. Does this official build include that bugfix?
Is there any technical reason why this version shouldn't be installed on A2017G?
xtermmin said:
UnjustifiedDev's unofficial TWRP is 3.0.2-2. I recall people were having issues with restoring some partitions (mostly EFS), so he backported the bugfix from the 7.0 TWRP code, which seemed to have fixed the issues. Does this official build include that bugfix?
Click to expand...
Click to collapse
That bug was fixed in September on the 6.0 branch.
_phk_ said:
Is there any technical reason why this version shouldn't be installed on A2017G?
Click to expand...
Click to collapse
I don't have any technical reason, just from what I've read it won't boot. You can try it, let me know what happens. Actually please do, because if it does boot it would be quite pleasing and I'd end up unifying them.
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
celoxocis said:
...If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail...
Click to expand...
Click to collapse
So far, none of the OTAs (at least for the US model) have done a check of persist, but who knows if they will for Nougat.
celoxocis said:
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
Click to expand...
Click to collapse
It uses a custom very minimal kernel configuration with modifications to make it more compatible with TWRP.
Why does modification of persist matter? Persist can't affect OTAs as it's meant to be modified, it's only a firmware/calibration cache.
If it ever had an issue you could simply type:
make_ext4fs /dev/block/bootdevice/by-name/persist
CM should not modify any partitions that are meant to be static.
The only partitions that will need to be fixed to take OTAs should be: boot, system, recovery, modem (NON-HLOS.bin)
The only reason modem needs to be fixed is because it's used in TWRP and I can't enable both backup and read-only at the same time.
Update: I'll just make two entries, backup/restore for raw modem emmc, and read-only mount for decrypt. (should be safe to do this with mounttodecrypt unmounting it)
xtermmin said:
So far, none of the OTAs (at least for the US model) have done a check of persist, but who knows if they will for Nougat.
Click to expand...
Click to collapse
They will not. There is no logical reason to check a partition that is designed to be modified.
In fact, I'll add Persist (calibration data) to the Wipe page!
jcadduono said:
It uses a custom very minimal kernel configuration with modifications to make it more compatible with TWRP.
Why does modification of persist matter? Persist can't affect OTAs as it's meant to be modified, it's only a firmware/calibration cache.
If it ever had an issue you could simply type:
make_ext4fs /dev/block/bootdevice/by-name/persist
Click to expand...
Click to collapse
Thanks for the clarification. I just remember when I was dirty flashing CM13 months ago when doing one of my devices bring-up. TWRP would complain with error 7 (I think?).
When I run a diff of the partitions it touched (I checked all init.rc's) I found the difference in persist. Reverting back the persist with DD (I always do a DD backup of my untouched devices, on all partitions before messing with them and store them on my NAS). The dirty flash went fine. Ever since that I include persist in my TWRP's.
I don't mind not having it in TWRP. I can bake my own anytime
celoxocis said:
Thanks for the clarification. I just remember when I was dirty flashing CM13 months ago when doing one of my devices bring-up. TWRP would complain with error 7 (I think?).
When I run a diff of the partitions it touched (I checked all init.rc's) I found the difference in persist. Reverting back the persist with DD (I always do a DD backup of my untouched devices, on all partitions before messing with them and store them on my NAS). The dirty flash went fine. Ever since that I include persist in my TWRP's.
I don't mind not having it in TWRP. I can bake my own anytime
Click to expand...
Click to collapse
I just replaced the -0 version, new one has modem read only and persist shows up in wipe page as "Persist (calibration data)" so people know what they're wiping.
There's a lot of partitions that seem scary and screw up your device when they're corrupt but you can just either format them (in the case of persist) or dd zeros to them (in the case of misc, modemst1, modemst2, efsg, and efsc) and the OS/firmware will regenerate everything on boot like you just took it out of the box.
any reason to flash this version of TWRP over the one UnjustifiedDev's made?? I can just flash the twrp.img file right?
celoxocis said:
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
Click to expand...
Click to collapse
I was under the impression that you couldn't install OTAb updates with an unlocked bootloader anyway. Is this not true?
abdi7451 said:
I was under the impression that you couldn't install OTAb updates with an unlocked bootloader anyway. Is this not true?
Click to expand...
Click to collapse
Bootloader status hasn't been checked by the OTAs so far (on the US model anyway). I've been able to go from a bootloader unlocked B20 -> official B27 OTA -> TWRP+CM13 -> Restore my B27 backup in TWRP + reflash stock recovery -> official B29 OTA -> reflash TWRP+CM13. As long as you are completely stock besides the bootloader, you can apply OTAs fine. (you can check the updater script in the OTA files for specifics on what it checks and what it patches)
xtermmin said:
Bootloader status hasn't been checked by the OTAs so far (on the US model anyway). I've been able to go from a bootloader unlocked B20 -> official B27 OTA -> TWRP+CM13 -> Restore my B27 backup in TWRP + reflash stock recovery -> official B29 OTA -> reflash TWRP+CM13. As long as you are completely stock besides the bootloader, you can apply OTAs fine. (you can check the updater script in the OTA files for specifics on what it checks and what it patches)
Click to expand...
Click to collapse
I am rooted and unlocked bootloader. How do apply the stock recovery in order to receive OTA updates?
Just wanna clarify this... B20 bootloader allows the fastboot OEM unlock command, and once you're unlocked, you can flash any bootloader you want. Flashing B29 bootloader does not lock you, once unlocked, always unlocked. Unless you relock it yourself. You can even go older than B20 bootloader. Feel free to play around with BL versions. I like B20 because no stupid 5 second warning thing.
If I already have the unofficial version for TWRP should I install this one over it or is it really the same thing?
@jcadduono, I think most people would find it helpful if you could list what's different between the now official version and @Unjustified Dev's version, as I know they've been developed semi in parallel.
Unofficial release -TWRP recovery for the Galaxy A7 - SM-A720F/DS, Exynos 7880
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
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
Mar 11, 2017
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 FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Update 12/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
NOTE: THIS IS CURRENTLY IN THE TESTING STAGE, THERE MAYBE BUGS, IT MAY NOT BOOT AT ALL. I DON'T OWN THIS DEVICE. I CAN'T FIX ISSUES IF PEOPLE DON'T POST RECOVERY LOGS OR PROPERLY DESCRIBE THE ISSUE. STOCK RECOVERY IS PROVIDED BELOW IF NEEDED.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7.
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 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.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-a720f_12417
Stock recovery: A720FXXU1AQC5_stock_recovery
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after 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 SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Hands off.
As usual nobody can find the time to report back.
Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"
moistcity said:
Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"
Click to expand...
Click to collapse
Can you save and post the recovery.log file.
ashyx said:
Can you save and post the recovery.log file.
Click to expand...
Click to collapse
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.
moistcity said:
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.
Click to expand...
Click to collapse
Just put it on pastebin.com and just post the link without the https://pastebin.com
OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?
ashyx said:
OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?
Click to expand...
Click to collapse
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.
moistcity said:
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.
Click to expand...
Click to collapse
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?
ashyx said:
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?
Click to expand...
Click to collapse
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY
moistcity said:
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY
Click to expand...
Click to collapse
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.
ashyx said:
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.
Click to expand...
Click to collapse
Please do. I'd want to root my A720F and remove these annoying bloat.
moistcity said:
Please do. I'd want to root my A720F and remove these annoying bloat.
Click to expand...
Click to collapse
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.
ashyx said:
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.
Click to expand...
Click to collapse
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP
moistcity said:
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP
Click to expand...
Click to collapse
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.
ashyx said:
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.
Click to expand...
Click to collapse
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?
moistcity said:
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?
Click to expand...
Click to collapse
The recovery log changes each time recovery is booted into.
If it's auto rebooting it would be difficult to catch it as it may not catch the error.
You can use the command below with ADB to try and grab it before it reboots.
Disable MTP then do:
adb devices
adb pull /tmp/recovery.log
There are also alternatives to get root.
You can try PHH Superuser.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Managed to pull the recovery log before the phone reboots itself.
Code:
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.002642 seconds, 757B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000393 seconds, 7.5KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000563 seconds, 17.3KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.001912 seconds, 0B/s
/tmp/updater: line 971: /system/toolbox: not found
- Extracting files
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
ashyx said:
There are also alternatives to get root.
You can try PHH Superuser.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Code:
adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.
moistcity said:
Managed to pull the recovery log before the phone reboots itself.
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.
Click to expand...
Click to collapse
Magisk and phh are both open source.
You don't need the root patch. If you want to keep your data unencrypted then you will need to flash the no-verity-no-encrypt_ashyx patch.
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A810F/DS, Exynos 7420
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
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
Mar 11, 2017
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.
Update 17/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
How we got here: https://forum.xda-developers.com/sa...w-time-to-getting-support-a8-2016-sm-t3511148
Instructions:
Flash with ODIN 3.10.7.
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 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.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-a810f_17417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after 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 SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, my testers(majinawaz, RootAgain)
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Awesome work dear if i able to buy a beer for you i must buy it
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
ivanox1972 said:
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
Click to expand...
Click to collapse
Post the recovery log file, so I can take a look.
How boss and which to do and to send result of it?
ivanox1972 said:
how boss and which to do and to send result of it?
Click to expand...
Click to collapse
twrp > advanced > save log
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
ivanox1972 said:
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
Click to expand...
Click to collapse
It's a protected partition so it can't mount. I should just remove it from the fstab.
You can just ignore it.
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
ivanox1972 said:
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
Click to expand...
Click to collapse
I don't see why not, the main partitions are able to be backed up.
After phone user Super burn recovery and their code is the code?
I could not do it. Do you have a video? Mount data failed
Awesome work
@ashyx Hi buddy, adb doesnt seems to work in twrp
AL_IRAQI said:
@ashyx Hi buddy, adb doesnt seems to work in twrp
Click to expand...
Click to collapse
Disable MTP in TWRP.
ashyx said:
Disable MTP in TWRP.
Click to expand...
Click to collapse
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
AL_IRAQI said:
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
Click to expand...
Click to collapse
I'd suggest installing the ADB drivers whilst in recovery mode.
Check device manager has detected it as an ADB device.
Hello ashyx adb is not working and shows adb device offline any solution please
[email protected] said:
Hello ashyx adb is not working and shows adb device offline any solution please
Click to expand...
Click to collapse
Disable MTP in TWRP first.
Thanks for your reply i will try it and reply you soon bro