I extracted system.img from galaxy a90 5g's firmware.
And what is the next step to port a90's firmware to my galaxy a32 4g (sm-a325n)?
(I do not have root access to my device.
So I used odin to port a90 5g's firmware.
But when I try to do it, It always fails).
I will look forward for your reply
Thank you
I'm going to take a wild guess here but your A32 is probably using dynamic partitions (system, vendor, odm and product) inside super.img. Unless you have TWRP to flash the system partition of it specifically, you won't be able to install A90's system.img
Or
An alternative would be to unpack your A32's super.img and replace the system.img inside with the A90 system.img
May I ask you how to unpack and repack super.img (to replace system.img)?
And how to flash repacked super.img (which contains a90's system.img)
Via odin (because odin does not support .img file flashing)
And it is able to boot if I only replace system.img? (or should I replace a90 5g's boot.img too?)
And doesn't it void knox warranty?
Starwars8k said:
May I ask you how to unpack and repack super.img (to replace system.img)?
Click to expand...
Click to collapse
I use SuperR's kitchen paid version
Starwars8k said:
And how to flash repacked super.img (which contains a90's system.img)
Click to expand...
Click to collapse
Do you not have TWRP?
Starwars8k said:
Via odin (because odin does not support .img file flashing)
Click to expand...
Click to collapse
Just pack the super.img into a .tar with 7zip or something
Starwars8k said:
And it is able to boot if I only replace system.img? (or should I replace a90 5g's boot.img too?)
Click to expand...
Click to collapse
Only system.img
Starwars8k said:
And doesn't it void knox warranty?
Click to expand...
Click to collapse
Yes
Why is knox broken?
Any ways to prevent?
Starwars8k said:
Why is knox broken?
Any ways to prevent?
Click to expand...
Click to collapse
Because it's not meant to be flashed on your phone, Samsung considers it custom.
And no, no way to prevent.
Do I need to unlock bootloader before flashing a32's super.img which contains a90's system.img instead of a32's ?
Starwars8k said:
Do I need to unlock bootloader before flashing a32's super.img which contains a90's system.img instead of a32's ?
Click to expand...
Click to collapse
Yes
Are you sure flashing a90's system.img to my a32 will not break compatibility and work perfectly?
Starwars8k said:
Are you sure flashing a90's system.img to my a32 will not break compatibility and work perfectly?
Click to expand...
Click to collapse
It won't work well because of the different chipset
Then I'll not port whole system.img
I just need dex firmware.
What firmware should I extract to use samsung dex?
And how to port It
Starwars8k said:
Then I'll not port whole system.img
I just need dex firmware.
What firmware should I extract to use samsung dex?
And how to port It
Click to expand...
Click to collapse
Pretty easy to answer this one... YOU CAN'T
Okay... I will port a90's whole system.img
Although a32 4g has unofficial twrp, my device is sm-a325n and it doesn't work.
And is it able to flash system.img eventhough a32 uses dynamic partition?
Does system.img contains samsung dex?
Starwars8k said:
Okay... I will port a90's whole system.img
Although a32 4g has unofficial twrp, my device is sm-a325n and it doesn't work.
And is it able to flash system.img eventhough a32 uses dynamic partition?
Does system.img contains samsung dex?
Click to expand...
Click to collapse
I already said: YOU CAN'T PORT THE WHOLE SYSTEM.IMG
A90 has VERY VERY different hardware. A32 has Mediatek and A90 has Snapdragon chipset.
I see.
Thank you for your advice.
Related
i have never made any thing for samsung.
but now i am going to make my kernel for samsung.
unlike others samsung have different bootloader.
fastboot flash boot boot.img won,t work here
so i can,t use boot.img.
so can anybody tell me how to pack boot.img and make odin flashable file.
also i need to know were can i find stock firmwares.
www.sammobile.com
andynroid said:
www.sammobile.com
Click to expand...
Click to collapse
what about making them odin flashable.
Extract them it becomes flashable in Odin as a PDA Package
andynroid said:
Ectract them it becomes flashable in Odin as a PDA Package
Click to expand...
Click to collapse
and also how can i make odin flashable pda package from boot.img that will be created after compiling kernel.
edit
never mind found a guide.
What device you are using ?
andynroid said:
What device you are using ?
Click to expand...
Click to collapse
galaxy tab 3 lite 7.0 sm-t111
Does anybody know why my a3 2017 fails to flash Nougat via odin package BL AP CP CSC im already rooted and on nougat but i want to flash all files instead of only the AP file and my model is A320FL downloaded the russia version for a320F.
khanvict90 said:
Does anybody know why my a3 2017 fails to flash Nougat via odin package BL AP CP CSC im already rooted and on nougat but i want to flash all files instead of only the AP file and my model is A320FL downloaded the russia version for a320F.
Click to expand...
Click to collapse
I don't think you can flash a full 4-file for a different model. Odin saves you a potential brick.
What was the error? pit file?
tys0n said:
I don't think you can flash a full 4-file for a different model. Odin saves you a potential brick.
What was the error? pit file?
Click to expand...
Click to collapse
Yes it was somthing with pit And so we only can flash AP nothing more ?
khanvict90 said:
Yes it was somthing with pit And so we only can flash AP nothing more ?
Click to expand...
Click to collapse
ODIN is prevening the flash to protect your device. The firmware is only partly compatible with your device. FL and F models likely have different partition sizes. This will cause a pit file failure.
khanvict90 said:
Does anybody know why my a3 2017 fails to flash Nougat via odin package BL AP CP CSC im already rooted and on nougat but i want to flash all files instead of only the AP file and my model is A320FL downloaded the russia version for a320F.
Click to expand...
Click to collapse
You won.t need to flash all the files.. Only the AP file.
But due different kernel, you will kinda break nfc and other stuff
ashyx said:
ODIN is prevening the flash to protect your device. The firmware is only partly compatible with your device. FL and F models likely have different partition sizes. This will cause a pit file failure.
Click to expand...
Click to collapse
thanks or the information mate!
MaDaLiNoSt said:
You won.t need to flash all the files.. Only the AP file.
But due different kernel, you will kinda break nfc and other stuff
Click to expand...
Click to collapse
thanks also for the inforamtion mate!!
Good Hello Everyone,
I rooted my SM-G985F but the camera stopped working and I don't know what caused it! Some users report theirs is working. Can you help me narrow it down or even fix this issue?
I patched AP TBM with MAGISK 72f6770d and then with 7z, I replaced the kernel with this one flashed all files in odin. And it seems like I have root, although only magisk modules worked so far from what I tested like @geiti94 said because of limitations of only read. Yeah only downside for me, I can't use the camera.
Did I used a old version of Magisk?
Did I replaced the kernel the wrong way?
Is it because my device is 4G?
thanks for help.
its because you used a kernel from another phone model.
instead, extract "virgin" boot.img.lz4 from ap file, tar it up and send to phone, patch in magisk and flash from odin.
Daniehabazin said:
its because you used a kernel from another phone model.
instead, extract "virgin" boot.img.lz4 from ap file, tar it up and send to phone, patch in magisk and flash from odin.
Click to expand...
Click to collapse
Oh Dude someone replied! Should I do it like this:
extract with 7z or RAR the boot.img file from a clean/stock AP file.
tar it up? What does that mean? just change the file extension? Just renaming it? Or is a different process?
and then just the boot.img via odin in AP slot or whole firmware?
sorry I know many noob questions...
But thanks so far.
chieco said:
Oh Dude someone replied! Should I do it like this:
extract with 7z or RAR the boot.img file from a clean/stock AP file.
tar it up? What does that mean? just change the file extension? Just renaming it? Or is a different process?
and then just the boot.img via odin in AP slot or whole firmware?
sorry I know many noob questions...
But thanks so far.
Click to expand...
Click to collapse
instead of typing instructions in this thread i just made a new thread with instructions so all could see, check it out: https://forum.xda-developers.com/galaxy-s20-plus/development/howto-root-phone-s20-t4067649
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!
Many users report imei errors months after rooting. I don't recommend rooting. we do not know the origin of the problem
Hi friends.
On Topjohnwu's github, there´s a note about root any Samsung without recovery
Basically, extract the AP from stock firmware, copy it to phone, install magisk from xda forum, patch it, download the patched file to your pc and flash it using Odin.
You must fresh flash the entire ROM and the patched AP, userdata MUST be formatted (use CSC, not HOME_CSC)
Use it at your own risk, Knox wil be tripped and you could brick your phone.
Search the note into Topjohnwu´s github, Magisk section, Install and search for specific samsung section.
Be careful and enjoy rooting!
edukardo said:
Hi friends.
On Topjohnwu's github, there´s a note about root any Samsung without recovery
Basically, extract the AP from stock firmware, copy it to phone, install magisk from xda forum, patch it, download the patched file to your pc and flash it using Odin.
You must fresh flash the entire ROM and the patched AP, userdata MUST be formatted (use CSC, not HOME_CSC)
Use it at your own risk, Knox wil be tripped and you could brick your phone.
Search the note into Topjohnwu´s github, Magisk section, Install and search for specific samsung section.
Be careful and enjoy rooting!
Click to expand...
Click to collapse
Well, currently i am not gonna root this devices. Still feel comfort with full stock ROM, maybe after custom ROM arrive for this devices it will changes my mind to root the devices.
gusbalaa said:
Well, currently i am not gonna root this devices. Still feel comfort with full stock ROM, maybe after custom ROM arrive for this devices it will changes my mind to root the devices.
Click to expand...
Click to collapse
Is OK, just a bit of work debloating...
edukardo said:
Hi friends.
On Topjohnwu's github, there´s a note about root any Samsung without recovery
Basically, extract the AP from stock firmware, copy it to phone, install magisk from xda forum, patch it, download the patched file to your pc and flash it using Odin.
You must fresh flash the entire ROM and the patched AP, userdata MUST be formatted (use CSC, not HOME_CSC)
Use it at your own risk, Knox wil be tripped and you could brick your phone.
Search the note into Topjohnwu´s github, Magisk section, Install and search for specific samsung section.
Be careful and enjoy rooting!
Click to expand...
Click to collapse
Here's my story, I patched the AP file and flashed it using odin, didn't add any other stock firmware files. I was able to attain root privileges, then the unthinkable happened. I received a call and it got disconnected instantly. The network signals vanished, I restarted the phone and was welcomed with a flash notification message "IMEI null or invalid."
I've since flashed it 10-12 times.
IMEI hasn't been restored, wifi works though.
I've given up hope now, my daughter attends her school classes on it.
I have never heard of such a case. Where did you get the boot.img from? It must be the same version as your phone. I recommend you flash a clean software by Odin, without root, and verify that everything is normal
edukardo said:
I have never heard of such a case. Where did you get the boot.img from? It must be the same version as your phone. I recommend you flash a clean software by Odin, without root, and verify that everything is normal
Click to expand...
Click to collapse
Downloaded and extracted the AP file from the original firmware. It has happened with another guy, he did post a video on youtube, fixed it using some Z3X box.
The firmware was the original, but was it the same version as the one you had installed?
edukardo said:
The firmware was the original, but was it the same version as the one you had installed?
Click to expand...
Click to collapse
Yes, downloaded it using frija.. I did just flashed the patched AP file, skipped the rest, maybe that was the reason..
Did you get the IMEI back?
edukardo said:
Did you get the IMEI back?
Click to expand...
Click to collapse
Nope, I've given up. Can't invest any more money on the Z3X box..
Why don't you flash the whole system from Odin? No modifications. That should work
edukardo said:
Why don't you flash the whole system from Odin? No modifications. That should work
Click to expand...
Click to collapse
I've already done that 10-12 times to no avail.
You must download the exact version of rom for your country/carrier. Search for it in sammobile.
Can't understand what the problem is.
I´ve got no problem at all
edukardo said:
I´ve got no problem at all
Click to expand...
Click to collapse
Were you able to root it?
Also, in addition to the patched AP file do we need to flash the BL, CP and CSC files?
Yep no issues. Magisk hide, all working.
When you extracted the boot img, there where another files into the AP file provided by samsung that must be flashed too.
Do you have the patched file? Try flashing BL, CP, CSC and AP and then flash again only the patched boot.img into AP.
But I think it has nothing to the root with loose of imei.
Was your phone a company one? Like verizon, etc?
edukardo said:
Yep no issues. Magisk hide, all working.
When you extracted the boot img, there where another files into the AP file provided by samsung that must be flashed too.
Do you have the patched file? Try flashing BL, CP, CSC and AP and then flash again only the patched boot.img into AP.
But I think it has nothing to the root with loose of imei.
Was your phone a company one? Like verizon, etc?
Click to expand...
Click to collapse
No, it's unlocked. Did you patch the whole AP file or just the boot file through magisk? I patched the entire AP file. If you could please list all the steps, it would be a huge help. Thanks.
edukardo said:
Yep no issues. Magisk hide, all working.
When you extracted the boot img, there where another files into the AP file provided by samsung that must be flashed too.
Do you have the patched file? Try flashing BL, CP, CSC and AP and then flash again only the patched boot.img into AP.
But I think it has nothing to the root with loose of imei.
Was your phone a company one? Like verizon, etc?
Click to expand...
Click to collapse
I saw a video of rooting the f62, here's the link. Please take a look and let me know if the steps are the same.
Ouch, working time...
Tutorial - Root - Samsung Galaxy A32 (SM-A325MDS)
--- It is necessary to see the entire video --- ============================ (Download Mediafire) you already have all the files, so the video tutorial starts at 14:23 1- unlock bootloader 2 - use (Odin) and install (magisk_patched-23000_6V0ws)...
forum.xda-developers.com