Related
Please post an MD5 or SHA checksum with every file you post, or link to!
This will allow downloaders to verify that they received the file intact. Flashing corrupt files is a bad thing.
On Mac OS X and Linux, use /usr/bin/shasum, like so:
Code:
$ shasum motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b motoboot.bin
On Windows, use a tool like one of the following:
http://corz.org/windows/software/checksum/
http://www.fastsum.com/press/md5-hash.php
Don't worry about what you use, computed checksums will match across platforms.
Thank you!
UPDATE 18-01-2013: new gapps
Based on dreamcwli's gapps.
gapps-minimal-jb-20130115-signed.zip
------------------------------------------
UPDATE: As you may have noticed, since yesterday we have nightly builds for the p3 at get.cm/?device=p3.
------------------------------------------
Get your update from there. You will still need to install the minimal gapps posted below. Also, still read pershoot's latest post on his blog.
To flash the first one:
fastboot erase system
fastboot flash recovery recovery.img
fastboot boot recovery.img
flash rom
flash minimal gapps
After that, you can use CM's built in update function.
Thanks pershoot for getting this up so quickly!
------------------------------------------
pershoot has built CM 10.1 for the p3:
I won't copy any information about the ROM here, everything you need to know you can find on his blog:
http://droidbasement.com/db-blog/
Gapps:
gapps-minimal-jb-20130115-signed.zip
There are some serious space issues on the system partition of the p3, that's why I created a minimal gapps version especially for our tablet.
They are taken from the 20130115 gapps from dreamcwli and are very bare. You'll need to install Google Search, Gmail, Calendar and all the rest from the Play Store
Send thanks to pershoot for supporting our tablet!
That is a Bad information man since the second test build u can use the normal gapps
http://goo.im/gapps/gapps-jb-20121212-signed.zip
The Rom is over 20 MB smaller everything fits now
Gesendet von meinem HTC One X mit Tapatalk 2
feraay said:
That is a Bad information man since the second test build u can use the normal gapps
http://goo.im/gapps/gapps-jb-20121212-signed.zip
The Rom is over 20 MB smaller everything fits now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
That is not true. To proof my point: right after you flash it in recovery, first the ROM and then the full gapps, check out /tmp/recovery.log . you'll see that the script has errors that there is not enough space to unpack and copy all the files. Further, mount /system and do a df -h /system. You will see that you have only around 4k left. I know it appears as if it had enough space but it doesn't. I've spent quite a lot of time together with pershoot to get this right.
After flashing the ROM, you have about 38 MB left. The full gapps are around 100MB unpacked. That obviously doesn't fit.
Ok but i have no probs arround here everything works fine
U know what i mean
I belive u but it is making no problems
Gesendet von meinem HTC One X mit Tapatalk 2
ramonams said:
That is not true. To proof my point: right after you flash it in recovery, first the ROM and then the full gapps, check out /tmp/recovery.log . you'll see that the script has errors that there is not enough space to unpack and copy all the files. Further, mount /system and do a df -h /system. You will see that you have only around 4k left. I know it appears as if it had enough space but it doesn't. I've spent quite a lot of time together with pershoot to get this right.
After flashing the ROM, you have about 38 MB left. The full gapps are around 100MB unpacked. That obviously doesn't fit.
Click to expand...
Click to collapse
Could you help me to get my errors resolved (see below)? I have installed from stockrom. Cleared dalvik cache and wiped everything else. Also flashed galaxy wipe.zip. I installed the rom zip and the directly after installed mini gapps. Should I remove the rom zip and everything else from the sdcard before continuing flashing gapps?
-- Installing: /sdcard/Download/gapps-minimal-jb-20121212-signed.zip
Finding update package...
I:Update location: /sdcard/Download/gapps-minimal-jb-20121212-signed.zip
I:using /data/media for /sdcard/Download/gapps-minimal-jb-20121212-signed.zip.
Opening update package...
Installing update...
***********************************************about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/system/addon.d/70-gapps.sh"
minzip: Extracted file "/system/app/ChromeBookmarksSyncAdapter.apk"
minzip: Extracted file "/system/app/GmsCore.apk"
minzip: Extracted file "/system/app/GoogleBackupTransport.apk"
minzip: Extracted file "/system/app/GoogleContactsSyncAdapter.apk"
minzip: Extracted file "/system/app/GoogleFeedback.apk"
minzip: Extracted file "/system/app/GoogleLoginService.apk"
minzip: Extracted file "/system/app/GooglePartnerSetup.apk"
Minimal Google Apps for Android 4.2.1 minzip: Extracted file "/system/app/GoogleServicesFramework.apk"
minzip: Extracted file "/system/app/MediaUploader.apk"
minzip: Extracted file "/system/app/NetworkLocation.apk"
minzip: Extracted file "/system/app/OneTimeInitializer.apk"
***********************************************
Mounting system...minzip: Extracted file "/system/app/Phonesky.apk"
minzip: Extracted file "/system/app/SetupWizard.apk"
minzip: Extracted file "/system/app/Talk.apk"
roid.maps.xml"
minzip: Extracted file "/system/etc/permissions/com.google.android.media.effects.xml"
minzip: Extracted file "/system/etc/permissions/com.google.widevine.software.drm.xml"
minzip: Extracted file "/system/etc/permissions/features.xml"
minzip: Extracted file "/system/framework/com.google.android.maps.jar"
minzip: Extracted file "/system/framework/com.google.android.media.effects.jar"
Copying files...minzip: Extracted file "/system/framework/com.google.widevine.software.drm.jar"
minzip: Extracted file "/system/lib/libfilterpack_facedetect.so"
minzip: Error writing 24576 bytes from zip file from 0xbeaf1bc4: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libgcomm_jni.so"
about to run program [/sbin/busybox] with 3 args
Fixing Permissions...
Unmounting system...
script result was [Installation complete!]
Installation complete!
Install from sdcard complete.
pinibo said:
Could you help me to get my errors resolved (see below)? I have installed from stockrom. Cleared dalvik cache and wiped everything else. Also flashed galaxy wipe.zip. I installed the rom zip and the directly after installed mini gapps. Should I remove the rom zip and everything else from the sdcard before continuing flashing gapps?
-- Installing: /sdcard/Download/gapps-minimal-jb-20121212-signed.zip
Finding update package...
I:Update location: /sdcard/Download/gapps-minimal-jb-20121212-signed.zip
I:using /data/media for /sdcard/Download/gapps-minimal-jb-20121212-signed.zip.
Opening update package...
Installing update...
***********************************************about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/system/addon.d/70-gapps.sh"
minzip: Extracted file "/system/app/ChromeBookmarksSyncAdapter.apk"
minzip: Extracted file "/system/app/GmsCore.apk"
minzip: Extracted file "/system/app/GoogleBackupTransport.apk"
minzip: Extracted file "/system/app/GoogleContactsSyncAdapter.apk"
minzip: Extracted file "/system/app/GoogleFeedback.apk"
minzip: Extracted file "/system/app/GoogleLoginService.apk"
minzip: Extracted file "/system/app/GooglePartnerSetup.apk"
Minimal Google Apps for Android 4.2.1 minzip: Extracted file "/system/app/GoogleServicesFramework.apk"
minzip: Extracted file "/system/app/MediaUploader.apk"
minzip: Extracted file "/system/app/NetworkLocation.apk"
minzip: Extracted file "/system/app/OneTimeInitializer.apk"
***********************************************
Mounting system...minzip: Extracted file "/system/app/Phonesky.apk"
minzip: Extracted file "/system/app/SetupWizard.apk"
minzip: Extracted file "/system/app/Talk.apk"
roid.maps.xml"
minzip: Extracted file "/system/etc/permissions/com.google.android.media.effects.xml"
minzip: Extracted file "/system/etc/permissions/com.google.widevine.software.drm.xml"
minzip: Extracted file "/system/etc/permissions/features.xml"
minzip: Extracted file "/system/framework/com.google.android.maps.jar"
minzip: Extracted file "/system/framework/com.google.android.media.effects.jar"
Copying files...minzip: Extracted file "/system/framework/com.google.widevine.software.drm.jar"
minzip: Extracted file "/system/lib/libfilterpack_facedetect.so"
minzip: Error writing 24576 bytes from zip file from 0xbeaf1bc4: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libgcomm_jni.so"
about to run program [/sbin/busybox] with 3 args
Fixing Permissions...
Unmounting system...
script result was [Installation complete!]
Installation complete!
Install from sdcard complete.
Click to expand...
Click to collapse
The amount of files you have on your sdcard doesn't have any influence on the success when flashing. do this:
- Put your tab in fastboot mode
- "fastboot erase system"
- "fastboot boot path/to/recovery.img"
- Flash the ROM
- in the recovery, go to mounts and storage and mount /system
- "adb shell"
- "df -h /system" and record what the output is
- unmount /system
- Flash the gapps
- in the recovery, go to mounts and storage and mount /system
- "adb shell"
- "df -h /system" and record what the output is
and check recovery.log again
basically, this should work like this and you should be left with about 1 MB on /system
Let me know how it goes.
EDIT: just to be sure, redownload the minimal gapps again. I put up another zip as I realised the first one wasn't the one I wanted there.
ramonams said:
The amount of files you have on your sdcard doesn't have any influence on the success when flashing. do this:
- Put your tab in fastboot mode
- "fastboot erase system"
- "fastboot boot path/to/recovery.img"
- Flash the ROM
- in the recovery, go to mounts and storage and mount /system
- "adb shell"
- "df -h /system" and record what the output is
- unmount /system
- Flash the gapps
- in the recovery, go to mounts and storage and mount /system
- "adb shell"
- "df -h /system" and record what the output is
and check recovery.log again
basically, this should work like this and you should be left with about 1 MB on /system
Let me know how it goes.
EDIT: just to be sure, redownload the minimal gapps again. I put up another zip as I realised the first one wasn't the one I wanted there.
Click to expand...
Click to collapse
After the fifth step (mount /system) you say to run adb shell. I assume this is only possible after leaving recovery and rebooting again. Correct?
Do I need to clear caches and execute all wipes?
pinibo said:
After the fifth step (mount /system) you say to run adb shell. I assume this is only possible after leaving recovery and rebooting again. Correct?
Do I need to clear caches and execute all wipes?
Click to expand...
Click to collapse
You don't need to leave recovery and reboot, actually, if you're still in the shell, you don't need to do that again, i just copy pasted. just don't be in the system directory and better unmount system in between flashing, otherwise the gapps flashing script will give an error that the partition is busy.
Why not use the 'format /system' option in CWM before flashing rom & gapps?
The ROM is great.
feraay said:
That is a Bad information man since the second test build u can use the normal gapps
http://goo.im/gapps/gapps-jb-20121212-signed.zip
The Rom is over 20 MB smaller everything fits now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
no, you cannot.
this will not work.
'your' rom is 20MB smaller when installed + normal gapps, because you've symlinked content on to /data to make room and/or youve deleted a massive amount of system content. that, or you have a special p3 with more system space then the others i've seen.
the builds from droidbasement or when is published to nightly status, require minimal gapps (above), if you use gapps.
pinibo said:
Could you help me to get my errors resolved (see below)? I have installed from stockrom. Cleared dalvik cache and wiped everything else. Also flashed galaxy wipe.zip. I installed the rom zip and the directly after installed mini gapps. Should I remove the rom zip and everything else from the sdcard before continuing flashing gapps?
Click to expand...
Click to collapse
you did not read droidbasement on installation instructions.
flash p4's modem via odin.
flash cwm 6.0.2.5.
fastboot erase system
fastboot boot CWM
flash unofficial 12/28 rom, flash minimal gapps (if you use gapps, above), clear all data/userdata, reboot.
pershoot said:
you did not read droidbasement on installation instructions.
flash p4's modem via odin.
flash cwm 6.0.2.5.
fastboot erase system
fastboot boot CWM
flash unofficial 12/28 rom, flash minimal gapps (if you use gapps, above), clear all data/userdata, reboot.
Click to expand...
Click to collapse
Followed now all the steps as indicated by ramon and pershoot's instructions on droidbasement.
Checked the log and finally no space issues detected anymore.
Great and many thanks!!!!
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
I used the latest ROM (28-12) and gapps as given by ramon. Now I have 1.1M free on system.
pinibo said:
Followed now all the steps as indicated by ramon and pershoot's instructions on droidbasement.
Checked the log and finally no space issues detected anymore.
Great and many thanks!!!!
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
I used the latest ROM (28-12) and gapps as given by ramon. Now I have 1.1M free on system.
Click to expand...
Click to collapse
That's how it should be.
pershoot said:
no, you cannot.
this will not work.
'your' rom is 20MB smaller when installed + normal gapps, because you've symlinked content on to /data to make room and/or youve deleted a massive amount of system content. that, or you have a special p3 with more system space then the others i've seen.
the builds from droidbasement or when is published to nightly status, require minimal gapps (above), if you use gapps.
Click to expand...
Click to collapse
When do you plan to bring it back to CM repository. C-o-M in the Galaxy Tab 8.9 forum made first builds for the P73xx devices. Maybe everything could be brought together again, so nothing is lost as the P73xx and P75xx are pretty similar.
shiko80 said:
When do you plan to bring it back to CM repository. C-o-M in the Galaxy Tab 8.9 forum made first builds for the P73xx devices. Maybe everything could be brought together again, so nothing is lost as the P73xx and P75xx are pretty similar.
Click to expand...
Click to collapse
i'm not the device maintainer on that tab variant. please speak with kallt kaffe for that device suite.
pershoot said:
i'm not the device maintainer on that tab variant. please speak with kallt kaffe for that device suite.
Click to expand...
Click to collapse
kallt_kaffe seems not to be available any more. Isn't it possible for you take over the device ownership? Can you send a request for this?
gonna flash this too but I was a bit more "agressive" and deleted most of the ringtones and notification sounds from the rom. reduced the size of the rom to a whopping 117 mb
and also deleted appolo since I use Google Music. Will report back as soon as possible
shiko80 said:
kallt_kaffe seems not to be available any more. Isn't it possible for you take over the device ownership? Can you send a request for this?
Click to expand...
Click to collapse
sorry i dont own that tab and dont have the resources to take on more like devices at this current time.
pershoot said:
sorry i dont own that tab and dont have the resources to take on more like devices at this current time.
Click to expand...
Click to collapse
Sorry, I didn't want you take over any further devices but I thought it would help if everything is back in the CyanogenMod repository and more developers would work on it at the same time. In my opinion it makes no sense that C-o-M gets your sources, modifies it and makes a firmware for P73xx. So why not working all in the same repository. The other advantage would be that we have nightly builds.
The sound for my tab is not very hard if i put it to the max. Same wit headphone, even if i ignore the warning and put it harder.
Had the same on my Samsung Note on cm10 but cm10.1 solved it and is about just right now.
Watching a movie our listing a mp3
Sent from my GT-P7100 using xda app-developers app
Hi,
just had a bad experience with the updater today. Due to a bad connection the downloaded zip files were corrupt causing the updater to try and abort every time.
Why not let the OTA Upgrade also download a associated MD5 file for each Upgrade ZIP? TWRP's default action if a .md5 file present is to check the file CRC before trying to apply a upgrade. If md5 is wrong it will be skipped.
a little change for a better upgrade process.
Thanks
Best person to answer this one is @Chainfire
solarizde said:
Hi,
just had a bad experience with the updater today. Due to a bad connection the downloaded zip files were corrupt causing the updater to try and abort every time.
Why not let the OTA Upgrade also download a associated MD5 file for each Upgrade ZIP? TWRP's default action if a .md5 file present is to check the file CRC before trying to apply a upgrade. If md5 is wrong it will be skipped.
a little change for a better upgrade process.
Thanks
Click to expand...
Click to collapse
MD5 is already checked I think. Are you sure it aborts because of that? Have you tried turning off secure flashing thing?
XpLoDWilD said:
MD5 is already checked I think. Are you sure it aborts because of that? Have you tried turning off secure flashing thing?
Click to expand...
Click to collapse
What I mean is placing the MD5 file on download to the zip file. Currenty TWRP is lcearly stating "No md5 file" so the CRC check is skipped. The problem was that one of my downloaded zip files was corrupt but it still startet to unpack it unfortunately it broke at 80% and left my device in a unfinished update state. This should never happen. Luckily I was able to recover by installing the latest full omni download which was still on the SD Card.
So my post here is just a suggestion to also add a .md5 file for each automatically downloaded zip update. There is not much more to do then this because twrp will do the remaining work and check CRC before starting extraction.
solarizde said:
What I mean is placing the MD5 file on download to the zip file. Currenty TWRP is lcearly stating "No md5 file" so the CRC check is skipped. The problem was that one of my downloaded zip files was corrupt but it still startet to unpack it unfortunately it broke at 80% and left my device in a unfinished update state. This should never happen. Luckily I was able to recover by installing the latest full omni download which was still on the SD Card.
So my post here is just a suggestion to also add a .md5 file for each automatically downloaded zip update. There is not much more to do then this because twrp will do the remaining work and check CRC before starting extraction.
Click to expand...
Click to collapse
Hmm, did you disable secure mode?
That should NOT have happened in secure mode because ZIP signature verification would have failed.
Entropy512 said:
Hmm, did you disable secure mode?
That should NOT have happened in secure mode because ZIP signature verification would have failed.
Click to expand...
Click to collapse
Nope no playing with the secure mode here. TWRP 2.6.3.0
Afe redownloading it and rebooting the recovery it was installed fine.
UPDATE 09/20/2016 - Root is now available for the SM-T285 (custom ROM and SM-T280 to follow) see post for details (http://forum.xda-developers.com/showpost.php?p=68777842&postcount=27)
After some work I've managed to debloat my Galaxy Tab A(6) 7.0 LTE (SM-T285/T280). We all know that with a locked bootloader we
can at least do customizations with the system partition:
Here is a simple guide with hopes that more people with the device can continue to allow for more ROM customizations:
Tools/Requirements:
================
- Ubuntu as my OS
- make sure you have adb installed and running (See the android developers guide on how to do this)
- Heimdall 1.4.1
- A copy of the stock firmware zip from samsung for your device
- 7zip to be able to unzip the firmware from above
- Android AOSP fsutils simg2img and make_ext4fs (Attached) (note that your make_ext4fs needs to be patched to be able to generate samsung patches easily see gist) for some reason samsung chose to use a slightly different sparse file layout for this device. Using the stock make_ext4fs to generate an image will cause heimdall ( ad Odin) to stop data uploads after the first packet stream.
Or if you still want to use stock make_ext4fs you can try using Chainfire's sgs4ext4fs and run this after you generate your system.img, I haven't tried this route personally myself.
Step By Step (Part 1 - Mount stock system.img for modification)
==========
1. Create a folder to do your work like samsing_kitchen for example. Place your
stock firmware package there
Code:
mkdir samsung_kitchen
cd samsung_kitchen
2. Extract your stock firmware's system.img using 7zip
Code:
7z x XTC-T285XXU0APCN-20160421170750.zip
7z x T285XXU0APCN_T285OLB0APC6_T285XXU0APCN_HOME.tar.md5
Should see a couple of image files, one of them is system.img.
3. Create mount point and convert from sparse image to mountable image and then mount it
Code:
mkdir system
simg2img system.img system.img.raw
sudo mount -t ext4 -o loop system.img.raw ./system
The contents of the system image should now be visible inside the system folder you
just created. You can now proceed to modifiying it (e.g. remove apps)
(Part 2 - Repackage image for flashing to device)
=================================================
DISCLAIMER: As always make sure you backup your important files in case
something goes wrong! I will not be responsible for any losses resulting from this
activity. Also this activity may void your warranty.
Prequisites:
- Make sure you have heimdall properly working.
- Make sure you have oem unlock. This should be visible in developer settings
To know if it is enabled/disable FRP protection should be disabled when you go
in Odin mode.
1. pull the file_contexts file from .your device ( or download the attached in this post).
Code:
adb pull file_contexts
on a connected device in developer mode. You will need this file so that the permissions are properly set when building the image
2. Exit from system back to your working folder (e.g. samsing_kitchen ) and run
the following:
Code:
sudo make_ext4fs -s -l 2147483648 -S file_contexts -a system new_system.img ./system
This should create a flashable image called new_system.img
3. Restart your SM-T285 into Odin Mode (Power-off, then hold home vol-down + power until Odin Mode shows up)
4. Flash using Heimdall
Code:
heimdall flash --SYSTEM new_system.img
Your device should automatically restart after this. If something goes wrong you can always flash the original system image back.
Making an ODIN flashable image
----------------------------------------
To create an image compatible with ODIN (tar.md5) make sure you have a copy of the stock image zip from samsung and extract (using 7zip) its contents to a folder:
An extracted file should look like this:
Code:
boot.img
cache.img
hidden.img
nvitem.bin
recovery.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
replace the stock system.img with the one you created from above:
Code:
cp ../new_system.img system.img
tar and md5 it:
Code:
tar -H ustar -c boot.img cache.img hidden.img recovery.img SPRDCP.img SPRDGDSP.img SPRDLTEDSP.img SPRDWDSP.img system.img >T285_CUSTOM.tar
md5sum -t T285_CUSTOM.tar > T285_CUSTOM.tar
mv T285_CUSTOM.tar T285_CUSTOM.tar.md5
as per ashyx this should also work as well:
Code:
tar -H ustar -c system.img > system.tar
md5sum -t system.tar > sytem.tar
mv system.tar system.tar.md5
Optionally Zip it if you want:
Code:
7z a T285_CUSTOM.zip T285_CUSTOM.tar.md5
This guide should work for the T280 as well, though I can't confirm it since I don't have access to that model.
Petition for samsung to unlock the device:
https://www.change.org/p/samsung-unlock-the-bootloader-for-the-samsung-galaxy-tab-a-7-0-2016?recruiter=286570213&utm_source=petitions_share&utm_medium=copylink
Custom ROM to enable move apps to sd (apps2sd like support):
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
@jedld
Nice guide, just a few things though.
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Regarding the chunk size, Chainfire created sgs4ext4fs to deal with this, it just needs to be run afterwards on the sparse image to patch the headers.
What is the source for the make_ext4fs patch or did you create this patch?
Lastly some people may prefer to use ODIN to flash.
So maybe you could add to the guide that the image can be repacked into a ODIN flashable tar using 7-zip.
By the way the guide will work for the T280 too, so you may want to add that.
Thanks.
ashyx said:
@jedld
Nice guide, just a few things though.
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Regarding the chunk size, Chainfire created sgs4ext4fs to deal with this, it just needs to be run afterwards on the sparse image to patch the headers.
What is the source for the make_ext4fs patch or did you create this patch?
Lastly some people may prefer to use ODIN to flash.
So maybe you could add to the guide that the image can be repacked into a ODIN flashable tar using 7-zip.
By the way the guide will work for the T280 too, so you may want to add that.
Thanks.
Click to expand...
Click to collapse
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Click to expand...
Click to collapse
I remember encountering a boot loop without that, let me check again and I'll update the guide.
What is the source for the make_ext4fs patch or did you create this patch?
Click to expand...
Click to collapse
Just applied the following patch on latest aosp sources:
https://gist.github.com/jedld/4f388496bda03b349f5744f367749a67
There is a magic number used which I can't figure out, the value is different between SM-T285 ROMS coming from different regions.
Nice to hear about sgs4ext4fs though, probably wouldn't be able to know based on the problem I encountered that the tool also applies unless someone pointed it out.
https://www.change.org/p/samsung-unl...edium=copyLink
Petition for unlocked bootloader for samsung, please sign
http://samsung4android.ru/?ipub=422
any thoguth on this?
klemen241 said:
http://samsung4android.ru/?ipub=422
any thoguth on this?
Click to expand...
Click to collapse
ashyx already tried everything. CF-auto root requires an unlocked recovery, the tablet won't even accept a repacked recovery image. Besides the guy in the video wasn't even using a SM-T285, if you look closely the files he used were for the SM-T550.
klemen241 said:
https://www.change.org/p/samsung-unl...edium=copyLink
Petition for unlocked bootloader for samsung, please sign
Click to expand...
Click to collapse
link is broken though, you must have used the auto truncated link, use this instead:
https://www.change.org/p/samsung-un...edium=copylink&recuruit_context=copylink_long
What about those custom roms? As far as i can see we can use modified stock rom. Can we go anywhere with that? And can someone explain how to make external storage bigger with SD?
SM-T285M with locked bootloader - research ...
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
klemen241 said:
What about those custom roms? As far as i can see we can use modified stock rom. Can we go anywhere with that? And can someone explain how to make external storage bigger with SD?
Click to expand...
Click to collapse
There are a number of things we can already do with a custom system.img like debloat, enable universal sd r/w, customizing apps, probably theming and fonts are also possible. Hopefully more people can come up with mods.
Unfortunately we need root/unlocked boot.img to do important things to fix the weakness of this device like changing partition sizes, enable apps2sd support, xposed framework, having customizable cpu performance governors/overclocking etc.
TopTongueBarry said:
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
Click to expand...
Click to collapse
i was wondering the same thing, if ther is any chance of unlocking it on earlier versions.
Also i sent email to samsung support again, maybe they will be sick of us begging and release the lock
klemen241 said:
i was wondering the same thing, if ther is any chance of unlocking it on earlier versions.
Also i sent email to samsung support again, maybe they will be sick of us begging and release the lock
Click to expand...
Click to collapse
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t285m
---------- Post added at 02:46 AM ---------- Previous post was at 02:36 AM ----------
TopTongueBarry said:
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
Click to expand...
Click to collapse
UPDATE: I was able to get the 3/10 stock factory rom flashed without changing the pit. Replaced the hidden.img file in this rom with a renamed copy of the boot.img from the same rom. Flashing does fail in the very end, but it completes before failing so I simply rebooted immediately into Odin mode again to flash jedid's debloated system.img for the T285. Done this a couple times now and the device comes up just fine. About device and Phone Info Samsung confirm it is running the 3/10 build.
Bad news is the bootloader is locked in this build too. No hope unless someone can do something with the source. See prior post.
is open source same for t280? i have 280 not 285
klemen241 said:
is open source same for t280? i have 280 not 285
Click to expand...
Click to collapse
not sure how having the kernel source would help since we can't even change the kernel on the device which is kinda awkward for samsung. Besides I remember ashyx having compilation issues with spreadtrum kernel sources by samsung and not just for this device.
TopTongueBarry said:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t285m
---------- Post added at 02:46 AM ---------- Previous post was at 02:36 AM ----------
UPDATE: I was able to get the 3/10 stock factory rom flashed without changing the pit. Replaced the hidden.img file in this rom with a renamed copy of the boot.img from the same rom. Flashing does fail in the very end, but it completes before failing so I simply rebooted immediately into Odin mode again to flash jedid's debloated system.img for the T285. Done this a couple times now and the device comes up just fine. About device and Phone Info Samsung confirm it is running the 3/10 build.
Bad news is the bootloader is locked in this build too. No hope unless someone can do something with the source. See prior post.
Click to expand...
Click to collapse
I remember flashing an earlier build thinking the same thing and yep the bootloader is still locked. Aside from that I ran kingroot to see if there was anything exploitable... did'nt work. What I haven't tried is to see if superuser is disabled in this kernel though.
jedld said:
After some work I've managed to debloat my Galaxy Tab A(6) 7.0 LTE (SM-T285/T280). We all know that with a locked bootloader we
can at least do customizations with the system partition:
Here is a simple guide with hopes that more people with the device can continue to allow for more ROM customizations:
Tools/Requirements:
================
- Ubuntu as my OS
- make sure you have adb installed and running (See the android developers guide on how to do this)
- Heimdall 1.4.1
- A copy of the stock firmware zip from samsung for your device
- 7zip to be able to unzip the firmware from above
- Android AOSP fsutils simg2img and make_ext4fs (Attached) (note that your make_ext4fs needs to be patched to be able to generate samsung patches easily see gist) for some reason samsung chose to use a slightly different sparse file layout for this device. Using the stock make_ext4fs to generate an image will cause heimdall ( ad Odin) to stop data uploads after the first packet stream.
Or if you still want to use stock make_ext4fs you can try using Chainfire's sgs4ext4fs and run this after you generate your system.img, I haven't tried this route personally myself.
Step By Step (Part 1 - Mount stock system.img for modification)
==========
1. Create a folder to do your work like samsing_kitchen for example. Place your
stock firmware package there
Code:
mkdir samsung_kitchen
cd samsung_kitchen
2. Extract your stock firmware's system.img using 7zip
Code:
7z x XTC-T285XXU0APCN-20160421170750.zip
7z x T285XXU0APCN_T285OLB0APC6_T285XXU0APCN_HOME.tar.md5
Should see a couple of image files, one of them is system.img.
3. Create mount point and convert from sparse image to mountable image and then mount it
Code:
mkdir system
simg2img system.img system.img.raw
sudo mount -t ext4 -o loop system.img.raw ./system
The contents of the system image should now be visible inside the system folder you
just created. You can now proceed to modifiying it (e.g. remove apps)
(Part 2 - Repackage image for flashing to device)
=================================================
DISCLAIMER: As always make sure you backup your important files in case
something goes wrong! I will not be responsible for any losses resulting from this
activity. Also this activity may void your warranty.
Prequisites:
- Make sure you have heimdall properly working.
- Make sure you have oem unlock. This should be visible in developer settings
To know if it is enabled/disable FRP protection should be disabled when you go
in Odin mode.
1. pull the file_contexts file from .your device.
Code:
adb pull file_contexts
on a connected device in developer mode. You will need this file so that the permissions are properly set when building the image
2. Exit from system back to your working folder (e.g. samsing_kitchen ) and run
the following:
Code:
sudo make_ext4fs -s -l 2147483648 -S file_contexts -a system new_system.img ./system
This should create a flashable image called new_system.img
3. Restart your SM-T285 into Odin Mode (Power-off, then hold home vol-down + power until Odin Mode shows up)
4. Flash using Heimdall
Code:
heimdall flash --SYSTEM new_system.img
Your device should automatically restart after this. If something goes wrong you can always flash the original system image back.
Making an ODIN flashable image
----------------------------------------
To create an image compatible with ODIN (tar.md5) make sure you have a copy of the stock image zip from samsung and extract (using 7zip) its contents to a folder:
An extracted file should look like this:
Code:
boot.img
cache.img
hidden.img
nvitem.bin
recovery.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
replace the stock system.img with the one you created from above:
Code:
cp ../new_system.img system.img
tar and md5 it:
Code:
tar -H ustar -c boot.img cache.img hidden.img recovery.img SPRDCP.img SPRDGDSP.img SPRDLTEDSP.img SPRDWDSP.img system.img >T285_CUSTOM.tar
md5sum -t T285_CUSTOM.tar > T285_CUSTOM.tar
mv T285_CUSTOM.tar T285_CUSTOM.tar.md5
Optionally Zip it if you want:
Code:
7z a T285_CUSTOM.zip T285_CUSTOM.tar.md5
This guide should work for the T280 as well, though I can't confirm it since I don't have access to that model.
Click to expand...
Click to collapse
Anyway to do this on a windows machine?????
lohtse said:
Anyway to do this on a windows machine?????
Click to expand...
Click to collapse
Not sure though since you need to be able to mount an ext4 image, make modifications to it and then write it back. Plus the tools required to write the image back properly are only available in linux so I doubt there will be one for windows unless someone puts in effort to make something for it. The best I can do is to make a docker image where you can run it under windows with those tools if anyone is interested.
Just a note regarding the guide, it's not really necessary to add all the other partition images when creating the ODIN flashable tar.
All that is required is:
tar cvf system.tar system.img
jedld said:
Not sure though since you need to be able to mount an ext4 image, make modifications to it and then write it back. Plus the tools required to write the image back properly are only available in linux so I doubt there will be one for windows unless someone puts in effort to make something for it. The best I can do is to make a docker image where you can run it under windows with those tools if anyone is interested.
Click to expand...
Click to collapse
is there no way to create a set of files(zip etc) we windows users could flash using odin? would be a huge help if that could be done! also anyone have a link to a stock rom??
and finally I noticed that the US samsung site has a pdf manual for this tablet that refers to marshmallow!!!!!
http://www.samsung.com/us/business/support/owners/product/SM-T280NZWAXAR
lohtse said:
is there no way to create a set of files(zip etc) we windows users could flash using odin? would be a huge help if that could be done! also anyone have a link to a stock rom??
and finally I noticed that the US samsung site has a pdf manual for this tablet that refers to marshmallow!!!!!
http://www.samsung.com/us/business/support/owners/product/SM-T280NZWAXAR
Click to expand...
Click to collapse
I highly doubt this thing will get mm. [emoji52]
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
John877 said:
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
Click to expand...
Click to collapse
It has to be added in AP not BL.
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Hani88 said:
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Click to expand...
Click to collapse
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
Click to expand...
Click to collapse
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
jenslody said:
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Click to expand...
Click to collapse
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
白い熊 said:
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
Click to expand...
Click to collapse
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Hani88 said:
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Click to expand...
Click to collapse
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
jenslody said:
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
Click to expand...
Click to collapse
But in odin in AP I am not able to import img file
Hani88 said:
But in odin in AP I am not able to import img file
Click to expand...
Click to collapse
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
jenslody said:
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
Click to expand...
Click to collapse
Thanks for the explanation.. I will do it tomorrow
Flashing a patched boot image will trip the knox counter right ? Of course mine is tripped but I want to know that
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
John877 said:
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
Click to expand...
Click to collapse
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
jenslody said:
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
Click to expand...
Click to collapse
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
白い熊 said:
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
Click to expand...
Click to collapse
I used the stock boot for J3, patched it through MagiskManager (one as *.img, one as *.img.tar), renamed the patched_boot.img to boot.img (taht's what Odin expects inside the tar, used Fedora's tar (I'm on Fedora 26) to create a tar archive from it and just for testing added a md5-checksum to one version of it.
MagiskManager is the 5.30 released with/for Magisk 14.4, bot patched. The fixes I mention were made by @topjohnwu in the (internal) beta-testing for 14.4.
To be clear:
the released Magisk with MagiskManager create img.tar-files that work for my J5 with the Odin-version I use (Odin3 v3.10.7) without any tweaking.
My self-tared versions are for testing purposes, to see if other Odin versions are more nitpicking than mine (about tar-headers). The included boot.img is exactly (binary) the same.
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
Click to expand...
Click to collapse
Same question here.. and you are not the only one who's feeling like an idiot now
---------- Post added at 09:23 AM ---------- Previous post was at 09:02 AM ----------
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Click to expand...
Click to collapse
here is it thanks for helping
https://drive.google.com/file/d/0B9_cANW46As_Y2Jwa0xsR1p2UkE
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now. [emoji14]
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Click to expand...
Click to collapse
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
白い熊 said:
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
Click to expand...
Click to collapse
When I extracted the boot.img file from the firmware it was boot.img. When I patched it from magisk manager, it was boot.img still even though I chose output format img.tar.