Develop Bugs

Can't launch fastboot after failed encryption

Hello
I built Nugget following Sony's AOSP instructions, flashed TWRP and installed OpenGapps...
After that I attempted to encrypt the phone, it was restarting for about 3 hours and then I think it drained the battery or something.
Now when I try to enter fastboot by pressing power+volume down nothing happens, the system won't recognize it so I can't flash the image again.
Power + volume up I think restarts it, it only vibrates and that's it.
I charged the battery and it went back to the Sony -> Android -> reboot cycle
Any advice on how to fix this?
Thanks in advance
Code:
[ 798.341224] usb 3-6: new high-speed USB device number 24 using xhci_hcd
[ 798.650007] usb 3-6: USB disconnect, device number 24
[ 827.400672] usb 3-6: new high-speed USB device number 25 using xhci_hcd
[ 856.350037] usb 3-6: new high-speed USB device number 26 using xhci_hcd
[ 856.510055] usb 3-6: Device not responding to setup address.
[ 856.713411] usb 3-6: Device not responding to setup address.
[ 856.916721] usb 3-6: device not accepting address 26, error -71
[ 885.026078] usb 3-6: new high-speed USB device number 28 using xhci_hcd
[ 885.186218] usb 3-6: Device not responding to setup address.
[ 885.389449] usb 3-6: Device not responding to setup address.
[ 885.592780] usb 3-6: device not accepting address 28, error -71
[ 914.038788] usb 3-6: new high-speed USB device number 30 using xhci_hcd
[ 942.688160] usb 3-6: new high-speed USB device number 31 using xhci_hcd
[ 942.848283] usb 3-6: Device not responding to setup address.
[ 943.051483] usb 3-6: Device not responding to setup address.

azzamite said:
Hello
I built Nugget following Sony's AOSP instructions, flashed TWRP and installed OpenGapps...
After that I attempted to encrypt the phone, it was restarting for about 3 hours and then I think it drained the battery or something.
Now when I try to enter fastboot by pressing power+volume down nothing happens, the system won't recognize it so I can't flash the image again.
Power + volume up I think restarts it, it only vibrates and that's it.
I charged the battery and it went back to the Sony -> Android -> reboot cycle
Any advice on how to fix this?
Thanks in advance
Code:
[ 798.341224] usb 3-6: new high-speed USB device number 24 using xhci_hcd
[ 798.650007] usb 3-6: USB disconnect, device number 24
[ 827.400672] usb 3-6: new high-speed USB device number 25 using xhci_hcd
[ 856.350037] usb 3-6: new high-speed USB device number 26 using xhci_hcd
[ 856.510055] usb 3-6: Device not responding to setup address.
[ 856.713411] usb 3-6: Device not responding to setup address.
[ 856.916721] usb 3-6: device not accepting address 26, error -71
[ 885.026078] usb 3-6: new high-speed USB device number 28 using xhci_hcd
[ 885.186218] usb 3-6: Device not responding to setup address.
[ 885.389449] usb 3-6: Device not responding to setup address.
[ 885.592780] usb 3-6: device not accepting address 28, error -71
[ 914.038788] usb 3-6: new high-speed USB device number 30 using xhci_hcd
[ 942.688160] usb 3-6: new high-speed USB device number 31 using xhci_hcd
[ 942.848283] usb 3-6: Device not responding to setup address.
[ 943.051483] usb 3-6: Device not responding to setup address.
Click to expand...
Click to collapse
Not familiar with building and development, but I know if there's no battery charge, fastboot won't work. I don't think any flashing activity can break fastboot, but not sure about development stuff...

[solved] Can't launch fastboot after failed encryption
levone1 said:
Not familiar with building and development, but I know if there's no battery charge, fastboot won't work. I don't think any flashing activity can break fastboot, but not sure about development stuff...
Click to expand...
Click to collapse
After many tries, I managed to enter, not very sure how, I think it eventually rebooted into fastboot like magic.

Return LG Nexus 5X to original Google ROM

Hello,
I have an LG Nexus 5X (Bullhead?) running PA 7.3.1-RELEASE (Android 7.1.2). It had PA installed on it when I purchased it from ebay some six months ago.
I really would like to go back to the original Google ROM but am struggling to do this.
I've downloaded SuperSU but when I run it I get "SuperSU SU Binary is occupied" and a "HOW TO SOLVE" button.
Clicking "HOW TO SOLVE" takes me to www supersu dot com faq subinaryoccupied which reassures me that: "Only needs a coffee's time to make it happen" and a Community link and Message Us link. Community Link returns a 502 Bad Gateway response (not very reassuring!), the Message Us link goes to a facebook group (SuperSUofficial). Is this route even worth entertaining? I feel I'm only at the tip of the iceberg in getting my phone returned to factory/OEM status.
Any advise would be most appreciated. (Sorry ,not allowed to post links as I'm under the 10 posts requirement)
Thanks, BloodBaz

Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp, that looks like exactly what I need. I'll give this a go this week and let you know how I get on. Thank you.

Jacquestrapp said:
Follow #10 in this guide, or #11 if you want to retain the contents of the phone's internal storage. You don't need SuperSU for anything.
Click to expand...
Click to collapse
Thanks Jacquestrapp. I'm struggling at the very first step.
Here's where I'm at:
Step 10 (How To Flash The Factory Images (And Return To Stock)) has the prerequsite that I have to unlock bootloader (section 1).
Gone to section 1
Enabled Developer mode (was already enabled)
Enabled OEM unlocking
Enabled USB debugging
Powered off phone
Booted into Bootloader (Power+Volume Down)
Connected phone to PC via USB cable
Opened command prompt, gone to platform tools but as you can see, I'm not connecting here:
Code:
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>fastboot devices
C:\android\platform-tools>adb devices
List of devices attached
00cad250a0599972 device
C:\android\platform-tools>fastboot reboot
< waiting for any device >
My PC is the latest Windows 10 Pro (64-bit).
I have an LG Nexus 5X (Model LGH791).
And I'm guessing I've not got the right drivers installed but I'm struggling to find where to get them (I'm in the UK)
Here's where I've tried:
Attempt 1:
Followed the same guide to "Google USB Driver Install": https://developer.android.com/studio/run/win-usb.html
which takes me to: "Click here to download the Google USB Driver ZIP file (ZIP)" (latest_usb_driver_winodws.zip 8.3MB).
Downloaded, unzipped.
Gone to Device Manager but my phone doesn't appear under "Portable Devices" or anywhere else in device manager.
Attempt 2:
Gone to LG's website, entered model which lead to this page:
https://www.lg.com/uk/support/softw...00008356&subCateId=CT00008358&modelNum=LGH791
(but alas, no software!)
Can anyone advise on how to get the phone and PC to communicate?
Thanks
Chris

You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.

Jacquestrapp said:
You mentioned that your phone has a custom ROM on it (Paranoid Android), which means it almost certainly has an unlocked bootloader. If you reboot the phone, the first thing you see when it reboots should be a message to this effect, advising you to lock the bootloader.
Click to expand...
Click to collapse
Thanks, yes it does! Sorry, I not good at this. So the pre-req for section 10 is already done.
(I'm assuming I will still need to get adb / fastboot working at some point though).
I'll start looking into section 10 now. Thanks.

Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.

Jacquestrapp said:
Are you connecting the phone to the PC through a USB hub? If so, try connecting directly to one of the PC's built-in USB ports. It's been a while since I first set up my PC for adb/fastboot so I'm not sure what to do about the fact that fastboot doesn't show the phone. I think I used the Android SDK manager, and not the ZIP file, to install the USB drivers.
Click to expand...
Click to collapse
No, directly onto USB port on top of PC. Tried both ports on top and a USB 3 port in the back. Still no sign of the phone in Device Manager.
I've got a laptop - I will try that next.
After that I will install the Android SDK manager (although I was hoping to avoid this for a one off job).
Thanks.

Okay, so I *think* my laptop is recognising the phone, however I still don't see the phone under Device Manager > Portable Devices or Device Manager > Other Devices (in fact, neither folder exists on my Laptop in Device Manager). However I have got "Nexus 5X" listed under Device Manager > USB Devices.
I'm now following instructions in section 10 of the guide you have given me:
"Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here (https://developers.google.com/android/nexus/images?hl=en)".
For me this is 8.1.0 (OPM7.181005.003, Oct 2018) under "bullhead" (https://dl.google.com/dl/android/aosp/bullhead-opm7.181005.003-factory-e23fac1c.zip)
I've done the appropriate unzips and copies and I have the following folder set up:
Code:
Volume in drive C has no label.
Volume Serial Number is 1202-7717
Directory of C:\android\images
19/10/2018 22:55 <DIR> .
19/10/2018 22:55 <DIR> ..
01/01/2009 00:00 101 android-info.txt
01/01/2009 00:00 12,068,070 boot.img
21/09/2018 12:04 4,731,396 bootloader-bullhead-bhz31b.img
21/09/2018 12:04 57,989,632 radio-bullhead-m8994f-2.6.41.5.01.img
01/01/2009 00:00 17,847,530 recovery.img
01/01/2009 00:00 2,002,471,632 system.img
01/01/2009 00:00 194,892,768 vendor.img
7 File(s) 2,290,001,129 bytes
2 Dir(s) 136,452,927,488 bytes free
C:\android\images>
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Booting up the phone and disconnecting and connecting the phone a couple of times re-established the device. This time I was able to run adb reboot bootloader but as soon as the phone starts to shut down for the reboot, the connection to the laptop is lost and the laptop shows an error popup (temporarily) (wish I knew how to keep the popup visible but it was something about an error with the USB device).
Q3) Should I select RECOVERY MODE before I can expect the USB connection to reconnect? Documentation just says to go into bootloader (with the menu)
Any more advice is appreciated. Thanks, Chris

BloodBaz said:
The next instruction is to "Boot into the bootloader and connect your phone to your PC via usb cable."
So I shut down my phone then booted it back up again using POWER +VOLUME DOWN buttons to get the screen with the big fat green START option and FASTBOOT mode showing
Connect USB cable to laptop and phone
BUT... now the device isn't showing anymore in Device Manager and running adb devices -l just says "List of devices attached" and nothing underneath!! Grrrrr!
Click to expand...
Click to collapse
That last command should be fastboot devices, not adb devices.
BloodBaz said:
Q1) Should the laptop still be able to communicate with the phone when the phone is booted into the bootloader?
Click to expand...
Click to collapse
Yes, but using fastboot commands, not adb commands. With the phone in bootloader mode (the green screen with the big Start sign), you should see it listed after the fastboot devices command. Here's what I see:
Code:
C:\adb>fastboot devices
00bc94d02c6ab546 fastboot
BloodBaz said:
Q2) Could there be something fundamentally wrong with the phone that is causing it not to be recognised?
Click to expand...
Click to collapse
The phone's type-C port can collect lint, and plugging the connector into the phone compacts the lint. Over time, the lint layer can build up to the point where the connector no longer makes full contact with the port. I don't think that's your problem though.

@Jacquestrapp, thank you for your replies. You've been a life line.
After a couple of hours I think I've now managed to do it. I've tried two laptops, multiple USB ports and two USB cables. Whatever is happening, the PC/Phone connection seems very tempremental and I have to unplug and replug in the USB cable after each reboot. However, as you say, the fastboot commands did work after I figured this out, and from the fastboot screen. Also, whenever the phone rebooted or I disconnected the USB cable, the error message was as per attached screenshot.
So, I ran the following commands:
Code:
C:\android\platform-tools>adb devices -l
List of devices attached
00cad250a0599972 recovery product:omni_bullhead model:Nexus_5X device:bullhead transport_id:5
C:\android\platform-tools>fastboot flash bootloader C:\android\images\bootloader-bullhead-bhz31b.img
< waiting for any device >
Sending 'bootloader' (4620 KB) OKAY [ 0.212s]
Writing 'bootloader' OKAY [ 0.238s]
Finished. Total time: 0.493s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\android\platform-tools>fastboot flash radio C:\android\images\radio-bullhead-m8994f-2.6.41.5.01.img
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 1.633s]
Writing 'radio' OKAY [ 0.543s]
Finished. Total time: 2.300s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.014s
C:\android\platform-tools>fastboot flash boot C:\android\images\boot.img
< waiting for any device >
Sending 'boot' (11785 KB) OKAY [ 0.538s]
Writing 'boot' OKAY [ 0.133s]
Finished. Total time: 0.786s
C:\android\platform-tools>
C:\android\platform-tools>fastboot flash recovery C:\android\images\recovery.img
Sending 'recovery' (17429 KB) OKAY [ 0.545s]
Writing 'recovery' OKAY [ 0.309s]
Finished. Total time: 0.900s
C:\android\platform-tools>fastboot flash system C:\android\images\system.img
Sending sparse 'system' 1/4 (508768 KB) OKAY [ 13.739s]
Writing sparse 'system' 1/4 OKAY [ 9.283s]
Sending sparse 'system' 2/4 (524230 KB) OKAY [ 14.787s]
Writing sparse 'system' 2/4 OKAY [ 8.650s]
Sending sparse 'system' 3/4 (501070 KB) OKAY [ 14.592s]
Writing sparse 'system' 3/4 OKAY [ 12.445s]
Sending sparse 'system' 4/4 (421469 KB) OKAY [ 11.842s]
Writing sparse 'system' 4/4 OKAY [ 16.174s]
Finished. Total time: 112.698s
C:\android\platform-tools>fastboot flash vendor C:\android\images\vendor.img
Sending 'vendor' (190324 KB) OKAY [ 5.424s]
Writing 'vendor' OKAY [ 5.682s]
Finished. Total time: 11.145s
C:\android\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
The pre-google animation too ages and eventually talked about corruption on the filesystem. This is presumably because it had Paranoid Android installed on it previously. So I took the option to wipe everything (I don't have anything precious on the phone that isn't already backed up) and I've got myself back to stock Google and I'm very happy!
Thanks again for your support @Jacquestrapp.
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks

BloodBaz said:
[MENTION=301158]
The only thing I haven't done yet is relock the bootloader.
The guide states this warning:
"Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock"
Now that I am booting up fine in standard Google Android 8.1, is it okay for me to issue the fastboot oem lock command? I'm not going to kill my phone am I? If it's a "yes", then I'll probably leave it a few days before I actually do it.
Thanks
Click to expand...
Click to collapse
You're welcome. I *think* you are OK to re-lock the bootloader, but I've never done it, so I can't say with 100% certainty. Both of the 5Xs in my house have been running custom ROMs since I bought them. Also, if the USB connection is as temperamental as you say, take a toothpick (or something else thin and non-conductive) and poke around gently in the USB port to see if lint is the problem. It probably isn't, but it's easy enough to fix if it is: just dig all the lint out.

Help Help help !!! Deep Cable / Flash Cable Moto Z2 Force

Hi everybody.
As I know that it is possible that someone wants to know why I need a deep cable here is a super summary of my catastrophe:
I made a root in my Z2 Force with the bootloader unlocked (thanks to the number that Motorola gives to do that) and with the SU, after that I knew (not before, damn) that some applications don't work on root cell phones (****) among these my bank app, Netflix app, Fox app (**** **** ****), even using the Root Cloak app and others like that the result is that they don't work, so I needed to return to the unroot state, until there everything manageable, buuuuuuuuut, when I had to flash the stock ROM I downloaded the wrong version (fuuuuuuuck), the result was that the cell phone doesn't recognize the SIM cards, doesn't allow the use of WIFI, my IMEI was lost (wtf!) and when I try to flash again (in fastboot) with the correct ROM stock the bootloader doesn't leave me because it says "Flashing_locked", (what? but if I already unlocked it before !, well no, the ****ing cell phone doesn't recognize that, if I try to unblock it through the fastboot commands give as results that the process was satisfactory, but when restarting the bootloader it says NO, I'm still locked mother****er ! ...........
Well, that's why I need a deep cable, to flash with the (foolish) "Flasing_locked" status. So, the problem is basically that I found on the Internet those who do the deep cable with micro-usb, I haven't found how to do it with a usb-c cable. In the cases with micro-usb you only have to bridge the black and green wires and "ta dah" everything is done, in others I also see in micro-usb the pin 4 is jumpered with pin 1 in the micro-usb connector, but on the usb-c cable I have something like 20 pins and more than 4 cables, so I don't know how I can do the deep cable with a usb-c.
Please, I need help :crying:

I think there is another way to go about this than putting your devices into Qualcomm 9008. That is what you are wanting the EDL Deep Cable for, right? Instead of that, why not try this thread here, https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783, and see if Uzephi's method doesnt get you back to stock. If for some reason his flashall doesnt work, then I would suggest using a blankflash for your version of Android to wipe the slate clean and then use the return to stock method for your device.

fast69mopar said:
I think there is another way to go about this than putting your devices into Qualcomm 9008. That is what you are wanting the EDL Deep Cable for, right? Instead of that, why not try this thread here, https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783, and see if Uzephi's method doesnt get you back to stock. If for some reason his flashall doesnt work, then I would suggest using a blankflash for your version of Android to wipe the slate clean and then use the return to stock method for your device.
Click to expand...
Click to collapse
Okay ! I'm going to try those two options and I'll write you what happens.
Thanks !

Well, I'm here again.
I tried the two methods that you kindly indicated to me:
1. https://forum.xda-developers.com/z2-...print-t3694783 The Flashall.bat file really does not do anything different than being an automated flash of what you can usually do manually, I mean, it does the flash using the fastboot file by file, so because it's the same process (but automated) I got the same result, when the Flashall.bat file tries to send / flash the files the response status is Failed, because the flashing status in the bootloader is locked.
2. Blankflash metod. This method seems to work when the cell phone is bricked and does not enter the bootloader, and that is not my case because I can access the cell phone, for example if I connect the cell phone to the computer in:
a) the boot manager mode, the "Device Manager" recognizes it as "Android Device / Motorola ADB Interface"
b) started the ROM (and activated the "USB Debugging"), the "Device Manager" also recognizes it as "Android Device / Motorola ADB Interface"
c) QCOM mode (selected from the bootloader) the "Device Manager" recognizes it as "Qualcomm HS-USB Diagnostics 9092".
Anyway, if I run the blank-flash file in:
a) bootloader mode, the CMD shows "waiting device" and does nothing
b) started the ROM (and activated the "USB Debugging"), the CMD shows "waiting device" and does nothing
c) QCOM mode (selected from the bootloader), the CMD shows "waiting for the device" and does nothing (this same result with or without the activation of "USB Debugging")
So I'm still the same, I think my only option is Deep Cable, what do you think?

Loperaco said:
Well, I'm here again.
I tried the two methods that you kindly indicated to me:
1. https://forum.xda-developers.com/z2-...print-t3694783 The Flashall.bat file really does not do anything different than being an automated flash of what you can usually do manually, I mean, it does the flash using the fastboot file by file, so because it's the same process (but automated) I got the same result, when the Flashall.bat file tries to send / flash the files the response status is Failed, because the flashing status in the bootloader is locked.
2. Blankflash metod. This method seems to work when the cell phone is bricked and does not enter the bootloader, and that is not my case because I can access the cell phone, for example if I connect the cell phone to the computer in:
a) the boot manager mode, the "Device Manager" recognizes it as "Android Device / Motorola ADB Interface"
b) started the ROM (and activated the "USB Debugging"), the "Device Manager" also recognizes it as "Android Device / Motorola ADB Interface"
c) QCOM mode (selected from the bootloader) the "Device Manager" recognizes it as "Qualcomm HS-USB Diagnostics 9092".
Anyway, if I run the blank-flash file in:
a) bootloader mode, the CMD shows "waiting device" and does nothing
b) started the ROM (and activated the "USB Debugging"), the CMD shows "waiting device" and does nothing
c) QCOM mode (selected from the bootloader), the CMD shows "waiting for the device" and does nothing (this same result with or without the activation of "USB Debugging")
So I'm still the same, I think my only option is Deep Cable, what do you think?
Click to expand...
Click to collapse
To use blankflash you need to be in 9008 mode, since you have adb working try issuing the command 'adb reboot-edl' or 'adb reboot edl' can't recall at the moment. You'll know when you're in edl/9008 mode because the screen will be blank and the device will recognize as 9008. If you can't reboot to edl through adb, go to fastboot and try 'fastboot oem blankflash' again you'll know when you're ready for blankflash because the device will recognize as 9008. If the commands don't take, boot into QCOM mode and try 'fastboot oem blankflash'
*To unlock the bootloader you need to select oem unlock in settings. If it's greyed out you need to connect to internet and sign into google. Try bluetooth connection or a cable since wifi and mobile is borked at the moment.

41rw4lk said:
To use blankflash you need to be in 9008 mode, since you have adb working try issuing the command 'adb reboot-edl' or 'adb reboot edl' can't recall at the moment. You'll know when you're in edl/9008 mode because the screen will be blank and the device will recognize as 9008. If you can't reboot to edl through adb, go to fastboot and try 'fastboot oem blankflash' again you'll know when you're ready for blankflash because the device will recognize as 9008. If the commands don't take, boot into QCOM mode and try 'fastboot oem blankflash'
*To unlock the bootloader you need to select oem unlock in settings. If it's greyed out you need to connect to internet and sign into google. Try bluetooth connection or a cable since wifi and mobile is borked at the moment.
Click to expand...
Click to collapse
Hi.
I have fresh news.
The first thing I tried was to enable the option to unlock the OEM because that option was in gray, try to connect the internet via USB cable and no option worked, but when connecting by bluetooth (which is not easy either for those who don’t know how) I did it! and once connected, I enabled the option again, so I activated it to allow me to unlock the OEM, but when restarting the bootloader to verify it was still showing the status "Flashing_locked" (sad face).
Even knowing this, try the options in this order and with these results:
1. Try the command 'adb reboot-edl' or 'adb reboot edl'. The first command that the console recognized was 'adb reboot -edl' but once accepted by the CMD the cell phone was rebooted alone and went back to the ROM, that is, it was not blank.
2. Go to fastboot and try 'fastboot oem blankflash'. When doing this the result obtained in the CMD was “(bootloader) Command Restricted FAILED (remote failure) finished. total time: 0.006s”, probably due to the fact that the bootloader still indicates "Flashing_locked".
3. Boot into QCOM mode and try 'fastboot oem blankflash'. When I start the QCOM option from the bootloader the cell phone automatically loads the ROM, after this I activated the USB Debugging and ran the command in question but the result was "<waiting for any device>" and nothing happens. I tried the command again without activating the USB Debugging and nothing happened either. If I enter the command "fastboot devices" the command does not give any results, I give way to the next line as if nothing happened.
4. I was sad after all this so I decided to retry everything, starting with the command to put the phone in mode 9008, so, just out of curiosity I tried the second sentence you wrote, that is, 'adb reboot edl' (without the line in the middle before the word “edl”), this command also recognized it but this time if it went to blank (yeah !!!). So after accomplishing this I followed the instructions of https://forum.xda-developers.com/z2-force/help/hard-bricked-blankflash-z2-force-t3705789, but the result when executing the Blank-Flash file was:
[ 0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.005] ...cpu.sn = 3632543294 (0xd884363e)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.012] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.013] Sending programmer
[ 0.091] ReadFile() failed, GetLastError()=0
[ 0.644] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.644] ERROR: sahara_download()->general error
[ 0.644] Check qboot_log.txt for more details
[ 0.645] Total time: 0.646s
[ 0.645]
[ 0.645] qboot version 3.85
[ 0.645]
[ 0.645] DEVICE {
[ 0.645] name = "\\.\COM11",
[ 0.645] flags = "0x64",
[ 0.645] addr = "0x28FD74",
[ 0.645] sahara.current_mode = "0",
[ 0.645] api.buffer = "0x2160020",
[ 0.645] cpu.serial = "3632543294",
[ 0.645] cpu.id = "94",
[ 0.645] cpu.sv_sbl = "0",
[ 0.645] cpu.name = "MSM8998",
[ 0.645] storage.type = "UFS",
[ 0.645] sahara.programmer = "programmer.elf",
[ 0.645] api.bnr = "0x20C7ED0",
[ 0.645] }
[ 0.645]
[ 0.645]
[ 0.645] Backup & Restore {
[ 0.645] num_entries = 0,
[ 0.645] restoring = "false",
[ 0.645] backup_error = "not started",
[ 0.645] restore_error = "not started",
[ 0.645] }
[ 0.645]​When executing the "blank-flash" file again, the result obtained was:
[ 0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 34.005] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.005] Check qboot_log.txt for more details
[ 34.005] Total time: 34.006s
[ 34.005]
[ 34.005] qboot version 3.85
[ 34.005]
[ 34.005] DEVICE {
[ 34.005] name = "\\.\COM11",
[ 34.005] flags = "0x64",
[ 34.005] addr = "0x28FD74",
[ 34.005] api.bnr = "0x612CA8",
[ 34.005] }
[ 34.005]
[ 34.005]
[ 34.005] Backup & Restore {
[ 34.005] num_entries = 0,
[ 34.005] restoring = "false",
[ 34.005] backup_error = "not started",
[ 34.005] restore_error = "not started",
[ 34.005] }
[ 34.005]​I thought I had made a worse mistake, but turning off the cell phone normally returned to enter the ROM without problem.
At this point I was left with no more ideas...

You need drivers so that your pc and the phone can communicate, here is a link and it also has a verified blankflash.zip that has worked many times for others in the past. The process is a bit hit and miss, meaning it can be finicky on some pcs. Make sure you use a usb 2.0 port off the mobo, and not a 3.0+ or a hub port, they're not all so universal and can cause problems, so stick to 2.0 mobo ports.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

41rw4lk said:
You need drivers so that your pc and the phone can communicate, here is a link and it also has a verified blankflash.zip that has worked many times for others in the past. The process is a bit hit and miss, meaning it can be finicky on some pcs. Make sure you use a usb 2.0 port off the mobo, and not a 3.0+ or a hub port, they're not all so universal and can cause problems, so stick to 2.0 mobo ports.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
Hiiiii.
Well, the file in the forum that you gave me works! I mean, it does something new, it generates a successful process and it was reinitiated to the bootloader, once there I noticed that there was a changed item "Software status: Official" (previously said modified), but the ítem of "Flashing_locked" is still the same ...
Anyway I tried to flash the stock ROM with that and I have the same result whenhen I get to the command "fastboot flash bootloader bootloader.img", here are the results:
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.266s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Another new thing found: in "bootloader logs" mode it says:
SSM: abl cvs roll back 0,1
Fastboot Reason: UTAG bootmode configured as fastboot
I feel that I am closer to each step, please continue to help me.

What firmware are you trying to flash? At this point it might be easier to use the lenovo moto smart assistant tool to do a rescue on your phone. Do a 'fastboot reboot bootloader' to get a fresh bootloader session, and run the lmsa tool and see it it will recover your phone. Either way, let me know what firmware you're trying to flash.

First of all, you need to make sure you are xt1789-? ? If x is 3, then he is the s version. You only need to install the rom of the corresponding carrier. I remember that the installation tool can choose whether to install the baseband and bp/bl lock (maybe)So your xt1789-? ? What is it?
Refer to the version number in the link image https://m.facebook.com/story.php?story_fbid=624595458056701&id=100015187571561

41rw4lk said:
What firmware are you trying to flash? At this point it might be easier to use the lenovo moto smart assistant tool to do a rescue on your phone. Do a 'fastboot reboot bootloader' to get a fresh bootloader session, and run the lmsa tool and see it it will recover your phone. Either way, let me know what firmware you're trying to flash.
Click to expand...
Click to collapse
Hi again !
I followed his advice to use the "lenovo moto smart assistant tool" but as a result I got that my device isn't supported by the software (see attached image).
On the other hand, regarding the firmware that I'm trying to recover, I don't know if I remembered that I told him to install a wrong ROM at the beginning of my problem, and I never backed up my original ROM, so I do not really have the least idea of ​​what is my stock ROM (for Colombia - South America), if I search for firmware I find many categorized with letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW) ... investigate how I can know which was the original of my phone (after having made a mess) and can not find any reference in this regard.
I keep trying.

潇霄小云 said:
First of all, you need to make sure you are xt1789-? ? If x is 3, then he is the s version. You only need to install the rom of the corresponding carrier. I remember that the installation tool can choose whether to install the baseband and bp/bl lock (maybe)So your xt1789-? ? What is it?
Refer to the version number in the link image https://m.facebook.com/story.php?story_fbid=624595458056701&id=100015187571561
Click to expand...
Click to collapse
Hi 潇 霄 小云!
I am sure it is an XT1789-05 however I do not know which firmware corresponds to me (never look before deleting my stock ROM) and when looking for the firmware of my device there are many with many letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW), so I do not know which one corresponds to me for Colombia (South America).
You can not see my model in the image you send me ...
Thanks for the help, I'm still investigating!

Loperaco said:
Hi again !
I followed his advice to use the "lenovo moto smart assistant tool" but as a result I got that my device isn't supported by the software (see attached image).
On the other hand, regarding the firmware that I'm trying to recover, I don't know if I remembered that I told him to install a wrong ROM at the beginning of my problem, and I never backed up my original ROM, so I do not really have the least idea of ​​what is my stock ROM (for Colombia - South America), if I search for firmware I find many categorized with letters at the beginning (AMXBR, AMXCO, AMXLA, AMXMX, ATT, ATTM, LRA, OPENMX, RETAIL, RETAPAC, RETBR, RETCN, RETEU, RETIN, RETLA, RETRU , SPRINT, TEFBR, TIMBR, TIMIT, TMO, USC, VFEU, VZW) ... investigate how I can know which was the original of my phone (after having made a mess) and can not find any reference in this regard.
I keep trying.
Click to expand...
Click to collapse
Well your device is showing -05, that's Mexico and South America I believe. There should be a model printed by the charge port on the phone. As for which firmware, look at your sim and see if you can get an idea from there, or if you can ask whomever you got your phone from. Do you remember what provider was listed under the software update channel originally? Your sim should be able to get you some info as to who the provider is even if it's just a subsidy of a major carrier.

Hi there !
Well today I have very good news!
At last I managed to reinstall everything. How it happened? So I went back to the steps in this way:
1. Having a wrong ROM version (it does not correspond to my stock) connect by bluethooth the cell phone to access the internet, so the cell phone recognized that the OEM had already been authorized and allowed me to access the option and change it (because before it was gray).
2. Go to the bootloader and find the indication "Flashing_locked", but as I knew I had already given the authorization from within the ROM I opened a console and wrote the command "fastboot oem unlock" AND RECOGNIZED IT!, Restart the bootloader and voila! the message already said "Flashing_unlocked"
3. After this it was a matter of trying (without lying) something like six firmware XT1789-05 version because I had no idea what mine was, it took me a long time because some left me without Wi-Fi again, but Finally, I managed to locate one that looked like the one I had (RETLA XT1789-05_NASH_RETLA_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml), so I tried hard there, but still shows a warning that a version is installed of the different operating system, but it works for me and that's how it will stay for a couple of months.
4. Then I was able to install the TWRP and the Magisk without any problems.
5. Problems that I had: Warning of the bootloader without blocking, Notice of the different operating system, Application of finding my device does not work (it stays looking for the cell phone and never locates it).
Many thanks to 41rw4lk, without your help this would have been impossible.
I hope to share my experience with someone else who may have my problem or something like it!
Postscript: Finally, they never gave me instructions on how to make the Deep Cable when the cell phone is a USB-C type port (lol), so if the data appears I would still be interested only in general knowledge.

System has been destroyed

I had unlocked bootloader but system has been destroyed !
I took endless time...
after restar system is still destroyed,
I can run fastboot and edl
Fastboot now recognize device, bot cant flash recovery. Error device is locked now.
How can I resolve it?

centrored said:
I had unlocked bootloader but system has been destroyed !
I took endless time...
after restar system is still destroyed,
I can run fastboot and edl
Fastboot now recognize device, bot cant flash recovery. Error device is locked now.
How can I resolve it?
Click to expand...
Click to collapse
theres 2 way. 1 is using vmbeta.img wich i dont know as ihavent done but have read about it. if you can enter fastboot screen download stock miui fastboot rom its like 3gb. and miflash tools and flash. happened to me once.

centrored said:
I had unlocked bootloader but system has been destroyed !
I took endless time...
after restar system is still destroyed,
I can run fastboot and edl
Fastboot now recognize device, bot cant flash recovery. Error device is locked now.
How can I resolve it?
Click to expand...
Click to collapse
The easiest way is to flash vbmeta using this command "fastboot flash vbmeta vbmeta.img". This has to be done from PC of course.

kostas gp said:
The easiest way is to flash vbmeta using this command "fastboot flash vbmeta vbmeta.img". This has to be done from PC of course.
Click to expand...
Click to collapse
Thanks.
Has worked!

HI
pleas hilp me
D:\REDMI NOTE8\platform-tools_r29.0.6-windows\platform-tools>fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
D:\REDMI NOTE8\platform-tools_r29.0.6-windows\platform-tools>

shrawi said:
HI
pleas hilp me
D:\REDMI NOTE8\platform-tools_r29.0.6-windows\platform-tools>fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
D:\REDMI NOTE8\platform-tools_r29.0.6-windows\platform-tools>
Click to expand...
Click to collapse
seems like your bootloader is locked...with locked bootloader you can't flash anything

how to unlock bootloader disable OEM-Unlock in developer settings?

shrawi said:
how to unlock bootloader disable OEM-Unlock in developer settings?
Click to expand...
Click to collapse
check this thread to see how to unlock bootloader.

FAILED (remote: Error flashing partition : Write Protected)
the_weird_aquarian said:
check this thread to see how to unlock bootloader.
Click to expand...
Click to collapse
i got this error while flash
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41604 KB)...
OKAY [ 1.761s]
writing 'recovery'...
FAILED (remote: Error flashing partition : Write Protected)
finished. total time: 1.850s
https://prntscr.com/u7wow6

Device can't detected by PC (not shown on device manager)
Guys, i'm so confused right now, my device system has been destroyed, when i about to flash vbmeta.img through fastboot, my PC can't detect any device when i plug my USB to device from my computer, like there isn't any device pluged on it, pls help me, is there any solution? Is the problem on redmi note 8 USB port? If yes, why when device condition is off, then i plug USB on it, it'll turn on, so what's the problem? And how to solve it?

Anthrofax said:
Guys, i'm so confused right now, my device system has been destroyed, when i about to flash vbmeta.img through fastboot, my PC can't detect any device when i plug my USB to device from my computer, like there isn't any device pluged on it, pls help me, is there any solution? Is the problem on redmi note 8 USB port? If yes, why when device condition is off, then i plug USB on it, it'll turn on, so what's the problem? And how to solve it?
Click to expand...
Click to collapse
maybe device drivers not installed properly

Anthrofax said:
Guys, i'm so confused right now, my device system has been destroyed, when i about to flash vbmeta.img through fastboot, my PC can't detect any device when i plug my USB to device from my computer, like there isn't any device pluged on it, pls help me, is there any solution? Is the problem on redmi note 8 USB port? If yes, why when device condition is off, then i plug USB on it, it'll turn on, so what's the problem? And how to solve it?
Click to expand...
Click to collapse
use this one may help you
https://forum.xda-developers.com/google-nexus-5/help/unlocking-bootloader-usb-debugging-t3761785
or
https://support.google.com/pixelphone/thread/17016500?hl=en
---------- Post added at 07:38 AM ---------- Previous post was at 07:33 AM ----------
tamil1996 said:
i got this error while flash
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41604 KB)...
OKAY [ 1.761s]
writing 'recovery'...
FAILED (remote: Error flashing partition : Write Protected)
finished. total time: 1.850s
https://prntscr.com/u7wow6
Click to expand...
Click to collapse
did u install all rquired ADB files in PC and your Phone's Drivers

Redmi 4A abdal said:
maybe device drivers not installed properly
Click to expand...
Click to collapse
No bro, i usually plug several phones to my computer, even i don't install the driver yet, my computer still shows a sound of notification about something pluged into my computer (even if it's failed to install), and android device Will be shown on device manager, but on my Case, there isn't any sound everytime i plug the phone and there isn't any device shown on device manager

Anthrofax said:
No bro, i usually plug several phones to my computer, even i don't install the driver yet, my computer still shows a sound of notification about something pluged into my computer (even if it's failed to install), and android device Will be shown on device manager, but on my Case, there isn't any sound everytime i plug the phone and there isn't any device shown on device manager
Click to expand...
Click to collapse
maybe this helps, run fastboot, go to adb folder open command window type "fastboot devices" if your device ID shows up or not ,
if not reinstall adb drivers,
, also check your data cable

Redmi 4A abdal said:
maybe this helps, run fastboot, go to adb folder open command window type "fastboot devices" if your device ID shows up or not ,
if not reinstall adb drivers,
, also check your data cable
Click to expand...
Click to collapse
No, it's not showed, and it's not possible if my data cable is broken, i already plug my data cable on my other phones too, and there's sound of notification about something plugged into my computer, but my redmi note 8, nothing

Anthrofax said:
No, it's not showed, and it's not possible if my data cable is broken, i already plug my data cable on my other phones too, and there's sound of notification about something plugged into my computer, but my redmi note 8, nothing
Click to expand...
Click to collapse
did you try clean flash in mi flash tool,
your other phone was on fastboot mode when you check it as a fastboot device ?
did you tried reinstalling adb drivers or trying on another computer

TWRP VBMETA GINKGO REDMI NOTE 8 - the system has been destroyed
TWRP VBMETA GINKGO REDMI NOTE 8 - the system has been destroyed
www.idhenovian.com

Anthrofax said:
No, it's not showed, and it's not possible if my data cable is broken, i already plug my data cable on my other phones too, and there's sound of notification about something plugged into my computer, but my redmi note 8, nothing
Click to expand...
Click to collapse
disable drive signature, then flash by mi flash tools. or disable drive signature then correctly unlock your phon by miunlocker and flash recovery

If you have bricked device who bootloop on "system has been destroyer ..." With Locked bootloader....and you Can accès to recovery ... Try this ......... Xiaomitoolv2 , connect to your account , put phone on mi assistant "recovery" you will see "sideload" (not fastboot )and click yes lot If Time in application ... I Hop i'm the first man who find this trick
Share Edit Flag

Solved without edl or other stuff lol

Fire TV 1 bricked (bootloader unlocked)

I tried an software update to the newst prerooted image from rbox but unfortunatelly installed Magisk V20 directly after it (without reboot).
After reboot my Fire TV 1 stopps now at the first white Amazon logo.
Fastboot via USB-A-to-A is working
dḿesg shows the follwing:
[10671.732229] usb 1-2: new high-speed USB device number 44 using xhci_hcd
[10671.887334] usb 1-2: New USB device found, idVendor=1949, idProduct=0401
[10671.887339] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10671.887343] usb 1-2: Product: FireTV
[10671.887346] usb 1-2: Manufacturer: Lab126
[10671.887348] usb 1-2: SerialNumber: xxxxxxxxxxxx
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
This is strange since I unlocked the bootloader years ago.
Is there hope for my Fire TV 1 or did I finally brick it?
Update:
"fastboot getvar unlocked" gives me:
"unlocked: "

veeroohre said:
This is strange since I unlocked the bootloader years ago
Click to expand...
Click to collapse
Magisk won't work on the first fireTV
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.

Sus_i said:
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.
Click to expand...
Click to collapse
Would love to do that, but as mentioned I get the error message "flashing not allowed for locked hw".
I read that sometimes fastboot is the problem and not the hardware. Could that be? I'm on Ubuntu LTS 18.04.

You need to reflash the boot. Extract the boot_unlocked.img from bueller-5.2.7.3-rooted_r1.zip and flash it from the command line when you have the FireTV connected with the USB A-A cable.
fastboot flash boot boot_unlocked.img
EDIT: Here's my thread about it: https://forum.xda-developers.com/fire-tv/help/warning-attempting-to-flassh-magisk-16-t3778096

Sizzlechest said:
fastboot flash boot boot_unlocked.img
Click to expand...
Click to collapse
As I wrote, unfortunately this does not work:
< waiting for any device >
target reported max download size of 805306368 bytes
sending 'boot' (6460 KB)...
OKAY [ 0.206s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.217s
Any other ideas?
Update:
Under Windows "fastboot devices" is not listing anything.

veeroohre said:
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
Click to expand...
Click to collapse
Maybe try 'fastboot boot recovery.img' instead of a flash.
veeroohre said:
Any other ideas?
Click to expand...
Click to collapse
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
If yes, you may be able to follow this Guide.
Take a look here too.

Sus_i said:
Maybe try 'fastboot boot recovery.img' instead of a flash.
Click to expand...
Click to collapse
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
Sus_i said:
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
Click to expand...
Click to collapse
With "fdisk -l" no partition shows up.
I think my box is dead :crying:

veeroohre said:
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
With "fdisk -l" no partition shows up.
I think my box is dead :crying:
Click to expand...
Click to collapse
It seems so.
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill

Sus_i said:
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill
Click to expand...
Click to collapse
You're right. I thought about it, too. But too expensive and time consuming for such an old device. Probably I'll buy a new one. Although I hate to dump hardware which in principle still works .