Database Users

[Q] Issues during Flashing - possibly bricked

Hi, hope this is the right place to post this.
So my Nexus 7 (2012) was stuck in a boot loop, Google logo followed the little splash thing and repeat wihtout actually loading up. All I could open was the fast boot menu and the four options: wipe data/clear cache etc. I downloaded the relevant drivers, Android SDK, the factory image etc.
I was following these instructions to unlock the bootloader so I could flash the tablet:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This all worked fine.
fastboot oem unlock was typed next and the bootloader unlocked fine.
I then went to typed **fastboot flash bootloader bootloader-grouper-4.23.img**. Apparently what's meant to happen is:
sending 'bootloader' <2100KB>...
OKAY [ 0.123s]
writing 'bootloader' ...
OKAY [ 9.876s]
finished. total time: 9.999s
However mine just got stuck at the "writing 'bootloader' ..." stage. It was like this for quite a few minutes when it's supposedly meant to take a few seconds. "Signature match" showed up in the top left corner of the tablet however it is unresponsive, you can't move the buttons to show the Recovery mode/Power Off options.
I foolishly closed the command window and opened a new one. I tried to do the next stage "fastboot reboot-bootloader" however it just says "FAILED (command write failed (unknown error))" You get basically the same for all the other commands either unknown error. If you try to flash the bootloader again it fails and says invalid argument. My tablet was still recognised by the PC, showing the fastboot screen with Start in the top right and signature match in the top left. However any other prompts would fail. Eventually I unplugged the tablet and was able to turn it off with the power button.
Previously I had had trouble opening the fastboot menu or even getting to load to the boot loop (not responding to the button presses very well) however so far the display hasn't powered on at all. The only response you get is when it's plugged in you hear to device connected and disconnected sounds, and it is recognised as APX in the Windows device manager.
So what should I do? Is it fully bricked? My tablet is out of the 1 year warranty (This probably voided it anyway). Greatly appreciate any help anyone can give me

Normally flashing of a bootloader with a signature mismatch should not work, there are some protections build in, so I see two possible situations for you:
Either you are stucked in APX-mode, but the old bootloader is still working: in that case hold down the power button for at least 20 seconds to turn it off completely and then try to restart the tablet again
or flashing of the bootloader started, but failed during writing the new image. In that case the probability that you have a brick is very high ...

Flashing Help - Mismatching image and device

Hi All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html

[solved]Bootloader and Baseband versions are blank

So my phone booted into the stock recovery (no TWRP installed) when I accidentally selected the wrong update method in magisk. It kept on rebooting to the recovery even after selecting reboot device and tried clearing cache. Even after that it booted back to the recovery. Then I turned off the phone. And now when the phone turns on it goes to bootloader even after selecting recovery mode. And in the bootloader "Bootloader Version" and "Baseband Version" are blank. This is what it shows;
Fastboot Mode
PRODUNT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - "Serial number available"
SECURE BOOT - yes
DEVICE STATE - unlocked
PC doesn't recognize it either.
Under device manager it says "Unknown USB Device (Device Descriptor Request Failed)
I'm having 6T 6GB RAM (International)
Bootloader unlocked
Any idea as to why this happens and how to solve it?
Thanks

PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader

dushan90 said:
PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader
Click to expand...
Click to collapse
Use MSM Tool to recover the device. That's the easiest option.

Does it wipes the device?
Also I was on 9.0.13. And I could find only MSM Tool 9.0.12.

Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.

dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
Beast mode nice job and thanks for sharing your fix
Sent from my [device_name] using XDA-Developers Legacy app

I have the same issue..
Is it possible to restore the baseband version by entering this commands?
In my situation, I already wiped and boot into the system.

dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
I get this error by trying your solution:
```$ sudo fastboot --set-active=b
error: Device does not support slots.```
```$ sudo fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Also tried the other option without better results:
```$ sudo fastboot --set-active=a
error: Device does not support slots.```
```$ sudo fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Maybe it's because I'm using OnePlus 6 instead 6T?

how was this fixed?

Fastboot stuck at 'sending'

Running the command (on Linux)
Bash:
~/platform-tools/fastboot flash recovery recovery.img
I get:
Code:
Sending 'recovery' (21101 KB)
...and that's it. Fastboot hangs indefinitely, seemingly not sending anything, and can only be killed by unplugging the USB. The phone says "FASTBOOT MODE" in green. I've tried all 3 USB ports on my laptop, the paths and filenames are correct, i've tried a lot and using both twrp and LineageOS recovery images, but I never get beyond this, except for getting an error sometimes, "FAILED (Write to device failed (Protocol error))", "FAILED (remote: 'unknown command')", or "FAILED (Write to device failed in SendBuffer() (Protocol error))", which turns into this after rebooting fastboot mode or trying again. What am I missing? I've unlocked the bootloader with the app, I'm trying to install a recovery to install LineageOS.
Edit: Doesn't seem like there's a solution, but I tried another computer and it worked. Annoying how buggy it is, but there.

How to revive a moto harpia phone that has Failed to pass validaton, backup to fastboot?

I have a motorola g4 play (HARPIA) phone, with the latest lineageos version available to ir, it was not used by several months and when turned on it lasted a couple of minutes at the initial screen (the blank one that says the phone is unlocked) and then battery died (my bad)
And now the phone fails at all when starting... it shows an error
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
I have adb & fastboot installed (it is a linux machine), adb do not see the device at all... using fastboot I have tried to flash recovery img file and it shows:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending ' recovery' (14526 KB) OKAY 0.876 s
Writing 'recovery' OKAY 0.188 s
Finished. Total time 1.423 s
Then tried to go to recovery mode and it fails...:
failed to validate recovery image
ERROR: Failed to pass to pass validaton, backup to fastboot
Boot up failed
Any idea? What to check? what to do? what to try? D-:

A very LONG time ago I have used a windows application, that flashed motorola factory rom files... someone remembers the name? and where to find those factory roms?

At first get Google's up-to-date ADB and fastboot for Linux.
Then get the latest TWRP recovery for harpia.
Then boot yout device to bootloader mode.
Now try the boot-option within fastboot:
--> fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.