[Q] copy files to recovery partition - Android Q&A, Help & Troubleshooting

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

Related

[Q] clockworkmod recovery help

After flashing clockworkmod recovery via rom explorer my phone will not boot into clockworkmod recovery- only the stock android recovery mode. I did notice that the clockworkmod "recovery-update.zip" file contains files that *look* like they want to be in the root directory (ie /sbin/*), but some of these files do not exist in my root directory. I'm guessing maybe that rom manager did not successfully extract the contents of this zip file? Should I manually copy the contents of this zip file over to my root directory?
When you boot into recovery from ROM Manager..you may need to hit "reinstall packages" a couple of times
yup
Thanks, that did it.

[Q] Is flashing an update.zip the same as installing a zip?

I have a couple questions about CWM and backups:
Is there a difference between flashing update.zip and installing a zip from the sdcard in CWM?
Also, let's say I make a change to boot.img and system.img and something goes wrong. Instead of flashing the backups of those two images from my computer to my phone using fastboot, can I just place them both in a zip file and install it from CWM? Would I need to include any other files?
How come a nandroid backup makes a system.ext4.tar and not a system.img? How do I turn that into a system.img?
How come I need unyaffs to read cache, data, and system.img files? I thought the filesystem was ext4 and not YAFFS?
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
marko! said:
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
So I found some links about the update-script and I'll be reading those shortly, but after skimming them I didn't see any mention of the binary. Is the binary an executable version of the same script or something else? Any links?
So what your saying is I could just skip the update.zip stuff, extract the images from the zip, and use advanced restore to flash each image? Obviously more work but it's good to know if these two processes are equivalent.
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
And also the last question about ext4 and YAFFS is still there. Thanks.
Most of those I'm really not sure. The update binary is the same for every zip. Just grab it from a rom or theme
I would go with the cwm zips. Way easier once you get them working.
sent from my Atrix via XDA premium
gsingh2011 said:
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
Click to expand...
Click to collapse
I was just looking at this too. My old recoveries from before atrix4.1 was released were all .img files and the post atrix4.1 backups are .ext3.tar (except for boot.img and recovery.img). I'm on a stock deodexed GB ROM, so I don't have any ext4 partitions. I think he changed this with the newest update so CWM can recognize the ext type and mount them appropriately.
This post should hopefully clarify a bit more than I can. I'm relatively new to all this so I'm still learning different aspects of modding. I'm guessing you have some ext4's because you're running one of the newer custom ROM's?

Using Fastboot with CWM backup containing blobs...

Hi
I've got a HUAWEI u8815 phone stuck in boot loop - I can use Fastboot to flash BOOT.IMG and RECOVERY.IMG to it fine.
Thing is I need to flash a SYSTEM.IMG but the only backup of the System is a CWM backup that is not in *.IMG format.
It has
- system.ext4.dup
- blobs (folder - containing loads of folders and files)
Question is can I make a SYSTEM.IMG from these files... or flash the blobs - but if so how?
I'm very stuck so any help appreciated.
Thanks
giblet
Fixed - by using Fastboot to update to latest ClockworkMod Recovery v6.0.2.7 that allowed me to access the file system by mounting the SD cards... I was sweating for a bit.

S III efs missing not booting

Dear Friends,
Need help please. I have installed another custom rom that was not meant for I9300 and now the EFS is corrupted. I tried installing orignal rom using ODIN but geting boot loop and the phone is not booting. On going into recovery i can see an error efs/ corupted or something like that. I have the backup of my EFS folder in tar.gz format however dont know how to install the same and recover my phone as not able to boot to android.
Please help me if someone can work it out. My phone has just 3 days of warranty left and it does not shows rooted anywhere except the count of installation is about 32 and rom says official and kernel says custom.
Please if someone can help me restore my phone back in working condition i shall always remain thankfull.
Regards,
Mush
mush2004 said:
Dear Friends,
Need help please. I have installed another custom rom that was not meant for I9300 and now the EFS is corrupted. I tried installing orignal rom using ODIN but geting boot loop and the phone is not booting. On going into recovery i can see an error efs/ corupted or something like that. I have the backup of my EFS folder in tar.gz format however dont know how to install the same and recover my phone as not able to boot to android.
Please help me if someone can work it out. My phone has just 3 days of warranty left and it does not shows rooted anywhere except the count of installation is about 32 and rom says official and kernel says custom.
Please if someone can help me restore my phone back in working condition i shall always remain thankfull.
Regards,
Mush
Click to expand...
Click to collapse
It is essential that you have a backup of the EFS partition and a way to place it back - the first two ways that I would think about are:
a) use a good recovery - like Philz recovery, that has commands to restore EFS
b) if the format of the backup is not exactly right you might be able to boot in recovery and use ADB commands.
xclub_101 said:
It is essential that you have a backup of the EFS partition and a way to place it back - the first two ways that I would think about are:
a) use a good recovery - like Philz recovery, that has commands to restore EFS
b) if the format of the backup is not exactly right you might be able to boot in recovery and use ADB commands.
Click to expand...
Click to collapse
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Ver3go said:
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Click to expand...
Click to collapse
I am new to adb commands. Will phylz recovery help me enter the commands? if yes then i shall be replying with the sd card efs tar file name. Will then you be able to guide me with the commands based on the tar file?
Thanks all of you in advance.
Mush
mush2004 said:
I am new to adb commands. Will phylz recovery help me enter the commands? if yes then i shall be replying with the sd card efs tar file name. Will then you be able to guide me with the commands based on the tar file?
Thanks all of you in advance.
Mush
Click to expand...
Click to collapse
No for ADB you boot into recovery, connect your computer via USB and run the ADB commands from either Linux Terminal or Windows Command Prompt.
The tool here:
http://forum.xda-developers.com/showthread.php?t=1703488
May help if you're new to adb.
Otherwise it's a case of downloading and installing the drivers for your phone and the Android SDK http://developer.android.com/sdk/index.html
Thanks for all your replies.
Just wanted to confirm if i have the efs backup in sd card as under folder backup_efs and there are two files in tar.gz format will i be able to use the phylz recovery to use this replace my efs folder? if yes then can you guide me the steps please.
Regards,
Mush
mush2004 said:
Thanks for all your replies.
Just wanted to confirm if i have the efs backup in sd card as under folder backup_efs and there are two files in tar.gz format will i be able to use the phylz recovery to use this replace my efs folder? if yes then can you guide me the steps please.
Regards,
Mush
Click to expand...
Click to collapse
I do not remember right now what creates an backup_efs folder but it really does not matter that much - the tar.gz is a "file archive" and .img is usually a partition image. Each could have minor advantages - the .img also contains the entire filesystem of the partition (and will work easier if the filesystem is bonked) but a tar.gz backup is more versatile when you have bad sectors or a changed partition.
Under an advanced recovery like Philz you would just navigate some menus and try to restore the EFS - see the info in those specific threads.
Under ADB you need to have stuff (drivers and some programs) installed in your PC, you connect the phone on USB and you run ADB commands from the command line.

[Q] New Device Need Help with CWM

Okay so I have a tablet that not many have CWM was not supported. a Pyle Astro 7 Tablet
Heres what i did so far.
1. Got Root Access and busybox successfully
2. Backed up Recovery.img System.img kernel.img Boot.img successfully via terminal emulator.
3. Used builder.clockworkmod.com and made CMW recovery for my device by extracting the recovery.fstab and using the stock device recovery.img
4.moved it to device
5. removed the install-recovery.sh
6. couldnt locate any other recovery related .sh or .p files except autorecoveryon.sh and autorecovery.off.sh also removed them for the time being.
7. attempted to flash cmwrecovery.img via terminal via following code.
flash_image recovery /sdcard/cwmrecovery.img (i named file cwmrecovery.img for easier access.
8.rebooted device into recovery.
Still stock recovery...
Am I missing anything?
Any help would be awesome! If needed i can upload the System.img Boot.img Recovery.img CWMrecovery.img and Kernel.img
Thank you in advance!
zonark said:
Okay so I have a tablet that not many have CWM was not supported. a Pyle Astro 7 Tablet
Heres what i did so far.
1. Got Root Access and busybox successfully
2. Backed up Recovery.img System.img kernel.img Boot.img successfully via terminal emulator.
3. Used builder.clockworkmod.com and made CMW recovery for my device by extracting the recovery.fstab and using the stock device recovery.img
4.moved it to device
5. removed the install-recovery.sh
6. couldnt locate any other recovery related .sh or .p files except autorecoveryon.sh and autorecovery.off.sh also removed them for the time being.
7. attempted to flash cmwrecovery.img via terminal via following code.
flash_image recovery /sdcard/cwmrecovery.img (i named file cwmrecovery.img for easier access.
8.rebooted device into recovery.
Still stock recovery...
Am I missing anything?
Any help would be awesome! If needed i can upload the System.img Boot.img Recovery.img CWMrecovery.img and Kernel.img
Thank you in advance!
Click to expand...
Click to collapse
How did you root your Pyle tablet? Any tips on the procedure? Im having trouble getting mine rooted.
Thanks!

Categories

Resources