Database Develop

[RECOVERY][UNOFFICIAL] TWRP 3.1.x

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:
via Paypal​
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

'good,i can t wait。

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...

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

rexxxlo said:
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
Click to expand...
Click to collapse
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.

Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg

decatf said:
Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg
Click to expand...
Click to collapse
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.

mistersixt said:
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.
Click to expand...
Click to collapse
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.

decatf said:
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.
Click to expand...
Click to collapse
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.

mistersixt said:
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.
Click to expand...
Click to collapse
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.

decatf said:
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.
Click to expand...
Click to collapse
Bingo, this version seems to be running fine again on the p4!
Thanks a lot,
Kind regards, mistersixt.

getting eror 70 flashing gapps

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.

xdatroxx said:
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.
Click to expand...
Click to collapse
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.

decatf said:
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.
Click to expand...
Click to collapse
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)

xdatroxx said:
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)
Click to expand...
Click to collapse
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.

Thanks for your support and fast response.
Yes, I did!
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?

xdatroxx said:
Thanks for your support and fast response.
Yes, I did!
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?
Click to expand...
Click to collapse
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.

Thank you very much!!!
Recovery was successful. :good:

Sorry, but I got another error message when trying to flash Viper4Athmos (https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137).
Installation of ZIP file aborts with error code 4. Log is attached.
Thanks for taking a look!

Ramdisk Compression Exchanger - systemless SuperSU/root on non-gzipped ramdisks

Some of you might face the next error during systemless SuperSU install:
...
- Decompressing ramdisk
failed
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
...
This means that the ramdisk of your boot image was compressed in a non gzip format.
Unfortunately SuperSU can only decompress and tweak gzip compressed ramdisks up to now.
However i tried to make a little script that will uncompress your boot image/ramdisk and recompress it to gzip then after flashing SuperSU it recompresses the ramdisk to the original format.
This way one can achieve systemless root temporarily on such devices by installing SuperSU.
Idk maybe it can also be used for Magisk???
Download v1.1 (rce_univ.zip):
http://viid.me/qoESak
in case you face any proglems with the above version, try the old one v1.0 (rce_univ_1.0):
http://viid.me/qir1u5
How to:
Boot into TWRP 3.0.0 or above (never tested below) and install rce_univ.zip before and after SuperSU.zip!
Video: http://viid.me/quIbOi
Consider flashing Chainfire's Boot image signer (in case you get soft bricked after the above steps):
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Detailed description in comment nr.3 (https://forum.xda-developers.com/showpost.php?p=70428981&postcount=3)
Supported ramdisk compressions:
bzip2, lz4, lzo, lzma, xz
Requirements:
Unlocked bootloader on most newer (marshmallow and lollipop) devices
Don't expect it to be working on every device!
The script is basically fool proof. I mean if anything goes wrong it will promt you and quit.
Then you can simply restore your boot partition (if you didn't forget to back it up) and boot up normally and deal with the non rooted idea...
Also it's not supposed to mess up anything that would cost you a hard brick. Soft brick is only possible if you forget to make backup of your boot image or if you get SuperSU intalled and rec_univ.zip cannot recompress your ramdisk (this is pretty much impossible anyways)
Naturally there are those Samsung and Sony devices with some tricky boot images... idk. Never tested but most likely not gonna work.
Probably there will be many devices on which there are not enough space to decompress and recompress ramdisks/boot images in TWRP.
In comment nr. 2 i will collect the devices that are compatible with this script and the method itself.
If you can't find your device there as i said it's fool proof but you better be careful! You can simply test it by backing up your boot images between each install and with the mount mtp function you put it on PC (you can't quit TWRP during the whole process - i mean during step 2) and with carliv image kitchen (https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658) you check if you can unpack them normally.
Or if you don't care so much you just try and the worst case you reflash your framework...
If you are about to post any errors or complains do it the right way:
- attach recovery.log
- describe your device (model name, firmware version, ...)
- attach your boot image you backed up (upload it somewhere and link it)
If you are about to post a succesful attempt of a not yet added device:
- describe your device (model name, firmware version, ...)
- maybe link to its thread
No promises... and no responsibility i take... !!!
Please don't upload it anywhere else just use link to this thread!
I have to say thanks jcadduono for LazyFlasher boot image patcher script i used for the ramdisk compression exchanger and also thanks goes to Chainfire for SuperSU (especially for the boot image finder srcipt which is took from the SuperSU installer).
The xz archiver was used from XZ Utility For Android by Tukaani http://tukaani.org/xz/ - i hope he doesn't mind. Let me know if he does!

Supported devices until now:
Lg K8 - https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Lg K10 - https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Note 4 n910v (7.1.1 rom) https://forum.xda-developers.com/showpost.php?p=72491391&postcount=18

Detailed description
Systemless root with SuperSU on devices with non gzip compressed ramdisk bootimage
0. Download rce_univ.zip from here: http://viid.me/qir1u5 and download SuperSU (latest or there are some cases that requires earlier versions): https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 and put them on your sd card (external sd card is usually necessary since sometimes TWRP cannot decrypt your data partition/internal sd).
1. Unlock your bootloader
1.1. Additional step for those who has no "...device corrupt..." message during every boot up after unlocking bootloader on Marshmallow and some Lollipop devices(*)
- Boot into TWRP
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- from now on you should have the message at every boot up
2. Boot into TWRP
- cancel decrypt data
- keep system read only
- go to Backup -> Backup your boot image! Maybe it comes handy later.
- go back from backup to install and install rce_univ.zip right after install SuperSUxxx.zip and then rce_univ.zip again.
- do not wipe anything during and after this step, just reboot! (this might take a while and a few bootloops...)
Video guide: http://viid.me/quIbOi
(3.) Verified boot?
In case of soft brick (or if you're sure you need the proper signature in the end of your boot partition - cos your device has verified boot) try flashing Chainfire's Boot image signer as a very last step before rebooting from TWRP:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(*) on some devices if there is no "device corrupt" message at every boot up after bootloader unlock then anything you do or change in your boot image or system partition your device will not boot up anymore but turning off right after showing you that device corrupt message.
but if you do that trick as written in step 1.1 and that message appears at every boot up then most likely you're goot to go...
You can find some video guides on my thread for the above steps: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
Pricniple of the installer - rce_univ.zip
What the script does:
Install rce_univ.zip before SuperSU:
1. Finds the boot partition (same way as SuperSU)
2. Dumps the boot image and unpacks it
3. Determines the format the ramdisk was compressed in
4. Uncomresses it then recompresses to gzip (so SuperSU can handle it).
5. Repacks the boot image and flashes it back on boot partition
Here is where you install SuperSU
Install rce_univ.zip after SuperSU:
1. Finds the boot partition
2. Dumps the boot image and unpacks it
3. Reads back the original format of the ramdisk compression
4. Uncomresses it then recompresses the ramdisk with the original compression method(so now the device can handle it).
5. Repacks the boot image and flashes it back on boot partition
As about me:
I was not a complete noob when i started it however it took a lot of effort and time. If you care to understand a bit more what it's about and you want to follow my struggling this is where it started (you can click through the threads):
https://forum.xda-developers.com/apps/supersu/supersu-v2-66-installed-lz4-compressed-t3296508

didn't work at samsung galaxy S2, it only have 8Mb space at boot partition. any solution ?
edit i use LineageOS 14.1 (cm 14.1) android 7.1.1

haris1976 said:
didn't work at samsung galaxy S2, it only have 8Mb space at boot partition. any solution ?
edit i use LineageOS 14.1 (cm 14.1) android 7.1.1
Click to expand...
Click to collapse
Can attach recovery log? And maybe boot image that you backed up in TWRP

this recovery log

haris1976 said:
this recovery log
Click to expand...
Click to collapse
I can not fully open it (no editor can fully load it). Could you zip it and attach compressed or just attach again?

gottlasz said:
Can attach recovery log? And maybe boot image that you backed up in TWRP
Click to expand...
Click to collapse
back up boot from twrp
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
gottlasz said:
I can not fully open it (no editor can fully load it). Could you zip it and attach compressed or just attach again?
Click to expand...
Click to collapse
maybe tommorow i have bad connection when upload recovery & boot with the zip

haris1976 said:
back up boot from twrp
---------- Post added at 03:23 PM ---------- Previous post was at 03:05 PM ----------
maybe tommorow i have bad connection when upload recovery & boot with the zip
Click to expand...
Click to collapse
Okay, you can send it in PM if you want...

gottlasz said:
Okay, you can send it in PM if you want...
Click to expand...
Click to collapse
recovery & boot

haris1976 said:
this recovery log
Click to expand...
Click to collapse
Now i could open the recovery log.
Unfortunately this part means that even if it's a 3.0.2 TWRP something is missing:
"- Found boot partition at: /dev/block/mmcblk0p5- Dumping & unpacking original boot image...WARNING: linker: /tmp/boot_repack/tools/armv7/unpackbootimg: unused DT entry: type 0x6ffffef5 arg 0x560"
Maybe you should try with a newer version of TWRP if there is one.
Or if you follow my older guide which was a manual unpacking and repaking with carliv image kitchen, that could work.
Check my old guide: https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Anyways give me until tomorrow, ill take a look at the script maybe i can avoid this error.

gottlasz said:
Now i could open the recovery log.
Unfortunately this part means that even if it's a 3.0.2 TWRP something is missing:
"- Found boot partition at: /dev/block/mmcblk0p5- Dumping & unpacking original boot image...WARNING: linker: /tmp/boot_repack/tools/armv7/unpackbootimg: unused DT entry: type 0x6ffffef5 arg 0x560"
Maybe you should try with a newer version of TWRP if there is one.
Or if you follow my older guide which was a manual unpacking and repaking with carliv image kitchen, that could work.
Check my old guide: https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Anyways give me until tomorrow, ill take a look at the script maybe i can avoid this error.
Click to expand...
Click to collapse
Same error for me on LG K8 4G Vodafone Spain (LGK350n, build MRA58K, MT6735, Android 6.0), i fix it change booting the TWRP image to k350n10f (k8_10f_twrp.img, https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894). It avoid for me" Error: Unpacking boot image failed!- Aborting..."
Works like a charm!!! thanks to gottlasz and XDA group!
sorry for my english

You should recompile all the used binaries as static, that should avoid a lot of issues.
Also, don't bother with older Samsung (everything before S3) and older Sony devices (not really sure until when). These use non-standard boot images that are very tricky to patch without outright recompiling. It can be done - I have done it in the past - but it is a major hassle and very errorprone.

Chainfire said:
You should recompile all the used binaries as static, that should avoid a lot of issues.
Also, don't bother with older Samsung (everything before S3) and older Sony devices (not really sure until when). These use non-standard boot images that are very tricky to patch without outright recompiling. It can be done - I have done it in the past - but it is a major hassle and very errorprone.
Click to expand...
Click to collapse
Thank you Master!
I know about the compiling situation, however the problem is that i did not compile anything since the whole stuff is based on jcadduono's LazyFlasher. He compiled the binaries I only tweaked the script and added some stuff... i don't have the resources to compile. Now i'm collecting static binaries to exchange them in the installer in order to solve these compatibility issues.
Basically i just wanted to help some of those unfortunate as me who has lz4 or other compressed ramdisks and unable to intall SuperSU. Well..., at least a handful of them.

New version is up. A few TWRP related compatibility issues are solved.

gottlasz said:
New version is up. A few TWRP related compatibility issues are solved.
Click to expand...
Click to collapse
i test the new version but no luck
this is the recovery log

haris1976 said:
i test the new version but no luck
this is the recovery log
Click to expand...
Click to collapse
How far does supersu intaller goes?
I mean can it unpack your boot image?
Install only supersu and make a recovery log please.
I tried to unpack your boot image with carliv image kitchen and no luck...
I think supersu can't even unpack your boot image and then there is no chance to install it. Even if we could change the ramdisk compression...
Are you sure supersu intaller gives you the same error message as it is stated in the OP?
I believe you have a non standard boot image as chainfire talked about.

It works great on 7.1.1 roms on Note 4 n910v. Thanks!

[RECOVERY][OFFICIAL] TWRP 3.1.1 for Exynos

Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09

Thanks!

OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.

Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!

Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.

any chance for g800h support?

sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.

ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]

Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.

I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).

ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps

@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.

ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk

Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem

Here also this message in unofficial builds, don't tried it, but I think its still present in this version.

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...

fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually

Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.

ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.

So I have a few questions

some information: I have a rooted with magisk moto g(6). if you need more information, just ask.
question 1: probably the most important one, my USB debugging keeps turning off. after a reboot, it was on before I rebooted but now it's off. I want to know how to fix this and what in the world is making this happen.
question 2: my sim card isn't being detected, I don't know id this is related to my IMEI number being unknown which leads to my next question...
question 3: why is my IMEI number unknown? this one is self-explanatory and I don't know how to explain it more
Question 4: final question, can I update. I am running android 9 with security patch January 1, 2019.
this is my first post here and I hope I didn't make any errors. if you have an answer for any of these questions, please share your knowledge.
I have fixed questions 2 and 3 by reflashing stock images a few times
I also believe that fixed question 1 so now I just really need to know how to update

I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.

WoKoschekk said:
I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.
Click to expand...
Click to collapse
O that sounds like it would work, I used to flash 16 something because I didn't know 19.3 worked, definitely gonna make a few backups too

16??

WoKoschekk said:
16??
Click to expand...
Click to collapse
Yes I saw it in a guide once. Why can TWRP sometimes not see my internal storage, it says there is 0 bytes there. Also if my backup is in internal storage, does that mess anything up?
O and when I try to update, it loads into TWRP recovery. Help.

I think the best way is to give you a complete guide...
But this only works for PPSS29.55-37-7-2.
If your current FW is PPSS29.118-15-11-2 this method ends up in a bootloop!! Then follow this thread, please.
Find below two download links. One of them is the fstab.zip which contains the patched fstab.qcom file. Unzip it and put the file somewhere accessible for you while following this guide.
BACKUP YOUR DATA IF POSSIBLE!
I AM NOT RESPONSIBLE FOR ANY DAMAGES ON YOUR DEVICE!
1.) Flash the latest firmware based on your software channel from here
2.) Let the phone boot to "Hello Moto" just to be sure everything is fine.
3.) Reboot to bootloder and flash the latest TWRP via fastboot.
4.) Boot directly into recovery by choosing it in the bootloader's menu.
5.) The first boot takes a few seconds and then TWRP requests a password to decrypt /data => press "cancel"
6.) Format /data (do not wipe) to remove encryption. After that format /data a second time and reboot into recovery.
7.) Format /data again.
8.) Now mount /vendor, open the file explorer and go to "/vendor/etc" and erase the file "fstab.qcom". Copy the patched file in this directory. This will disable forceencryption on your device. The trick is to replace the word "forceencryption" by "encryptable" in line 9.
9.) Open the terminal and type these commands:
Code:
cd vendor/etc
chmod 644 fstab.qcom
touch -r gps.conf fstab.qcom
With the last command (it's optional) you restore the original timestamp of the file by copying it from another. I use gps.conf because it's pretty short and fast to type.
Check the commands with
Code:
ls -l fstab.qcom
The output should look like this:
Code:
-rw-r--r-- 1 root root 1680 2009-01-01 07:00 fstab.qcom
It's very important to have the right permissions -rw-r--r-- root root
10.) Almost done... Flash Magisk v19.3 and not the latest v20.3 or you will get a bootloop.
I don't know why it bootloops... But AFAIK the only difference between those versions are the signing keys that are used to sign the boot.img after patching it with Magisk.
While installing Magisk the .zip disables dm-verity so you don't need an additional tool for that.
11.) If you like you can delete some system apps or what ever you want.
12.) It's done! Reboot to system and enjoy your rooted and unencrypted Moto g6 with disabled dm-verity!!
Don't panic if your device reboots one time after a few seconds. That's normal.

I wish I knew about the fstab file, I assume it removes the need to do the formatting but I already set up everything after I figured the update thing out. Would it be worth it to try and do the fastab?
Also why does it say I can turn OEM unlocking on again in my developer settings? I find that weird. And why when I boot up do I get a screen like this
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
I would think that my code would be where it says ID. Also it's as accurate as I can make it but in reality the code is overlapping the contact stuff. Just wondering if this is normal or if it's a sign that my phone's gonna explode or something. And are there any custom ROMs I should look into?

What exactly is the problem??
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
To solve all the issues with your device you should flash a clean stock rom to get things into shape. There're several things messed up on your phone I think. A clean installation is the basic for all.

Bulbasaur Army said:
Would it be worth it to try and do the fastab?
Click to expand...
Click to collapse
Encrypted = you have to format /data every time before you are going to use TWRP
Decrypted = TWRP works perfect
Bulbasaur Army said:
Also why does it say I can turn OEM unlocking on again
Click to expand...
Click to collapse
Magisk enables the verity_state which leads to those options.
Bulbasaur Army said:
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
Click to expand...
Click to collapse
really?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
What about learning some basics before modifying your device?? I don't get in a car, sit down behind the wheel without even knowing how to drive.
I gave you a very detailed instruction about how to root your device. You will finally manage to get root or not.

I see, I already had my phone rooted but I didn't see the guide for fastab so I was wondering if I should apply it, I will attempt to do so later today. Thank you for all the help you have given.
PS: what does the "---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------" is it part of XDA?

[Treble Project] How to download and install Treble Project for J7 Prime

Steps to install Treble ROMs on Galaxy J7 Prime.
Prerequisite:
1. Flash TWRP recovery. For Treble Project I suggest version 3.2.1 here because there is an issue about mounting /preload partition with 3.2.3+. You can try newer versions for your choices. If you see /preload error, Some suggested to ignore this error.
2. For emergency, please download Stock ROM here. If you accidentally mess up your partitions or consistently bricks, Stock ROM will reset everything back to start.
Needed Files:
1. Files from Project Spaget X here.
Exynos7870_CreateVendor.zip is to create /vendor partition.
Exynos7870_ProjectSpaget_V3.0.zip is to install necessary for Treble Project.
Exynos7870_RevertVendor.zip is to delete /vendor partition, in case of uninstalling Treble Project.
2. Treble ROM with ARM64 A only here. My favorite Treble ROMs are Lineage, Arrow and Havoc. I am currently using Arrow.
3. ARM64 GAPPS here.
4. Kraken Kernal here or here. Please download for Treble only. RC12 is universal.
5. Magisk here.
Step I Flash Treble project:
1. boot TWRP recovery
2. wipe Data, Cache, Dalvik, System
3. flash Exynos7870_CreateVendor.zip and reboot to recovery
4. flash Exynos7870_ProjectSpaget_V3.0.zip
Step II Flash Treble ROM:
1. flash Treble ROM ARM64 A only, no need to reboot to recovery in order to install the ROM.
Edit: Reboot to Recovery > Install > press Install Image > choose your Rom.img
2. After flashing the ROM, I usually reboot to system in order to test whether or not the flashed ROM can boot nicely.
2.1 If the flashed ROM cannot boot or brick or bootloop in Logo, press Home + Power + Vol Down to force reboot to Bootloader and boot to recovery.
2.2 Back to recovery. wipe Data, Cache, Dalvik, System
2.3 flash Exynos7870_ProjectSpaget_V3.0.zip before flashing new Treble ROM.
Step III Flash ARM64 GAPPS:
1. Choose Wipe > Advanced Wipe > choose System > Repair > Resize. Sometimes you need to do this twice in order to resize since the first time will show error.
2. flash GAPPS
Step IV Flash Kraken Kernal:
1. Mount > System and Vendor partitions
2. flash KRAKEN-Kernel-RC12-universal7870-Treble-20200314.zip (The latest version of Kraken)
3. reboot to system
I usually reboot once to system before flashing Magisk.
Step V Flash Magisk:
1. Mount > System and Vendor partitions
2. flash Magisk to root
3. reboot to system
4. run Play Store and set up your account
5. run Magisk Manager. When you press Tap to start SafetyNet check, you will find out that ctsProfile: false.
Please note that Usually it will be installed when you have GAPPS installed. If not, you can install Magisk Manager manually.
6. choose Downloads > search "SafetyPatch by hackintosh" > download and install > reboot This will fix ctsProfile false to be true.
Now you are done the basice steps to flash Treble ROMs for your J7 Prime. Any questions please leave a message under the thread.
Cheers, :highfive::highfive::highfive:

Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
Click to expand...
Click to collapse
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help

dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help
Click to expand...
Click to collapse
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.

siamese007 said:
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.
Click to expand...
Click to collapse
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much

dctviphb2 said:
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much
Click to expand...
Click to collapse
You're welcome. I honestly never experience this kind of error.
I found a solution about this error on youtube.
This solution is to extract ROM file and edit updater-script file with notepad++.
Edit: try this Spaget X file. I followed this youtube tutorial trying to fix error 7 that you got when flashing Spaget X.
Another possibility of this error is Partition messed up.
I would try to flash stock ROM with Odin to reset everything to factory default.
Caution: Back up your data before flashing Stock ROM.
Follow the instruction of how to flash Stock ROM in the Stock ROM page or here. Flashing Stock ROM will also remove TWRP recovery and re-partition.
Hope one of this solution help, :highfive::highfive::highfive:

Thank you so much. I think the problem is I am using HROM, which has Repatition.zip, so I think that my partition has messed up, that the reason I face the issue. I will try to solve it with your idea. Thanks so much for helping me, if I can solve the problem I will tell you

Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much

dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
That's great NEWS. You've managed to find a solution for No OS installed error.
By the way, for the deep sleep problem that you mentioned, I also experience the same thing. My solution is to press home button to immediately wake the phone up from deep sleep.

[HELP]Treble Incompatible device (J7 PRIME)
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone

hussain_mdj said:
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone
Click to expand...
Click to collapse
Unpack .xz file

TWRP still doesn't detect the image
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
...
---------- Post added at 12:53 AM ---------- Previous post was at 12:48 AM ----------
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
i'm dummy dum so forgive and thenk

dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
There is a solution...in phh treble settings go to doze then turn on out of pocket feature....works like a charm for me.....
------------
HAPPY TO HELP..