[GUIDE] EFS/NV_DATA full backup and restore manually -- Extract / Post your pit file - Galaxy S 5 General
Here i will show you how to backup & restore EFS and NV_data manually for some variants of Galaxy S5 without a third party app or tool.
Sure a third party app or tool will do the job, but it is good to learn something.....
Backuping efs partition is an essential step to keep it safe after rooting since a bad flashing/modding of your S5 may result in a corruption of that partition. so it is better to be safe than sorry, so any disturbance in the EFS data might result in null IMEI and baseband version.
This will backup data like device specific essential information such as the IMEI (International Mobile Station Equipment Identity), wireless device MAC address, baseband version, product code, system ID and NV data.
You must have a proper root access in addition to busybox installed (preferred)
you can dump these partitions also using adb shell command. but here i will show you how to backup using a terminal emulator.
{
"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"
}
How to do it
Backup EFS/NV_data for SM-G900F/T/P/A/I/M/W8 variants:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/modemst1.bin
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/modemst2.bin
copy images from internal sdcard to a safe place such as pc.
Note that the size of .img and .bin must be as follow: efs (14MB) modemst1/2 (3MB each)
Restore EFS/NV_data for SM-900F/T/P/A/I/M/W8 variants:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!) :
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p12
dd if=/mnt/sdcard/modemst1.bin of=/dev/block/mmcblk0p13
dd if=/mnt/sdcard/modemst2.bin of=/dev/block/mmcblk0p14
Backup EFS/NV_data for SG-900H variant:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
copy images from internal sdcard to a safe place such as pc.
Note that sizes of .img and .bin must be as follow: efs (20MB) m9kefs1/2/3 (4MB each)
Restore EFS/NV_data for SG-G900H variant:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!):
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
pit files
Extract / Post your pit file
Pit file is needed to be flashed when the partition table of your device is corrupted due to some reason such as a wrong flash of your variant.
When partition table is corrupted or missed from your device, odin will tell you when flashing firmware that there is "no pit partition" or "Re-Partition operation failed", in this case pit file must be flashed along with the stock firmware (or alone) with "re-partition" ticked in odin.
--DO NOT flash pit file if there is no need for it--
There is some ways to extract pit file from your device such as using "heimdall" or some tools.
Here i will show you how to extract the pit file manually with a simple way using terminal emulator or adb shell command.
your phone must have a proper root access, with busybox installed (preferred).
how to do it
With terminal emulator:
Download and install terminal emulator from play store.
Open it and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See the pit file in your internal sdcard, move it to pc
With adb shell:
You must have android sdk installed in your pc.
Enable "usb debugging" in "developer options", connect your phone to pc, open a cmd window (shift+right mouse click) and type:
Code:
adb devices
adb shell
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See your pit file in your internal sdcard and move it to pc.
Please attach the extracted pit file in a zip in this thread and mention your S5 variant name and storage (16/32GB) that other users can benefit from it
THX to
@linty
@xtechx
@fffft
@jeffreylin_
@tdunham
@ratatouille
@LoSt180
@babygau
@felstar
@born4trance
@demdix
@qwerty22
@/ofAllEvil
@Max One
@hawst
@androidrouen
reserved
attachment and content removed, can delete post if desired.
xtechx said:
thanks! I've attached a PIT from my phone, if anyone needs it
Click to expand...
Click to collapse
hmm... can not open it with pit magic tool
there is something wrong.
can you post outcome of
Code:
cat /proc/partitions
attachment and content removed, can delete post if desired.
xtechx said:
weird. I'm running it from Ubuntu 14.04, x64, but I don't think that should matter. I have a couple Windows systems here too... I'm suspect of this cable, it seemed to damage a zip file I tried to flash once (was supposed to be 570MB< but it only copied 70MB)...but everything else has copied fine, including that file when I did it a second time...so not sure...
I re-ran the command, just in case. I've also included the output from /proc/partitions
addition: this time I zipped it on my computer, where as last time I zipped it with root explorer
Click to expand...
Click to collapse
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
samersh72 said:
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
Click to expand...
Click to collapse
Done
xtechx said:
Done
Click to expand...
Click to collapse
:good: yes it worked!
thank you
i will add it to second post
samersh72 said:
:good: yes it worked!
thank you
i will add it to second post
Click to expand...
Click to collapse
You're welcome! I'll edit my posts to remove the bad zip files, so that no one downloads them by mistake.
SM-G900F pit file added.
Looking for someone rooted that is willing to create an SM-G900T (Tmobile) PIT that can be used with Heimdall or JOdin. No Windows machines in my house.
Thanks!
i have this error msg with SM-G900F pit
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANCE_G900FAUT1ANC7_G900FXXU1ANCE_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
joeknoob said:
i have this error msg with SM-G900F pit
Click to expand...
Click to collapse
I see problem in connection at first flash
But in second step Pit is set properly.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer
Why you are flashing with pit?
Sent from my N91
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
..
samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
i need pit for my G900F - 16GB AUT (Switzerland)
this is reason for my flashfail
(sorry for my bad english)
jeffreylin_ said:
.pit file for the SM-G900H 16 GB variant.
Click to expand...
Click to collapse
thank you, but the zip is empty!?
jeffreylin_ said:
Huh, that was weird. Let me try that again.
Click to expand...
Click to collapse
Pit Zip added! thank you :good:
samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
Hi.
I have this problem too. I`m searching pit file g900f for firmware (SER) region Russia. Maybe you have this file?
Related
[Q] [HELP] Samsung Galaxy S Anycall M110S Nandroid Backup/ Soft Brick
Good Day Folks. So yesterday I was flashing my Samsung Galaxy S M110S (Korean Version) with a stock rom (M110S-Gingerbread-HOME-IMAGE-REV03-VG26-1812-USER.tar) and installing Tegrak Kernel V29. Everything works smoothly until I flashed a ClockworkMOD Recovery not intended for my phone(sorry I was foolish and flash a CWM meant for other device) then when I open my device I am always brought to this (Samsung Stock Recovery) Samsung utils blah. blah. # MANUAL MODE # E:failed to mount /cache (Invalid Argument) E:Can't mount /cache/recovery/recovery_kernel_log E:copy kernel file :: Can't open /cache/recovery/recovery_kernel_log E:failed to mount /cache (Invalid Argument) E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log blah.blah Click to expand... Click to collapse I am only allowed to navigate with 3 options; Reboot, Wipe Data, Wipe Partition. Rebooting only brings me to the recovery, both wipes provides the same error. So I try to flash again with the same stock rom and ODIN keeps on throwing me this: <ID:0/003> Added!! <ID:0/003> Odin v.3 engine (ID:3).. <ID:0/003> File analysis.. <ID:0/003> SetupConnection.. <ID:0/003> Initialzation.. <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> modem.bin <ID:0/003> <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Click to expand... Click to collapse Left with no idea, I flashed an iCarus SpeedMod kernel(via ODIN) to see what will happen. Luckily the recovery is now CWM and I was entitled with so many options. One of this is the Backup/Restore option so I think that if I have the right backup files stated below, I can put it into the internal SD card(I have access) and launch the Restore option to bring my phone back to life. cache.img data.img dbdata.img nandroid.md5 and all the other files you get when backup-ing files using CWM. I am asking for your full help. Please be noted that my device: Can access Download Mode Can access Recovery Mode(no function) Can be recognized by ODIN and be flashed. ...and is in need for a very big help! So for those of you who has a nandroid backup(if my terms are correct) of a Samsung Galaxy S M110S or has an idea to resurrect my device I will be very thankful. And If I can add I can also select Apply Update Via ZIP. Does that mean I can also apply zip updates? If yes, where can I find those?
please help me with this one.
gertnilo said: please help me with this one. Click to expand... Click to collapse Seems an old post (just came across this ....anyway You need to flash files from the repair kit, download from links below
Help internal mmc block !! galaxytab P1000
recently my galaxy tab keep crashing till it suck in the startup in a flashing logo of samsung i tried odin never works then i went to samsung maintenance they say u hav to change the motherboard !! i really dont think the problem from the board i really hope it can be fixed by using some kind of software here is the text that i got from the recovery mode --verfing internal mmc block E: failed to mount mmc : open file internal mmc checksum verify failed. #MANUAL MODE# --updating application ... E: failed to mount /preload (no such file or directory) E: install_application_for_customer:cant mount / preload your storgare not prepare yet , please use UI menu for for format and reboot actions . --Appling multi-csc... installing multi -csc multicsc : scan access to ojxcom . multicsc : opera mini[lib] reset . appliedthe CSC-code 'xss'. successfully applied multi-csc . Click to expand... Click to collapse
I think the problem should be solved if you restock to stable gingerbread.. . Sent from my GT-P1000 using xda app-developers app
tnx for the reply i tried gingerbread it never works :/ kies cant open the tab my rom was froyo 2.2
He meant you should flash GB using Odin, not upgrade via Kies. Follow my signature, download Overcome's PDF guide, and GB-Stock-Safe-v5 (it has all the tools you need in it). Open the guide, jump to page 7, put tab to download mode, and flash according to that guide.
so no need to kies. cuz when it happen i tried other tut required kies i couldn't pass the first stage in oden then it bricked i'll try it hope it will work tnx guys
sorry guys same result it failed in the end of first stage i got this message in odin <ID:0/004> Added!! <ID:0/004> Odin v.3 engine (ID:4).. <ID:0/004> File analysis.. <ID:0/004> SetupConnection.. <ID:0/004> Initialzation.. <ID:0/004> Set PIT file.. <ID:0/004> DO NOT TURN OFF TARGET!! <ID:0/004> Get PIT for mapping.. <ID:0/004> Firmware update start.. <ID:0/004> boot.bin <ID:0/004> cache.rfs <ID:0/004> dbdata.rfs <ID:0/004> factoryfs.rfs <ID:0/004> movinand.mst <ID:0/004> <ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Click to expand... Click to collapse
Looks like a bad internal sd chip.
Follow ChrisCTX's guide...search for it Sent from my GT-P1000 using xda app-developers app
Help with extracting AT&T S5 G900A Stock Rom and change Language
hi guys i need your help my phone S5 G900A AT&T Rom 5.1.1 With no root and can't downgrade or add custom recovery i need unpack to change my phone language and delete AT&T Programs in lollipop ROM 5.1.1 stock ROM I made the next steps.. if could clarify the wrongs in those steps .. thank you very much i am using ubuntu 16.04 LTS first : i have stock ROM with 4 files AP - BL - CP - CSC G900AUCU4COI5_CL5869384_QB6398515_REV00_user_low_s hip_MULTI_CERT i need to extract AP_G900AUCU4COI5_CL5869384_QB6398515_REV00_user_lo w_ship_MULTI_CERT.tar.md5 and edit system.img.ext4 by right click on file system.img.ext4 and open with ARK and extract it now i have those files boot.img - persist.img.ext4 - recovery.img - system.img.ext4 I've downloaded "img-tools" to change ext4 to img i take a system.img.ext4 file and but it in img-tools folder in my home and do this commands right click and chose Open in Terminal in img-tools folder sudo su enter password simg2img system.img.ext4 system.img makdir system mount -t ext4 -o loop system.img system/ Click to expand... Click to collapse now i have mounted system.. i well open it with this command sudo nautilus enter password Click to expand... Click to collapse and delete APK files > Code: system/APP/*.APK system/framework/framework-res.apk system/framework/twframework-res.apk from the same ROM and replace it with the same files from other ROM S5 G900H lollipop 5.1.1 with national language when finished i need to repack files with this command tune2fs -l system.img | grep "Block size" Block size: 4096 tune2fs -l system.img | grep "Block count" Block count: 656384 ech $((4096 * 656384)) 2688548864 make_ext4fs -s -l 2688548864 -a system system.img.ext4 system Click to expand... Click to collapse now i have my edited sysytem.img.ext4 i need to but it back in the same folder with the next files to repack it in "tar.md5" file to flash it Code: boot.img persist.img.ext4 recovery.img this commands well do it tar -H ustar -c boot.img persist.img.ext4 recovery.img system.img.ext4 > my_final_packeg.tar md5sum -t my_final_packeg.tar >> my_final_packeg.tar mv my_final_packeg.tar my_final_packeg.tar.md5 Click to expand... Click to collapse finally i have the last file to flash it ((my_final_packeg.tar.md5)) the problem is when i flash it by odin3 v3.11 i have this massage <ID:0/003> Added!! <ID:0/003> Odin engine v(ID:3.1101).. <ID:0/003> File analysis.. <ID:0/003> SetupConnection.. <ID:0/003> Initialzation.. <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> SingleDownload. <ID:0/003> boot.img <ID:0/003> NAND Write Start!! <ID:0/003> persist.img.ext4 <ID:0/003> recovery.img <ID:0/003> system.img.ext4 <ID:0/003> FAIL (auth)! <ID:0/003> <ID:0/003> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/003> Removed!! Click to expand... Click to collapse i need your help and Sorry about my bad language
Softbricked my old Galay GT P1000 - can anyone help.
Heyas. I'm hoping someone can point me in the right direction. I'm trying to refresh an old Galaxy Tab (GT-P1000) for my son. Not the first time I've done this but the first time I've hit a deadlock. I've reviewed the [Guide]How to unbrick your galaxy tab. Not helping unfortunately. Background: I've installed TWRP (CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar) on the device using ODIN. Installed OK. Booted into the OS fine afterwards. I copied the firmware (cm-13.0-20160519-UNOFFICIAL-p1.zip) and GAPPS from the microsd card to the /download folder as I've had issues seeing the card from the recovery app. Booted into recovery - did a system, data and dalvik cache wipe. Installed the CM13 image and rebooted. The message I got was: failed to mount '/system' (invalid argument) failed to mount '/data' (no such device) In an attempt to fix the mount issues I reflashed including a PIT. Now nothing is mounting - I'm guessing I've blown away the partitions. I can get to the Clockwork recovery application but I can't flash from the SD card as it needs a file system to mount to I'm guessing. Can anyone point me in the right direction to begin troubleshooting this? If I try to reflash using ODIN, a PIT file and GB_Stock_Safe_v5.tar ODIN zips through till it gets to: <ID:0/004> factoryfs.rfs At which point it seems to hang up. eventually ODIN times out with a Fail message. If I reboot I get the soft brick logo of the mobile and PC with the yellow triangle. From this point I can reflash Clockwork Recovery Mod (CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar) and get to the download screen again if need be. I just don't seem to be able to get a working OS up. Message log reads: <ID:0/004> Added!! <ID:0/004> Odin v.3 engine (ID:4).. <ID:0/004> File analysis.. <ID:0/004> SetupConnection.. <ID:0/004> Initialzation.. <ID:0/004> Set PIT file.. <ID:0/004> DO NOT TURN OFF TARGET!! <ID:0/004> Get PIT for mapping.. <ID:0/004> Firmware update start.. <ID:0/004> boot.bin <ID:0/004> cache.rfs <ID:0/004> dbdata.rfs <ID:0/004> factoryfs.rfs <ID:0/004> Removed!! <ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
Question Error by Flashing - Odin - <D:0/006> Re-Partition operation failed.
Hello everyone
{
"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"
}
I followed this video to root my S21 Ultra 5G (
).
Everything really worked wonderfully and I have repeated each step several times to rule out errors.
Unfortunately, at the final step, the error "Re-Partition operation failed." happens and I can't find any information on what exactly this could be. I have also tried a new version of Magisk and Odin, re-downloaded the firmware several times, also fetched the AP files via adb pull from the device after patched with magisk, but the error unfortunately remains the same.
Software: Frija 1.4.3
Model: SM-G991B
CSC: MAX
Firmware: G991BXXU3AUE1 (this was also installed before)
As written in the video, I used the file "CSC_OMC_OXM_G991BOXM3AUE1...." for CSC, and not HOME_CSC_OMC_OXM_......
Odin 3B PatcheD/ModdeD v3.14.1 (also tested with 4.14.4)
I hope someone else has an idea :/
Best regards
CYB3RV3N0M said: Hello everyone I followed this video to root my S21 Ultra 5G ( ). Everything really worked wonderfully and I have repeated each step several times to rule out errors. Unfortunately, at the final step, the error "Re-Partition operation failed." happens and I can't find any information on what exactly this could be. I have also tried a new version of Magisk and Odin, re-downloaded the firmware several times, also fetched the AP files via adb pull from the device after patched with magisk, but the error unfortunately remains the same. Software: Frija 1.4.3 Model: SM-G991B CSC: MAX Firmware: G991BXXU3AUE1 (this was also installed before) As written in the video, I used the file "CSC_OMC_OXM_G991BOXM3AUE1...." for CSC, and not HOME_CSC_OMC_OXM_...... Odin 3B PatcheD/ModdeD v3.14.1 (also tested with 4.14.4) I hope someone else has an idea :/ Best regards Click to expand... Click to collapse Saw this posted on Android Central. You could try: Copying/extracting the pit file from the CSC file of your firmware using 7zip ( you will have to remove the .md5 extension from the file name ) Load Odin with all files (bl,ap,cp,csc) in options section select re-partition in pit section load pit file ( one you extracted from csc ) then flash in Odin Using pit file will erase any data on your phone
Hi spawnlives, Thanks for your reply. I did some more tests today and really don't understand where the error is. I downloaded the firmware (Frija-v1.4.3) unzipped with 7Zip and loaded in Odin3 v3.14.1_3B_PatcheD all the original files and still there is the same error. I specially used a USB 2 port after that was also mentioned in a forum as a possible reason. Test 1 Original-Files (BL, AP, CP, CSC_OMC) unchecked auto reboot, check re-partition Result: Code: <ID:0/007> Odin engine v(ID:3.1401)... <ID:0/007> File analysis... <ID:0/007> Total Binary size: 10652 M <ID:0/007> SetupConnection... <ID:0/007> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Test2 I also followed your tip, unpacked the CSC_OMC_OXM_G991BOXM3AUE1_CL21556388_QB39941804_REV01_user_low_ship_MULTI_CERT.tar with zip, but it gave an error message: "There are some data after end of payload data". Then loaded all files from the firmware (BL, AP, CP, CSC_OMC), added the PIT file, activated the checkbox re-partition. Result: Code: <ID:0/007> Odin engine v(ID:3.1401)... <ID:0/007> File analysis... <ID:0/007> Total Binary size: 10652 M <ID:0/007> SetupConnection... <ID:0/007> Can't open the serial(COM) port. <OSM> All threads completed. (succeed 0 / failed 1) Test 3 Files from firmware loaded (BL, AP, CP), no CSC file, additionally the PIT file added, the checkbox re-partition activated. Result: Code: ID:0/007> Odin engine v(ID:3.1401)... <ID:0/007> File analysis... <ID:0/007> Total Binary size: 9694 M <ID:0/007> SetupConnection... <ID:0/007> Initialzation... <ID:0/007> Set PIT file... <ID:0/007> DO NOT TURN OFF TARGET!!! <ID:0/007> <ID:0/007> Re-Partition operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Test 4 Files from firmware loaded (BL, AP, CP, HOME_CSC) Result: Code: <ID:0/007> Odin engine v(ID:3.1401).. <ID:0/007> File analysis.. <ID:0/007> skip file list for home binary <ID:0/007> userdata.img <ID:0/007> misc.bin <ID:0/007> metadata.img <ID:0/007> Home Binary Download <ID:0/007> Total Binary size: 9705 M <ID:0/007> SetupConnection.. <ID:0/007> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Best regards
CYB3RV3N0M said: Hello everyone I followed this video to root my S21 Ultra 5G ( ). Everything really worked wonderfully and I have repeated each step several times to rule out errors. Unfortunately, at the final step, the error "Re-Partition operation failed." happens and I can't find any information on what exactly this could be. I have also tried a new version of Magisk and Odin, re-downloaded the firmware several times, also fetched the AP files via adb pull from the device after patched with magisk, but the error unfortunately remains the same. Software: Frija 1.4.3 Model: SM-G991B CSC: MAX Firmware: G991BXXU3AUE1 (this was also installed before) As written in the video, I used the file "CSC_OMC_OXM_G991BOXM3AUE1...." for CSC, and not HOME_CSC_OMC_OXM_...... Odin 3B PatcheD/ModdeD v3.14.1 (also tested with 4.14.4) I hope someone else has an idea :/ Best regards Click to expand... Click to collapse Oh man, you're flashing the wrong firmware. You say that you have a S21 Ultra 5G but you are referring to the SM-G991B device which is the REGULAR S21 !!! The S21 Ultra is SM-G998B ...
Oh my ****ing god... this is so embarrassing... you're absolutely right, I was going by the model name in the video and didn't notice that he might have a different model.... Of course with the right firmware it worked right away, no problems. Many many thanks Shame on me...