Any droid xpert here from or.......
I tried to create CTR on my phone huawei-g700-u10 V100R001C100B126 by stock files ..my phone doesnt have any CWM
So i tried to build
But when i tried to unpack my stock boot-sign.img it only extract kerenal and ramdisk.cpio.gz
There should been ramdisk folder with it..!!
Its becuse my boot.img and recovery is secure ..
How yo break and extract using apktool??
I tried also with pc for making twrp ?????
I guess your device is mtk based.. .. You have to unpack your image file as an mtk rom or recovery.. .... and the best tool to do that as far as I know is CarlivImageKitchen
This thread will surely help you
http://forum.xda-developers.com/android/development/guide-how-to-port-custom-cwm-based-t2970004
Sami Devo said:
Any droid xpert here from or.......
I tried to create CTR on my phone huawei-g700-u10 V100R001C100B126 by stock files ..my phone doesnt have any CWM
So i tried to build
But when i tried to unpack my stock boot-sign.img it only extract kerenal and ramdisk.cpio.gz
There should been ramdisk folder with it..!!
Its becuse my boot.img and recovery is secure ..
How yo break and extract using apktool??
I tried also with pc for making twrp
Click to expand...
Click to collapse
have found the way to? Stuck in the same with teclast x10 3g....
Related
Hello !
Unlocked my Bootloader and tried to flash CM 9 and 10.
Copied all necessary files of the rom on my sd and extracted de boot.img to my fastboot directory.
If i fastboot flash boot boot img. there allways some crazy errors like range errors etc or it just hangs at "sending boot.img"... After that phone want boot again.
When i flash a stock kernel "called kernel.elf for example" everythings fine and phone works again.
i hope you can help me,i dont understand wheres the problem i just followed the steps as described at the FXP homepage ??
Solved ... Need second try to recognize i have to use the Nozomi file pkg .... :good:
hi guy!i tried to flash that kernel form file zip,i exact that file and copy file boot.img out on my destop.so after i falshed it ,my phone is always on plane mode.Please help me!
JourNo said:
hi guy!i tried to flash that kernel form file zip,i exact that file and copy file boot.img out on my destop.so after i falshed it ,my phone is always on plane mode.Please help me!
Click to expand...
Click to collapse
put kernel's boot.img inside your fastboot files then flash it via cmd.
then flash the zip file in recovery.
tomascus said:
then flash the zip file in recovery.
Click to expand...
Click to collapse
thanks,i did it well^^
http://forum.xda-developers.com/showpost.php?p=46763215&postcount=4108
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Progress update
The only unpacking tool that seemed to correctly repack the image was MTK_Extractor_V2.63 - all of the other (many) utilities I tried did not seem to repack the ramdisk correctly and caused the phone to boot into the recovery screen.
Changing the init.rc and init_samsungexynos7570.rc files as follows finally led to success.
In file init.rc
delete everything under "on charger" then add back setprop sys.powerctl reboot
Under "service lpm /system/bin/lpm"
delete class sec-charger critical and replace with trigger late-init
In file init_samsungexynos7570.rc
delete everything under "on property:ro.bootmode=charger"
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
AndyJN said:
I have a boot.img file that i can use to root my Samsung J2 SM-J260F - if I flash this with Odin everything is Ok. Now I want to edit a file in the ramdisk of the boot.img to make the phone boot on power. However simply unpacking the Boot.img and unzipping the ramdisk then repacking fails - even when i do not edit anything in the ramdisk. When the repacked boot.img is flashed with Odin the device gets into a boot loop.
I am using the Carliv Image Kitchen for Androidv1.3 tool to do the packing and unpacking.
Is there some specific aspect of the Samsung boot.img such as a signature that is causing this to fail?
Click to expand...
Click to collapse
TBM 13 said:
Did you unlocked the bootloader?
Also i would recommend you to use a custom recovery like TWRP to flash boot.img
Click to expand...
Click to collapse
Which.... does not exist. J2 Core doesnt get the same love.
I recommend Android Image Kitchen (AIK) by Osmosis. Havent failed me once in my case.
Prove N. said:
Which.... does not exist. J2 Core doesnt get the same love.
Click to expand...
Click to collapse
I'm sorry, my bad.
has anyone tried to port the 9 pie firmware from J260A to other J260F/M/G?
Hi everyone!
I need to edit an APK in stock ROM (system.img) of my device. I have unpacked system.img and repacked with some programs on Windows. But When I unpack and repack the system.img file and change it with original system.img file (even though I didn't change any APK or anything), I can flash it through fastboot or port 9008 successfully. BUT When I try to start my phone, It stuck on MI Logo screen.
So There is no problem with flash any rom. But I want to unpack rom and edit an APK then repack it. This is my issue. How can I do it? I think there is a problem on unpack/repack step. I'll be glad if anyone can help me about it.
Thanks in advance!
p.s. I can't flash a recovery rom because of I can't run phone.
Hey guys can someone please upload the boot.img from the FW V13.0.5.0.SKOEUXM?
I did a big mistake and thought that android 12 can boot in twrp (recovery). Flashed a wrong boot.img and cant get my phone working now. Only Fastboot is working - the normal Recovery didnt boot so i cant even install the Update through the orignal system recovery.
Cause theres only a Recovery zip of it online i cant use the MiFlash Tool, since a downgrade to Android 11 isnt possible
thanks a lot!
You can download the OTA zip file from Xiaomi firmware updater or by using the app MiuiDownloader from Playstore
Unzip, you will find payload.bin inside - use the PC tool (there is a thread on XDA) Payload_Dumper to dump boot.img and other images
Anyway, here is the link to the boot-stock-lisa_EEA_V13.0.5.0.SKOEUXM_12.0.img
I had extracted and renamed (name does not matter):
File on MEGA
mega.nz
oh god! thank you very much!
will test it in few minutes
edit: It worked instantly! you made my day
Can someone please upload the boot.img from V13.0.2.0(SKOMIXM) to root?