Hi I am using Alcatel ideal 4060a, with Android 5.1.1, I have rooted this phone using king root. Then I edited /fstab.qcom file (added one more line, with backup file fstab.qcom.bak). Now the phone is in bootloop. I have dd image of all my partitions, but I don't know which partition is / partition. /data /system /dev /mnt /storage /modem /persistent are mounted on / but which is /. (I tried resotring boot thinking that I holds / file system, but did not helped either.). I have working TWRP. I boot it using
HTML:
$fastboot boot /home/xyx/TWRP.img
Help me plz, how to restore that backup /fstab.qcom.bak. reply soon. Thanks
Related
Hey guys!
It has been already a while messing around with my Defy but one question still remains unanswered for me.
If /cache, /data and /system partitions are Ext3 formatted (you can check this by typing mount in Terminal Emulator), why do nandroid backup images have Yaffs2 filesystem then? Why does this conversion occur? Doesn't it make much more sense to image the partition in its original filesystem?
Thanks in advance...
Nandroid backup - image with YAFFS filesystem. - not dump of partitions.
When recovery is simply unpack files on the ext3 partition.
i suppose earlier (android) adoption of yaffs2 played a big part of that decision, but now it may very well be tar.
it's just a lot easier not to change what's not broken, isn't it?
Will soon be changed to TAR format (Recovery 4.0 will support the two formats)
It sounds good.
Wish the recovery would be more powerful after its source open.
I've compiled a recovery.img of ClockworkMod 4.0.0.4 for anyone interested. This is actually git committish 7905c80940acfe796619631e74999202f3dd5394.
Now you're asking yourself if this is worth it: I don't believe so. It does not allow us to root devices that aren't, and it doesn't restore amend functionality. Because I don't know of any value to it, I'm not providing install instructions until there's a good reason to use it
THIS IS AN UNOFFICIAL RECOVERY, it's not supported, it might cause gnomes to steal your headphones, or the end of the world. You have been warned
I created this for no particular reason other than to test s-off fastboot flashing. Again, I don't know of any benefits of this over any other recovery.
Removed until I can solve the nandroid issues.
I could not get nandroid backup/restore to work for me...
From what ladios said,offmode charging would be the only thing.however thank-you for compiling and uploading it.
Sent from my Liberty using XDA App
nandroid backup doesn't work in this recovery :-/
s0be said:
nandroid backup doesn't work in this recovery :-/
Click to expand...
Click to collapse
it worked for me as far as ive seen?
drowningchild said:
it worked for me as far as ive seen?
Click to expand...
Click to collapse
Hmmm.... odd. I just built 4.0.0.5 which has a few bug fixes. Will see if I still have problems.
s0be said:
Hmmm.... odd. I just built 4.0.0.5 which has a few bug fixes. Will see if I still have problems.
Click to expand...
Click to collapse
I'll try to restore to see if there's any issues
Sent from my Liberty using XDA App
No issues so far
Backed up & restored fine from a full wipe
Sent from my Liberty using XDA App
Nandroid should be fine, after I've added sd-ext to recovery.fstab.
An easy customization is to put an OC kernel into recovery image. My recovery run at 806 max as default. Note that since offmode-charging (image resources) added, kernel size has become a bit limited. Building the kernel without TUN, CIFS, and WLAN, then it should be small enough to fit in the image.
Very odd... my cwm restarted every time it tried to backup or restore system. 2.5.x.x works fine. Will have adb access in a couple hours to see what's up.
Sent from my Liberty using XDA App
Still stumping me:
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at c2a6c00000000
I:Set boot command ""
SD Card space free: 10378MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Starting recovery on Sat Jun 18 20:13:24 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v4.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
mtd: successfully wrote block at c2a6c00000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Anyone have any hints how to get more verbose errors out of CWM?
I just repo synced and built recoveryimage and it was 4.0.0.5. It backed-up with nandroid just fine, but I think it hosed the sd-ext partition as it rebuilt the dalvik cache. My dalvik is on sd-ext. So what is the best working version of 3.X that has offline charging?
Edit: Nevermind, this 2.5.0.7 version seems to be the best recovery I have found for my device. http://forum.xda-developers.com/attachment.php?attachmentid=563834&d=1302280803
the one that was posted works 100% for me?
sd-ext fine
drowningchild said:
the one that was posted works 100% for me?
sd-ext fine
Click to expand...
Click to collapse
Ill try it again. Nothing to lose but dalvik on sd-ext.
Is there a way to boot into clockworkmod, and make changes to the recovery files? I have a second partition on my sd card (formatted as ext3), but when I boot into CWM, the /etc/fstab file always has it listed as ext4. It will only mount the second partition if I manually mount it as ext3 (through adb). Is there a way to make a change to the /etc/fstab and /etc/recovery.fstab, and have those changes persist after a reboot?
This partition mounts perfectly fine booting normally, its just in CWM that I have issues.
Bump. Any way to permanently change the image and reapply them after updating CM?
I was wondering if the root of the phone (not root access, but root folder) gets messy over time when installing and flashing different roms? Or when I do a full wipe in twrp does this format the root of the phone as well? Why I'm asking this is because I'm curious is there might be any left-over files or folders that can mess things up with certain apps or rom functionality.
Everything related to rom exists in /system only. Rest of the folders in root are bootloader and efs modem files you can not delete them and if you even tried your phone will die forever.
qasim799 said:
Everything related to rom exists in /system only. Rest of the folders in root are bootloader and efs modem files you can not delete them and if you even tried your phone will die forever.
Click to expand...
Click to collapse
When I take a look in the root there are 22 folders and 40 files. Is this a normal structure for the root? Will a stock firmware flash via odin replace the root or is this exactly the same as flashing a rom from xda in twrp?
The root folder (/) of an Android device is just temporary expect those folders;
Mounted on physical partitions;
/data
/system
/cache
/efs
/persdata
/preload
/sbfs
/vendor (symlink of /system/vendor)
What you see in root folder (/) is just an extracted gzip (or lzma, depends on kernel builder) image which is a part of boot.img expect of those folders;
These are auto-generated by Linux kernel while booting;
/dev
/proc
/sys
/acct
forumber2 said:
The root folder (/) of an Android device is just temporary expect those folders;
Mounted on physical partitions;
/data
/system
/cache
/efs
/persdata
/preload
/sbfs
/vendor (symlink of /system/vendor)
What you see in root folder (/) is just an extracted gzip (or lzma, depends on kernel builder) image which is a part of boot.img expect of those folders;
These are auto-generated by Linux kernel while booting;
/dev
/proc
/sys
/acct
Click to expand...
Click to collapse
So if I understand it correctly, it's impossible to have left over files or folders from changing roms?
Well they are important boot files which are made by hardware while booting up. We are only concerned with system partition. You can also see inside any rom zip file only system folder and boot img. So stop bothering everything except system and data partition.
Hi All,
I am having issues recovering my crDroid system.
I have moved the correct backup folder from one ID directory to the other parent directory that BRP can see.
I was able to select the backup and run Restore but after reboot it's in a bootloop.
I assume these TWRP of different versions are incompatible or I flashed too many partitions perhaps I should deselect some of them.
At the time TWRP auto-selected partitions for backup:
Code:
System
Vendor
Vendor Image
Boot
Data (excl. storage)
DTBO
Persist
Persist Image
NVCFG
NVDATA
NVRAM
Protect F
Protect S
VBMETA
and these all were selected and restored.
BRP digested all the backup files and found no issue but at the end of restore there was one problem:
Code:
Formatting Persist using mke2fs...
mke2fs -t ext4 -b 4096 /dev/bock/sdc10 18040
process ended with ERROR: 1
Unable to wipe Persist.
Is there anything that can be done about it?
Just to mention this is a MediaTek chip phone.
Kardell said:
Hi All,
I am having issues recovering my crDroid system.
I have moved the correct backup folder from one ID directory to the other parent directory that BRP can see.
I was able to select the backup and run Restore but after reboot it's in a bootloop.
I assume these TWRP of different versions are incompatible or I flashed too many partitions perhaps I should deselect some of them.
At the time TWRP auto-selected partitions for backup:
Code:
System
Vendor
Vendor Image
Boot
Data (excl. storage)
DTBO
Persist
Persist Image
NVCFG
NVDATA
NVRAM
Protect F
Protect S
VBMETA
and these all were selected and restored.
BRP digested all the backup files and found no issue but at the end of restore there was one problem:
Code:
Formatting Persist using mke2fs...
mke2fs -t ext4 -b 4096 /dev/bock/sdc10 18040
process ended with ERROR: 1
Unable to wipe Persist.
Is there anything that can be done about it?
Just to mention this is a MediaTek chip phone.
Click to expand...
Click to collapse
How about flashing stock rom with Manufacture Tool? I also used to have /vendor error. Solved by flashing stock rom then wipes everything and Flashed a Rom(it has vendor in it)