Hi all.
I'm not able to create an image file for LiveSuit to flash an A10 Allwinner based tablet.
have been following tons of tutorials but Linux to me is something too hard
http://www.allmost.org/2012/11/how-to-allwinner-image-building-or.html
I already have dumped the firmware images with Uberizer software but I need to create this IMG file for LiveSuit, ,PhoenixSuit or PhoenixCard programs
it's very simple to flash Rockchip based tablets with RK Android Tool but this process doesn't work on Allwinner based tablets unfortunately.
the question is: could someone here make a LiveSuit image for me ?
I just have to upload the dumped files: boot, bootloader, data, recovery, system...
thanks :good:
Please don't create duplicate threads,
http://forum.xda-developers.com/android/help/linux-experts-convert-dump-to-img-t3435329
Thanks! And thread closed.
Related
I am trying to unpack the recovery image of a Yuhua Touchstone running Android 2.1 (marketed as an I-Mobile i858). I have tried every method mentioned on this forum and wiki and elsewhere on the internet (extensive Googling) and the standard perl scripts, such "unpack-bootimg.pl" and "split_bootimg.pl" are not working. They say that a ramdisk is not found or Android Magic is not found, respectively, and then quit. I need help deciphering the recovery image so I can replace it with a custom recovery program.
To give more insight, when the phone is updated, the recovery.img is written raw to the partition.
Ex. write_raw_image PACKAGE:recovery.img RECOVERY:
Here is the latest recovery.img for this device. Thanks in advance for any suggestions, advice and assistance.
recovery.img from I-Mobile i858 (Yuhua Touchstone) Android 2.1 rom version 1632
mid w9 use rk2818 chip
i use rk2808 mod tools unpack the system.img but not
pls help me how to unpack/pack to the w9 system.img
thanks master
any one help me
You got any luck with that? I have been trying everything I could think of without success.
http://twitter.com/naobsd has expressed interest in helping.
He needs a system dump
RK2818 can be rooted with UniversalAndRoot
You then need to run a Terminal Emulator application to dump the contents of /system into a tar and upload it
If you can dump the contents of other useful partitions, that might be good as well.
sorry for my inaccurate explaination.
I don't want dump image itself.
I already know
1. system.img in update.img is encrypted (other files are not encrypted, same as RK2808)
2. RKAndroidBatchUpgrade.exe for RK2818 decrypt system.img, then flash into device
3. decrypted system.img(cramfs) can be get by dumping system partition on live device
4. dumped decrypted system.img can be unpacked by fsck.cramfs
then, I want know following procedure can be done:
5. pack update.img with dumped decrypted system.img from device
6. flash update.img(5.) by RKAndroidBatchUpgrade.exe for RK2818
it should be easy to try, but I don't have any RK2818 device. I'll get ONN-N2 but no official firmware is released yet. so I can't make complete update.img for ONN-N2. (no RK28xxLoader(L).bin)
--
I know old flash tool for RK2808 can flash single partition. I think it should work on RK2818 because new flash tool for RK2818 can be used for my RK2808 device (iRobot)
but, anyway, I don't have RK2818. I can't test anything on real RK2818 device.
need your help! see here: http://www.slatedroid.com/index.php?topic=12683.msg105067#msg105067
Wopad?
I'm not sure if I have the same device as in this thread, but I'm familiar with adb and rooting. I've tried universal Androot on my device and it doesn't give me root. Z4root does but only temporary. I would love to help with whatever you guys need, just need a couple commands and will send files.
Oh it's a wopad rk2818 capacitive no trackball 2.1 model 7001
i can give any other info if needed. Hopefully we can get some kind of development going on this tab. It's a good little device, Rom is not so good though.
For reference, W9 ROM:
http://ramos.com.cn/support.php?support_downid=264
2010-12-08
fun_ said:
sorry for my inaccurate explaination.
I don't want dump image itself.
I already know
1. system.img in update.img is encrypted (other files are not encrypted, same as RK2808)
2. RKAndroidBatchUpgrade.exe for RK2818 decrypt system.img, then flash into device
3. decrypted system.img(cramfs) can be get by dumping system partition on live device
4. dumped decrypted system.img can be unpacked by fsck.cramfs
then, I want know following procedure can be done:
5. pack update.img with dumped decrypted system.img from device
6. flash update.img(5.) by RKAndroidBatchUpgrade.exe for RK2818
it should be easy to try, but I don't have any RK2818 device. I'll get ONN-N2 but no official firmware is released yet. so I can't make complete update.img for ONN-N2. (no RK28xxLoader(L).bin)
--
I know old flash tool for RK2808 can flash single partition. I think it should work on RK2818 because new flash tool for RK2818 can be used for my RK2808 device (iRobot)
but, anyway, I don't have RK2818. I can't test anything on real RK2818 device.
need your help! see here: http://www.slatedroid.com/index.php?topic=12683.msg105067#msg105067
Click to expand...
Click to collapse
My tablet is based on the rockchip 2818 ref. design, the pure odm device as it were, model is the yifang m7.
The issue i stumbled upon is that the little ****er is still encrypted on the blocklevel device. (mtdblock4 for /system)
Hi everybody,,,
I have a problem with my Garmin Asus A10 system partition that made the phone unable to boot and stuck on the startup screen.
I'm able to use fastboot,,,,and I can flash img images.
My main request is i want the system.img and boot.img (if available) dumped files for the garmin asus A10 in order to flash the system partition to bring the phone back to life.
Can anybody upload this file? plz....
I have the raw file: 512_A10_PACKAGE.raw Recovery image but i don't know how to extract the .img files from it.
Thanks,,,,
Hello guys. I have an firmware update file for a rk3188 tvbox with android in .img extension
It is based on Android 4.2.2 and I want to unpack it to see how can I get an Android 4.4.2 firmware to run or edit this one. Can someone tell me if there is a tool for doing this kind of unpacking and repacking also? Windows based, or maybe linux but I'm gonna use it in a virtual machine. Many thanks!!
Just use CRB image kitchen tool
[TOOL][LINUX][ANDROID][WINDOWS] Jancox Tool Unpack Repack ROMs
Jancox Tool Unpack Repack ROMs Jancox tool is a tool for unpacking and repacking ROMs, in other words this is a tool for modification Android ROM, and it supports Linux, Android and Windows. Requestment Requestment Linux - Installed Python 3...
forum.xda-developers.com
Hey XDA community!
I'm facing a problem while trying to build TWRP for my Motorola Moto G72 [Vicky]. I am unable to locate the "recovery.img" file in the firmware.zip of my device. I've searched extensively, including through the root storage of my device using Zarchiver, but I couldn't find any file named "recovery" or "recovery.img".
Here are some details about my device:
Device: Motorola Moto G72 [Vicky]
Partition Type: A/B (Dual-Partition System)
I've tried using MTK tools and MTK Client GUI 2.0 to extract the recovery.img file from the firmware, but unfortunately, my device fails the handshake when in BROM mode and boots directly into the bootloader.
Building TWRP requires the stock recovery image, and without it, I'm unable to proceed with the development of TWRP for my device.
I'm reaching out to the XDA community for assistance with the following:
If anyone with knowledge about the Motorola Moto G72 [Vicky] or similar devices has successfully extracted the recovery.img file from the firmware, I would greatly appreciate guidance on how to locate it.
If there's an alternative method or tool I can use to extract the recovery.img file from my device's firmware.zip, please provide suggestions or step-by-step instructions.
If there are any developers who have successfully built TWRP for the Motorola Moto G72 [Vicky] or have experience with devices using the A/B partition system, I would appreciate any insights or advice you can share.
I'm eager to contribute to the development of TWRP for my device, but this roadblock has prevented me from proceeding. Any assistance or guidance from the XDA community would be highly valuable.
Thank you in advance for your support and expertise!
Best regards,
FiniteCode
FiniteCode said:
Hey XDA community!
I'm facing a problem while trying to build TWRP for my Motorola Moto G72 [Vicky]. I am unable to locate the "recovery.img" file in the firmware.zip of my device. I've searched extensively, including through the root storage of my device using Zarchiver, but I couldn't find any file named "recovery" or "recovery.img".
Here are some details about my device:
Device: Motorola Moto G72 [Vicky]
Partition Type: A/B (Dual-Partition System)
I've tried using MTK tools and MTK Client GUI 2.0 to extract the recovery.img file from the firmware, but unfortunately, my device fails the handshake when in BROM mode and boots directly into the bootloader.
Building TWRP requires the stock recovery image, and without it, I'm unable to proceed with the development of TWRP for my device.
I'm reaching out to the XDA community for assistance with the following:
If anyone with knowledge about the Motorola Moto G72 [Vicky] or similar devices has successfully extracted the recovery.img file from the firmware, I would greatly appreciate guidance on how to locate it.
If there's an alternative method or tool I can use to extract the recovery.img file from my device's firmware.zip, please provide suggestions or step-by-step instructions.
If there are any developers who have successfully built TWRP for the Motorola Moto G72 [Vicky] or have experience with devices using the A/B partition system, I would appreciate any insights or advice you can share.
I'm eager to contribute to the development of TWRP for my device, but this roadblock has prevented me from proceeding. Any assistance or guidance from the XDA community would be highly valuable.
Thank you in advance for your support and expertise!
Best regards,
FiniteCode
Click to expand...
Click to collapse
Your not find recovery.img in most phones after Android 11 so has boot.img.
After that so depend about kernel. As we know your device Helio G99 can have 5.4 or 5.10 kernel and after that so the phones has boomi.mg but simple kmi google kernel. Not has the recovery_Ramdisk.
So these structure into vendor_boot.img now.
If you want custom recovery so that's need flash in the vendor_boot partition.
Simple
1. 3. => My friend @lopestom has knowledge and has TWRP with Helio G99 working.
You can find anything in the github.
DragonPitbull said:
Your not find recovery.img in most phones after Android 11 so has boot.img.
After that so depend about kernel. As we know your device Helio G99 can have 5.4 or 5.10 kernel and after that so the phones has boomi.mg but simple kmi google kernel. Not has the recovery_Ramdisk.
So these structure into vendor_boot.img now.
If you want custom recovery so that's need flash in the vendor_boot partition.
Simple
1. 3. => My friend @lopestom has knowledge and has TWRP with Helio G99 working.
You can find anything in the github.
Click to expand...
Click to collapse
Hey there!
I appreciate the information you provided about the changes in the file structure and the absence of the recovery.img file in newer devices. I was able to understand the concept, but I still have a question regarding the process of building a TWRP device tree without the files inside the recovery.
Specifically, I'm wondering how I can proceed further with the TWRP build if I need access to the files inside the recovery to create the device tree. Since the recovery.img is not available, I'm unsure how to extract the necessary files or gather the required information for building the device tree.
If you could provide some guidance on how I can gather the required files or extract the necessary information without the recovery.img, it would be immensely helpful. Any specific tools or methods I should consider for this purpose?
Thank you for your assistance and insights!
Best regards,
FiniteCode
FiniteCode said:
Hey there!
I appreciate the information you provided about the changes in the file structure and the absence of the recovery.img file in newer devices. I was able to understand the concept, but I still have a question regarding the process of building a TWRP device tree without the files inside the recovery.
Specifically, I'm wondering how I can proceed further with the TWRP build if I need access to the files inside the recovery to create the device tree. Since the recovery.img is not available, I'm unsure how to extract the necessary files or gather the required information for building the device tree.
If you could provide some guidance on how I can gather the required files or extract the necessary information without the recovery.img, it would be immensely helpful. Any specific tools or methods I should consider for this purpose?
Thank you for your assistance and insights!
Best regards,
FiniteCode
Click to expand...
Click to collapse
If you use the Source Code by company/carrier so you need knowledge.
If you only using stock vendor_boot.img so use this from alecxs
Issues with finding device tree blob (.dtb) file on Moto G72 running Android 12.1
Hi everyone, I'm currently having trouble finding the device tree blob (.dtb) file on my Motorola phone running Android 12. I've tried unpacking the boot image file using various tools, but I haven't been able to locate the .dtb file. Here are...
forum.xda-developers.com
& learning more about vendor_boot click
DragonPitbull said:
If you use the Source Code by company/carrier so you need knowledge.
If you only using stock vendor_boot.img so use this from alecxs
Issues with finding device tree blob (.dtb) file on Moto G72 running Android 12.1
Hi everyone, I'm currently having trouble finding the device tree blob (.dtb) file on my Motorola phone running Android 12. I've tried unpacking the boot image file using various tools, but I haven't been able to locate the .dtb file. Here are...
forum.xda-developers.com
& learning more about vendor_boot click
Click to expand...
Click to collapse
The even funnier part that thread was too started by me and you were there too!
FiniteCode said:
The even funnier part that thread was too started by me and you were there too!
Click to expand...
Click to collapse
It's very simple
Direct questions will have direct answers.
Questions about a broad subject will have broader answers.
If your goal was always about custom recovery then you should have prioritized that in your questions.
DragonPitbull said:
It's very simple
Direct questions will have direct answers.
Questions about a broad subject will have broader answers.
If your goal was always about custom recovery then you should have prioritized that in your questions.
Click to expand...
Click to collapse
I didn't, I had both the goals for roms and for custom recovery