TWRP 3.3.0.0 shows "Digest verification failed" - LG G6 Guides, News, & Discussion

TWRP is unable to install any ROM on my G6 due to the "Digest verification failed" error.
I've updated TWRP to the latest version, which at the moment is 3.3.0.0.
I've try the [ROM][Stock] LG-H870 OPEN EU 20I ROM, Lineage and a few others, the situation is always the same.
I have placed the MD5 file next to the custom ROM file (the stock one above), I have searched for the solution for over 4 hours in youtube, (hindu-english sounds terrible...), xda, github and other sites, but haven't came up with the solution... TWRP is also showing that it is unable to read internal memory of the phone - I have to format DATA to exFat, and then back to ext4, than it can see internal storage.
I have downloaded the ROM files in SD card, and placed it into the phone, I have downloaded the ROM files directly through the phone via browser... nothing helps.
Any idea?

thread closed as per OP request

Related

Cyanogenmod error 7, tried solutions but I'm not getting anywhere, help a noob please

UPDATE 6/19
So I installed CM12 12 or 13 require 23C, 24B, or 35 (TWRP 2.8. has those versions mentioned in the fail error script)
I kept getting the boot error and so I started over and flashed KDZ's in order from 10 to 23c
With the 23c you can use the one click program to root but also have the bootloader that CM12 OR CM13 needs
After root the error code did not show up
After bustbox the error did not show up
I used TWRP manager app to install 4 different TWRPs, all gave a boot code error and would reboot to CM or stock but obviously something was wrong
So then after research I found others that had trouble and used Autorec to solve the issue
Autorec:
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
UPDATE 6/15 - Bootloader error?
It says:
SECURE BOOTING ERROR!
ERROR 1003
So I updated to 24B and I have CM 12.1 running. I did notice a boot error "error 1003" right before TWRP opened to install the ROM and just before the cyanogenmod boot screen popped up - Is that going to be okay, everything seems to be working fine?
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to out it in airplane mode and open the apk): http://forum.xda-developers.com/lg-g...3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download cm 12.1 files tot the TWRP backup files
5.) Reboot into TWRP recovery
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset - wipe dalvic and cache again
8.) Installed CM 12.1 and rebooted system
Original issue: Failed ROM flash on 12B and TWRP3.0
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
stewbuntu said:
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
Click to expand...
Click to collapse
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
RedWingsFanEd said:
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
Click to expand...
Click to collapse
I was just trying 12.1 for stability, for now
Should I try and go to 24B with TWRP 3.0 and see if that works?
UPDATE
TWRP 2.8 failed and said that CM12 also wanted the bootloader for 23C or greater. I read somewhere that TWRP 3.0 is the cause of the boot error 1003 when flashing CM so I'll try TWRP 2.8
So I updated and I have CM 12.1 running. I did notice a boot error 1003 right before TWRP opened to install the ROM and just before the CM boot screen popped up - Is that going to be okay? I have been running with no issues for half a day now.
I was able to update SuperSU
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to put the phone in airplane mode and open the apk): http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download CM12 or CM 13 files to the TWRP backup files folder
5.) Reboot into TWRP recovery via app
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset, wipe dalvic and cache again
8.) Installed Cyanogenmod 12.1 and rebooted system

Updater process ended with ERROR: 7

Hallo everyone,
So I wanted to install cyanogenmod on my Galaxy S III i9300, but unfortunately I got stuck and dont know what to do further.
-I installed twrp-3.0.2-1 using Odin3 v3.09
-Downloaded cm-13 nightly and GAPPS
-Wiped everything
-Tried to install cyanogenmod
Reconstructing the log:
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
symlink: some symlinks failed
Updater process ended with ERROR: 7
Error installing zip file "(directory and name of the zip)
So at this point I tried several TWRP versions and several cyanogenmod version ending up with the same result and getting pretty desperate.
Can anyone help me here?
Thanks in advance
Edit: I of course tried to find a solution without posting first. I saw something about the SD memory formatted as internal memory, but couldnt make a sense of it or how to change it. Also I just bought a micro SD today to do this.
Also I always have to run Odin with the TWRP versions after i got the error since my phone wont return to the menu only to the downloading status with the green android guy
Consider me stupid....
Seems like the i9305 stuff is working better on my phone
Answer to Goeffrey
Goeffrey said:
Hallo everyone,
So I wanted to install cyanogenmod on my Galaxy S III i9300, but unfortunately I got stuck and dont know what to do further.
-I installed twrp-3.0.2-1 using Odin3 v3.09
-Downloaded cm-13 nightly and GAPPS
-Wiped everything
-Tried to install cyanogenmod
Reconstructing the log:
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
symlink: some symlinks failed
Updater process ended with ERROR: 7
Error installing zip file "(directory and name of the zip)
So at this point I tried several TWRP versions and several cyanogenmod version ending up with the same result and getting pretty desperate.
Can anyone help me here?
Thanks in advance
Edit: I of course tried to find a solution without posting first. I saw something about the SD memory formatted as internal memory, but couldnt make a sense of it or how to change it. Also I just bought a micro SD today to do this.
Also I always have to run Odin with the TWRP versions after i got the error since my phone wont return to the menu only to the downloading status with the green android guy
Click to expand...
Click to collapse
the solution is
1. wipe some partitions using the advanced wipe. the app will automatically updates the partition
2. reinstall the ROm
This thread is over a year old. Error 7 message may be due to an outdated custom recovery or the ROM was not made for the phone.

Update Fota Lollipop 43 to MM 13.6.5.30 (WW)

I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos

Can't install new ROM version with twrp

Hey guys,
I have an OP5 and wanted to update my OOS 5.1.3 to OOS 5.1.5. I already have rooted my phone with currently Magisk 16.0, but I wanted to upgrade Magisk too directly after installing OOS, bc you have to install it again (if I have to install the orld version again first and only can upgrade after a restart, please write me). I use TWRP 3.2.1-1.
So I downloaded the OOS 5.1.5 version. Then I copied on my phone, restarted into recovery and then created a checkfile. For the zip "OnePlus5Oxygen_23_OTA_038_all_1808082017_028e075c45a84106.zip" I created the checkfile "OnePlus5Oxygen_23_OTA_038_all_1808082017_028e075c45a84106.zip.md5" with "96628db3bc3e5575677adad648ec616a *OnePlus5Oxygen_23_OTA_038_all_1808082017_028e075c45a84106.zip" as content ("<checksum> *<filename>" in the file <filename>.md5). So I tried to installed the new OOS version. I wiped cache and dalvik and then selected the zip file. I turned zip signature verification on. But It said
Code:
Installing zip file '<file>'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing '<file>'
Updating partition details...
...done
I wiped cache/dalvik again and tried without zip verification.
Then I got
Code:
Installing zip file '<file>'
Checking for Digest file...
Digest matched for '<file>'.
vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
Error installing zip file '<file>'
Updating partition details...
...done
So I downloaded it again, directly on an USB flash drive and tried both with and without zip signature verification. Nothing was different. Then I changed the checkfile so it only had the checksum as content without the filename behind, because I saw it this way once. But nothing changed. Now I don't know what I should do... I saw someone said you should download the zip directly to your phone and don't move it, but I can't select my phone as download destination. On the USB flash drive I downloaded it only and didn't moved the file, but idk if it is a problem that I had to unplug it from my pc to plug it in my phone.
When I rooted my phone I had the same problem but after trying some times it worked. This was when I had no OS installed and installed OOS 5.1.3.
pastebin com / xx0scV4s
Here i have the complete log I got from TWRP.
Sry but I can't insert links so I have to use this ****ty method

Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup

Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Can you tell me how you rooted the SM-T380 I tried rooting it using the 2018 guide but it's not working and I tried patching the Boot.img ( from Sammobile) with magisk but when i open the magisk app it says Installed: N\A Ramdisk: Yes A\B & Sars: no.
Or can you share the stock boot animation from the T830 since I'm not a big fan of the Marvel's avengers/iron man boot animation.
i just installed this and it works great, total life saver. i was about to toss my tablet in the trash
@xfk110, out of sheer desperation I want to try this. I understand why and how it should work, and I'm downloading your backup now. But a couple of questions first if I may:
1. Will Titanium Backup work with this rooted firmware? That's most important and my biggest frustration, after trying every other way described in the T380 threads, with both Oreo and Pie, TWRP or patched boot image. Nothing has worked well enough for me.
. . . My Tab A arrived with XAR 3CTH4 which meant I could downgrade it to the last Oreo update 3BSD1, and I've been back and forth between versions trying to make something work with TiBu. I'm a diehard Titanium user. I have tried 4-5 different root methods and every effort has failed somehow, if only that TiBu would not run. (Most efforts were even worse failures though.)
2. How important is the firmware version (and CSC) on my Tab A? . . . My T380 came with XAR firmware . . . Should I match the 3CSL2 version of your backup exactly, i.e., should I flash 3CSL2 first? Or if I'm on 3CSI5, would that be close enough? (I ask because I'm getting really really tired of changing firmware on this Tab lol, and I already have 3CSI5 downloaded and unpacked.)
3. You mention "all of those files" -- for a TWRP restore I would expect to select ONE FOLDER to restore from, so I'm a little confused about what you mean by "all of those files". Wouldn't it necessary to copy all of those files to one new folder under TWRP/BACKUPS/my-serial-number? Maybe named 2022-01-18, something short and simple.
I do truly truly hope this will work for me. Thanks in advance for however much you can help me understand everything I need to do to get a solid working root.
Just wanted to thank you for providing this guide. It worked first time for me and I'm very happy with the improved speed and space.
Thank you!
zfk110 said:
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Hello could you please make a video, the truth is that I do not understand anything.
Can this process be done using internal storage?
banistersmind said:
Can this process be done using internal storage?
Click to expand...
Click to collapse
No, unfortunately, this process can only be completed with a micro sd card and another computer with an sd card reader. the sd card must be at least 8gb to work.
Still works great as of 3rd May, 2023! Thanks mate.
@banistersmind @mehmeh.re I just did it without an SD card using internal storage. Works fine.

Categories

Resources