Possible to Recover Data with Fastboot Only? - Samsung Galaxy Nexus

Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?

Phylum said:
Short Version: Phone doesn't complete boot, bug droid red triangle exclamation in recovery. Only fastboot works in bootloader; adb doesn't work at any point anywhere. Is it possible to recover data somehow? (that's all he wants to know)
Long Version:
My coworker was at the Baltimore races this past weekend, taking pictures & video. Phone got down to about 29% so it holstered it. A while later he reaches for the phone but its dead. "Must be a dead battery" he thought. Got home, charged it up but the phone doesn't successfully boot.
This is a stock Verizon Galaxy Nexus (Toro) running 4.0.4: not unlocked & not rooted and thus USB debugging never enabled. The phone will turn on, and it displays the Google logo but never progresses beyond that. We are able to boot into the bootloader and fastboot is able to communicate with the phone without issue. But when we try booting into recovery, it takes a while and we end up seeing the droid logo with the red triangle; nothing else displayed on screen.
If we hold the three buttons from there, text fills the screen with errors like:
Code:
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Failed closing /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (I/O error)
...
From recovery if we try wiping cache it says
Code:
-- Wiping cache...
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
Cache wipe complete.
(more of the same cache errors as above)
From recovery if we try to reboot it eventually reboots, but not before showing loads of errors, and it doesn't actually reboot - it turns the phone off but its in an odd state that requires battery pull.
All he really wants to do is recover as much data; mainly pictures etc. Is this possible?
Click to expand...
Click to collapse
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.

Petrovski80 said:
If he has fastboot, boot a custom recovery image using 'fastboot boot recovery nameofrecovery.img. Then boot into recovery, this will allow adb access. Use adb to pull the /sdcard.
Click to expand...
Click to collapse
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only

qtwrk said:
??? for real? Recovery can use ADB ??? i always thought it has to be in the Android system only
Click to expand...
Click to collapse
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM

kyokeun1234 said:
Nope, CWM and TWRP has USB debug on and thanks to that, ADB is possible through them. Really useful when you do a SuperWipe and need to transfer ROM or just clumsy and wiped without transferring ROM
Click to expand...
Click to collapse
so , we can use ADB commands in Recovery just as the same way we do in Android ???

qtwrk said:
so , we can use ADB commands in Recovery just as the same way we do in Android ???
Click to expand...
Click to collapse
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?

on$ said:
So flashing a custom recovery ROM will not affect the other data stored on the internal memory of the phone?
Click to expand...
Click to collapse
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app

Zepius said:
If you have a custom recovery yes
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
mrgnex said:
Flashing a custom recovery will only affect the recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
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 (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-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. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??

on$ said:
I have essentially the same issue that this thread started with, no root, locked phone.. essentially bone stock verizon moto droid razr maxx HD (XT926).. and it's boot looping at the red eye.. I can get the bootloader menu and I can get into recovery, but I'd like to get data off of it before I do a FDR...
THEREFORE;
I tried the commands "fastboot boot recovery imgname.img" and I get cannot load 'recovery': No such file or directory
I'm not sure if that is an issue with the version of the fastboot utility on my computer or on my handset (getvar shows vanquish & 109B(*) and hardware revision 0x8300
I tried the command "fastboot boot imgname.img" and I get the following
downloading 'boot.img'...
OKAY [ 0.522s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.554s
I can confirm that my device is connected via the fastboot devices command
here is a list of options from my version of fastboot
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 (and format if supported by partition type)
-u do not first erase partition before formatting
-s <specific device> specify device serial number or path to device port
-l with "devices", lists device paths
-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. default: 0x10000000
-n <page size> specify the nand page size. default:2048
-S <size>[K|M|G] automatically sparse files greater than size. 0 to disable
is this an issue of getting the right version of fastboot on my computer or just formatting the fastboot boot recovery command in a different way that works with my version??
Click to expand...
Click to collapse
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Click to expand...
Click to collapse
OK- so here's what I get
>fastboot boot recovery.img recovery
cannot boot a boot.img *and* ramdisk​
however if I use the OTHER command
>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7890 KB)...
OKAY [ 0.613s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.760s​
on my phone the initial fastboot display reads as follows:
AP Fastboot Flash Mode (S)
10.9B(*) (SHA-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 32GB
Device is LOCKED. Status Code: 0
Battery: OK
Transfer Mode:
USB Connected
Invalid image size for partition recovery​
it gave me the same response for both the Clockwork Recovery and the clockwork Touch Recovery which I copied into the directory and renamed "recovery.img" in both cases... going to try the TWRP and oudhs next..but I'm wondering if I might actually have a variation of the xt926 and not know it?? (it is a droid razr maxx HD)... any other suggestions??

Your device is locked. But when you unlock it you'll lose all your data..
Sent from my Galaxy Nexus using xda app-developers app

Similar issue
mrgnex said:
You used the wrong command. What you need to do: put the recovery.img you downloaded into the same folder as where your fastboot is located. Then for the sake of it rename the recovery image to: "recovery.img". Then fire up cmd and type: "fastboot flash recovery recovery.img". If you want to boot into it once: "fastboot boot recovery recovery.img". This should do it (without the quotes of course Hoped this helped!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s

xtravaluemeal said:
I am having a similar issue getting twrp to install...
./fastboot flash recovery twrp-2.8.6.0-m8.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (5 KB)...
OKAY [ 0.131s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.133s
Click to expand...
Click to collapse
Can you still boot into the OS?
If you can remove an app and see what happens, if moments later or after reboot the app is there again your EMMC might be fried.
To check that lock the bootloader. If that is locked upon reboot you're fine, if not the EMMC is fried. If this succeeds though your data is lost.
If all this does not apply to you, then it is probably a driver culprit.

Related

Samsung Galaxy Nexus SCH-I515 Will not go past google start screen

The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
the lock symbol means your phones bootloader has been unlocked allowing for custom development. i assume you have bought the device second hand as you obviously didnt unlock it yourself.
to make your phone boot i suggest cleaning your devices cache.
-power off device
-hold power up+down while pressing power button
-use the volume buttons to scroll down to recovery and press power to select
-after google logo disappears a little android with a blue thingy will come up, at this point hold the power button then press volume up and another selection screen will come up.
-select clean cache and then press power to select. when this is done reboot your device.
im not 100% sure this is your problem but its worth a try.
I was stuck at the same screen this morning. I tried booting into CWM Recovery from Jelly Bean and my phone wasn't having any part of it. I kept waiting and eventually pulled the battery. Luckily, I was able to boot into the ROM on my second battery pull. I doubt this helps though, just my two cents.
joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
me too same problem.how to solve?
can you tell me about this?or Anybody have..?
Boot into boot loader. Flash stock. Flash clockwork. Flash a rom that works
Yes had the same issue. I had to walk away and give it time and I came up.
How long have u let it go?
Sent from my Galaxy Nexus using xda app-developers app
animal24 said:
Boot into boot loader. Flash stock. Flash clockwork. Flash a rom that works
Click to expand...
Click to collapse
Thanks to reply
but i don't understand about flash. i can do fastboot mode only then...............what do? which software help me to flash?
i download [mysid-icl53f-factory-65895fa8.zip] file from goo.im but this is zip file.no software.
so please help me out.
sattar_00977 said:
Thanks to reply
but i don't understand about flash. i can do fastboot mode only then...............what do? which software help me to flash?
i download [mysid-icl53f-factory-65895fa8.zip] file from goo.im but this is zip file.no software.
so please help me out.
Click to expand...
Click to collapse
the newest released stock images are here https://developers.google.com/android/nexus/images
down towards the bottom should be imm76k for the mysid
its a zip, but inside, there is a bootloader, 2 radios, and a system image, maybe some other tidbits
so just unzip it to the same directory as your fastboot.exe
assuming you're unlocked.
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
after that i always boot into recovery and do another factory reset, but thats me.
enjoy!
animal24 said:
the newest released stock images are here https://developers.google.com/android/nexus/images
down towards the bottom should be imm76k for the mysid
its a zip, but inside, there is a bootloader, 2 radios, and a system image, maybe some other tidbits
so just unzip it to the same directory as your fastboot.exe
assuming you're unlocked.
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
after that i always boot into recovery and do another factory reset, but thats me.
enjoy!
Click to expand...
Click to collapse
on fastboot mode show follow status on screen
Code:
FASTBOOT MODE
PRODUCT NAME-tuna
VARRIANT -toro
HW VERSION-9
BOOTLODER VERSION-PRIMKK15
BASEBAND VERSION-I515.EK02 CDMA-I515.EK05
CARRIER INFO-NONE
SERIAL NUMBER-0146970F11019005
SIGNING-production
LOCK STATE-UNLOCKED
so i download [mysid-icl53f-factory-65895fa8]
but while flashing stop on
sending 'boot' (4074 KB)...
OKAY [ 0.420s]
writing 'boot'...
full log is
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\sattar>cd C:\Users\sattar\Desktop\mysid-icl53f
C:\Users\sattar\Desktop\mysid-icl53f>fastboot-windows
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
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
< waiting for device >
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.830s]
finished. total time: 21.074s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.069s]
writing 'radio'...
FAILED (remote: Unknown Partition)
finished. total time: 1.082s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.061s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 42.821s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot -w update image-mysid-icl53f
error: failed to load 'image-mysid-icl53f'
C:\Users\sattar\Desktop\mysid-icl53f>fastboot -w update image-mysid-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I515.EK02
Serial Number........: 0146970F11019005
--------------------------------------------
checking product...
OKAY [ 0.008s]
checking version-bootloader...
OKAY [ 0.009s]
checking version-baseband...
OKAY [ 0.009s]
checking version-cdma...
OKAY [ 0.009s]
sending 'boot' (4074 KB)...
OKAY [ 0.420s]
writing 'boot'...
what happean this?
You skipped the part where it was suggested to go download the IMM76K image. I'd start there. You're trying to flash an older build.
Cilraaz said:
You skipped the part where it was suggested to go download the IMM76K image. I'd start there. You're trying to flash an older build.
Click to expand...
Click to collapse
still no luck. try all image but not sucess. what i do?
sattar_00977 said:
still no luck. try all image but not sucess. what i do?
Click to expand...
Click to collapse
Try flashing the images one by one, instead of using "fastboot update". See here.
efrant said:
Try flashing the images one by one, instead of using "fastboot update". See here.
Click to expand...
Click to collapse
really i am a fool. i can't understand even many people teach me.
i extract all file like this on desktop.
Uploaded with ImageShack.us
it,s right?
Then first i write bootloader
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.832s]
finished. total time: 21.075s
Click to expand...
Click to collapse
it's done
then try radio it take upto 1 hour but not sucess
this time show fastboot status --flash radio on buttom of screen
i wait upto 1 hour but sucess then i remove
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\sattar>cd C:\Users\sattar\Desktop\mysid-icl53f
C:\Users\sattar\Desktop\mysid-icl53f>fastboot-windows
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
C:\Users\sattar\Desktop\mysid-icl53f>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.009s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot reboot bootloder
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
continue continue with autoboot
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\sattar\Desktop\mysid-icl53f>fastboot reboot bootloader
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
continue continue with autoboot
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\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.832s]
finished. total time: 21.075s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.067s]
writing 'radio'...
Click to expand...
Click to collapse
sattar_00977 said:
really i am a fool. i can't understand even many people teach me.
i extract all file like this on desktop.
it,s right?
Then first i write bootloader
it's done
then try radio it take upto 1 hour but not sucess
this time show fastboot status --flash radio on buttom of screen
i wait upto 1 hour but sucess then i remove
Click to expand...
Click to collapse
I can't view your screen shot. It's too small.
Your reboot command didn't work because you are missing the dash. It is "fastboot reboot-bootloader" not "fastboot reboot bootloader".
Not sure why the radio is not flashing for you. Try skipping it and move to the next image.
Sent from my Galaxy Nexus using Tapatalk 2
I have this same but problem but I tried what Efrant suggested doing from the bootloader and it appeared to work, my phone booted up and was back to stock. I continued to test restating it and it would go through the google splash screen only about 5-10 times to boot, so i thought that it was fine and continued to use my phone throuhgout the day.
Well I restarted it again later and it went right back into the bootloop. I flashed to stock again following Efrants directions and it worked for a little but soon went back into the bootloop.
What else can I do? I dont want to have to get a new one through Asurion because you never know what kind of ****furb you'll get and its 50$..
Don't mean to hijack but I can't find answers anywhere else!
jigawut said:
I have this same but problem but I tried what Efrant suggested doing from the bootloader and it appeared to work, my phone booted up and was back to stock. I continued to test restating it and it would go through the google splash screen only about 5-10 times to boot, so i thought that it was fine and continued to use my phone throuhgout the day.
Well I restarted it again later and it went right back into the bootloop. I flashed to stock again following Efrants directions and it worked for a little but soon went back into the bootloop.
What else can I do? I dont want to have to get a new one through Asurion because you never know what kind of ****furb you'll get and its 50$..
Don't mean to hijack but I can't find answers anywhere else!
Click to expand...
Click to collapse
That is very strange. If you successfully flashed ALL the stock images as per that guide, and the device boots properly, but you are still getting bootloops, it is either an app that you have installed that is causing it, or a hardware issue.
finitestruggle said:
the lock symbol means your phones bootloader has been unlocked allowing for custom development. i assume you have bought the device second hand as you obviously didnt unlock it yourself.
to make your phone boot i suggest cleaning your devices cache.
-power off device
-hold power up+down while pressing power button
-use the volume buttons to scroll down to recovery and press power to select
-after google logo disappears a little android with a blue thingy will come up, at this point hold the power button then press volume up and another selection screen will come up.
-select clean cache and then press power to select. when this is done reboot your device.
im not 100% sure this is your problem but its worth a try.
Click to expand...
Click to collapse
Doesn't this mean he is locked, not unlocked.the lock symbol has to be one of an open lock.this could be why flashing falls.
joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk 2
koftheworld said:
Doesn't this mean he is locked, not unlocked.the lock symbol has to be one of an open lock.this could be why flashing falls.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If it was locked there would be no symbol
efrant said:
That is very strange. If you successfully flashed ALL the stock images as per that guide, and the device boots properly, but you are still getting bootloops, it is either an app that you have installed that is causing it, or a hardware issue.
Click to expand...
Click to collapse
Yes I'm pretty sure all the images flashed succesfully but when i did the last one it said something about something not being available, not home right now or else I'd check. I really hope this isnt a hardware problem but I don't see how it could be. When it started doing this I was downloading a bunch of files on my phone at work and it randomlly restarted and went into the bootloop. Is there anything I could try before getting a replacement?
how many time take for flashing?
i need tested working fastboot.exe for window.

[Q] TWRP recovery Stuck at Booting recov image

Hi, it's the second time i try to install TWRP recovery v2.2.0+ and each time it keeps getting stuck at the boot with the message
Bootloader version 0.03.06-ics unlock mode
Booting recovery kernel image.
Waited for more than 10 minutes and nothing happened.
i can reboot and and log into ics normally i just don't have access to a recovery.
---I want to know how to properly install twrp , what went wrong and how to fix it.:
the script:
@echo off
cls
echo reboot to bootloader
adb wait-for-device
adb shell su -c "mount -o remount, rw /system/ && mv /etc/install-recovery.sh /etc/install-recovery.offsh;"
adb reboot-bootloader
echo flashing recovery
fastboot flash recovery recovery-A100ICS-TWRP-2.2.0.img
echo -
echo -
fastboot reboot
adb wait-for-device
echo check the recovery XXXXXXXXXXXXXXXX--This is where i'm stuck at.
adb reboot recovery
MY SETUP:
ROM FLEX-A100-REAPER-RELIX_Rev2 , OC A 1500, CWM was working ok.
WIN64
I would suggest downloading the image again, then trying the install script after you delete the current image with the newly downloaded image.
If you feel OK using a terminal its pretty straight forward
Open a terminal and CD to the folder with adb fast boot and recovery image
Example
cd c:\recovery
If powered on type
adb reboot bootloader
After it boots into download protocol type
fastboot erase recovery
fastboot flash recovery twrp.img
Twrp.IMG being whatever the file name is.
fastboot reboot
Let it boot into android then
adb reboot recovery
See what it does.
Tapatalked from my Galaxy S II.
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
IamModeste said:
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
Click to expand...
Click to collapse
That's the only boot loader we can flash on so that's fine. Did you download the image again?
Tapatalked from my Galaxy S II.
pio_masaki said:
Did you download the image again?
Click to expand...
Click to collapse
yes i did , donloaded openrecovery-twrp-2.2.2.1-a100.img,
renamed to recovery.img and flashed without any problem.
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
IamModeste said:
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
Click to expand...
Click to collapse
Did you erase recovery before flashing?
Theonew said:
Did you erase recovery before flashing?
Click to expand...
Click to collapse
Agreed.
I would try again make sure to: 'fastboot erase recovery', then 'fastboot flash recovery recoveryname.img' (make sure it's recovery [space] then the img name).
You can also try Zeronull's 2.1.1/2.2.0 and Linuxsociety's 2.2.2.0. It could be a bad upload of the 2.2.2.1 img
Answer
There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it.
sounds like you may need to start fresh.
Use fastboot to erase the system, boot, recovery and cache, perform a fastboot -w and then install the new recovery and ROM. Erasing the system will kill that recovery file from above.
Let me know. There are a couple of other options that I can think of.
---------- Post added at 06:48 AM ---------- Previous post was at 06:32 AM ----------
Here is what it should look like in fastboot on the command prompt yours will be different of course because mine is setup differently. But basically load up fastboot on windows or whatever you use and first erase the recovery then run fastboot -w and then flash the twrp recovery image and finally fastboot reboot. After reboot hold down volume button and enter recovery as usual. Should work then. My explanation is above. It's the install_recovery.sh file fastboot -w takes care of it! Sorry for bumping and old thread. But it doesn't look like it ever got solved.
Code:
C:\>C:/android/fastboot.exe erase recovery
erasing 'recovery'... OKAY [ 0.733s]
finished. total time: 0.734s
C:\>C:/android/fastboot.exe -w
erasing 'userdata'... OKAY [ 5.480s]
erasing 'cache'... OKAY [ 2.052s]
finished. total time: 7.533s
C:\>C:/android/fastboot.exe flash recovery C:/recoverytwrp.img
sending 'recovery' (4410 KB)... OKAY [ 0.491s]
writing 'recovery'... OKAY [ 0.255s]
finished. total time: 0.746s
C:\>C:/android/fastboot.exe reboot
rebooting...
finished. total time: 0.001s

Format partitions in fastboot mode

Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply
Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium
LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.
Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..
LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:

Recovering an Acer A200 and sharing

Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
A200 dead
gabriel_agm said:
Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
Click to expand...
Click to collapse
Could you list the steps you took for the last successful attempt?
I tried all method but stuck at recovery.
Also does following;
"fastboot flash:raw boot boot.img-kernel boot.img-ramdisk.gz
fastboot flash recovery recovery.img"
unable to recover stock.
My bootloader is unlocked
Before Rooting ROM:
Kernel version: 2.6.39.4+
Image version : Acer_AV041_A200_RV10RC02_WW_GEN1
Build No. : Acer_AV041_A200_1.076.00_WW_GEN1

Fastboot failing

Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.
Terrarist said:
Running fastboot on my HOX and getting this result:
Code:
C:\Users\Michael\Documents\Handheld\Android\fastboot>fastboot format system
formatting 'system' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.143s
Same happens with data and userdata.
Click to expand...
Click to collapse
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery
Thant said:
Ofcorse will fail no comanf fastboot format system only fastboot flash recovery recovery.img and for the boot fastboot flash boot boot.img, fastboot erase cache and some minnor commands if you want to format system do it from custom recovery
Click to expand...
Click to collapse
This is a big problem. I've got the burnt out IC that blacks out the screen so unless I connect to a monitor I can't see anything. And I have a working MHL cable but it doesn't work in recovery or bootloader mode. Sweating profusely now

Categories

Resources