how create recovery.img
A recovery image for HTC is similar to a boot.img.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Thread moved to Q&A.
Related
I have been attempting to apply a work around from tjayz thread for restoring recovery. In the CWD folder we are supposed to search for 5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
I only see files with names like -2110140792 and -21108160.
Does anyone know if you can rename these files as described in his post?
Thanks
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Thanks first.
Is possible that copy files to recovery partition via adb?
The way it is, I'm porting CW Recovery to a new device, flash img to recovery, it's not work at all, stop at bootlogo.
I try to extract ramdisk.gz from native recovery.img, but failed, gunzip/cpio is useless. someone said copy files to recovery partition, CW Recovery worked. How to? via adb?
If it's possible, copy compiled files first, dump_image recovery secondly, packbootimg finally.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hello everyone, As I can get the original recovery.img from evo 3d gsm???
Thanks,
Njoa said:
Hello everyone, As I can get the original recovery.img from evo 3d gsm???
Thanks,
Click to expand...
Click to collapse
In my opinion, the best source for stock recovery image files are the original RUU leaks we're provided.
Generally, the user named Football posts them in the development threads. Sometimes they are made sticky. I would suggest searching for the RUU thread by Football for the specific software version you're wanting the stock recovery image from.
An alternate mirror source is http://goo-inside.me . As they mirror many RUU files which contain the stock recovery image.
Goo-inside.me usually posts the rom.zip file located inside the RUU.exe which saves the end user a few steps of extracting the rom.zip themselves from the RUU.exe.
Inside the rom.zip file, there will be another file called firmware.zip, this should contain a file named recovery.img, which is the original stock recovery image for that specific software version.
If the process seems convoluted, you can thank HTC! Hope those steps help make sense of the issue!
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11 stock (RUI2.0_A.15). Bootloader - unlock. Root - Magisk_canary_92546e8a (patched boot.img).
1. Backup super.img by Partitions Backup & Restore or Universal Mount SystemRW.
2. Flash stock super.img without any changes
fastboot flash super super.img
3. Device does not boot into the system. Stays in fastboot mode.
Can anyone advise which way to dig?
The goal is to make the system partition writable. The problem is that it is not possible to write a super.img back, even without making any changes.
diogen78 said:
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11 (RUI2.0_A.15). Bootloader - unlock. Root - Magisk_canary_92546e8a (patched boot.img).
1. Backup super.img by Partitions Backup & Restore or Universal Mount SystemRW.
2. Flash stock super.img without any changes
fastboot flash super super.img
3. Device does not boot into the system. Stays in fastboot mode.
Can anyone advise which way to dig?
The goal is to make the system partition writable. The problem is that it is not possible to write a super.img back, even without making any changes.
Click to expand...
Click to collapse
@diogen78
Prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
IJoseph23 said:
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
Click to expand...
Click to collapse
Hello and good afternoon, @IJoseph23
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
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
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
these kind of img files are partition images of linux file systems, sometimes sparsed with simg2img to reduce file size.
usually, partition images can mounted in linux only, same as partitions. windows is not capable of mounting linux file systems natively.
"extracting" linux images on windows is just some nasty hack and not intended for "repacking", because windows file system (NTFS) cannot handle linux file names and its metadata (like permissions, uid/gid, secontext)
the proper way is to mount (EXT4) partition image on linux, delete files, and unmount it.
additionally it might need img2simg/simg2img (not for dynamic partitions on super partition)