[Q] Kernel Update thru' Odin - General Questions and Answers

guru's... can you help me on how to update my I9100G kernel using superatmos v.1
i have joint two files using hjsplit and as a result of one file which is a zip file. i tried to flash using odin but could not distinguish the zip file. therefore i have extracted the zip file and have 6 files on it.
- boot.img
- cache.ext4.tar
- data.ext4.tar
- nandroid.md5
- recovery.img
- system.ext4.tar
Odin usually uses the tar files but i don't know to which should i put in the following:
- Bootloader
- PDA
- PHONE
- CSC
could anyone guide me through flashing.
thank you in advance.

another concern is...
i have successfully tried to flash superatmos v2.2 because it is already on tar file. but after flashing, i notice a yellow triangle during boot and i have my binary count of 1.
so to make it unroot, i have flash again to my original rom 2.3.6 jkk1 and the triangle was gone but the binary count isn't. i there any consequences of having binary count?

I think flashing an un secure kernel increase the binary count.

@pamma...
did you try rooting your smartphone? any experience with yellow triangle?

Related

boot.img --> boot.tar.md5 then flasing it with odin

My cwm got broken (though my phone is working ok , but I am not able to flash anything cmw does not detect sdcard),
Now I have extracted boot.img from the kernel.
I want to flash it with the odin.
When I convert the boot.img using Caboomi's_Recovery_img2tar_odin_maker, it just makes a 11kb file. and the terminal shows the following information,(in the image).
I have two Queries:
1) How shall I convert boot.img to boot.tar.md5
2) In the Odin , Where shall I pick the boot.tar.md5 file . (in bootloader, in pda, in phone, or in CSC?)
Regards,
Shikhar
PS: Its Galaxy Y Pro Dous 5512

restock problem

Hi all
I flashed some custom ROMS for my Galaxy SL GT-I9003,it was very slow and unstable
so I decided to flash stock firmware for my phone.
I'm flashing by ODIN v1.82 or v1.85
but I can't to find and haven't necessary files
PIT,BOOTLOADER,PHONE and CSC.
I have flashed firmware only with PDA,but only there is bootanimation.
and system don't starts.
firmware: I9003XXLE4
Please help me.
Thorgoton said:
Hi all
I flashed some custom ROMS for my Galaxy SL GT-I9003,it was very slow and unstable
so I decided to flash stock firmware for my phone.
I'm flashing by ODIN v1.82 or v1.85
but I can't to find and haven't necessary files
PIT,BOOTLOADER,PHONE and CSC.
I have flashed firmware only with PDA,but only there is bootanimation.
and system don't starts.
firmware: I9003XXLE4
Please help me.
Click to expand...
Click to collapse
Greetings;
If your ROM file extension is: *.zip | *.rar | *.tar | *.tar.gz | etc...
You must de-compress it and you will have the files you need.
Some developers pack their ROMs Differently.
i.e: 1 file (*.tar - Zip kind)
To flash them you must enter Recovery Mode (i assume you have ClockWork Mod Recovery) and install from "ZIP File"
If you have only 1 or 2 files:
in example: "I9003XWKPG_I9003XXKPN_I9003DBTKP2_HOME.tar.md5"
These files you must Load the file under PDA Section.
if the file extension is *.pit (obviously) just load under PIT section.
Let me know if you need any further help.
Please Press Thanks Button if it Helped you as this will keep me motivated to help others, doing Tutorials; Apps etc...

Note 3 neo boot loop. Nand erazed. No backup.

hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide
@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/
SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here

[APP] [T285] [2017/12/08] Boot Logo Changer

Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
gian20 said:
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
Click to expand...
Click to collapse
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
gian20 said:
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
gcrutchr said:
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
Click to expand...
Click to collapse
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Unable to change Boot Logo
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
Click to expand...
Click to collapse
SM T285 flash wrong bootlogo.zip
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
hassansys2 said:
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
soaib333 said:
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
gcrutchr said:
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
Click to expand...
Click to collapse
yes sir the jpg file is around 600 kb..... sir please help me..... :crying::crying::crying::crying::crying::crying:... please tell me sir what can i do for recover my device... sir please...... please sir :crying::crying::crying::crying::crying::crying::crying:
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
sir please, can you send me stock boot logo tar.md5 file for SM-T285 ...... beacuase my phone is bricked.. only download mode is working...... if i flash the orignal bootlogo.tar.md5 i hope it will recover please sir help me.... i request you sir please :crying::crying::crying::crying::crying::crying:
I have a huge problem. I made the .jpg file too big and now the tablet won't boot except for DOWNLOAD MODE. I wasn't able to backup so I just downloaded the param.ifs from this reply.
gian20 said:
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Click to expand...
Click to collapse
Now I am using Windows 7 Heimdall to flash this. Except with this I am unable to flash because it's showing "Error: Failed to retrieve config descriptor."
Need help ASAP
Update: After a few tries, now it says
"Initializing Protocol...
Error: Failed to send data!Releasing device interface...
Solution: Used Odin. Basically, using 7zip, packed the param.lfs to a tar file, then packing that to a gzip file, then prooding to flash via ODIN
Any one have stock param.tar file for flashing on sm-t285?? Plz help me? ? ?
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Darksnite said:
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Click to expand...
Click to collapse
How big is the image you are trying to install?
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 150 kb i dont have it now but i can get it again but i did make sure the picture was below 200 kb
And when i factory data reseted the phone it still have the same logo
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Darksnite said:
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Click to expand...
Click to collapse
You need yo rename your image to: logo.jpg
Then use 7zip or winrar to open bootlogochanger. replace the logo.jpg in the zip file with your logo.jpg

Insert ROM in PDA file

I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing. I have a PDA file for my old GT-S6102 Galaxy Y,........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is also specific to your device as well.
https://forum.xda-developers.com/galaxy-y
With that guidance...
Your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2063534
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
Click to expand...
Click to collapse
It doesn't quite work like that, you can create your own Odin flashable file(.tar.md5) containing the custom ROM, but it isn't as simple as just pasting the system.img into the .tar.md5.
Here are some threads for extracting Odin files and for creating your own .tar.md5 using the custom ROM file.
This thread is for correctly extracting the existing .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=74
This thread is for creating your own Odin flashable .tar or .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=92
Sent from my LGL84VL using Tapatalk

Categories

Resources