When I saw that CWM 6 was available for our Flyer, I jumped to install it without waiting to see results of other users (stupid move, I know). Using DoomLord's touch recovery, I installed and rebooted. Seeing as I had nothing new to flash, I didn't boot back into recovery. Today, I decided I wanted to try out IOIDroid's newest work, and rebooted into recovery to prep for install.
CWM 6 was gorgeous! Only one problem: any action taken made all options text disappear! (nothing but the CWM logo would show until the power button was pushed again) I was able to reboot manually, installed ROM Manager, and CWM 5 through ROM Manager. Reboot to recovery, and nothing but a beautiful white screen/HTC logo... Manually rebooted again, and tried to re flash DoomLord's touch recovery through ROM Manager, reboot, same result. Tried using GooIM to flash the same recovery, and nada...
Luckily the ONEXXL still boots, but I'm stuck with no recovery, now... I'm thinking if I uninstall ROM Manager, delete the CWM folder from my SD, reinstall ROM Manager/CWM, that might fix it? I kinda feel like I'll get the same splash screen, though...
Any other ideas? Never completely lost recovery before...
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
Use fastboot.
yes fastbot flash the recovery img
fastboot flash recovery "name of file.img"
That's the reply I was dreading... Lol. I've always had problems with fastboot / adb on my laptop... Think it's got something to do with Windows 7. CMD prompt opens and immediately closes when I try to open either... I'll try it again, though...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
mcord11758 said:
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
Click to expand...
Click to collapse
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
IP IHI II IL said:
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
Click to expand...
Click to collapse
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Woah, dude! You ROCK! With 4 kids, and helping my fiancée with her daycare it's not easy to find the time to tinker, and you just saved my heinie! Thanks a TON!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Here are my failed attempts:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>devices
'devices' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>C:\android\fastboot flash Flyer-HC-CWM5-Recovery-DooMLoRD-v02-T
ouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>c:\android\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>c:\android\fastboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>c:\android\fastboot update update.zip
error: failed to load 'update.zip'
C:\Users\PHILTHY>c:\android\fastboot flashall
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android\fastboot flash c:\android\recovery.zip
unknown partition 'c:\android\recovery.zip'
error: cannot determine image filename for 'c:\android\recovery.zip'
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android
'c:\android' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>c:\android\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
EDIT: ok, so I re-downloaded/installed the SDK and tools. I put the recovery.img in the folder "C:\android\platform-tools" and ran:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
WTH am I doing wrong?! I know it's user error...
EDIT 2: MORE failed attempts... starting to get frustrated...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\PHILTHY>C:\android\platform-tools\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.512s]
finished. total time: 0.514s
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\recovery.img
unknown partition 'C:\android\platform-tools\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\recovery.i
mg'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash Flyer-HC-CWM5-Recovery
-DooMLoRD-v02-TouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>
I have the recovery.img in "C:\android\platform-tools". I also created a folder named "fastboot" and put it in there, and tried to run it to no avail...grrrrr
IP IHI II IL said:
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Click to expand...
Click to collapse
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
pravus_nephilim said:
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
Click to expand...
Click to collapse
I'll can't believe I forgot to enter the cd command... All that frustration over 2 lil letters... I promise I used to know this stuff well... Guess I've been outta the game for too long... That did it! Thanks for all your help guys, and SUPER thanks to pravus for goin the extra mile to help a dolt!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
vinteri said:
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
Click to expand...
Click to collapse
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
pravus_nephilim said:
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
Click to expand...
Click to collapse
vinteri said:
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
Click to expand...
Click to collapse
Okay, so you're S-OFF with the Honeycomb hboot and trying to flash another HC ROM in recovery. How did you flash the touch recovery? I don't fully understand what you mean when you said "Everytime I got flash closed on recovery".
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
vinteri said:
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Surely you can reboot into the bootloader, go to fastboot and try reflash the a recovery.img? Check the md5 of your downloaded recovery.img in case something is off.
Related
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Same Thing
Hi mjamsek,
I have exactly the same experience as you. I cannot enter the fastboot mode since unlocking/rooting my tf201. Did you solve the problem. ANY help is greatly appreciated!
mjamsek said:
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Click to expand...
Click to collapse
I'm having this exact issue except I used Kingo to root instead of Motochopper. I also tried all of the above to fix it, nothing yet.
@mjamsek
Hey it is not going to fix your issue but, you cant run adb commands in fastboot....
So it should look more like this.....
Code:
fastboot reboot-bootloader
What is your bootloader version ?
Maybe try this as long as you are on a bootloader that ends in 2.17 or 2.18
type this
Code:
fastboot erase recovery
then reboot bootloader
then flash a CWM recovery
then reboot-bootloader
then flash TWRP....
Try that and tell me where it gets you...
Thx Josh
I have a similar issue, I will try your cmd lj50036
Exactly the same issue there...
Device rooted and unlocked. Recovery flashed ( CMW), but unable to entered on....
So anyways i was dissecting dlx 3.06.405.4 ad i happened to stumble across this file in the same directory in the rom.zip. i know this might not be a surprise to some. at first i thought that maybe it was just a regular old fastboot.exe. but in fact when i executed the file i was surprised to find different commands and options. ive searched all over for the commands that are underlined but had no luck. if anybody has anything to contribute to this topic feel free.
C:\Users\Homer\Desktop>htc_fastboot.exe
usage: fastboot [ <option> ] <command>
commands:
flash <partition> [ <filename> ] write a file to a flash partition
dump emmc <filename> <start sector> <sector number> dump the emmc content to the specified file
dump ram <filename> <start address> <size> dump the memory content to the specified file
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
getfb <filename> get frame buffer
boot <kernel> [ <ramdisk> ] download and boot kernel
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
version show Version num
options:
-d disable the auto resend function for Hboot pre-update
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-m <memory usage> specify the max. memory usage(1~100MB) for zip flash. default: 10
C:\Users\Homer\Desktop>
Found the same thing
I found the htc_fastboot.exe as well.
New options.
Have you had any luck experimenting with it?
Enable Developer Mode:
( on the watch )
tap clock, swipe up and go all the way down to “About”
tab build number several times. You’ll know
up one menu, “Developer Options” -> “ADB debugging”
your phone will ask you to allow debugging
dock it, plug usb to computer
in terminal:
adb usb
adb devices (check out your device’s serial #)
adb shell (woot! shell on your watch!)
Backup contents of system partition
mkdir system
adb pull /system ./system
Void the warranty (unlock bootloader)
adb reboot-bootloader
fastboot oem unlock
follow instructions on device
device will factory reset & reboot
Root ( needed to dump partition images, otherwise not particularly useful )
credit for this: androidpolice.com/2014/07/05/how-to-android-wear-enable-debugging-take-screenshots-unlock-the-bootloader-and-root-the-lg-g-watch/
get this: androidfilehost.com/?fid=23501681358558067
adb reboot-bootloader
Boot the image: fastboot boot LGGW-rootboot.img
DO NOT FLASH THE IMAGE!!!! FOR THE LOVE OF GOD DON’T FLASH IT!!!!!!!
intended to boot only once (installs su, etc)
adb shell
su
now what?
Dump some partitions: ( in a root shell on the watch )
partition layout
mmcblk0p15 - boot
mmcblk0p16 - recovery
mmcblk0p19 - system
mmcblk0p20 - cache
mmcblk0p21 - userdatadump some partitions. for example: ( jump into adb shell, as root )
dd if=/dev/block/mmcblk0p15 of=/sdcard/backup/boot.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/backup/recovery.img
dd if=/dev/block/mmcblk0p19 of=/sdcard/backup/system.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/backup/cache.imgDONT TRY TO BACKUP mmcblk0p21 to the sdcard!!! the “sdcard” is on that partition!!
pull the images. for example: ( on your computer )
adb pull /sdcard/backup/boot.img .
adb pull /sdcard/backup/recovery.img .
adb pull /sdcard/backup/system.img .
adb pull /sdcard/backup/cache.img .maybe delete those images from the device when you are done
Have Fun!
Restore images (flash via fastboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
The following may be tricky, might break stuff, and is generally not recommended unless you really know what you are doing
You have been warned!
Install a zip file using the stock recovery (might only work with signed updates, not roms)
In a terminal on your computer:
adb push whatever-new-rom.zip /sdcard/update.zip
adb shell
cp /sdcard/update.zip /cache/update.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/update.zip' >> /cache/recovery/commandreboot recovery
Enable Bluetooth debugging (really slow, kinda lame)
connect your phone over usb
on watch, in developer settings, Debug over Bluetooth
on phone, open wear app, in settings Debugging over bluetooth
on computer:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb shell
Install Debian chroot
on your phone (thats right, your phone) install Debian Kit from Play Store
open it, it the download button in top right corner
download debian-kit-1-6-testing.shar
open an adb shell to your phone ( i prefer usb)
su
cd /sdcard/Download
on my phone it always downloads it as a .jpeg rename it to .shar
mv debian-kit-1-6-testing.jpeg debian-kit-1-6-testing.shar
sh debian-kit-1-6-testing.sharAnswer Y to unpack
read the menu, then choose 0j (wheezy does not work in this script, don’t want it anyway)
it will now create /sdcard/debian.img (512mb) (will take a couple minutes)
next it will mount the image
next it will debootstrap a basic installation of jessie to the image (this takes a long time, ~30 minutes)
you might see an error “cannot create symlink…” that’s good, we don’t want to touch /system anyway
once its done. copy that debian.img from your phone to your computer
adb pull /sdcard/debian.img .we also need everything it unpacked to /data/local/deb
mkdir deb
adb pull /data/local/deb ./deb
unplug phone and plug in the watch, then push those to the watch
adb push debian.img /sdcard/
adb push deb /data/local/debian will not have internet access, the watch has no wifi. need to figure out how to forward over bluetooth
now what? check out this page: sven-ola.dyndns.org/repo/debian-kit-en.html
Also, the best Fastboot Doc ever: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Froz3nsolid said:
Thanks for the Info
If I backup the files, would I be able to flash those same files back to recover the device ,kinda like a unbricking method. Coudlnt I do it though fastboot ?
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The IMAGES (boot.img, etc) can be flashed from fastboot:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, there is no way (that i have found yet) do dump images using fastboot; dumping must be done on the device itself
updating op...
Thanks
Sent from my LG-D851 using XDA Premium 4 mobile app
I have Zenfone 5 phone, and i want to flashable system.img for the fastboot.
I tried dump system.img with help of this topic: http://forum.xda-developers.com/showthread.php?t=2450045
I used this code for the know what devblock is system for the zenfone:
Code:
adb shell
ls -al /dev/block/platform/intel/by-label/
And the mmcblk0p9 showed as system. Than I dumped system image with this command:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img
After dump of system.img, I tried flash it via fastboot with this command:
Code:
fastboot flash system system.img
But the flashing process is aborted with this error:
Code:
invalid sparse file format at header magi [I]-> This error appeared in Windows CMD, others in the below, appeared in the fastboot screen[/I]
e:unknowing chunk type
failed: bad file number
In summary; I dumped system.img and flashed it via fastboot and, it wasn't flashed, and give error.
I tried to convert system.img to system.raw via Ubuntu with simg2img file, I took this error:
Code:
invalid sparse file format at header magi
How to solve this "invalid sparse file format error"? Please help me? I'm making a rom, but this error blocked me
I got my hands on a ls660 finally. It is possible to use send_command.exe to flash and backup the phone. I already tested this myself.
There is no need to zero your laf partition to enter fastboot to flash twrp!
1. copy the twrp bumped image on the sd card
2. cd into the folder that you have the send_command.exe stored.
3. with your ls660 turned off hold volume up and plug in the usb data cable
4. after the phone is in download mode send this command to the apropriate diag port:
Code:
Send_Command.exe \\.\COM14
The phone will show
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
6. This command backs up your recovery image and names it OGrecovery:
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/external_SD/OGrecovery.img
7. This command flashes your phone with the twrp image:
Code:
dd if=/storage/external_SD/recovery_bumped.img of=/dev/block/mmcblk0p17
8. Send the following command in all caps:
Code:
LEAVE
When you reboot to recovery you should load twrp recovery.