Related
Hi,
my TouchPad seems to be in a boot loop, or bootloader is corrupt, dunno.
I am using linux, btw.
This happend:
I did install CM7 since after the first alpha release and upgraded each release without a hassle. I had both OS parallel for a long time dual booting regulary, but using Android more and more often.
Since Christmas then I havent even been in WebOs.
Two weeks ago, I started WebOS again, and got a message to update my software.
I clicked yes.
Then it took an hour or so and the Pad rebooted ..... and got stuck - never came up again since then.
It just stays a bit where the round HP sign comes up, and reboot after a minute or so.
here is the dmesg:
Code:
[37240.196350] usb 2-1.3: new high-speed USB device number 8 using ehci_hcd
[37240.317306] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37240.317318] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37240.317325] usb 2-1.3: Product: Palm
[37240.317330] usb 2-1.3: Manufacturer: bootie
[37522.496211] usb 2-1.3: USB disconnect, device number 8
[37552.413914] usb 2-1.3: new high-speed USB device number 9 using ehci_hcd
[37552.534865] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37552.534877] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37552.534884] usb 2-1.3: Product: Palm
[37552.534889] usb 2-1.3: Manufacturer: bootie
[37579.309737] usb 2-1.3: USB disconnect, device number 9
I tried a hard reset, and same same happens again:
It resets, the hp logo shows up, then after a minute it reboots again.
So after this I tried to use memboot. but I can't get even into usb mode!
Holding Volume up + Power does exactly nothing! Novacom doesn't recognize my TouchPad.
Holding Volume down + Home + Power does nothing as well - despite throwing this into dmesg:
Code:
[37197.120415] usb 2-1.3: new high-speed USB device number 7 using ehci_hcd
[37197.240971] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9008
[37197.240977] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37197.240981] usb 2-1.3: Product: QHSUSB_DLOAD
[37197.240984] usb 2-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[37197.241877] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[37197.242395] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[37238.172562] usb 2-1.3: USB disconnect, device number 7
[37238.173155] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[37238.173359] qcserial 2-1.3:1.0: device disconnected
btw, webdoctor certainly doesnt recognize my device, neither in linux nor in windows 7 - nonetheless it shows up in explorer as palm device without device drivers installed (yes I did install novacom drivers in Windows as well as in linux).
What to do now? Any hints?
Do the reset again then when it starts to reset hold volume up only.
hopefully that should be you in webos recovery.
Then you can try to flash moboot again because the update does break moboot.
thanks....
had to do it three times, then it worked out!! maybe my vol key is lose?
Anyway, you made my week!! :-D
Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery
[Solved? product ID change] Fastboot not working - ADB ok XT1068
jc56au said:
Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery
Click to expand...
Click to collapse
After another 4 hours of my life tried:
adb reboot bootloader
while usb connected and lsusb showed:
"Bus 002 Device 007: ID 22b8:2e80 Motorola PCS"
Note the different id
and selected recovery by <up>- TWRP appeared without any further computer stuff.
Had previously tried: "fastboot flash recovery TWRP2801-titan-motog-2014.img"
and following "waiting for device" had closed xterminal
@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD
LuK1337 said:
@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD
Click to expand...
Click to collapse
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit
jc56au said:
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit
Click to expand...
Click to collapse
Yes. For fastboot to work, you have to put your phone in fastboot (bootlader) mode. That is the screen you get when pressing power+ vol.down. Only then you can use the fastboot commands.
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue
Hi,
i used an 'Engineering Flash Cable' . After this i find no device with both commands:
If i take a look in Ubuntu i see :
tail -f /vaadb devices
fastboot devicesr/log/syslog
Dec 31 21:38:32 martin-ws kernel: [393207.220567] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Dec 31 21:38:32 martin-ws kernel: [393207.220609] qcserial 8-1:1.0: device disconnected
Dec 31 21:39:04 martin-ws kernel: [393239.302742] usb 8-1: reset high-speed USB device number 6 using xhci_hcd
Dec 31 21:39:04 martin-ws kernel: [393239.432734] qcserial 8-1:1.0: Qualcomm USB modem converter detected
Dec 31 21:39:04 martin-ws kernel: [393239.433338] usb 8-1: Qualcomm USB modem converter now attached to ttyUSB0
or
Dec 31 21:39:55 martin-ws kernel: [393290.332927] usb 8-1: new high-speed USB device number 7 using xhci_hcd
Dec 31 21:39:55 martin-ws kernel: [393290.465347] usb 8-1: New USB device found, idVendor=05c6, idProduct=9008
Dec 31 21:39:55 martin-ws kernel: [393290.465358] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 31 21:39:55 martin-ws kernel: [393290.465363] usb 8-1: Product: QUSB__BULK
Dec 31 21:39:55 martin-ws kernel: [393290.465367] usb 8-1: Manufacturer: Qualcomm CDMA Technologies MSM
Dec 31 21:39:55 martin-ws kernel: [393290.466591] qcserial 8-1:1.0: Qualcomm USB modem converter detected
Dec 31 21:39:55 martin-ws kernel: [393290.467094] usb 8-1: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
but its not possible to power on the mobile (The Screen is only black).
In the Screenshot you can see that i have no USB-Device instead of this i have an COM&LPT Connector
http: // abload.de/thumb/handyiqjpv.png
MiFlash brings only Timeouts
Do you have any ideas or is the device finaly bricked ?
is LED flashing? I had the same problem, its motherboard propably. Wwith ROM you've got?
ranseyer said:
Hi,
i used an 'Engineering Flash Cable' . After this i find no device with both commands:
If i take a look in Ubuntu i see :
but its not possible to power on the mobile (The Screen is only black).
In the Screenshot you can see that i have no USB-Device instead of this i have an COM&LPT Connector
http: // abload.de/thumb/handyiqjpv.png
MiFlash brings only Timeouts
Do you have any ideas or is the device finaly bricked ?
Click to expand...
Click to collapse
I bricked my mi5 last week. No leds showing up, no fastboot, no recovery. Seemed like it was completely dead.
In Windows however device was showing up as Qualcomm HS-USB QDLoader 9008. Miflash could see this device, but when trying to flash it always failed.
How did i fix it?
I had to press down volume up, volume down and power button at the same time as long as device would disappear from device manager and show back again. After this device was actually in proper qualcomm recovery mode. After this procedure miflash Beta was able to successfully flash rom in to device.
(In windows it was required to boot Windows in safe mode to disable driver signing and also install miflash Beta in safe mode also)
This was done in windows, but tested it also with Debian 8(no safe modes needed). Some driver witchery may be required As they said in some article, these newer snapdragon devices are pretty much impossible to brick completely unless there is hardware malfunction.
Link to miflash beta http://en.miui.com/thread-281979-1-1.html
Reqular miflash was useless.
Hi,
i have fixed it with flashing an fastboot ROM via this flash-tool: https : // mirror.byteturtle.eu/apps/MiFlash/MiPhone_20160401.exe
Thanks for your hints.
Regards
Hi,
A few months ago, I tried flashing e-os on my old Moto X (2014). Something went wrong and I didn't look at it until now because of a lack of time.
When I connect the phone to my computer or a power brick, it goes immediately in AP Fastboot Flash Mode (S). I think I flashed something wrong in the wrong place. I can't connect with adb or fastboot (tried the fastboot from the package in the openSUSE linux repositories, the one from the android-platform tools on the android website and linux-fastboot from mfastboot), I tried different USB-cables (even one labeled as a "data cable") and ports.
The screen looks like this:
AP Fastboot Flash Mode (S)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
eMMC: 16GB Sandisk RV=06 PV=07 TY=17
DRAM: 2048MB Samsung S4 SDRAM DIE=4Gb
Up Time: 10 minutes
Device is UNLOCKED. Status Code: 3
Battery OK
Transfer Mode: USB Connected
Boot Mode Selection Menu
Vol Up Selects, Vol Down Scrolls
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
Fastboot REason: Flash Failure
USB connected
Selecting Recovery shows the "bootloader unlocked" warning screen and then an android on his back with a red warning triangle ().
Selecting Factory or BP Tools leads to the warning screen and then the menu again.
Normal Powerup gives the warning screen, a black screen (and vibrates, probably it restarts), the warning screen again and then the dead android with the warning triangle.
I don't remember what exactly I did last time.
Thank you for any advice.
Kind regards,
Twijg
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
Thank you for the reply.
No new usb-device showed up, which is weird. I tried all three ports and two different cables. The ports at least work with my keyboard and mouse.
This is an output I got, it was the same with or without the phone attached:
Code:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 004: ID 13d3:5458 IMC Networks USB2.0 HD UVC WebCam
Bus 003 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
Bus 003 Device 006: ID 13d3:3563 IMC Networks Wireless_Device
Bus 003 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0781:55ae SanDisk Corp. Extreme 55AE
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I also tried again with my keyboard and mouse unplugged.
disconnect usb, power off phone, press and keep holding both volume keys, connect usb
Thank you, that helped indeed. I was able to connect with fastboot and flash the recovery img.
That issue is solved now.
I now have a different problem where selecting recovery leads to an endless series of restarts to the unlocked bootloader warning screen. If you happen to know what the reason for that could be... I'll go looking online and in the fora as well and edit this message with the link to a solution if I find one.
Thank you again!