i made a mistake,formatted persist partiton.The camera does not work anymore.So,I need a persist backup image to fix camera ,hope some can send me thank you very much.
fixed by fastboot flash persist.img
Related
Hi I'm trying MIUI and CM7nightly. When I want to change between nandroids of these roms I have problems with cwm3, so I tried to install last bootmenu (0.8.6) from this web http://wiki.rvr.kr/android/bootmenu in MIUI to have both roms with CWM3. When I try to restore MIUI nand CWM3 erase boot and system but has an error writing system so I have to flash sbf. Any idea of how to solve that problem? thanks
i've made a fix in the lastest nightly (110523) (CWM recovery is in /system/bootmenu/recovery/sbin/recovery) to protect us and never format partitions on the defy... (forced to use only the "rm -rf" command)
https://github.com/tpruvot/android_bootable_recovery/commit/5a3c0c49fcc539114d953aa09e2b5aebfaa4bbd0
that could be enhanced also to never unmount partition but i cant test for the moment...
Epsylon3 said:
i've made a fix in the lastest nightly (110523) (CWM recovery is in /system/bootmenu/recovery/sbin/recovery) to protect us and never format partitions on the defy... (forced to use only the "rm -rf" command)
https://github.com/tpruvot/android_bootable_recovery/commit/5a3c0c49fcc539114d953aa09e2b5aebfaa4bbd0
that could be enhanced also to never unmount partition but i cant test for the moment...
Click to expand...
Click to collapse
thanks, but why I can't restore that nandroid? I have to mount system before restore nand? if we have this error, can we restore boot aplying the bootmenu update zip before restart? thanks
Hello everyone,
i bricked my a511 because i had the stupid idea to set go back factory defaults with the old cwm.
so, i know that the problem is the damaged data partition, is it possible to recreate this partition ?
I had the same Problem. I flashed a data.img. This works. you can even mount the system partition? and the cache?
The Fastboot commands are "fastboot flash userdata C:\[your path to the data.img]" and "fastboot flash system C:\[your path to the data.img]"
and "fastboot flash cache C:\[your path to the data.img]"
Webitu
No, it's not the partition that's damaged, but the NAND chip itself.
Hi,
My device is kind of bricked, since it doesn't boot up due to EFS mounting problems.
I tried to restore through adb but there is no /dev/block/mmcblk0p3 location.
Any ideas how I should restore the EFS folder (i have an efs.img saved in my pc) ?
Thanks !
merandrei0508 said:
Hi,
My device is kind of bricked, since it doesn't boot up due to EFS mounting problems.
I tried to restore through adb but there is no /dev/block/mmcblk0p3 location.
Any ideas how I should restore the EFS folder (i have an efs.img saved in my pc) ?
Thanks !
Click to expand...
Click to collapse
There is no mmcblk0p3 for galaxy s6.
Efs mount can be found in the block > /dev/block/sda3
batuzai04123 said:
There is no mmcblk0p3 for galaxy s6.
Efs mount can be found in the block > /dev/block/sda3
Click to expand...
Click to collapse
Thanks!
I succesfully mounted the sda3 block, but still not passing the logo.
Any idea how may I unbrick this guy ?
Hmm try my method
http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
Dont forget to mount /system partition in custom recovery before doing adb commands
batuzai04123 said:
Hmm try my method
http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
Dont forget to mount /system partition in custom recovery before doing adb commands
Click to expand...
Click to collapse
Thanks a lot!
I managed to make it boot, now is usable but still, if I type *#06# it shows me a generic IMEI 3500...06/02 and my SN disappeared, and when I flashed a stock rom have the same problem (stuck at logo).
I've been flashing UniKernel again with odin and all was good.
Is there any chance that I can run stock rom and kernel, and make this go away?
Thank you again !
Hmm ur imei i guess is broken. Did you tried to backup first and restore the efs?
Im not sure but im unable to get my phone to stock . Only custom recovery works for me.
Accidentally I deleted boot and boot1 partitions on my Mi4 while extending system partition. Could create system partitions as ext2 but I do not understand what type of filesystem boot and boot1 belong to. Could someone help in creating back the lost partitions? Thanks in advance
[update]
I think I messed up boot partition...so tried to flash rom via fastboot(since I created the system partition already). Now I can't flash recovery also. Can enter only fastboot mode.Is my mobile permanently bricked?
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)