Fastboot commands not working - Essential Phone Questions & Answers
I am having an irritating issue with my Essential PH-1 and Arch. I can issue adb commands without any issue, both booted into the system as well as in recovery (TWRP) - adb devices lists it as a device or in recovery correctly, I can reboot the device into bootloader or recovery, I can push and pull files/folders consistently in both. The issue lies with fastboot.
Fastboot commands are only recognized a handful of times. Otherwise, they return "Remote: unknown command". Sometimes fastboot doesn't say it, however; it runs the command and then hangs indefinitely. I can change slots when this happens, but fastboot never confirms that the slot switching has completed (I can see it in recovery). I cannot flash anything, seemingly.
I have libmtp, android-tools, and android-udev installed (basically ensuring that my computer can use MTP, has adb and fastboot, and has the proper rules to recognize my phone). I have also tried simply using my own udev rules, using different versions of adb and fastboot (platform tools pulled directly from Google, others), not much seems to work. I can mount the device and interact with it via Thunar just fine.
The issue seems localized to my installation as when using the same laptop (Macbook Pro 11,1) the commands all work fine in OSX (Leopard+). Additionally, they work on an Ideapad running Manjaro Cinnamon (I didn't do anything except install android-tools) and Windows 10, the newest MacBook Pro in both OSX Mojave and Windows 8. Oddly they do not work on a PC running Windows 10, but I have no explanation for that. I have had this issue with Arch off and on for the last few years, but never really properly investigated - I always just booted back into OSX when I had to. I've recently removed OSX and don't want to keep it around just for fastboot, so I'd like to sort this.
I have included some logs from both dmesg and lsusb, as well as a snippet of what I see with fastboot.
I'm cross-posting this to the Arch forums just in case someone there can also shed light.
$ lsusb #adb
Code:
Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0259 Apple, Inc. Internal Keyboard/Trackpad
Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 007: ID 2e17:c032
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb #bootloader
Code:
Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0259 Apple, Inc. Internal Keyboard/Trackpad
Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 008: ID 2e17:c009
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb #recovery
Code:
Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0259 Apple, Inc. Internal Keyboard/Trackpad
Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 010: ID 18d1:4ee2 Google Inc. Nexus Device (debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ dmesg # snipped; shows adb, fastboot, and recovery in sequence
Code:
[ 155.611958] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 155.753376] usb 1-2: New USB device found, idVendor=2e17, idProduct=c032, bcdDevice= 2.23
[ 155.753383] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 155.753387] usb 1-2: Product: PH-1
[ 155.753391] usb 1-2: Manufacturer: Essential Products
[ 155.753393] usb 1-2: SerialNumber: PM1LHMA7B0304243
[ 194.716447] usb 1-2: USB disconnect, device number 7
[ 201.673283] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[ 201.814408] usb 1-2: New USB device found, idVendor=2e17, idProduct=c009, bcdDevice= 1.00
[ 201.814411] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 201.814413] usb 1-2: Product: Mata
[ 201.814415] usb 1-2: Manufacturer: Essential Products
[ 201.814416] usb 1-2: SerialNumber: PM1LHMA7B0304243
[ 225.328643] usb 1-2: USB disconnect, device number 8
[ 241.717526] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 241.858738] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.23
[ 241.858744] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 241.858747] usb 1-2: Product: PH-1
[ 241.858749] usb 1-2: Manufacturer: Essential Products
[ 241.858751] usb 1-2: SerialNumber: PM1LHMA7B0304243
[ 247.209126] usb 1-2: USB disconnect, device number 9
[ 247.597186] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[ 247.738482] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee2, bcdDevice= 2.23
[ 247.738487] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 247.738489] usb 1-2: Product: PH-1
[ 247.738492] usb 1-2: Manufacturer: Essential Products
[ 247.738493] usb 1-2: SerialNumber: PM1LHMA7B0304243
Various fastboot commands
Code:
PM1LHMA7B0304243 fastboot
$ fastboot getvar current-slot
getvar:current-slot FAILED (remote: unknown command)
Finished. Total time: 0.002s
$ fastboot getvar current-slot
current-slot:
Finished. Total time: 0.002s
$ fastboot getvar current-slot
getvar:current-slot FAILED (remote: unknown command)
Finished. Total time: 0.002s
$ fastboot getvar current-slot
current-slot:
Finished. Total time: 0.002s
$ fastboot getvar current-slot
current-slot: _a
Finished. Total time: 0.002s
$ fastboot getvar all
all:
Finished. Total time: 0.001s
$ fastboot getvar all
getvar:all FAILED (remote: unknown command)
Finished. Total time: 0.001s
$ fastboot getvar all
all:
Finished. Total time: 0.001s
$ fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4222
(bootloader) version-baseband:2.0.c4-M2.0.9
(bootloader) version-bootloader:mata-b9326aa
(bootloader) variant:eek:PENUS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1986B57000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:6
(bootloader) slot-unbootable:_b:no
(bootloader) slot-successful:_b:yes
(bootloader) slot-retry-count:_a:6
(bootloader) slot-unbootable:_a:no
(bootloader) slot-successful:_a:yes
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:PM1LHMA7B0304243
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
Finished. Total time: 0.005s
What cable are you using to connect your device to the computer?
Sent from my PH-1 using Tapatalk
had a similar problem, fixed it with using this adb and fastboot
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
also i recommend flashing the stock fastboot images as well, re-doing the process from stock with the new adb and fastboot
Sudo fastboot xxx
Sent from my PH-1 using XDA Labs
This sounds like the problem I just hit on my new AMD Ryzen/motherboard (with the latest USB spec) and an Essential PH-1.
I tried setting the ports to USB2 mode with:
Code:
sudo lspci -nn | grep USB | cut -d '[' -f4 | cut -d ']' -f1 | xargs [email protected] sudo setpci -H1 -d @ d0.l=0
and that did not work. This is on Debian Buster.
After six hours of swearing, I switched over to my 2014-era i7 laptop, also on Debian Buster, and everything worked perfectly out of the gate.
I saw some advice on another thread that ADB and USB3 behave poorly together. The suggestion there is to use a USB2 hub between the phone and computer. I haven't had a chance to try that yet, but if you're up for an experiment, it would be interesting to hear your result.
Also, be aware that Debian Buster currently has a packaging problem and mke2fs does not work from fastboot. There's a bug on it, without traction currently.
rignfool said:
What cable are you using to connect your device to the computer?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I have used three different cables, all USB A to USB C.
yenkoPR said:
had a similar problem, fixed it with using this adb and fastboot
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
also i recommend flashing the stock fastboot images as well, re-doing the process from stock with the new adb and fastboot
Click to expand...
Click to collapse
I have tried this page already, successfully flashing in Manjaro and and Windows the provided links. I have attempted it in Arch with the same problem.
avd said:
Sudo fastboot xxx
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I have already tried this, as well as running as super user from the start, and also have added my user to relevant groups. Still persists.
bill_mcgonigle said:
This sounds like the problem I just hit on my new AMD Ryzen/motherboard (with the latest USB spec) and an Essential PH-1.
I tried setting the ports to USB2 mode with:
Code:
sudo lspci -nn | grep USB | cut -d '[' -f4 | cut -d ']' -f1 | xargs [email protected] sudo setpci -H1 -d @ d0.l=0
and that did not work. This is on Debian Buster.
After six hours of swearing, I switched over to my 2014-era i7 laptop, also on Debian Buster, and everything worked perfectly out of the gate.
I saw some advice on another thread that ADB and USB3 behave poorly together. The suggestion there is to use a USB2 hub between the phone and computer. I haven't had a chance to try that yet, but if you're up for an experiment, it would be interesting to hear your result.
Also, be aware that Debian Buster currently has a packaging problem and mke2fs does not work from fastboot. There's a bug on it, without traction currently.
Click to expand...
Click to collapse
This is the most likely issue in my mind given the ways the problem has persisted and resolved through the use of different machines. Unfortuntaley, similar to you, the command did not work for me either.
Related
Problems getting pit file -- discovered a curious error. -- need help figuring it out
So I currently am running ubuntu 15 and another computer with mint 17. ON both computers I have tried heimdall and Jodin. Both have been unable to obtain a pit file. I get that error -7 which appears to be something related to not receiving any packets back from the phone. When I connect the phone outside of download mode - adb works also $Dmesg | tail [email protected]:~$ dmesg | tail [ 2663.619751] cdc_acm 3-1.1:1.1: failed to set dtr/rts [ 2663.691610] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device [ 2663.693138] usb 3-1.1: USB disconnect, device number 7 [ 2663.911119] usb 3-1.1: new high-speed USB device number 8 using ehci-pci [ 2664.021218] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=6860 [ 2664.021231] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2664.021238] usb 3-1.1: Product: SAMSUNG_Android [ 2664.021245] usb 3-1.1: Manufacturer: SAMSUNG [ 2664.021250] usb 3-1.1: SerialNumber: 4b6bda34 [ 2664.023462] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device [email protected]:~$ adb devices List of devices attached 4b6bda34 device In download mode...$dmesg | tail [email protected]:~$ dmesg | tail 1062.584521] usb 3-1.1: new high-speed USB device number 3 using ehci-pci [ 1062.693317] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=685d [ 1062.693328] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1062.693334] usb 3-1.1: Product: MSM8960 [ 1062.693339] usb 3-1.1: Manufacturer: Sasmsung [ 1062.807263] cdc_acm 3-1.1:1.0: ttyACM0: USB ACM device [ 1062.807597] usbcore: registered new interface driver cdc_acm [ 1062.807601] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [email protected]:~$ adb devices List of devices attached Not quite sure what to make of this. Especally the spelling of "Samsung" ...the product doesn't match. I don't know why its showing as a CDC_ACM modem. I was toying with the idea of blacklisting it again. But I tried that on my mint distro and it had no effect. ADB also shows no devices but Heimdall detects it. Fastboot also shows no devices during download mode. I'm kind of stuck here. Not sure how to fix this error. -All drivers are installed - 51 rules don't fix it -blacklisting cdc doesn't work -swapping doesn't work Anyone have any ideas?
? http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
USB Debugging On Linux
USB debugging on Linux Maybe it's just me being blind, but does anyone have `adb` working on Linux? Device ID shows up as 0fca, and I've added this to my udev rules, but still no device. Notification shows "USB debugging connected - Touch to disable USB debugging" with "Media device (MTP)" and "Camera (PTP)" USB connections. Code: 07:32:04 ~$ lsusb |grep Research Bus 001 Device 003: ID 0fca:8032 Research In Motion, Ltd. Code: [ 397.648593] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 397.920791] usb 1-1: New USB device found, idVendor=0fca, idProduct=8032 [ 397.920796] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 397.920798] usb 1-1: Product: BlackBerry [ 397.920799] usb 1-1: Manufacturer: BlackBerry [ 397.920801] usb 1-1: SerialNumber: <x> Code: 07:39:49 ~$ adb devices List of devices attached Thanks!
Figured it out. My Linux environment (Ubuntu 14) had the package 'android-tools-adb' installed, but that version of `adb` doesn't seem to work. The `adb` binary with the SDK tools works fine. I removed the 'android-tools-adb' and all is well again. :laugh:
P9 Lite crashed: black screen nor bip and no green o red light
Hi everybody, First I apologizes for my poor English. Nobody is perfect I'm French.. Whell, On my new P9 lite buy on October 20.... I have made some changes. I' have rooted it and suhide it. After that I have tried to put Xposed, and.... crash... black screen on boot, no bip, no little green or red light. First on linux with dmesg linux see it like: [510675.849532] usb 3-2: Product: vns [510675.849533] usb 3-2: Manufacturer: HUAWEI [510675.849534] usb 3-2: SerialNumber: FUH7N16627059031 [511731.855900] usb 3-2: USB disconnect, device number 103 [511735.297752] usb 3-2: new high-speed USB device number 104 using xhci_hcd [511735.426016] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [511735.426019] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [511735.426020] usb 3-2: Product: Fastboot2.0 [511735.426021] usb 3-2: Manufacturer: Fastbo [511735.426022] usb 3-2: SerialNumber: FUH7N16627059031 [511753.734515] usb 3-2: USB disconnect, device number 104 [511763.010163] usb 3-2: new high-speed USB device number 105 using xhci_hcd [511763.139415] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2 [511763.139418] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [511763.139419] usb 3-2: Product: vns [511763.139420] usb 3-2: Manufacturer: HUAWEI [511763.139421] usb 3-2: SerialNumber: FUH7N16627059031 [512470.759942] usb 3-2: USB disconnect, device number 105 [512622.440907] usb 3-2: new high-speed USB device number 106 using xhci_hcd [512622.628306] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2 [512622.628309] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [512622.628319] usb 3-2: Product: vns [512622.628320] usb 3-2: Manufacturer: HUAWEI [512622.628321] usb 3-2: SerialNumber: FUH7N16627059031 [512711.648289] usb 3-2: USB disconnect, device number 106 [512858.258337] usb 3-2: new high-speed USB device number 107 using xhci_hcd [512858.444693] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2 [512858.444696] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [512858.444697] usb 3-2: Product: vns [512858.444698] usb 3-2: Manufacturer: HUAWEI [512858.444699] usb 3-2: SerialNumber: FUH7N16627059031 [513073.322806] usb 3-2: USB disconnect, device number 107 [513075.949626] usb 3-2: new high-speed USB device number 108 using xhci_hcd [513076.077907] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [513076.077910] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [513076.077911] usb 3-2: Product: Fastboot2.0 [513076.077913] usb 3-2: Manufacturer: Fastbo [513076.077914] usb 3-2: SerialNumber: FUH7N16627059031 [513106.427014] usb 3-2: USB disconnect, device number 108 [513109.556986] usb 3-2: new high-speed USB device number 109 using xhci_hcd [513109.685423] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [513109.685426] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [513109.685427] usb 3-2: Product: Fastboot2.0 [513109.685428] usb 3-2: Manufacturer: Fastbo [513109.685429] usb 3-2: SerialNumber: FUH7N16627059031 [513110.427719] usb 3-2: USB disconnect, device number 109 [513210.899154] usb 3-2: new high-speed USB device number 110 using xhci_hcd [513211.027436] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [513211.027439] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [513211.027440] usb 3-2: Product: Fastboot2.0 [513211.027441] usb 3-2: Manufacturer: Fastbo [513211.027442] usb 3-2: SerialNumber: FUH7N16627059031 [513245.019570] usb 3-2: USB disconnect, device number 110 [513257.462374] usb 3-2: new high-speed USB device number 111 using xhci_hcd [513257.590785] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [513257.590788] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [513257.590789] usb 3-2: Product: Fastboot2.0 [513257.590790] usb 3-2: Manufacturer: Fastbo [513257.590791] usb 3-2: SerialNumber: FUH7N16627059031 [513749.414149] usb 3-2: USB disconnect, device number 111 [513832.330178] usb 3-2: new high-speed USB device number 112 using xhci_hcd [513832.458459] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [513832.458462] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [513832.458463] usb 3-2: Product: Fastboot2.0 [513832.458464] usb 3-2: Manufacturer: Fastbo [513832.458465] usb 3-2: SerialNumber: FUH7N16627059031 [514378.819119] usb 3-2: USB disconnect, device number 112 [514429.084772] usb 3-1: USB disconnect, device number 92 [514690.700924] usb 3-1: new full-speed USB device number 113 using xhci_hcd [514690.832742] usb 3-1: New USB device found, idVendor=1ea7, idProduct=0066 [514690.832744] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Etc... But now on dmesg I have only: [545310.125871] usb 3-2: USB disconnect, device number 125 [545338.435131] usb 3-2: new high-speed USB device number 126 using xhci_hcd [545338.563716] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [545338.563730] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [545338.563733] usb 3-2: Product: Fastboot2.0 [545338.563735] usb 3-2: Manufacturer: Fastbo [545338.563737] usb 3-2: SerialNumber: FUH7N16627059031 I don' have access to m phone! My question is how could I have access? I have tried Vo+ an power, Vol- and power, vol+and - and power and nothing, no signs of my phone.... Anybody have solution or my phone is dead?? Thanks in advance for your help. Richard PD: Well, now I progress. Whith android-sdk-linux I have now this output: fastboot devices FUH7N16627059031 fastboot But still black screen and others... someone have an idea or a solution??
Try to install the full stock firmware of your phone model. Copy it in /sdcard/dload folder and use 3 bottons to update.
Hi SevenSlevin SevenSlevin said: Try to install the full stock firmware of your phone model. Copy it in /sdcard/dload folder and use 3 bottons to update. Click to expand... Click to collapse How?? I haven't access to my phone, I don't see any partitions and folders... I tried to use 3 buttons, but nothing happen. I tried to access via linux and Windows but in windows nothing and on Linux jus visible on dmesg, can't mounting the phone or the sdcard... That's crazy!!
fastboot reboot bootloader works?
snapdesign said: fastboot reboot bootloader works? Click to expand... Click to collapse Yes: [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.023s] finished. total time: 0.073s And : fastboot getvar rescue_phoneinfo rescue_phoneinfo: VNS-L31C432B150 finished. total time: 0.003s And: fastboot oem check-rootinfo ... (bootloader) old_stat: RISK (bootloader) now_stat: RISK (bootloader) change_time: 1476921460 (bootloader) Check System: PASS OKAY [ 0.004s] finished. total time: 0.004s fastboot getvar rescue_phoneinfo rescue_phoneinfo: VNS-L31C432B150 finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot getvar rescue_versionrescue_version: rescue0.3 finished. total time: 0.001s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot oem get-build-number ... (bootloader) :VNS-L31C432B150 OKAY [ 0.003s] finished. total time: 0.003s fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot oem get-psid ... (bootloader) SN:FUH7N16627XXXXXX (bootloader) IMEI:8694000293XXXX (bootloader) IMEI:8694000294XXXX OKAY [ 0.002s] finished. total time: 0.002s But....: Next don't work fastboot oem backdoor info ... FAILED (remote: Command not allowed) finished. total time: 0.006s fastboot erase cache erasing 'cache'... FAILED (remote: Command not allowed) finished. total time: 0.010s adb shell su -v error: device '(null)' not found ... Any idea??
RicoMotril said: Yes: [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.023s] finished. total time: 0.073s And : fastboot getvar rescue_phoneinfo rescue_phoneinfo: VNS-L31C432B150 finished. total time: 0.003s And: fastboot oem check-rootinfo ... (bootloader) old_stat: RISK (bootloader) now_stat: RISK (bootloader) change_time: 1476921460 (bootloader) Check System: PASS OKAY [ 0.004s] finished. total time: 0.004s fastboot getvar rescue_phoneinfo rescue_phoneinfo: VNS-L31C432B150 finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot getvar rescue_versionrescue_version: rescue0.3 finished. total time: 0.001s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot oem get-build-number ... (bootloader) :VNS-L31C432B150 OKAY [ 0.003s] finished. total time: 0.003s fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.003s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model... (bootloader) HUAWEI VNS-L31 OKAY [ 0.003s] finished. total time: 0.003s fastboot oem get-psid ... (bootloader) SN:FUH7N16627XXXXXX (bootloader) IMEI:8694000293XXXX (bootloader) IMEI:8694000294XXXX OKAY [ 0.002s] finished. total time: 0.002s But....: Next don't work fastboot oem backdoor info ... FAILED (remote: Command not allowed) finished. total time: 0.006s fastboot erase cache erasing 'cache'... FAILED (remote: Command not allowed) finished. total time: 0.010s adb shell su -v error: device '(null)' not found ... Any idea?? Click to expand... Click to collapse yeah... you have l31, download latest update.app, use huawei update extractor and get system, boot,recovery, cust... and flash them in fastboot with fastboot flash system system.img etc... you can find some tutorials on p8 lite section... or simply try to flash twrp and see if the device boots in recovery "fastboot flash recovery twrpnamehere.img"
I have flashed the last TWRP and no change, I gonna test with the last update. the B151 is good?? snapdesign said: yeah... you have l31, download latest update.app, use huawei update extractor and get system, boot,recovery, cust... and flash them in fastboot with fastboot flash system system.img etc... you can find some tutorials on p8 lite section... or simply try to flash twrp and see if the device boots in recovery "fastboot flash recovery twrpnamehere.img" Click to expand... Click to collapse
Update Well, I used VNS-L31C432B151 (L31) Update.zip don't work: archive does not contain 'android-info.txt' Nest I have split to images and: Require Maj like BOOT.img and no boot.img... I suposed.. fastboot flash boot BOOT.img fastboot reboot rebooting... finished. total time: 0.072s fastboot reboot rebooting... finished. total time: 0.072s But my fone don' work... Black screen no light, and buzz... I tried fastboot flash system SYSTEM.img that don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... Anything wrong?? why that don't work? please
Update Well, I used VNS-L31C432B151 (L31) Update.zip don't work: archive does not contain 'android-info.txt' Nest I have split to images and: Require Maj like BOOT.img and no boot.img... I suposed.. fastboot flash boot BOOT.img fastboot reboot rebooting... finished. total time: 0.072s fastboot reboot rebooting... finished. total time: 0.072s But my fone don' work... Black screen no light, and buzz... I tried fastboot flash system SYSTEM.img that don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... Anything wrong?? why that don't work? please
RicoMotril said: Well, I used VNS-L31C432B151 (L31) Update.zip don't work: archive does not contain 'android-info.txt' Nest I have split to images and: Require Maj like BOOT.img and no boot.img... I suposed.. fastboot flash boot BOOT.img fastboot reboot rebooting... finished. total time: 0.072s fastboot reboot rebooting... finished. total time: 0.072s But my fone don' work... Black screen no light, and buzz... I tried fastboot flash system SYSTEM.img that don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... I tried: fastboot flash boot twrp-3.0.2-0-eva.img Don't work... Anything wrong?? why that don't work? please Click to expand... Click to collapse You are using a P9 twrp probably there is something wrong. Anyway to install update.app of b151 you need stock recovery and put that file in sdcard (dload folder) using PC (without phone). Huawei has 2 recovery, the second is ercovery. You need to flash the first 1 and be sure that you have flashed it.
I need to flash B151?? and where i can find stock recovery? What SDcard? the intern or the extern?? in twice I don't can access to folders or partitions... only to fastboot commands and not all by example I can't erase userdata or cache and i can't access to the shell.. SevenSlevin said: You are using a P9 twrp probably there is something wrong. Anyway to install update.app of b151 you need stock recovery and put that file in sdcard (dload folder) using PC (without phone). Huawei has 2 recovery, the second is ercovery. You need to flash the first 1 and be sure that you have flashed it. Click to expand... Click to collapse
RicoMotril said: I need to flash B151?? and where i can find stock recovery? What SDcard? the intern or the extern?? in twice I don't can access to folders or partitions... only to fastboot commands and not all by example I can't erase userdata or cache and i can't access to the shell.. Click to expand... Click to collapse External Sd Card man! Put your external sd card on PC and just copy from pc to it the update.app of b151 or b150 (I think it's the same), in a folder called "dload" (just create it) . After put your external on your phone and use 3 buttons.
Don't work. SevenSlevin said: External Sd Card man! Put your external sd card on PC and just copy from pc to it the update.app of b151 or b150 (I think it's the same), in a folder called "dload" (just create it) . After put your external on your phone and use 3 buttons. Click to expand... Click to collapse Hi SevenSlevin, I tried your solution but that don't work that continue black screen, no buzz no red light.. have you or anybody another solution please??
More and more strange... Take a look: usb 3-2: new high-speed USB device number 24 using xhci_hcd [35458.945542] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [35458.945556] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [35458.945558] usb 3-2: Product: Fastboot2.0 [35458.945560] usb 3-2: Manufacturer: Fastbo [35458.945562] usb 3-2: SerialNumber: FUH7N16627059031 [38407.154339] usb 3-2: USB disconnect, device number 24 [38409.399645] usb 3-2: new high-speed USB device number 25 using xhci_hcd [38409.528094] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d [38409.528097] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [38409.528099] usb 3-2: Product: Fastboot2.0 [38409.528100] usb 3-2: Manufacturer: Fastbo [38409.528101] usb 3-2: SerialNumber: FUH7N16627059031 Why the manufacturer have change to Fastbo?? why the product name is now Fastboot2.0?? I dont understand
for recovery and twrp is fastboot flash recovery not boot...other than that yeah you are using twrp for p9(eva). Try with the tools on this forum to flash twrp... and you just tried with boot and system...i told you to flash more files... and we need another info about why system flash failed... also check if bootloader is unlocked... maybe it's re locked
Like snapdesign wrote before, obtain the b151 firmware (vns-l31 or vns-l21 depending on your model). Extract the zip file. Then you will get the update.app. Use Huawei Update Extractor to extract the firmware files from the update.app. ONLY flash boot.img, system.img and recovery.img. DON'T flash anything else. If you really want to flash everything either flash trough the phone after it boots properly or use DC-Phoenix (paid and dangerous, it will flash anything). Don't mess with backdoor commands. Those commands require a special packet to be enabled. Edit: And whatever you do, DO NOT use dd to flash those images. They all seem to have some kind of header in the beginning of the file (most likely a signature for validation). Edit 2: Since you are flashing a wrong twrp recovery (P9 instead of P9-lite) and you are flashing it to the boot partition instead of the recovery partition, it is normal that your phone doesn't boot. Flash each image to the proper partition.
Nogood news.. Well, I used the good tool now and with the SRKToolHuawei-STABLE-V1.3-20160619 I tried to connect via ADB with the drivers on Windows 7. I can't connect on ADB.... I have a message "waiting for the device" non stop!! I can't access to my device. I tried with fastboot on Linux this commands: fastboot flash recovery stockrecoveryp9mm.img target reported max download size of 471859200 bytes sending 'recovery' (35180 KB)... OKAY [ 1.102s] writing 'recovery'... OKAY [ 0.440s] finished. total time: 1.542s And I tried this see on one web site booth don't work the firs have ok message but nothing on reboot and the second have error message. ~/Bureau/android-sdk-linux/tools$ fastboot flash recovery/boot stockrecoveryp9mm.img target reported max download size of 471859200 bytes sending 'recovery/boot' (35180 KB)... OKAY [ 1.102s] writing 'recovery/boot'... FAILED (remote: partition error) finished. total time: 1.124s I don't know where the problem is.. Thank for helping me. Richard
randhackr said: Like snapdesign wrote before, obtain the b151 firmware (vns-l31 or vns-l21 depending on your model). Extract the zip file. Then you will get the update.app. Use Huawei Update Extractor to extract the firmware files from the update.app. ONLY flash boot.img, system.img and recovery.img. DON'T flash anything else. If you really want to flash everything either flash trough the phone after it boots properly or use DC-Phoenix (paid and dangerous, it will flash anything). Don't mess with backdoor commands. Those commands require a special packet to be enabled. Edit: And whatever you do, DO NOT use dd to flash those images. They all seem to have some kind of header in the beginning of the file (most likely a signature for validation). Edit 2: Since you are flashing a wrong twrp recovery (P9 instead of P9-lite) and you are flashing it to the boot partition instead of the recovery partition, it is normal that your phone doesn't boot. Flash each image to the proper partition. Click to expand... Click to collapse Hi, I have do this now with b151 vns-l31 firmware and my phone have no change: ~/Bureau/android-sdk-linux/tools$ fastboot flash boot BOOT.img target reported max download size of 471859200 bytes sending 'boot' (14002 KB)... OKAY [ 0.432s] writing 'boot'... OKAY [ 0.326s] finished. total time: 0.758s [email protected]:~/Bureau/android-sdk-linux/tools$ fastboot flash system SYSTEM.img target reported max download size of 471859200 bytes sending sparse 'system' (451070 KB)... OKAY [ 13.916s] writing 'system'... OKAY [ 5.886s] sending sparse 'system' (457911 KB)... OKAY [ 14.172s] writing 'system'... OKAY [ 5.639s] sending sparse 'system' (460613 KB)... OKAY [ 14.565s] writing 'system'... OKAY [ 6.551s] sending sparse 'system' (454334 KB)... OKAY [ 14.091s] writing 'system'... OKAY [ 5.747s] sending sparse 'system' (451030 KB)... OKAY [ 13.811s] writing 'system'... OKAY [ 5.571s] sending sparse 'system' (284111 KB)... OKAY [ 8.716s] writing 'system'... OKAY [ 3.559s] finished. total time: 112.226s fastboot flash recovery RECOVERY.img target reported max download size of 471859200 bytes sending 'recovery' (33120 KB)... OKAY [ 1.009s] writing 'recovery'... OKAY [ 0.752s] finished. total time: 1.761s fastboot reboot rebooting... finished. total time: 0.122s Any idea??
Odd. But now you should create a folder on the microsd card named dload and copy the update.app there. Try to boot the recovery (power + vol up). If it works reboot the phone and do the three button combo. Edit: You can try to do a factory reset or also try dc-phoenix to flash the phone but it costs 15€ and doesn't flash the oeminfo partition (and again it is a dangerous tool).
randhackr said: Odd. But now you should create a folder on the microsd card named dload and copy the update.app there. Try to boot the recovery (power + vol up). If it works reboot the phone and do the three button combo. Edit: You can try to do a factory reset or also try dc-phoenix to flash the phone but it costs 15€ and doesn't flash the oeminfo partition (and again it is a dangerous tool). Click to expand... Click to collapse Hi randhackr, I tried all your solutions and no one work with my crazy phone.. I tried to with dc-phoenix and that is the output: Detecting phone : selection : manufacturer - Huawei phones model - Auto detect (recommended) Found Phone : HUAWEI VNS-L31 Model : Huawei phone in fastboot mode IMEI : 869400029XXXXXX Serial NR. : FUH7N16627059031 Firmware : VNS-L31C432B150 IMEI:8694000294XXXXX FB LockState: LOCKED USER LockState: UNLOCKED unlocked Battery state: 0 Is it normal? AND: Authorising phone... Phone authorization fail! Port unavailable anufacturer - Huawei phones model - Huawei P9 series Selected Diagnostics port COM19 The soft cant contact in ADB mode or in fastboot mode i Think... I'm gonna be crazy!! i have buy phone las week, do you think is it possible to change it by warranty?
Hard Bricked Note 7, I hope this is temporary
[SOLVED] Used the guide here for EDL mode and back up. https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543 Went to restore my OrangeFox backup, everything seemed well, so I rebooted.. nothing, no bootlogo, but the screen is lit. Ok, try fastboot, hold powerbutton down for 12 seconds, rebooted (vibrated), hold volume up and power.. no fast boot.. I hope I haven't borked something, can't get into fastboot or recovery. screen is black, no boot logo, nothing but screen is lit. nothing shows up on adb devices while at the black screen. Before backup restored, USB Plugged in looked like this: [ 2532.267203] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2532.267204] usb 4-5: Product: SDM660-MTP _SN:50B88856 [ 2532.267205] usb 4-5: Manufacturer: Xiaomi [ 2532.267206] usb 4-5: SerialNumber: ******** [ 2732.465636] usb 4-5: USB disconnect, device number 12 [ 2743.383822] usb 4-5: new high-speed USB device number 13 using ehci-pci [ 2743.513131] usb 4-5: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.23 Click to expand... Click to collapse Now it looks like this 6395.629532] usb 4-5: new high-speed USB device number 24 using ehci-pci [ 6395.758655] usb 4-5: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00 [ 6395.758658] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 6395.758660] usb 4-5: Product: Android [ 6395.758661] usb 4-5: Manufacturer: Google [ 6395.758662] usb 4-5: SerialNumber: ******** Click to expand... Click to collapse
Ok, I see, EDL mode it is.. https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
Errors with SP Flash tools on Ubuntu 18.04
I have been trying to flash some old M2 Note units and so far I can't get the Preloader to talk over USB: Code: [ 1774.167123] usb 1-1: new high-speed USB device number 35 using xhci_hcd [ 1774.320150] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00 [ 1774.320152] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1774.320153] usb 1-1: Product: MT65xx Preloader [ 1774.320153] usb 1-1: Manufacturer: MediaTek [ 1774.344085] cdc_acm 1-1:1.0: Zero length descriptor references [ 1774.344093] cdc_acm: probe of 1-1:1.0 failed with error -22 [ 1774.384238] cdc_acm 1-1:1.1: ttyACM0: USB ACM device [ 1776.971989] usb 1-1: USB disconnect, device number 35 I tried adding the vendor ID and product ID to the new_id of the cdc_acm driver and also masking/disabling the ModemManager service in case it was interfering. I had the same issue on WIndows... it would reset immediately and kick into normal Android mode. Anyone has any advice? I'm going to trying using the OTA zip with the modified/unlocked images for the preloader. Flashing TWRP via Flashify did not work out.... rebooted into recovery to the default Meizu one.