I boot into recovery from clockwork and I do not see "install .zip from sd card"
I see all the options such as:
" Android System Recovery <2e>
-for BML-
-Reboot System Now
-Reinstall Packages
-Delete all User Data
-Delete Cache Data
--Movi_check Start..!!
*checksum confirmation need_checksum[0]
*Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# Manual Mode #
-- Appling Muti-CSC..
*Installing Muti-CSC "
what am i doing wrong?? ><
and yes.. i have put the file on the internal sd card with 14 GB.
thanks for any help in advance! =)
reinstall packages...which should reboot you into CWM. You are in the stock 2e recovery...
I'm having an issue in Recovery, It won't let me wipe battery stats and I get into recovery I go advanced --> wipe battery stats --> yes.
Nothing happens, no indication that the stats have been deleted or wiped. If i try to delete delvick then i get E: Can't mount /dev/block/mmcblk0p2 (File exists)
are the two related?
This thread is an all in one recovery thread.
Prereqs:
1. You must have a rooted device
2. Adb setup on computer (terminal on phone can be used in place of adb but adb is preferred)
3. Phone charged 30% or greater is required to use nandroid.
Supported devices:
LG Ally (aloha)
LG Optimus S
LG Optimus V
LG Optimus M
LG Vortex
LG Chic (alessi)
LG Optimus P500, Optimus T P509 (thunderg)
HTC Droid Incredible See link here Xda
LG Shine Plus
Gz'One Commando (in testing)
Want to submit a new device see thread here : How to submit a new device for recovery creation
Recovery Features:
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
(dinc only) mount /Emmc
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
As of 2.2.1 sd-ext is backed up as whole so link2sd users should work fine
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse. (Fixed dir-browsing)
Flash Zip From Emmc (Dinc only)
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe .android secure : Wipes froyo native .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (requires kernel support for ext4 which all but shine have)
Mounts:
Gui mounts to avoid typing in terminal to mount and cd into a dir to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix apk uid mismatches
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Wipe Sdcard
(Dinc only)
Format /data as ext3 | ext4 : format(reformat) /data between ext3,ext4. (This wipes /data also) Requires modification of init.inc.rc & and compatible rom kernel see dinc thread link above
I have included flash_eraseall binary to recovery which can be used to fix/erase corrupted partitions that will not mount correctly to nandroid restore to.
Useage from adb shell is : flash_eraseall /dev/mtd/mtd4 (where mtd4 is the number of the partition from "adb shell cat /proc/mtd" you want to erase)
Trouble Shooting:
1. Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
2. If you get an out of memory error reboot device and do it on a fresh reboot.
3. If you get a file not found on the "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak" skip it and move to the next step as this file will not be in your rom unless it has recieved an ota-update and if so needs to be disabled.
4. Permission denied means you are not root user (#)
5. If rebooting into recovery you get a little android guy with a ! and does not look like picture above you still have stock recovery and did not remove the install-recovery.sh.
6. You did check the md5sum for a match before flashing correct?
Please check all the above issues before posting. This is the format I request to be used for troubleshooting.
Device :
Recovery Version :
Error :
Please upload the recovery.log AS AN ATTACHMENT that you moved to sdcard and read. Posts without this log will be ignored!!!
Please no PM's!!!!!
Device system paths:
Ally: /dev/block/mtdblock4
Optimus M: /dev/block/mtdblock5
Vortex: /dev/block/mtdblock4
Optimus V: /dev/block/mtdblock5
Optimus S: /dev/block/mtdblock5
Optimus P500/Optimus T: /dev/block/mtdblock1
Chic: /dev/block/mtdblock1
Shine Plus: /dev/block/mtdblock1
Directions to flash recovery:
Download your device specific recovery and check md5sum for a match before flashing. Download flash_image.zip and unzip it to root of your sdcard. (Not in any folder)
Copy your devices recovery.img to root of sdcard.
Below can be done via adb shell or terminal emulator on phone via root # shell not a $ shell
Note do not type the # or $ as they are for reference only!
Code:
$ su
# mount -o remount,rw -t yaffs2 (your device /system path) /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/(your device recovery.img name)
# sync
Example for LG Ally above would be:
mount -o remount,rw -t yaffs2 dev/block/mtdblock4 /system
Device specific recovery keys:
Key mapping for Optimus Line & Vortex:
Move up & down = Vol-up & Vol-down
Select = Menu
Backup = Back
Boot recovery from device off: Vol-down + Home + Power and release at LG logo.
Chic(alessi): Vol-up + Vol-down + Power
LG Ally & LG Shine Plus:
Move up & down = Up & down on sliding keyboard
Select = Enter on keyboard
Backup = Vol-down
Boot recovery Ally: Send + Menu + Power
Boot recovery Shine Plus: Vol-down + Home + Power
Adb reboot recovery can also be used to boot custom recovery on most devices.
WARNINGS:
Do not flash a radio.img
Do not factory reset your device via Android OS. Use wipe in recovery.
Source for recovery & recovery kernels My Github
Amon_Ra's Recovery
Reboot system now :: Self explanatory.
Reboots device
USB-MS toggle :: USB Mass Storage.
Mounts the SD card
Backup/Restore (See NANDroid backups
for more information)
Nand backup :: Creates a backup of /
system, /data, /boot, /cache, and /
sdcard/.android_secure (on SD card)
Nand + ext backup :: Creates a Nand
backup plus /sd-ext ( apps2SD) (on SD
card)
Nand restore :: Restores a backup (from
SD card)
Backup Google proprietary system files ::
Creates a backup of gapps
Restore Google proprietary system files ::
Restores a backup of gapps
Flash zip from sdcard :: Flash (install) a
properly formated .zip file
Wipe
Wipe ALL userdata :: wipes /data, /
cache, /sd-ext, and /
sdcard/ .android_secure
Wipe only /data :: wipes /data (user
data)
Wipe only /sd-ext :: wipes /sd-ext
(traditionally Apps2SD)
Wipe only /sdcard/ .android_secure ::
wipes /sdcard/ .android_secure (froyo
Apps2SD)
Wipe only /cache :: wipes /cache
(sometimes used as temp storage for
updates, etc)
Wipe only Dalvik-cache :: wipes /data/
dalvik-cache
Wipe only battery stats :: wipes battery
usages stats
Wipe only rotate settings :: wipes
rotation (accelerometer) data
Partition sdcard
Partition SD :: Starts a wizard to
partition the SD card
Repair SD:ext :: attempts to repair the /
sd-ext partition
SD: ext2 to ext3 :: converts /sd-ext from
ext2 to ext3
SD: ext3 to ext4 :: converts /sd-ext from
ext3 to ext4
Mounts
Mount/Unmount /system :: Mounts or
Unmounts the /system partition
Mount/Unmount /cache :: Mounts or
Unmounts the /cache partition
Mount/Unmount /data :: Mounts or
Unmounts the /data partition
Mount/Unmount /sd-ext :: Mounts or
Unmounts the /sd-ext partition
Mount/Unmount /sdcard :: Mounts or
Unmounts the SD card
Other
Fix apk uid mismatches :: Attempts to fix
the apks permissions
Move recovery.log to SD :: moves
recovery.log to the SD card
Toggle Signature Verify :: Turns
Signature Verification on/off, allowing
you to flash unsigned .zip files
Power off :: Self explanatory
CLOCKWORK MOD
reboot system now
apply update from sdcard :: Installs the
update.zip located in the root of your SD
card
wipe data/factory reset :: Obvious -
clears everything (except your SD card,
hopefully)
wipe cache partition :: erases and
formats /cache
install zip from sdcard
apply /sdcard/update.zip :: Installs the
update.zip located in the root of your SD
card
choose zip from sdcard :: Lets you
browse for and pick the update or
installation zip file
toggle signature verification :: Turns zip
package signature requirement on/off
toggle script asserts
backup and restore
backup :: Performs a full backup (boot,
system, data, cache)
'restore :: Restores the most recent full
backup
advanced restore :: Allows you to select a
backup, as well as select what part of the
backup to restore (boot, system, data,
cache, sd-ext)
mounts and storage
unmount /cache
mount /data
unmount /sdcard
mount /system
mount /sd-ext
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error :: Creates recovery.log in /
sdcard/clockworkmod/ so you can use it
to sumbit error reports using ROM
Manager
Key Test :: Allows you to test your
hardware keys on the device
Partition SD Card :: Allows you to create
an ext partition on your SD card from
128M to 4096M
Fix Permissions :: Resets system
permissions back to their default values
power off
Control files
when placed at /sdcard/clockworkmod/
These files alter clockworkmod default
behavior *use with caution*
options for response fields
.no_confirm
.one_confirm
options for taskbars
.hidenandroidprogress
source - cyanogenmod
for some terms in clockwork like mount refer to amonra they both are the same
Hey Everyone,
So I have an Asus ZenPad C 7.0 Z170C and I was working on rooting the device. Long story short, I messed up and now I have a brick... or paper weight. I can at least use a paper weight for something....
Here is what my devices does currently:
When I try to boot the device, it gets stuck at the 2ND Asus screen and never actually boots up. I can get my device into fastboot (the GREEN background).
I can also get the device into RECOVERY mode by pressing (POWER + VOLUME DOWN) when booting the device.
However, I can only get the device to the screen with the DEAD ANDROID and "No Command" text screen. If I try getting the BOOTLOADER list to pop up, from the DEAD ANDROID screen, by pressing POWER + VOLUME UP, I get an error. The error is different depending on whether I have my EXTERNAL SD card in my device.
The error messages say the following:
EXTERNAL SD Card LEFT IN Device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52347
"
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_locale
"
----------------------------------------------------------------------
EXTERNAL SD Card Taken OUT of the Device:
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52348
"
E: failed to mount /sdcard (No such file or directory
E: Can't mount /sdcard/P01Z_SDUPDATE.zip
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/lastlocale
"
Ive been searching and searching endlessly online all day and couldnt find anything that works. The closest I got was with the following:
Asus Flash Tool: Seems to work fine at first but then hangs. The "Unzip Image" step finishes and then it says "Rune Flash Image Script..." and does nothing. I let it run for over 1 hour and nothing changed.
Please let me know if there is anything else I can try. I do NOT care if my data is lost.
Thank you in advance!!
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
yes, I can do both.. whats your recommendation to restore?
InvisiBot said:
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
Click to expand...
Click to collapse
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
5.0.1
Excellent. Sounds simple enough... I will try this out when I get some time. Thanks you for your help!
Much Appreciated!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
Deleted
So I FINALLY got around to trying your steps and.... IT WORKED!!
Can't thank you enough. I decided to "Apply Update using ADB" instead of the SD card and your step by step guide was perfect.
Thanks Again!!!!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
..
deleted
i did al those steps with thw zenpad 7, because the thing stays in the logo, but im able to set it in recovery mode and fastboot; but when i flashed the latest firmware (from december) it asks for a newer one because the firmware on it is dated 10 april but that is not rolled out on the asus website; any adeas? gr bennie
C:\adb>fastboot flash recovery recovery.bin
(bootloader) recovery partition type: raw
target reported max download size of 1019215872 bytes
sending 'recovery' (8044 KB)...
(bootloader) Ready to receive: 0x007db000 size of da
OKAY [ 0.243s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
FAILED (remote: Fail to flash partition: recovery)
finished. total time: 0.266s
why show error when i flash recovery ,...
i face problem in recovery
try in fastboot
fastboot format cache
fastboot format userdata
fastboot flash recovery (here the extract from above)
check recovery then!
I flash the zip with no errors but after reboot it says "ERROR FW image Verify Fail, Init: Tlv set update list fail" in the recovery menu
What is it mean what should i do?
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
can you extract recovery.bin and vrl.bin
from UL-P01V-WW-12.26.5.49-user from this firmware
my asus zenpad cant turn model number p01v
when i turn on it come no command stuck on there
what i will do
need system.img
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
Can you post the system.img file for the Zenpad C 7..0 and maybe the other factory images too? I accidentally overwrote it and have no way to recover it since I forgot to back up the ROM.