After unlocking bootloader there is an irritating warning msg, and after flashing custom software (like magisk patched rom) it gets worse.
In this guide, i will show how to remove both of them. (the bootloader warning msg and custom software one)
NOTE: You can try the following steps on any Samsung device, this guide is universal (but i am not sure it will work, it should work on devices launched after Q2 2019).
On some devices you would have to unpack param.bin instead of up_param.bin (like a30), so see where are bootloader images stored yourself
You can just flash attached up_param.tar.img for m307f with "BL_M307FXXU2ASL2_CL17283099_QB27878150", Just rename "up_param.tar.img" to "up_param.tar" and flash in BL section of Odin.
OR use The Manual Method below to create your own .tar file and flash
STEP 1:
Download the correct firmware of your Samsung device using SamFirm or Frija (see This)
There will be 4 different .md5 files, we need only "BL_XXXX.md5" one.
STEP 2:
Unzip the "BL_XXXX.md5" file with This. (right click -> 7-Zip ZS -> extract to "BL_XXXX.tar")
STEP 3:
Open the "BL_XXXX" folder and Extract the "up_param.bin.lz4" file WITH 7-ZIP EXTRACTOR
Now you will have "up_param.bin".
STEP 4:
Extract param.bin WITH 7-ZIP EXTRACTOR. There are some images in the extracted folder.
Look for the jpg image: booting_warning (contains the yellow triangle image and red text). We will replace this image later with a black one
The svb_orange.jpg file (1080 x 2340 pixels) contains the warning message with the option that says PRESS POWER KEY TO CONTINUE. If you want you can change it to an image identical to the boot or leave it unmodified.
Both images are attached below.
STEP 5:
Open param.bin with 7-zip and replace booting_warning.jpg and svb_orange.jpg by dragging the files into the window.
STEP 6:
Close 7-zip, now you have modified param.bin.
STEP 7:
Convert param.bin to TAR format to flash with ODIN: Select param.bin, right click, choose 7-zip ZS, then add to the file, finally click on file format and change to tar. Accept (OK) and ready we will have the param.tar file ready for ODIN.
STEP 8:
Open ODIN , start your phone in download mode, load the param.tar file in the BL section, Untick Auto-reboot, and click on start.
Enjoy.
Thanks to @blascogm for the original guide located here
Good work ?
Related
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Well its simple just rename it to .tar and use winrar to extract it. the md5 extension makes odin calculate a hash to check if the firmware you're flashing is not corrupted.
hi,
I did that and I got a message "there is no correct record at the end of archive"
the files are extracted but I think it is corrupted because dsixda kitchen can't read it.
just extract it by 7-Zip and don't care about message
I have this problem too, my 7-zpi say that can´t open file format unknowed or damage.
your download maybe interupted, try download it again and do md5 checksum
Ace Duos Kernel
how to get s6802 custom kernel??
jeckyvanz said:
how to get s6802 custom kernel??
Click to expand...
Click to collapse
You can find a beta release custom kernel for the Samsung Galaxy Ace Duos from here.
kernel
thanks. but the download link doesnt work again.
MD5
I've problem with restoring through CWM.
it said "md5 sums mismatch. how to troble it?
logic5 said:
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Click to expand...
Click to collapse
You might be opening the wrong file.
You have to download 2 files:
xxxx.tar
xxxx.tar.md5
the first one is the one you have to open.
the second one is the one that only have the MD5 result of the first.
( http://en.wikipedia.org/wiki/MD5 )
jeckyvanz said:
I've problem with restoring through CWM.
it said "md5 sums mismatch. how to troble it?
Click to expand...
Click to collapse
Redownlaod and try to unzip again. Kitchen should open it, make sure u have kitchen scripts for your phone or edit from flashable zip. Afaik
best idea
dont use 7zip but use unoversal extractor. it will extract everything.
I have the same issue for 5301. I have to get either the recovery or system img for creating a custom rom. Usually samsung firmware files can be extracted using izarc, 7zip or universal extract tool. some can be opened with ultraISO or similar tool. I tried dsixdas kitchen as well. That does not even acknowledge this ROM. These firmwares come as a single tar file with md5 sum attached. There is something different about this ROM file that wont even let let the regular tools see what is inside the file. I tried to open it with a hex editor and it looks similar what a regular tar.md5 file would look. Looking at the log file from universal extractor:
TrID/32 - File Identifier v2.02 - (C) 2003-06 By M.Pontello
Definitions found: 2641
Analyzing...
Collecting data from file: C:\Technical\S5301XXALJ7_S5301OXXALJ8_S5301XXLJ7_HOME.tar.md5
99.3% (.TAR) TAR archive (149/5)
0.6% (.LZMA) LZMA compressed file (1/1)
7-Zip Tar archive extractions cannot be logged.
If Odin can flash these files using the same boot, recovery and system... images then there must be a way to extract these img files. wonder if odin extracts to a temp location?
Here is a link to the file http://hotfile.com/dl/198648982/cfb...5301_EUR_1_20130214151121_61bveu8l1b.zip.html
logic5 said:
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Click to expand...
Click to collapse
Use odinatrix to extrat system.img n modem files..
Its the easiest tool do so...
U may also use splitfus2 bt its way trickier to use than odinatrix.
masum73 said:
I have the same issue for 5301. I have to get either the recovery or system img for creating a custom rom. Usually samsung firmware files can be extracted using izarc, 7zip or universal extract tool. some can be opened with ultraISO or similar tool. I tried dsixdas kitchen as well. That does not even acknowledge this ROM. These firmwares come as a single tar file with md5 sum attached. There is something different about this ROM file that wont even let let the regular tools see what is inside the file. I tried to open it with a hex editor and it looks similar what a regular tar.md5 file would look. Looking at the log file from universal extractor:
TrID/32 - File Identifier v2.02 - (C) 2003-06 By M.Pontello
Definitions found: 2641
Analyzing...
Collecting data from file: C:\Technical\S5301XXALJ7_S5301OXXALJ8_S5301XXLJ7_HOME.tar.md5
99.3% (.TAR) TAR archive (149/5)
0.6% (.LZMA) LZMA compressed file (1/1)
7-Zip Tar archive extractions cannot be logged.
If Odin can flash these files using the same boot, recovery and system... images then there must be a way to extract these img files. wonder if odin extracts to a temp location?
Here is a link to the file http://hotfile.com/dl/198648982/cfb...5301_EUR_1_20130214151121_61bveu8l1b.zip.html
Click to expand...
Click to collapse
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
frankito777 said:
You might be opening the wrong file.
You have to download 2 files:
xxxx.tar
xxxx.tar.md5
the first one is the one you have to open.
the second one is the one that only have the MD5 result of the first.
( http://en.wikipedia.org/wiki/MD5 )
Click to expand...
Click to collapse
Now there is only one xxx_home.tar.md5 file..
That was old days.
Be a part of new world.
N now u cnt extract through an archve manager.
U need espicial tools like splitfus2 n odinatrix to extract files.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
Thanks SArnab! so finally I am able to split the files using odinatrix. Now for this type of turbo ROMs how do I create odin flashable file???
I created a regular odin tar file with md5 sum but that does not go past 'NAND Write Start'. Please advise.
masum73 said:
Thanks SArnab! so finally I am able to split the files using odinatrix. Now for this type of turbo ROMs how do I create odin flashable file???
I created a regular odin tar file with md5 sum but that does not go past 'NAND Write Start'. Please advise.
Click to expand...
Click to collapse
Your pc shud b superfast so that odintrix can work witout lag.
My HP G6 lapi took around 10 mins to extrqct the one .tar.md5 file..
The tool will automatically extract diffrnt .tar files such as modem_xxx.tar pda_xxx.tar n csc_xxx.tar
Now u can use these to flash through odin witout any prb.
U can use pda.tar in kitchen to get boot.img n system.img.
Kitchen will also help u extract sysmtem foldr from system.img.
U can also flash through odin the single .tar.md5....
Choose that in pda field...
Odin is smart enough to do rest of the part.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
Appreciate the quick response. I guess my question was not clear enough. I extracted the recovery and created a clockwork recovery named recovery.img. Now I want to flash this recovery back on the device. I created the tar file using:
tar -H ustar -c recovery.img > CWMrecovery.tar
md5sum -t CWMrecovery.tar >> CWMrecovery.tar
mv CWMrecovery.tar CWMrecovery.tar.md5
When I flash this using odin3_v3.07 md5 is verified but he flash does not go through and stops at NAND write start. Is there a special way to create a odin flashable tar.md5 file foe these turbo firmwares?
masum73 said:
Appreciate the quick response. I guess my question was not clear enough. I extracted the recovery and created a clockwork recovery named recovery.img. Now I want to flash this recovery back on the device. I created the tar file using:
tar -H ustar -c recovery.img > CWMrecovery.tar
md5sum -t CWMrecovery.tar >> CWMrecovery.tar
mv CWMrecovery.tar CWMrecovery.tar.md5
When I flash this using odin3_v3.07 md5 is verified but he flash does not go through and stops at NAND write start. Is there a special way to create a odin flashable tar.md5 file foe these turbo firmwares?
Click to expand...
Click to collapse
Sorry, I have no idea bout wat u r talkin.
I never did this so cant help u in tis part.
Oh ya where did u put the tar file in odin??
In pda fieled or csc or modem??
I think its need to be in pda field.
I cnt help more on this.
But ya I wnt leave it here.
A user named Deadly can help u.
He is great in converting odin to cwm n cwm to odin.
Hope u understan wat I mean.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
System App
how to install custom system ui/android status bar on system. my device gt-s6802. what's compatible with mine??
I've read that the latest 4.0.4 release (XWLPO) still has MMC_CAP_ERASE enabled in it's kernel.
Am I correct in thinking if I replace the zImage file in XWLPO's tar.md5 file with Siyah 3.4.1's zImage file, then flash the firmware through Odin then:
1. I will eliminate the possible brick bug
2. Device will be automatically rooted
I might replace the new bootloader (Sbl.bin) with the old one while I'm at it.
I know I'll have to install Tungstwenty's 4.0.4 camera/video fix after flashing.
Is there anything else I should consider if tweaking the official SamMobile tar file?
Cheers
...
I've tried updating the .tar.md5 archive but I have the following problems/questions:
1. When I open the XWLPO .zip file, as well as the .tar.md5 file, there is an SS_DL.dll file. What is this?
2. When I open the .tar.md5 archive with 7Zip it says "no correct record at the end of the archive"
3. Probably because of this error, if I try to update the archive 7Zip then says "not implemented"
Does anyone know how I can add/replace files in a SamMobile .zip file please?
Thanks
1-Ignore this file. Not needed for nothing.
2-Remove .md5 from the the end of extension .tar.md5 and 7zip open file without problem.
3-7zip does not update tar file. You have to unpack the whole archive and recreate the tar file
So this is taken from http://forum.xda-developers.com/showthread.php?t=2316543 and credit for this goes to the people who figured it all out.
I rewrote, cleaned up, and tailored it to the M7.
This should work with all HTC ONE w/ S-OFF if not you probably need to set your CID to the SuperCID which can be done with this App.
***Disclaimer***
I am no way responsible for what You do with Your Device, You assume all risk and consequences if something goes wrong, everything is provided 'as is' enjoy.
GUIDE
1. Download the Attached Zip SplashCreator .zip (it has everything you need minus the image) i.e. adb and fastboot.
2. Extract the SplashCreator.zip to a folder on your desktop. e.g. ...desktop\splash
3. Take your image and size it to 1080x1920 save as PNG, JPG, or BMP. (use what ever editor you like)
4. Take the image and place it in the 'image' folder of the zip you downloaded and extracted
5. based on the image extension you used select from the menu and convert to splash1.nb0
6. Open the splash folder and copy/ADD the splash1.nb0 you created to the splash.zip file inside of the 'other' folder
7. Select option 5 to flash and follow the prompts.
7a. If the boot splash doesn't take effect select option 5 and set your CID to the SuperCID. (You can revert after you're done using option 6)
If you get stuck at the grey HTC logo don't worry just hold power till the device resets or use option 8 and start over.
I've uploaded the boot image I've been using if anyone else wants to use it feel free, download mushroom.zip, extract and follow instructions 6 and 7.
( MD5: 7F253CBCCEDC97C0E410AB9BCA14D10C SoltySplashCreator.zip )
( MD5: 03077AF50936A6F39E2349FCD55411B9 Mushroom.zip )
Updated everything and should all be working now. Let me know if you have any issues.
Hi all recently purchased the Mecool KM8 P 2GB/16GB S912 Amlogic, updated the firmware to 7.1 but lost root access. I have managed to find some instructions on a Russian website to root the stock firmware but can't make head nor tale of it and don't want to brick the device.
The google translate version of the instructions reads as follows:
To get root 7 Androide did:
1.Nado SuperSu create a text file without an ending .txt textBOOTIMAGE = / dev / block / boot
2. Flash card throw Recovery for 7 Androyd created Fail SuperSu and SuperSU.zip (5,63 MB)
3. Boot into Recovery with USB there "Advanced" ==> "File Manager" find the file on a flash drive that put his name it .SuperSu in and copy it into the folder / system
3. Without leaving the Recovery go to "Set" and set SuperSU.zip (5,63 MB)
Can someone please help to decipher the above?
Here's the link to the instructions website. The downloads are pinned to the top of the page. Please let me know if you have any success...
http://4pda.ru/forum/index.php?showtopic=807465&st=1100#entry62380504
1. Create a texfile with this content:
BOOTIMAGE = /dev/block/boot
If I am not mistaken then this file should be saved wit the name .SuperSU and no extension.
2. Copy this file and the Supersu.zip onto a SD with a working TWRP recovery.
3. The file .SuperSu is now to be copied into the system folder - it does not specify if the one from the box or the one from the recovery is used - I assume the one on the box. But needs to be tested to be sure.
4. Without ending the recovery session go back and install install SuperSu.
Thing is you need a recovery that works with Nougat to do any of this.
But then again translators suck and someone capable of reading russing could bring some light on it....
Managed to get it to work. Steps in common English are as follows:
To get root on Android 7.1:
1. Create a text file (eg in Notepad) and name it Supersu without an ending .txt with the folowing text BOOTIMAGE = / dev / block / boot
2. On a microsd card copy Recovery.img (TWRP 7), the created SuperSu file (from step 1) and SuperSU.zip (5.63 MB)
3. Insert the card into Boax and boot into Recovery.
4. Using theTWRP recovery got to Advanced" then "File Manager" find the created Supersu file (from step 1) and copy it into the folder / system.
5. Without leaving the Recovery go to "Install" and flash SuperSU.zip (5.63 MB) from the Microsd card
can you post the required Files here?
i dont understand russian so i dont know what they wrote on 4pda.ru
I have found all file and attached at end of the Post
1. decompress km8p.zip to the root of your TF-Card so you have 3 Files on the root of your TF-Card (.SuperSU, SuperSU.zip and recovery.img)
2. power off your KM8P
3. Press Reset and hold it
4. Power your Box on and hold Reset
5. If you see the TWRP-Logo you can stop press Reset
6. On the Screen accept write and modifying Systemfiles
7. go to Advanced" then "File Manager" copy .Supersu file from TF-Card in/ system of your Box
8. then go to "Install" and flash SuperSU.zip (5.63 MB) from the TF-Card
9. Reboot and now you have root installed
MetaIIica said:
I have found all file and attached at end of the Post
Click to expand...
Click to collapse
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
afehst said:
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
Click to expand...
Click to collapse
I attached the TWRP for Android 7 here, if you still need it.
I have also started a thread on how to root with Magisk instead of supersu, as supersu wouldn't work for me.
https://forum.xda-developers.com/android-stick--console-computers/amlogic/howto-km8-p-2gb-8gb-s912-amlogic-tv-box-t3745937
Got my SM-A217F rooted first attempt,
So what i did was.....
1) used Frija-v1.4.4 to download my latest stock firmware "SM-A217F_1_20210807114045_mzeyu27v8u_fac.zip"
2) Extracted the zip file and flashed the 4 files with "Odin3_v3.14.4"
3) after that i let the phone restart and boot up entered my google account details etc etc
4) on PC i used winrar and extracted the "boot.img.lz4" file only from "AP_A217FXXU6CUH1_CL21842546_QB42174009_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5"
5) on PC i then used "lz4_win64_v1_9_3" i copied the extracted "boot.img.lz4" file into the "lz4_win64_v1_9_3" folder
6) op PC inside the "lz4_win64_v1_9_3" folder i dragged the "boot.img.lz4" file onto "lz4.exe" wich created a new file "boot.img"
7) copied the "boot.img" file onto my phones internal storage
8) on phone i installed "Magisk_patched_for_A21S.apk" and opened it --> chose "Install" -->"select and patch a file" --> select "boot.img" from step 7 --> normal android way
9) That created a "magisk_patched-22104_0x2Ov.img" file in my phones "download" folder
10) Renamed that "magisk_patched-22104_0x2Ov.img" to "boot.img" on my phone
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
13) On PC i used "Odin3_v3.14.4" and flashed the "boot.img.tar" file to my device, i left "Auto reboot" and "F reset time" ticked
14) after flashing and getting the green "PASS" logo i left my phone pluged into the the pc the whole time while the phone was restarting
15) after phone rebooted i installed "Magisk" with the "Magisk_patched_for_A21S" app --> let it reboot again after install
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
AND THATS IT
ONE A21S SUCCESSFULLY ROOTED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NB: thank grccorps for this excellent magisk
thanks you
[email protected] said:
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
Click to expand...
Click to collapse
This is not completely clear for me.
Compressing boot.img to .tar is action different from renaming it.
What exactly happened?
BTW:
Similar case with boot.img.lz4 and boot.img.
Renaming doesn't mean uncompressing or compressing file then finally people might have two different things inside what could cause confusion and in one of two described situations potential bootloop/brick.
Maybe this was the reason that some folk achieved success and other not?
Let's clarify that for benefit all of us.
Please anyone explain.
F308 said:
This is not completely clear for me.
Compressing boot.img to .tar is action different from renaming it.
What exactly happened?
BTW:
Similar case with boot.img.lz4 and boot.img.
Renaming doesn't mean uncompressing or compressing file then finally people might have two different things inside what could cause confusion and in one of two described situations potential bootloop/brick.
Maybe this was the reason that some folk achieved success and other not?
Let's clarify that for benefit all of us.
Please anyone explain.
Click to expand...
Click to collapse
Okay i see how this might cause confusion,
###########################################################################
STEP 10 : was just a rename no software used
STEP 11 : i used "ZArchiver" to comprerss and change the file from ".img" to ".tar" (not just rename)
###########################################################################
Thank you.
I will root my M12 soon, it will eventually save me some hours of unnecessary efforts.
My English is pretty bad, so please excuse me..
I copied the "boot.img.tar" to my PC.
under which tab do I have to insert them in ODIN?
But no matter what I try I get an error.
No, I changed them in step 11 with ZArchiver.
I just want to root my phone. Greeze
At start - don't apologize your English.
Not even Englishmen speak English.
At step two:
You are lucky you didn't land in bootloop or brick zone.
Even I was there because I was too fast to go into action.
I suggest to read at least 500 posts about rooting, myself I did it.
You will avoid lot of headache and will save much time.
[email protected] said:
Got my SM-A217F rooted first attempt,
So what i did was.....
1) used Frija-v1.4.4 to download my latest stock firmware "SM-A217F_1_20210807114045_mzeyu27v8u_fac.zip"
2) Extracted the zip file and flashed the 4 files with "Odin3_v3.14.4"
3) after that i let the phone restart and boot up entered my google account details etc etc
4) on PC i used winrar and extracted the "boot.img.lz4" file only from "AP_A217FXXU6CUH1_CL21842546_QB42174009_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5"
5) on PC i then used "lz4_win64_v1_9_3" i copied the extracted "boot.img.lz4" file into the "lz4_win64_v1_9_3" folder
6) op PC inside the "lz4_win64_v1_9_3" folder i dragged the "boot.img.lz4" file onto "lz4.exe" wich created a new file "boot.img"
7) copied the "boot.img" file onto my phones internal storage
8) on phone i installed "Magisk_patched_for_A21S.apk" and opened it --> chose "Install" -->"select and patch a file" --> select "boot.img" from step 7 --> normal android way
9) That created a "magisk_patched-22104_0x2Ov.img" file in my phones "download" folder
10) Renamed that "magisk_patched-22104_0x2Ov.img" to "boot.img" on my phone
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
13) On PC i used "Odin3_v3.14.4" and flashed the "boot.img.tar" file to my device, i left "Auto reboot" and "F reset time" ticked
14) after flashing and getting the green "PASS" logo i left my phone pluged into the the pc the whole time while the phone was restarting
15) after phone rebooted i installed "Magisk" with the "Magisk_patched_for_A21S" app --> let it reboot again after install
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
AND THATS IT
ONE A21S SUCCESSFULLY ROOTED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NB: thank grccorps for this excellent magisk
Click to expand...
Click to collapse
If this works id pay you if i had money
Scia0 said:
If this works id pay you if i had money
Click to expand...
Click to collapse
It works ive done this personally
Does it work on Android 12 and with u8 protection
hamada2001 said:
Does it work on Android 12 and with u8 protection
Click to expand...
Click to collapse
Hello everyone.
I have read all the messages from the first to the last post from root to a21s.
Currently I just have to follow the steps in the first message without using modified magisk to be able to root?
Forgive my English I am Spanish and I use google translate.
localdemoda said:
Hello everyone.
I have read all the messages from the first to the last post from root to a21s.
Currently I just have to follow the steps in the first message without using modified magisk to be able to root?
Forgive my English I am Spanish and I use google
Click to expand...
Click to collapse
what android version are you on
I have android 12 but I can install android 11, which one is better for root?
ies thiss is best guide to root a21s im downgroaded to android11 (U8) .dont forget oem lock/bootloader unlock mode.