Hello,
Many many many moons ago i decided to try install LineageOS on my old pixel c, then the world when weird and the tablet has lived in a drawer, today it came out and i can't remember where i got up to so looking for guidance before i kill it.
This is what i do know:-
1. Doesn't have an OS as it won't boot properly
2. Get to a recovery menu but trying to boot to "Android recovery" doesn't work (just reboots)
3. Message in the recovery menu states "OS on your tablet is damaged. Needs Recovery" this is along side the Product name, Hardware Version, Bootloader Version and Lock State.
And advice on where to start very much appreciated.
I took another punt at this, tablet is "waiting for fastboot command...." from my mac when attempting to write the recovery image using the following: ./fastboot flash recovery twrp-3.7.0_9-1-dragon.img from my Mac i hit the following error:-
Sending 'recovery' OKAY
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: command failed
./fastboot oem unlock says it is unlocked already
Related
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
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.
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
Hi guys,
Quick backstory: I've got a Pixel XL 3, I sold my Pixel XL on eBay with a description like "PIxel XL, bootlocker unlocked, rooted and blah blah". The user has returned the phone to me claiming it is not working. I've received the device and sure enough it's in some sort of bootloop (although this was definitely not how I sent it to him). This post is not to rant about how I've been shafted by the buyer although I am still furious because I now have a phone which I hope is not actually bricked. (and I know I'd never win a dispute process cause I cannot prove the phone was in a working state when I sent it).
To cut to the chase:
The phone boot loops - it shows the "G" on the white background for less than a second, then reboots, after 2 seconds, it comes back up with the "G" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED" - which is definitely NOT how I previously had the phone.
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way?
wizzkidd said:
Hi guys,
Quick backstory: I've got a Pixel XL 3, I sold my Pixel XL on eBay with a description like "PIxel XL, bootlocker unlocked, rooted and blah blah". The user has returned the phone to me claiming it is not working. I've received the device and sure enough it's in some sort of bootloop (although this was definitely not how I sent it to him). This post is not to rant about how I've been shafted by the buyer although I am still furious because I now have a phone which I hope is not actually bricked. (and I know I'd never win a dispute process cause I cannot prove the phone was in a working state when I sent it).
To cut to the chase:
The phone boot loops - it shows the "G" on the white background for less than a second, then reboots, after 2 seconds, it comes back up with the "G" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED" - which is definitely NOT how I previously had the phone.
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way?
Click to expand...
Click to collapse
If you can boot fastboot mode:
This is may work:
- Download the latest SDK Platform-tools (r28.0.3)from here to your computer.
- Download the latest Pixel XL (marlin) Factory Image ( May 2019) to your Computer.
- Install the SDK Platform-tools.
- Extract the Pixel XL (marlin) Factory Image in the Platform-tools folder.
Note: If you have your Pixel 3 XL Factory Image (crosshatch) extracted in the Platform-tools folder. Move the flash-all.bat, flash-all.sh and flash-all.base to another folder before extracting the Pixel XL (marlin) Factory Image to the Platform-tools folder.
- Open a Command prompt in the Platform-tools folder #1 in the guide
- Type flash-all
- If it works, it should boot.
- login to your google account and set up your phone.
[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Then if you purchased you Pixel XL from Google Do #3 to unlock the bootloader.
Thanks Homeboy76 for taking the time to provide a detailed response. However unfortunately this did not work. I tried it already (but with what possibly could have been an older version of the platform tools and older factory image). So I gave it another shot using platform-tools r28.0.3 and the marlin factory image version 9.0.0 (PQ3A.190505.001, May 2019).
The results were the same as my previous attempt. I get several errors on certain commands in the flash-all.bat file. These all provide a error responses complaining about the bootloader, my guess is because it is locked and using flash-all requires an unlocked bootloader. Whereas a side-load is said to work regardless of it being locked, but is only possible via recover (which isn't working for me). For clarity, the out put of flash-all looks like this:
Sending 'bootloader_a' (32424 KB) OKAY [ 0.789s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.016s
Sending 'radio_a' (57156 KB) OKAY [ 1.400s]
Writing 'radio_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.012s
--------------------------------------------
Bootloader Version...: 8996-012001-1812132253
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT69L0203996
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.047s]
Checking 'version-bootloader' OKAY [ 0.047s]
Checking 'version-baseband' FAILED
Device version-baseband is '8996-130181-1811270246'.
Update requires '8996-130281-1903110834'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Random question. How did this guy manage to lock the bootloader when it was unlocked by me using 'dePixel8' a very long time ago. He did question why the phone was starting up with the warning message, and I explained that it's by design because the bootloader is unlocked. I guess he decided to try and "fix" that, and ended up screwing up this phone. Hence sending it back with a fake story.
wizzkidd said:
Thanks Homeboy76 for taking the time to provide a detailed response. However unfortunately this did not work. I tried it already (but with what possibly could have been an older version of the platform tools and older factory image). So I gave it another shot using platform-tools r28.0.3 and the marlin factory image version 9.0.0 (PQ3A.190505.001, May 2019).
The results were the same as my previous attempt. I get several errors on certain commands in the flash-all.bat file. These all provide a error responses complaining about the bootloader, my guess is because it is locked and using flash-all requires an unlocked bootloader. Whereas a side-load is said to work regardless of it being locked, but is only possible via recover (which isn't working for me). For clarity, the out put of flash-all looks like this:
Random question. How did this guy manage to lock the bootloader when it was unlocked by me using 'dePixel8' a very long time ago. He did question why the phone was starting up with the warning message, and I explained that it's by design because the bootloader is unlocked. I guess he decided to try and "fix" that, and ended up screwing up this phone. Hence sending it back with a fake story.
Click to expand...
Click to collapse
Darn CRS ( Can't Remember S#@t) your original post did say the bootloader was locked.
Locking the bootloader is easy but , if he locked the bootloader without returning the phone to 100 percent stock. He most likely bricked the phone.
I had a guy screw up a phone the day he got it. Luckily he admitted to everything and did not try to return.
I bet you can get this guy to admit fault if you try hard enough.
Sent from my SM-P205 using Tapatalk
Did you every find a way to fix the issue? I'm in the EXACT same boat with a Pixel 3 XL stuck in a boot loop. Only thing I can access is Fastboot. My scenario is EXACTLY how you described yours.
So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b