I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
eliotargy said:
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Can anyone advise me further?
Click to expand...
Click to collapse
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Snowby123 said:
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Click to expand...
Click to collapse
My other implied question was: Did I do everything right?
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
search for lz4 on either xda or google.
( you need to unpack it)
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Why are you trying to patch? Please follow my guide for rooting the N9600.
christis said:
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Click to expand...
Click to collapse
No luck. Also no response to my post.
zxzxzxzxzxzxzxzxzx said:
Why are you trying to patch? Please follow my guide for rooting the N9600.
Click to expand...
Click to collapse
Where is your guide?
Again, where is your guide that you speak of?
eliotargy said:
No luck. Also no response to my post.
Click to expand...
Click to collapse
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
christis said:
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
Click to expand...
Click to collapse
Mine falls at patching with Magisk. N9600.
Related
V20B (CIS)
V20O (DEU)
Root on V20B
information deleted
I used google translator and that's the result of the post above:
All items are strictly in the order do not jump over them and keep the sequence!
Spoiler (+ / -) (I advise you to read before flashing)
to the root of drive C:
Two. Download Attachment SmartFlashTool_External.rar (1.18 MB) Number of downloads: 37
and extract the root of drive C:
3. Download Attachment Superuser.zip (611.2 KB) Number of downloads: 51
and put ( no need to unpack ) File on the SD-card phone
4. Turn off the phone.
Five. We hold the Volume Up (+) and insert the USB cable one end into the computer, the other into the phone
6. We will have the text of S / W Upgrade Please wait while upgrading ...
Spoiler (+ / -)
7. Run the file B_SmartFlashTool_Extern.exe
Eight. Go to the tab ROM copy D / L
9. Select the two files that you extracted from the archive [PATCHED] BIN_LGP970AT-00-V20a-CIS-XXX-JAN-06-2012 +0.7 z
10. Check:
Spoiler (+ / -)
11. Click the Start button
12. Go to the process of the firmware, go to drink coffee \ tea shorter depart away from your computer to your phone
13. When you sign Download Comlete! Go to the phone
Spoiler (+ / -)
14. On the phone, we see the regime Recovery (touch it, the management of a finger)
15. Select install zip from sdcard
16. Then choose zip from sdcard
17. Prolistyvayem and choose Superuser.zip
18. Prolistyvayem and select Yes - Install SuperUser.zip
19. Select + + + + Go back + + + +
20. Choose wipe data / factory reset
21. Prolistyvayem and select Yes - delete all user data
22. Then reboot system now
That's it! Phone is loaded, if you do it right!
As a result, we have a firmware with the Root-V20A human touch and Recovery! Thank you all and good luck to you in the firmware!
Click to expand...
Click to collapse
Dont exactly know, what it does, but as far as I get it, it roots the device and installs CWM touch.
Credits go to poster, if it is successful.
Hey, thanks for posting here. Here is v20b : http://www.lgmobiles.com/gsm/download/P970 V20B(Gingerbread Version).rar
We don't have it for N version. I saw the russian forum and wanted to ask you about howvyou managed to root v20a before this method.
Sent from my LG-P970 using XDA App
this method is working just v20a(attachment patched bin file) right?
Where how I convert .kdz to .bin file?
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Thread moved
Unless it's a ROM or kernel you've created yourself, this doesn't belong in Development.
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Kraaz said:
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Click to expand...
Click to collapse
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
SnegovikRZN said:
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Click to expand...
Click to collapse
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
adxgrave said:
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
adxgrave said:
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Since Telcel's v20a is is just out, its going to be pretty good news if it works.
mihaiolimpiu said:
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Click to expand...
Click to collapse
Yes it does.
Redpik said:
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
adxgrave said:
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Redpik said:
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Click to expand...
Click to collapse
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
I bet our rom cooker knew how to unpack and repack. So, anyone?
Sent from my LG-P970 using XDA App
jimakos29 said:
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
Click to expand...
Click to collapse
update: doing some research and it seems to extract the bin files you need lgutils and the .dll file you get from the kdz extraction but I am not at home to look into it any further.
Stable ROOT METHOD found!
You don't need this, disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Here is the proof
http://forum.xda-developers.com/showpost.php?p=22195743&postcount=417
Here are the drivers I used:
http://forum.xda-developers.com/showpost.php?p=22196019&postcount=21
I used Windows 7 32 bit, the original poster used Win7 64 bit...
I downloaded a zip file from sammobile.com's OTA files section. The ZIP contains the following files:
debug_info ==> 1kb (size)
delta.hidden ==> 856kb
delta.modem ==> 1kb
delta.platform ==> 84455 kb
delta.Sbl ==> 1280kb
delta.ua ==> 241 kb
delta.zImage ==> 4936kb
the ZIP file won't install using Mobile Odin, Odin, and CWM. In mobile Odin, it says that the file is not an OTA / Update ZIP file, and merely extracted the contents.
the filename of the downloaded file is GT-N7000_SMA_93970111.zip.
any idea how i can install the OTA file?
I have tried searching this forum and google, but to no avail. it appears that nobody knows how to use the ZIP file.
Any leads would be greatly appreciated.
Thanks in advance for your help.
What was your purpose in downloading this OTA file anyway? A firmware zip file either contains a single file with "tar.md5" as the extension or 3 files for CSC, Modem/phone and PDA file all of which are recognized automatically by mobile odin or can be loaded on PC odin. I don't think sammobile has files for CWM. No idea about the several files that are contained on the one you downloaded. From the size of the files alone we can conclude that this is NOT firmware as normal size is 600-900 MB.
What I understand from the word OTA is Over The Air and as such can only be used either within the device itself to update or thru kies.
Good luck!
I think it is a very specific scenario to use ota.
The ota file probably need you to have previous released versions of csc installed.
Dont know much about mobile odin.
I think ota is a new feature in mobile odin. Best to check cf mobile odin thread.
Sent from my GT-N7000 using Tapatalk 2
when Mobile Odin extracts the zip file you'll get a.md5 file. After the extraction just select this md5 file in Mobile Odin and you're good to go
According to the OP there is no md5 file contained on the zip file.
As per sammobile:
OTA files
This section is specially for the die-hard Samsung owner.
The person who love to tweak with their device fully on their own RISK!
If you dont know what to do with these files, you probably shouldn't touch them.
Let those who knows do it insead.
Not all OTA updates are officially released to public! Samsung may use OTA firmwares as tests first.
SamMobile will not help you with all kind of OTA updates.
Using OTA updates is fully at your own risk.
Feel free to use our forums for any kind of question regading update with the OTA files.
Click to expand...
Click to collapse
AFAIK OTA updates are firmware specific.You must be on certain firmwares to flash the OTA.For exampleTA update yyy may need you to be on xxx firmware for it to work.But sadly I dont know how to flash it....
Could it be that you have to be totally stock unrooted to be able to flash it via stock recovery (3e)? If that's the case the OTA .zip must be stored in external sd. I don't think need to rename it to update.zip, because we can still flash any .zip with the right signature on 3e. Thinking of trying on my Note but it has been 'out of flashed' for close to a month!
kopitalk said:
Could it be that you have to be totally stock unrooted to be able to flash it via stock recovery (3e)? If that's the case the OTA .zip must be stored in external sd. I don't think need to rename it to update.zip, because we can still flash any .zip with the right signature on 3e. Thinking of trying on my Note but it has been 'out of flashed' for close to a month!
Click to expand...
Click to collapse
So we just need to sign the file - any idea?
chikess said:
So we just need to sign the file - any idea?
Click to expand...
Click to collapse
No, it's not necessary (and it's not what I meant about the whole thing).
kopitalk said:
No, it's not necessary (and it's not what I meant about the whole thing).
Click to expand...
Click to collapse
then tell us what do you want to do? the 3e recovery wont take the file even if it is renamed or not... I've got totally unrooted and on stock.
So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!
.tar.md5 is a text file which contains hash of the original file. It is used to check the integrity of files.
Compare the sizes of .tar and .tar.md5 files.
Sorry @Shished that has really not helped me at all, I'm just as confused as ever. Thank you for trying though. What is "the original file"? What am I comparing, should I have some other kind of file here? Can I get the original file out of my .tar.md5? I have one file that I believe is a factory boot image and it's a .tar.md5. Believe me when I say I am a complete noob on this and I need the basics of the basics.
Edit: The file originally came as a zip, is THAT the original file?
screenshot of files: https ibb.co/fas1o7
Questioneer said:
So I tried to install Magisk via patching my boot image, but it failed, and I know from the instructions that I need my stock image rom to be a .img.tar if I want to flash through ODIN. However my stock boot image is a .tar.md5, and even trying to research the issue I just end up getting more confused. Does the rom need to end in .img? Can I convert/extract my .tar.md5 to an .img.tar(.md5?)? Is a .tar.md5 the same as a .tar (the hashing bit I understand) so that whenever someone refers to a .tar, either a .tar or a .tar.md5 is acceptable?
These Linux extensions driving me crazy and I really can't figure out what's what. It might be useful for the main Magisk thread to have a section that explains this kind of basic stuff for the less-savvy. If someone could straighten me out I would be highly appreciative, thanks in advance!
Click to expand...
Click to collapse
.tar is the compression used for Samsung. If you extract the .tar, you will find an .img in it. A .tar.md5 is just the .tar with the hash file appended.
madbat99 said:
.tar is the compression used for Samsung. If you extract the .tar, you will a .img in it.
Click to expand...
Click to collapse
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?
A S Ovin said:
Does it mean that .img file can always be extracted from a .tar or .tar.md5 file?
Click to expand...
Click to collapse
There will likely be several .img files inside of it.
I have the stock firmware for my device (a Galaxy J6). I've downloaded it from sammobile, and it's in a zip file. Supposedly, all I need to do is extract this file with an extraction program like winrar and presto, I should have the necessary boot.img. But all I get are these useless .md5 files. What is going on? Did I misinterpret something?
More than anything, I would just like it if someone finally just explained to me what the hell I'm supposed to do. The Magisk installation guide doesn't even go into detail about how to get a boot.img, it just assumes you have it. It's infuriating.
AndreM962 said:
I have the stock firmware for my device (a Galaxy J6). I've downloaded it from sammobile, and it's in a zip file. Supposedly, all I need to do is extract this file with an extraction program like winrar and presto, I should have the necessary boot.img. But all I get are these useless .md5 files. What is going on? Did I misinterpret something?
More than anything, I would just like it if someone finally just explained to me what the hell I'm supposed to do. The Magisk installation guide doesn't even go into detail about how to get a boot.img, it just assumes you have it. It's infuriating.
Click to expand...
Click to collapse
If it's an OTA full upgrade there should be a file named payload.bin.
You need to unpack it to get the img files. Do it using this tool:
https://androidfilehost.com/?fid=818070582850510260
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Um, when I tried downloading your program, the page said there were no mirrors found.
Also, there doesn't appear to be any payload.bin file on the zip, just md5 files. And it's been that way for every j6 firmware I've downloaded in the past.
Maybe you should try downloading the firmware from sammobile and seeing whether you can extract boot.img from it?
AndreM962 said:
Um, when I tried downloading your program, the page said there were no mirrors found.
Also, there doesn't appear to be any payload.bin file on the zip, just md5 files. And it's been that way for every j6 firmware I've downloaded in the past.
Maybe you should try downloading the firmware from sammobile and seeing whether you can extract boot.img from it?
Click to expand...
Click to collapse
Give me the link and i will see what can i do.
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
https://www.sammobile.com/firmwares/galaxy-j6/SM-J600GT/ZTO/download/J600GTVJU3ASA1/257858/
You might need to make a sammobile account if you don't have one already. Good luck!
AndreM962 said:
https://www.sammobile.com/firmwares/galaxy-j6/SM-J600GT/ZTO/download/J600GTVJU3ASA1/257858/
You might need to make a sammobile account if you don't have one already. Good luck!
Click to expand...
Click to collapse
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Sorry for the late reply. I did it. I found the boot.img file! I'll be using it shortly.
Thank you so much. Your advice was absolutely invaluable!
How can I get boot.IMG from my firmware
My device is mafe air and I download Its firmware from a website but I am unable to get boot.img file from it because it have recovery.img and other system file where can I found my device supported boot.img in my device firmware. Please help me I need it to root my device using magisk. Please reply
My device is itel A14 max running on Mediatek chip and I downloaded it's firmware to root using magisk but when extract the zip file using 7zipper, I can't find the boot.img file. The file that I get is in .pac format and I am failing to extract it further to get boot.img file. Is there any way I can be helped please?
I have oppo f15 phone and i downloaded its stok rom after extract it ,8 can't find boot.img file how to do it plz help..
hank81 said:
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
and the last step there is unpack or extract the boot.img from the boot.img.lz4 file cause i just did it
Click to expand...
Click to collapse
Please tell me how to extract latest firmware of oppo f15 cph2001ex_11_C.47 which is in ozip format please help me
hank81 said:
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Click to expand...
Click to collapse
For me, on my note 10 lite I have a problem with 7zip when i try to open the boot.img.lz4 it says that I dont have an app Installed to perform that action
hank81 said:
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Click to expand...
Click to collapse
My Friend
I have same problem above: find boot.img of my device ( SM-G532MT).
I have a firmware downloaded from firmware.mobi. Works fine.
But, when decompressed, shows only the archives for instalation for Odin ( CSC, AP, etc... ). No boot.img under other format.
hank81 said:
I downloaded a random J6 firmware in another site.
You have to use 7zip software, it's free, much better than WinRar and supports tons of compression formats. Do these steps with 7zip:
-Unpack zip file.
-Rename the "*.tar.md5" to "*.tar".
-Open the ".tar" file and unpack "boot.img.lz4".
-Unpack "boot.img.lz4" file.
-It's done, you now have the "boot.img" file you were looking for
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
Click to expand...
Click to collapse
Cloviscard said:
My Friend
I have same problem above: find boot.img of my device ( SM-G532MT).
I have a firmware downloaded from firmware.mobi. Works fine.
But, when decompressed, shows only the archives for instalation for Odin ( CSC, AP, etc... ). No boot.img under other format.
Click to expand...
Click to collapse
read this https://android.stackexchange.com/a/179248
and this https://forum.xda-developers.com/t/extracting-boot-img-from-stock-firmware.3909612/#post-79106875
I read carefully and...
Forgive me, but the article DON'T answer my question: How to extract the boot.img from a stockrom in .img format...
Cloviscard said:
I read carefully and...
Forgive me, but the article DON'T answer my question: How to extract the boot.img from a stockrom in .img format...
Click to expand...
Click to collapse
forgive me about that too
Samsung devices by default don't have .img ...
usually stockrom come as .zip then you need to extract it (use 7zip since winrar is not capable of extracting .lz4)
-Rename the "AP_xxx.tar.md5" to "AP_xxx.tar". <~ any similar file with AP from the start
-Open the "AP_xxx..tar" file and if you see boot.img extract "AP_xxx..tar" then grab boot.img it's done, you now have the "boot.img" file you were looking for
-some device have "boot.img.lz4" file. <~ use 7zip again to extract .lz4 file then grab boot.img it's done, you now have the "boot.img" file you were looking for
also it is stupid to grab your boot.img when you are Samsung since Odin only accept .md5 format (does Samsung have access to fastboot or they are stuck using Odin idk never has Samsung phone lmao)
also i forgot to say that you can actually patch "AP_xxx.tar" via Magisk itself so less work
For anyone else having trouble getting the boot.img, but on a custom recovery:
1. Go to recovery
2. Open recovery terminal
3. Enter:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
4. Press enter to confirm the command
5. Reboot to system
The boot.img is now on your SD card.
<deleted>
discovered id posted a duplicate link
Immortal68 said:
For anyone else having trouble getting the boot.img, but on a custom recovery:
1. Go to recovery
2. Open recovery terminal
3. Enter:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
4. Press enter to confirm the command
5. Reboot to system
The boot.img is now on your SD card.
Click to expand...
Click to collapse
Thank you very much for rally... very helpfull...
But still 1 question: if the referred boot.img was previously patched with another root aplication like suroot???
I have been running into an issue while trying to flash and change regions for my GW3. I know I have the file that is needed for the AP part of the procedure. But after connecting to my watch via wireless download, Odin will not see the files in file explorer on Windows 10.
Watch is Canada region with latest build, and running Tizen 5.5.0.2.
Have ECG, BP, and Samsung health manager caravan loaded via .apk. Just trying to get sp02 running as well until health Canada approves it for the north.
Has anyone run into this issue? Or any insight to a fix?
?
netOdin and Odin and can only handle 2 fileextension...
Code:
.tar.md5
.tar
Best Regards
So if the file I have downloaded includes the .7z extension as well is there a way to convert it to what Odin will recognize? Sorry if this is covered somewhere. If it is, than I missed it. I'm using the YouTube guide for switching regions. Which was where I got the download link from. I do have experience flashing pixels and iPhones. This is my first foray into Odin for flashing files.
ryan9000 said:
So if the file I have downloaded includes the .7z extension as well is there a way to convert it to what Odin will recognize? Sorry if this is covered somewhere. If it is, than I missed it. I'm using the YouTube guide for switching regions. Which was where I got the download link from. I do have experience flashing pixels and iPhones. This is my first foray into Odin for flashing files.
Click to expand...
Click to collapse
Download 7zip (free open source) https://www.7-zip.org/
Use that to open the .7z file and extract the .tar.md5 file
tripjnj said:
Download 7zip (free open source) https://www.7-zip.org/
Use that to open the .7z file and extract the .tar.md5 file
Click to expand...
Click to collapse
Excellent. Thank you very much.
Deleted cause I'm dumb