http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html
in the above tutorial. on boot.img editing..they hav said to Replace the files boot.img-zImage, boot.img-dtb, boot.img-ramdisk.cpio.gz after extracting the boot.img.
BUt when i extract the boot image using kitchen it only gives me one folder(boot.img-ramdisk) and Zimage FIle and i can't find those above mentioned files..
so i totally replaced the boot.img file..but it makes boot loop.
pls any suggestions to extract the boot.img correctly..
thank you
jo77077 said:
http://www.osbusters.net/2015/11/how-to-port-miui-7-rom-to-qualcomm-smartphones.html
in the above tutorial. on boot.img editing..they hav said to Replace the files boot.img-zImage, boot.img-dtb, boot.img-ramdisk.cpio.gz after extracting the boot.img.
BUt when i extract the boot image using kitchen it only gives me one folder(boot.img-ramdisk) and Zimage FIle and i can't find those above mentioned files..
so i totally replaced the boot.img file..but it makes boot loop.
pls any suggestions to extract the boot.img correctly..
thank you
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
See this thread for unpacking boot.img [TOOL] Boot.img tools [unpack, repack, ramdisk].
You can ask further questions in Android Q&A,Help and Troubleshooting or in one of the noob friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you!
Good Luck
___
v7
XDA Assist
Related
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
here u go!
Kishan Mahadevwala said:
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
Click to expand...
Click to collapse
follow this guide and use this tool. ( http://forum.xda-developers.com/showpost.php?p=54644719 )
I hope you will success.
don't forget to hit thanks.
Kishan Mahadevwala said:
Friends Please Help Me To Repack Boot.img Please!! i Try Many But Didn't Found Zimage I Go To Port Diffrent Chipset Rom
Click to expand...
Click to collapse
Mostly we want to update zImage in boot.img. so suggest you not to go for unpack and repack. just update your custom zImage into defualt boot.img by running this command:
#abootimg -u boot.img -k zImage.
Then try to flash this boot.img in your phone. If you are r changing initrd.img also then you can go for unpacking and repacking
but always take backup of your default boot.img, because if anything gone bad with this custom boot.img then your defuault will help to bring back your phone.
Find
I Already Find Thank You For Your Help I Already Do With Kitchen
Hi!
My main aim is to root a china phone (symphony w67).
I made the scatter file, rom and stuffs. Now the problem I end up with is when I want to make the cwm recovery image using the Mtk Droid Tools. Here is the log:
--------------------------------------------------------------------------------------------------------------------------------------
--->>> Connect to device <<<--- --- The preservation folder on the computer: C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack_141029-124724\ --- scatter is write to the file:
C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack_141029-124724\MT6572_Android_scatter.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
------------------------------------------------------------------------------------------------------------------------------------------------
As u can see there are 2 errors:
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
and also no modified cwm recovery image is created in the backup folder. So may I please have some solution for this error? I became very desperate, been trying to root this device for 4 days.
Below are more details about the mobile if it helps in anyway:
Model number: W67
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD,WG.MP.V43, 2014/05/22 18:56
Kernel version: 3.4.67
Build number: W67_1_XXX_V01.0_V2.0_20140809
Hi,
The best place to ask your question will be in the thread dedicated to the mtk droid tools found here
http://forum.xda-developers.com/showthread.php?t=2160490
But as xda recently changed some rules I am not sure if you can post in the dev section, so if not try the general q&a and link your question to that thread
http://forum.xda-developers.com/android/help
Best of luck!
demkantor said:
Hi,
The best place to ask your question will be in the thread dedicated to the mtk droid tools found here
http://forum.xda-developers.com/showthread.php?t=2160490
But as xda recently changed some rules I am not sure if you can post in the dev section, so if not try the general q&a and link your question to that thread
http://forum.xda-developers.com/android/help
Best of luck!
Click to expand...
Click to collapse
Pleaseeeeeeee could you forward this question to the the developer section? I am not yet allowed to ask questions there. I really need your help!
Create the thread in the general q&a section I pointed you to and if there is no response I will forward a link to that thread
Good luck!
demkantor said:
Create the thread in the general q&a section I pointed you to and if there is no response I will forward a link to that thread
Good luck!
Click to expand...
Click to collapse
I posted it for a few days now in the q&a section as you pointed out, still no reply.
Adib254 said:
I posted it for a few days now in the q&a section as you pointed out, still no reply.
Click to expand...
Click to collapse
Done! I'll be closing the thread now
Best of luck
i have extracted system.img and edited it and now i want to repack it to flash in my mobile how to repack it ?
Sir,
You have already asked in the right forums so you must wait an answer there.
> Android Development and Hacking > Android General > how to repack system.img file i extracted to flash it with odin
> Android Development and Hacking > Android Software and Hacking General [Developers Only] > [Q] How to repack system.img file to flash using odin
Also, you can read this tutorial: HOWTO: Unpack, Edit, and Re-Pack Boot Images
Good luck
Thread closed, thank you.
all the methods and commandlines described on your forums to convert the recovery.img to an ODIN flashable .tar or .md5 file simply compresses the .img file itself and puts the .img into the .tar file (so if I open the .tar file with winzip ill see the initial recovery.img I started with inside the .tar file) WHICH in fact is NOT flashable by ODIN please help?
XDA Visitor said:
all the methods and commandlines described on your forums to convert the recovery.img to an ODIN flashable .tar or .md5 file simply compresses the .img file itself and puts the .img into the .tar file (so if I open the .tar file with winzip ill see the initial recovery.img I started with inside the .tar file) WHICH in fact is NOT flashable by ODIN please help?
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Unfortunately I cannot find such a guide under the SII forums. If it was a guide for a different device, there is no guarantee it will work for the SII.
There is a cheater method though, if you have a working system with root. Enable ADB debugging, connect the phone to your PC, fire up adb shell, su, and then dd a copy of the recovery.img on the phone to the recovery partition (sorry I cannot give you the exact path since it varies by model, but it would be along the lines of /dev/block/platform/msm_sdcc.1/by-name/recovery).
To further explore this, or option A (the original thought), please go ahead and create an account. From there, add a post to this thread:
> Samsung Galaxy S II I9100 > Galaxy S II Q&A, Help & Troubleshooting > [Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Hope this helps, and good luck!
Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!
drunk_santa said:
Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!
Click to expand...
Click to collapse
drunk_santa said:
Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!
Click to expand...
Click to collapse
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com