i can use boot.img from rom to another rom (replace the boot.img) ??? thanks
Yes! Should work fine. If it doesn't, put the boot.img in one if my old (pre-anykernel) zips
Related
i am making a custom rom i dnthave a boot.img ...how to make one or can i use a boot.img of another rom???
U can use the stock boot.img and edit it, to make it ext4 and u can make your own zimage... U can use the zimage of squadzone and the ramdisk of ur rom's base's boot.img...
I have made a backup of my ROM after I rooted my Acer Z110 (MT6575 based) and made it ready for a possible flash with SP Flash Tool. I wanted to extract only stock ROM (without any app, user data and IMEI info) so that it can be flashed on another Z110 from my same country (Italy, Acer does not provide italian rom) just like the official UK rom that can be downoaded from Acer website.
Additional info: original stock rom and backup have in common boot.img and recovery.img
OK, this might be lengthy, so hang on.
Is it a zip? Is it a rar? Is it something else? Tell me what it says after the dot (e.g. something.zip)
Now, if it is a zip, open it, and delete the data or user files/folders/images/archives.
Try flashing it and see if there is any data left over.
Let me know how it goes
It's a set of .img and .bin files just like the original rom
Code:
MT6575_Android_scatter.txt
DSP_BL
boot.img
cache.img
recovery.img
secro.img
system.img
userdata.img
userdata_nvram_only.img
logo.bin
preloader.bin
uboot.bin
Original ROM lacks cache.img and userdata_nvram_only.img while userdata.img is considerably smaller than the backupped one (6mb vs 171mb) just like system.img and secro.img (these two however are not so different in sizes).
I think that MTK Droid Root & Tools makes also a nandroid backup if necessary but it can't be flashed on the device as there is still no custom recovery for it.
Also it could be helpful to know that originl rom is for a dual-sim version of the device while mine is single-sim (they however are different only in software as someone flashed that rom and everything works, except they can't insert SIM2 as there s no space in our device).
Please, upload your ROM
Gigi4 said:
It's a set of .img and .bin files just like the original rom
Code:
MT6575_Android_scatter.txt
DSP_BL
boot.img
cache.img
recovery.img
secro.img
system.img
userdata.img
userdata_nvram_only.img
logo.bin
preloader.bin
uboot.bin
Original ROM lacks cache.img and userdata_nvram_only.img while userdata.img is considerably smaller than the backupped one (6mb vs 171mb) just like system.img and secro.img (these two however are not so different in sizes).
I think that MTK Droid Root & Tools makes also a nandroid backup if necessary but it can't be flashed on the device as there is still no custom recovery for it.
Also it could be helpful to know that originl rom is for a dual-sim version of the device while mine is single-sim (they however are different only in software as someone flashed that rom and everything works, except they can't insert SIM2 as there s no space in our device).
Click to expand...
Click to collapse
Can you upload that ROM for the dual-sim device? Please!
I really need it...
Thanks in advance!
Is there anyway to flash a full ROM already rooted older version for this model?
This would remove the step to return to factory initial condition to take the upgrade? (I know the device is young, but some established phones this is the way to do it if bootloader and modem is up to date) so the first question is possible to create such a ROM and post?
You could use https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
extract system.img from update.app, unpack system.img using Imgextractor.exe.
Unpack boot.img from update.app.
Extract boot.img using Android Image Kitchen.
Preroot ramdisk.
Make a flashable zip from extracted system.img and boot.img. Set up permissions, copy files..., etc in updater-script. Make the script flash boot.img.
Done. (In theory, I've not built a rom for any Huawei device yet.)
But to answer your question: Yes.
Just look at the KangVIP roms over in Development. You could just build a stock rom with root.
Edit: Imgextractor actually saves permissions to a file.
Edit 2: You could just flash the newer boot.img in TWRP and root it there, then extract boot image using dd and include that in your rom.
OR use su in /system/bin/
Edit 3: Any rom makers here? Would VENDOR and PRODUCT need to be extracted and flashed as well? (Assuming you're on a pre B183 C567 stock rom)
Nevermind, system.img is unextractable :/
Or the tool I use is not compatible with android N.
That would be awesome I'm stuck on c636 and have no way of going to c567 without paying.
Your headed in a direction, lots of us owners have been waiting for...
Sent from my MHA-L29 using Tapatalk
Benefits of 567 over 636?
Anyone have vendor_boot, dtbo and boot.img from 11.2.9.9 le25aa ?. Install a custom kernel and I need to go back to stock
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
gorilla p said:
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
Click to expand...
Click to collapse
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Partigiano0105 said:
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Click to expand...
Click to collapse
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
mattie_49 said:
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
Click to expand...
Click to collapse
how can I do that?
You can download the zip file containing th full update of your version in a thread here, them using the payload dumper tool you extract all img files inside
I don't know how to edit so more details about this process:
1. Go to sticked thread Repo of oos builds
2. Download the zip file of the firmware you are using
3. Download the payload dumper here: https://androidfilehost.com/?fid=818070582850510260
4. Once extracted extract the payload.bin from firmware zip into payload_input directory
5. Launch payload_dumper.exe
6. Process take few minutes depending on your computer, result img files are stored in payload_output directory
7. Have fun with your img file
Hello,
I'm just getting into Android, and I've been messing around with boot.img with Magisk.
The boot.img that I'm specifically looking at is Pixel 6a.
I used `magiskboot unpack boot.img`, but I only got a kernel file.
Now, I'm wondering where the ramdisk.cpio. From what I read, ramdisk determines what to mount and whatnot.
Even without a ramdisk, I can fastboot flash boot boot.img it to my device and it will still work.
If there is no ramdisk in boot.img, then how does the device know what to mount or what the file hierarchy is when I flash it?
If the stock boot.img doesn't have a ramdisk, does not mean I have to generate my own?
Thanks!
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
alecxs said:
init is on system, no ramdisk required.
https://source.android.com/docs/core/architecture/partitions/system-as-root#sar-partitioning
Click to expand...
Click to collapse
does that mean if I do include ramdisk.cpio, it overrides the one on system?
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
alecxs said:
Yes, if you modify the kernel so ramdisk is extracted and processed (that's what Magisk does)
Click to expand...
Click to collapse
Thank you so much for the link. I read up on it, and as you said, boot.img just carries a kernel file and ramdisk is in system.img.
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img? Is it because boot.img has a kernel file?
Thanks
Magisk also mods the DTB from "skip_initramfs" to "want_initramfs".
drunk_santa said:
It looks like you can also unpack, modify, and repack system.img and flash it onto pixel devices, so do you know why Magisk decided to create ramdisk.cpio and repack it into boot.img when it could have modified system.img?
Click to expand...
Click to collapse
Because Magisk is systemless-root method
https://topjohnwu.github.io/Magisk/boot.html