Hi,
With the release of Galaxy Tab Gingerbread 2.3.3 by Chainfire
( http://forum.xda-developers.com/show....php?t=1073854 ), I intend to update my Galaxy Tab (running Froyo 2.2) to Gingerbread. Since I use only Linux in my computer, the only option to flash my Tab is to use Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ).
What I wish to know is:
1. The procedure using Odin calls for repartitioning. Is it okay to repartition using Heimdall?
2. There is a file called hidden.rfs in the official stock rom provided by Chanifire. How do I flash this hidden.rfs using Heimdall? Heimdall accepts only the following arguments as per it's man page:
action: flash
[--pit <filename>] [--factoryfs <filename>] [--cache <filename>]
[--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--secondary-boot-backup <filename>]
[--param <filename>] [--kernel <filename>] [--recovery <filename>]
[--efs <filename>] [--modem <filename>]
(Nowhere is any mention of hidden.rfs. I am confused as how to include it while flashing my Galaxy Tab).
3. Do I flash dbdata.tar in the first shot along with the firmware? Or do I need to flash dbdata.tar after rebooting the Galaxy Tab as instructed by Chainfire?
If someone can help me, I would very much appreciate it.
Thanks in advance.
1st of all. Im a windows user, my answers would relate to my experience using heimdall under windows and not under linux. Though i believe they would behave jjust the same.
1. From my experience uaing heimdall. Heimdall does partitioning juat as good as odin.
2. I don't know how it behaves in linux, butwhen i used heimdall to flash my tab i just put all the files in the same folder and the hidden.rfs seems to have been flashed as well.
3. You could flash the dbdata.rfs with the other firmware files in one flashing.
Cheers.
noxxious said:
1st of all. Im a windows user, my answers would relate to my experience using heimdall under windows and not under linux. Though i believe they would behave jjust the same.
1. From my experience uaing heimdall. Heimdall does partitioning juat as good as odin.
2. I don't know how it behaves in linux, butwhen i used heimdall to flash my tab i just put all the files in the same folder and the hidden.rfs seems to have been flashed as well.
3. You could flash the dbdata.rfs with the other firmware files in one flashing.
Cheers.
Click to expand...
Click to collapse
Thank you noxxious for your help.
Heimdall being a multiplatform open source program, it is supposed to behave consistently in all platforms (Linux/Windows/Mac).
I was told by user jkurl15 in thegalaxytabforum (sorry XDA won't allow me to post the link) not to repartition using Heimdall as it might brick the Galaxy Tab. Can you please throw some light on this?
Did you use the repartition option in Heimdall when you flashed your Galaxy Tab?
As regards to the hidden.rfs file, from what I noticed after concatenating the gt-p1000_mr.pit, is that it contains a mention of hidden.rfs inside it. Don't know if it helps.
Thank you once again.
If done correctly repartioning via heimdall will not cause a brick. Especially if all files that you would use is from 1 tar package in this case the gingerbread package.
Ive done repartioning via heimdall on my tab way back when i was still on jk2. It did a pretty good job restoring my tab.
Thanks for your insight. It was really a great help. I will give heimdall a try to flash my galaxy tab.
What is your opinion regarding the bootloaders present in the gingerbread rom? I have an unbranded unlocked galaxy tab and don't want to restrict myself by flashing any signed bootloader. Do you think I can flash my tab with gingerbread rom without the bootloaders?
Sent from my GT-P1000 using XDA App
Hi, did you succeed? If so, any news on how to upgrade?
I've done: heimdall flash --pit gt-p1000_mr.pit --factoryfs factoryfs.rfs --cache cache.rfs --param param.lfs --kernel zImage --modem modem.bin
Using http://www.samfirmware.com/WEBPROTECT-p1000.htm and both 1_EUR pit and gt-1000_m I can't load the firmware.
I get Optional PIT check failed! To disable this check don't use the --pit parameter.Ending session...
Rebooting device...
Re-attaching kernel driver...
Any ideaS?
SO.. Just to clarify for all Linux users..
Am I correct in thinking :-
1) Back everything up.
2) Extract The base 2.3 GB-stock-safe.zip into a folder, and the .tar file you should use in ODIN (GB_Stock_Safe_v1.tar) , that one comes from the Overcome 2.0 BETA2 download.
3) Copy the gt-p1000_mr.pit and the correct modem.bin into the extracted .tar folder aswell.
4) Plug Tab in to computer and do
Code:
adb reboot download
5) (Once in downlaod mode) run this function from the folder where the .tar file extracted
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
6) basically the movinand.mst and hidden .rfs files are ignored?
Just want to be sure..
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
mj_blue said:
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
Click to expand...
Click to collapse
You're telling adb to push the file into a zip? Anyways, ADB sadly does not work in our CWM (nor USB mounting as you might have noticed), so the only way you can restore functionality and start again (no erasure of your SDcard contents so don't worry) is to use ODIN back to stock. From there, start again. It could be your download was corrupted (download again), because I could flash it fine, but eventually went back to KJ5 for functionality.
Edit: Check my guide below for ODIN FAQ and how-to if necessary.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
kallt_kaffe said:
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
Click to expand...
Click to collapse
Edit: Sent you a PM.
was there a resolution to this issue? i have the same exact problem as the OP.
However, I cannot restore back to stock with ODIN. when writing my system.img.md5 my restore fails.
I know my devices can be fixed! i just have not found my answer yet.
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
ellokomen said:
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
Click to expand...
Click to collapse
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
wyatt23 said:
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
Click to expand...
Click to collapse
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
nirogu325 said:
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
Click to expand...
Click to collapse
I have done this. when i re-flash the odin stock image, i get stuck at the restoration of system.img.md5.
I uninstalled and reinstalled the samsung usb drivers and installed the latest. i've tried different usb ports. i am truly at a loss.
i installed an odin flashable version of CWM 5.0.2.6 (? i think thats the version), but adb was not available on that.
Does adb work on the stock recovery? Do you know where i can find this CM9 Kang thread? do you know if their version of CWM in flashable via Odin? that's the only way i can push anything onto the tablet as of right now.
btw... if i restart the tab unconnected to any USB cables, I get a message saying to reconnect to Kies and perform a recovery. IMHO kies is useless.
I am still stuck. I am open to literally anything not physically harmful to my tab.
Is nvflash an option for fixing this? I've never used it before, but if it can help I would be down.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
If i push files, they look as tho they are transferring, but i think they are not really making their way their on to the device.
After doing a little prying today at work, I found a .pit file. I read that this contains the partition information for drive.
I downloaded the stock 3.1 image, extracted it, and i found a P5.pit. Perhaps, I can use that PIT file, while keeping Re-Partition checked, and reflash the overcome CWM?
I know others have run into my exact problem and fixed it. there's gottttta be a way.
i will keep posting my progress and/or reading for others' suggestions.
When trying to flash KJ4 , i get the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7310XEUKJ4_P7310XXKJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img.md5
<ID:0/006> NAND Write Start!!
<ID:0/006> bootloader.bin.md5
<ID:0/006> cache.img.md5
<ID:0/006> hidden.img.md5
<ID:0/006> recovery.img.md5
<ID:0/006> system.img.md5
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then when looking at my galaxy tab screen i see the following:
Code:
Partition size is small! [Bin:173568 > Part:147968] (4KB unit)
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
I have to believe my partition table is all botched.
wyatt23 said:
I have to believe my partition table is all botched.
Click to expand...
Click to collapse
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
nirogu325 said:
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
Click to expand...
Click to collapse
and should i keep 'Re-Partition' Checked?
---------- Post added at 02:21 PM ---------- Previous post was at 02:12 PM ----------
wyatt23 said:
and should i keep 'Re-Partition' Checked?
Click to expand...
Click to collapse
ehh, so i tried it without re-partition. didn't work. still cannot mount /sdcard.
tried it with repartition checked with clockwork 5.0.2.6 and I'm stuck at the "choose download mode or recovery mode" screen. if i select recovery, the screen blinks.
TO FIX THIS: I can use odin 1.85 to flash KJ4. however, this will fail at system.img.md5. However, stock recovery will be bootable. stock recovery will give me errors saying most of my partitions cannot mount.
I then can use odin to flash clockwork 5.0.2.6 and enter recovery.
the partitions are still botched if i go that route.
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Glad to hear you fixed your issue, thought I'd add a few side notes as I had the same problem as you pretty much but fixed it at 3am and went straight to bed and was gonna post this morning.
For my situation I was doing it all on a lenovo T500 so for any1 using one flash with the usb port closest to you, in win 7 there seems to be a difference in this port possibly being the only port with always on charge feature, the drivers handle this port differently.
Install or reinstall drivers with the tab unplugged and only plug it in once your already in download mode.
I used the same pit file posted on the previous page and used the stock 3.1 pda, no csc or modem or bootloader files, would still hang wen other files were included. Re-partition checked. Only use pit file once, later flashes shouldn't require it as you've just rectified you partition table.
Once you got 3.1 on there then continue the 3.2 flashes as you wish and hopefully no more problems.
All done trough odin and please people take your time with these steps, the rom should only take 2-3 mins and if it pauses for more than 1:30, its hung, just press and hold power button leaving everything plugged in and odin open and go straight back into download mode and try again.
I've done this several more times with 8 more roms and havent had an issue with any (all morning). I've broken it on purpose then gone through these steps so that the information is as functional as I can make it.
I know its querky but hopefully this saves someone the anguish we went through.
Sent from my GT-P7300 using Xparent Blue Tapatalk
wyatt23 said:
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Click to expand...
Click to collapse
Lol no I don't develop. But I am glad you found the way! That was the objective!
Sent from my SGH-T959.
Hello my honorable SGT colleagues, I managed to roll back from Overcome P7300 v2.3.0 to the Russian v3.1 stock ROM (PDA/CSC/PHONE) flashing it by Odin 1.85 together with p5_0614 PIT mapping table file kindly provided above by Nirogy325, however in my case in attempt to fix modem firmware. All operations including ROM re-partitioning went absolutely smoothly! However to my regret, this has not fix my problem – every ROM (either stock and custom) I used to try do not flash PHONE firmware properly, with basedband version always indicated as “unknown” in the system properties and GSM/CDMA modem not operable… this malfunction happened after Google map app inadvertently hanged up and I tried to shut down the tablet.. does anybody have a clue what happened with the damned tablet and what might be possible cure? Will be extremely grateful for any advice
Thank you!
Thanks wyatt23 & nirogu325. I had this exact problem and downloaded 7-8 pit files that weren't working until I found this. I was about to get a baseball bat and go Office Space on the tablet. It's working fine now and will get a custom mod as soon as it charges.
Before flashing a new rom, I tried formatting /data and /system manually, via recovery. I also tried (because I'm smart that way) to format the file system drive via a nice little tool called diskwipe, which succeeded. Ever since then, i think I don't have a hard drive anymore on my phone, because it seems the roms I've tried to install are being placed on the sdcard. Windows won't recognize it either (it sees the sdcard).
In linux, it shows me that the filesystem is active, just separate from the phone's memory, which can't be accessed. Also, the /mnt folder is empty.
Roms install fine, just without any access to google play or the beginning step-by-step google registration process and so on. I don't have anything on the phone I can't do without, so any help would be vastly appreciated, because it seems I turned a smartphone into an old Nokia :good:
Thanks!
m
Could you connect your phone still to your pc and does Odin detect it in download mode?
Think then you can try to Restock with repartition selected and do so a clean new flash of the rom of your choice....
rodman01 said:
Could you connect your phone still to your pc and does Odin detect it in download mode?
Think then you can try to Restock with repartition selected and do so a clean new flash of the rom of your choice....
Click to expand...
Click to collapse
yep, works, thanks! my question is how to use it with only one zip file, when odin requests all those separate files. i have the ops file, but where do i put the rom zip? I know there's the one package option, but they're zips, not md5's or whatever. I can just ignore that and load the zip?
No via odin you have to take a tar file...and to restock propperly, take a three parted firmware and partition ticked with 512 pit.
Here is a thread with different tools and especially the first row, with rescue and recovery kits is what you need and can take.
http://forum.xda-developers.com/showthread.php?t=1796807&highlight=adb+download
or take slappys rescue kit, link is indcluded in an other of m post:
http://forum.xda-developers.com/showpost.php?p=36168807&postcount=5
managed to get back to stock via odin and one of the samfirmware packages. many thanks to all! :laugh:
Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
goodflood said:
Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
Click to expand...
Click to collapse
Flashing Stock rom should fix it...
Sent from my moto g(7) play using Tapatalk
@PoochyX That did it; thank you so much!
I have a Samsung SM-T290, running Android 9. Whatever I do, Magisk seems to shrink my data partition from 32G to 8G. I think I scrupulously followed topjohnwu's directions (except that I put the stock AR module on the SD card and moved it between the device and my laptop via sneakernet rather than adb pull). I used Odin to flash BL, the patched AP, CP and CSC (not Home-CSC). Magisk was installed alright, and I achieved root, but my storage was reduced to 8GB.
The only way I've found so far to bring my storage up to 32GB was to factory reset, which removes Magisk and root. I tried extracting the PIT file from CSC in the stock ROM and doing a NAND erase and reformat, but as long as I'm using the patched AR with Magisk, I end up with 8GB.
What am I doing wrong?
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
pgurwitz said:
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
Click to expand...
Click to collapse
I think the speed difference is due to whether it's ending with n.n.tar.md5 or just n.n.tar. The time probably has to do with the unpacking of md5.
By the way: My capacity also shrunk from 32 to 16 GB on my Xcover 4s