[RECOVERY][UNOFFICIAL] TWRP 3.1.x

Search This thread

decatf

Senior Member
Dec 27, 2011
649
2,674
UNOFFICIAL TeamWin Recovery Project
for
Samsung Galaxy Tab 10.1
(p4wifi / GT-P7510)
(p4 / GT-P7500)
(p4tmo / SGH-T859)

Downloads
Mirror

Changelog:
Code:
3.1.1-20171009_v2
 - Fix issue with some updater script functions.

3.1.1-20171009
 - Use correct ramconsole address.

3.0.3-20170120
 - Compile on android-6.0 base

3.0.3-0 (20161229-p4wifi)
 - Update prebuilt kernel

3.0.3-0
 - Fix adb sideload
 - Enable TRIM
 - Reduce GPU carveout size
 - Update F2FS
 - Compile on Android 7.1.1 base

Donate:

XDA:DevDB Information
TWRP 3.1.x, Tool/Utility for the Samsung Galaxy Tab 10.1

Contributors
decatf
Source Code: https://github.com/decatf


Version Information
Status: Stable

Created 2016-12-19
Last Updated 2019-05-01
 

ENRIQUEMM

Senior Member
Jan 20, 2014
287
167
Samsung Gear S3
Moto G10
Update from twrp 3.0.2 and after reboot in the new version only perform a cache cleaning and dalvik-cache, it was done indefinitely and after twenty minutes I had to restart by pressing the power button for a few seconds, Reboot so you might have completed the cleanup. How can I get a log of the bug? Maybe help him to correct it.
Sorry for my bad English...
 

rexxxlo

Senior Member
May 13, 2011
127
0
buffalo
i tried this last night
it installed fine and boots to recovery fine,

but when i tried to install a new rom it freezes and i have to reboot it by holding the power button

the same thing happens if i try to do a wipe
 

mistersixt

Senior Member
Jun 17, 2011
467
217
i tried this last night
it installed fine and boots to recovery fine,

but when i tried to install a new rom it freezes and i have to reboot it by holding the power button

the same thing happens if i try to do a wipe

Same here on the p4: formatting partitions or installing images never end (and one cannot see any error/warning either). And it the same behaviour when trying to push files via adb while the formatting process or the install of an image hangs --> simply nothing happens (it hangs,too, like if it is blocked).

Fortunately I had an old 2.8.7.0 version on my p4, so this version 3.0.3.0 definately is not working properly on the p4.

Let me know in case I can do some logging or debugging.

Kind regards, mistersixt.
 

decatf

Senior Member
Dec 27, 2011
649
2,674
Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg
 

mistersixt

Senior Member
Jun 17, 2011
467
217
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.

I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.

Kind regards, mistersixt.
 

decatf

Senior Member
Dec 27, 2011
649
2,674
I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.

Kind regards, mistersixt.

Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.
 

xdatroxx

Member
Nov 17, 2011
39
2
Recovery unsucessful

I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.
 

decatf

Senior Member
Dec 27, 2011
649
2,674
I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.

Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.
 

decatf

Senior Member
Dec 27, 2011
649
2,674
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)

Did you create a file or folder at /data/app/com.android.vending-1.apk ? Perhaps from one of the methods to prevent Play Services from updating? I can reproduce the same issue by doing this.
 

xdatroxx

Member
Nov 17, 2011
39
2
Thanks for your support and fast response.
Yes, I did! :D
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?
 
Last edited:

decatf

Senior Member
Dec 27, 2011
649
2,674
Thanks for your support and fast response.
Yes, I did! :D
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?

The permissions are too restrictive such that recovery can't overwrite that file.

Remove that file then restore.
Code:
chattr -i /data/app/com.android.vending-1.apk
rm /data/app/com.android.vending-1.apk

You don't need that hack anymore. Install Play Services 10.5.
 
  • Like
Reactions: xdatroxx

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    UNOFFICIAL TeamWin Recovery Project
    for
    Samsung Galaxy Tab 10.1
    (p4wifi / GT-P7510)
    (p4 / GT-P7500)
    (p4tmo / SGH-T859)

    Downloads
    Mirror

    Changelog:
    Code:
    3.1.1-20171009_v2
     - Fix issue with some updater script functions.
    
    3.1.1-20171009
     - Use correct ramconsole address.
    
    3.0.3-20170120
     - Compile on android-6.0 base
    
    3.0.3-0 (20161229-p4wifi)
     - Update prebuilt kernel
    
    3.0.3-0
     - Fix adb sideload
     - Enable TRIM
     - Reduce GPU carveout size
     - Update F2FS
     - Compile on Android 7.1.1 base

    Donate:

    XDA:DevDB Information
    TWRP 3.1.x, Tool/Utility for the Samsung Galaxy Tab 10.1

    Contributors
    decatf
    Source Code: https://github.com/decatf


    Version Information
    Status: Stable

    Created 2016-12-19
    Last Updated 2019-05-01
    2
    I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.

    Kind regards, mistersixt.

    Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.
    2
    Updated to 3.1.1-20171009_v2. Fixes issues with some update-binary functions.

    The kernel was updated. The recovery binaries were repackaged from the previous version. Hence the old date string.
    1
    Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.

    Bingo, this version seems to be running fine again on the p4!

    Thanks a lot,

    Kind regards, mistersixt.
    1
    @maximalandroid
    twrp311-20180416-BIGSYS.zip is only for AOSP 8.1, it use a hidden partition for the system memory.

    You have to use older gapps version from 2018 but best performance is without gapps
    ok, thanks I only want the gapps for access to stuff like play books, which would of been downloaded with play store, but since play store no longer seems to work that hard, also I was having problems with the AOSP 8.1 OS, when installed with open gapps, it seems to cause the device to hard freeze now, and apart of that play store , something google serives seems to be crashing on it another problem, I just haven't not used this old tablet for anything, I turn it on this week to try to at least make it work as a ebook reader, I don't use my old tablet for much since I do have a newer one that can run android 11. I can manually install play books version for the correct android if I have to with that Apk installer if I recall they have, just wanted to get the play store working, but again this device is no longer supported, so it makes normal stuff on the old tablet harder to do. I hit like on your post, there doesn't seem to be a thanks button. :)