Develop Bugs

[Q] Stuck unable to get into recovery from hboot

Everyone here is awesome.
first off.. I have
hboot0.83.0001
radio-5.09.00.20
I'm stuck at hboot can't get into recovery. I've searched all the possibilities and tried all of them so far. I'm either stuck at black screen or white HTC screen, sometimes with black bar across top sometimes not. I've tried the blind button pusshing and I don't have a gold card made.. so those didn't work. Even had help from a senior member, who was amazing help, just lacked experience with this phone.
We were thinking that we could push recovery from ADB but couldn't get the command lines to work.
Tried these lines so far..
" fastboot flash recovery recovery-clockwork-2.5.0.1-bravo-slcd.img "
resulted in this error
sending 'recovery' (4230 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.000s
so we tried this line
fastboot boot recovery recovery-clockwork-2.5.0.1-bravo-slcd.img
and then
fastboot boot recovery-clockwork-2.5.0.1-bravo-slcd.img
which resulted in
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
could someone give me command lines to push recovery to the phone?
Or if needed an alternate out.. probably using ADB me thinks

as a side note, yes I've searched and yes I've tried other things. But none of the answers work. For some reason ADB doesn't recognize my device as being there, but when I search through fastboot it does... just get those error messages. Hoping a genius sees this and knows the issue

Toolkit Rooting Question FAILInvalid Command"

I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick

put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058

I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.

is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img

It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.

waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2

I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?

crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.

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

Pixel 2 XL flashing stock images, target didn't report max-download-size

Hey everybody.
So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0). Running Android P beta p2.
I wanted to simply restore the phone to it's stock state. Main idea was to get OS reinstalled and stock recovery flashed over TWRP.
When ever I tried to flash the boot.img from the stock image in fastboot I got the error saying "FAILED (remote: Requested download size is more than max allowed".
So mid process I read somewhere I might have to unlock unlock_critical. I tried running that but no response from the phone. I didn't want to interrupt so I left it running for a few minutes, came back and nothing has changed. Except for the phone not being able to boot to Android. And so here I am stuck in a boot loop.
So I read here: https://forum.xda-developers.com/pixel-2-xl/help/hard-bricked-t3770769
And realized maybe I should try this skipsoft toolkit. Well no luck.
This is what I get when I try to use option 9. (Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]). I choose to flash the whole ROM.
Here is what I got.
Starting Flash Process..
Flashing Bootloader Image..
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Hold the Power and Volume Down buttons until it reboots to Fastboot Mode.
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
Press any key to return to the Main Menu..
I gave Deuces Bootloop tool script a try and this is what I got:
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
File Not Found
File Not Found
fastboot: error: Device does not support slots
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _b does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
Slot _a does not exist. supported slots are:
a
b
fastboot: error: Device does not support slots
fastboot: error: cannot load 'abl.img': No such file or directory
fastboot: error: cannot load 'aes.img': No such file or directory
fastboot: error: cannot load 'apdp.img': No such file or directory
fastboot: error: cannot load 'boot.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'cmnlib64.img': No such file or directory
fastboot: error: cannot load 'devcfg.img': No such file or directory
fastboot: error: cannot load 'dtbo.img': No such file or directory
fastboot: error: cannot load 'hyp.img': No such file or directory
fastboot: error: cannot load 'keymaster.img': No such file or directory
fastboot: error: cannot load 'laf.img': No such file or directory
fastboot: error: Failed to identify current slot
fastboot: error: cannot load 'msadp.img': No such file or directory
fastboot: error: cannot load 'pmic.img': No such file or directory
fastboot: error: cannot load 'rpm.img': No such file or directory
fastboot: error: cannot load 'tz.img': No such file or directory
fastboot: error: cannot load 'vbmeta.img': No such file or directory
fastboot: error: cannot load 'vendor.img': No such file or directory
fastboot: error: cannot load 'xbl.img': No such file or directory
Flashing System A
fastboot: error: cannot load 'system.img': No such file or directory
Flashing System B
fastboot: error: cannot load 'system_other.img': No such file or directory
fastboot: error: Device does not support slots
Setting current slot to 'b' FAILED (status read failed (Too many links))
Finished. Total time: 5.871s
< waiting for any device >
Any help would be greatly appreciated.
Thank you in advance.

jan_ruc said:
Hey everybody. So I had my phone rooted for a week now, but I had plenty of problems with root (Magisk 16.4, TWRP 3.2.1.0)...
Click to expand...
Click to collapse
I don't have this device but, your best bet is probably to post this question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3702418
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

HELP! Pixel 2 XL may be bricked

Long story short, I attempted to flash the first 9.0.0 factory image and now my phone is seemingly bricked. I keep getting errors that say that fastboot can't detect the current slot. When I try to manually select the slot with --set-active=a/b it returns with my device doesn't support slots. If I try to flash anything individually like the bootloader/radio cmd/powershell just sits there with the "_" underscore blinking for all eternity. TWRP is already flashed and when I try to boot to it it sits on the splash screen indefinitely. I can't fastboot boot TWRP either because I can't flash anything. Deuce's script did the same thing. I tried 3 different cables and am using a brand new computer and latest Platform Tools.
Should I contact google for a warranty replacement? I don't have the order # but that should be irrelevant I think since this phone is still under a year old.
Any ideas????
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
Update: I installed Android Studio and subsequently, the USB drivers from the SDK manager and somehow I got the phone to boot again. I still cannot flash anything though, I still get the "unable to identify current slot error above.

I hate the the windows Powershell. I always open a command window and work from that.
Make sure you have the most current drivers, and that USB debugging is turned on.
From the horror stories I've read, i always always always do an adb or fastboot devices before i do anything.
If you flash a factory image, don't unzip the file inside the factory image. The flash all.bat file expects that zip to be there.
I've also gotten into the habit of booting the phone that has just been flashed before I root it.
Have you wiped the cache's? Done a reset?
Just throwing things out there...
Good luck I hope you get it all sorted out.