Database Users

[Q] Nexus 10 Hard bricked

Hi all,
My Nexus 10 seems to be hard bricked.
Here the symptoms:
- Can sometimes be put in bootloader mode
- In bootloader mode, no way to put into recovery mode (the buttons vol up/down do not change the mode = it stays onlw in "Start")
- In bootloader mode, fastboot does not show the device (and of course no way to flash)
- Of course, no OS installed and no way to boot properly
The device seems to be recognized as "Samsung Gadget Serial"..
Any help is welcome !
Thanks
OK FORGET ABOUT IT
I found how to put in recovery mode : press power and BOTH volume UP and DOWN at the same time.

opolette said:
Hi all,
My Nexus 10 seems to be hard bricked.
Here the symptoms:
- Can sometimes be put in bootloader mode
- In bootloader mode, no way to put into recovery mode (the buttons vol up/down do not change the mode = it stays onlw in "Start")
- In bootloader mode, fastboot does not show the device (and of course no way to flash)
- Of course, no OS installed and no way to boot properly
The device seems to be recognized as "Samsung Gadget Serial"..
Any help is welcome !
Thanks
OK FORGET ABOUT IT
I found how to put in recovery mode : press power and BOTH volume UP and DOWN at the same time.
Click to expand...
Click to collapse
Seems an hw problem...

attempted downgrade to kitkat failed -flash-all.bat unable to find boot.img
roscio1975 said:
Seems an hw problem...
Click to expand...
Click to collapse
Hi Guys,
I'm a newb to XDA-developers.
I'll start from the beginning. downloaded image of kitkat from developers.google.com. and abd tools. Typed the fastboot oem unlock in the cmd line and wiped the cache and date/factory reset.
following this I then restarted the tablet and ran flash-all.bat.
On doing this the following was stated in the cmd line:
erasing "recovery"
OKAY
******Did you mean to fastboot format this partition?
erasing 'system'...
OKAY
******Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY
sending 'bootloader'...
OKAY
writing 'bootloader'...
OKAY
rebooting into bootloader...
OKAY
(at this point the tablet restarts)
<waiting for device>
error: update package missing boot.img
I am now left with it continually with the droid on its back no matter what option I select apart from power off.
If it helps, here's the device info
Product name: manta
Variant: wifi
H/W VERSION: 8
BOOTLOADER VERSION: 8
CARRIER INFO: NONE
SERIAL NUMBER: iT STATES IT
LOCK STATE: UNLOCK
REBOOT MODE FLAG: NONE
Its the none that really worries me
Please help!!!!!
Thanks

Moto G4 XT1621 After 7.0 update

Hi, yesterday I decided to flash my Moto g4 xt1621 I put a rom of 7.1.2 and I did not work some things and I decided to put a stock rom of 6.0, I appeared a poster of software update to 7.0 and I gave it yes, I left it updating and never started again.
Try fastboot mode, with usb, charging, with the button on 10 minutes, but nothing turns on the screen, the only thing the phone does when connecting to the charger is the charging LED that turns on and off. The phone has 2 months , no computer recognizes the device.
I know that when I put a non-original rom I lost the warranty.
Upgrade.
After researching a lot, now my computer recognizes the device as two devices.
"Unknown USB device (link in compliance mode) and Fastboot athene_13mp S"
I managed to make it even though the phone boot, but it does not let me do anything in fastboot. (I do not see the rare android logo), and I get these messages:
Start Up Failed: Your device did not startup successfully.
Use the software repair assistant on computer
to repair your device.
Connect your device to you computer to get
the Software Repair Assitant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No boot imge found. Skip to fastboot
Boot up failed
ERROR: No boot imge found. Skip to fastboot
Boot up failed
ERROR: No boot imge found. Skip to fastboot
Boot up failed
USB Connected
Try putting the boot.img of the stock rom rom that I put and it will not let me either:
"downloading 'boot.img' ...
OKAY [0.533s]
booting
FAILED (remote failure)
finished. total time: 0
new edit: no have imei/meid and "sku"
"

Phone stuck on Essential Logo (Powered by Android) screen while trying Oreo B2 OTA

I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.

Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.

Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk

You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.

I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?

You could try: (you will lose all your data)
fastboot -w
fastboot reboot

ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..

update im still stuckk

Have you tried booting to bootloader and mounting /system?

This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.

I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything

Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay

Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???

[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?

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance

you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417

alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.

if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673

you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload

Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.

what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios

alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...

OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.

faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.