Database Users

MSM8960 jtag!

This thread was initially started for the purpose of unbricking the HTC evo 4g lte (HTC Jewel) with the possible help of JTAG. But since i was unable to find any corresponding jtag mod/pinouts for any other phone, the thread has been re-titled as MSM8960 Jtag. It would be good if members share there knowledge about possibilities of discovering JTAG locations on newer Snapdragon S4 based chipsets
A short history how the phone was bricked.
Code:
My phone was S-OFF with lazypanda and flashed the OMJ 1.13 stock rooted odex rom. After that i downloaded latest radio from the radio thread and flashed it. However it seems that the wifi gave up due to this, it only showed error. It never turned on, so i tried to flash another previous version radio which seems to be flashed normally without any issues. After this the phone never showed anything, windows detects it as QHUSB_DLOAD. I have tried to use lazypanda evo lte unbricker but it is not able to find the device!
[QUOTE][email protected]:~/new$ sudo ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[/QUOTE]
However the getbrickdevice script which is in with yarrimapirate downgrade thread is able to pick the phone
[QUOTE][email protected]:~/hboot$ sudo ./getbrickdrive.sh
Your bricked phone is accessible at /dev/sdd[/QUOTE]
lsusb output
[QUOTE][email protected]:~/hboot$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 154b:0059 PNY
Bus 003 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 046d:c068 Logitech, Inc. G500 Laser Mouse
[/QUOTE]
Now, when i use this command
[QUOTE]sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576[/QUOTE]
It outputs the below results
[QUOTE][email protected]:~/hboot$ sudo ./emmc_recover_new -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdd12 -c 24576
================= emmc_recover 0.3 alpha 2 ==========================
Using chunksize 24576
Messing up with device /dev/sdd12, ARE YOU SURE?
CTRL+C if not, ENTER to continue
Waiting for device.
[/QUOTE]
Running the lanzypanda unbricker shows
[QUOTE][email protected]:~/unbrick$ sudo ./PandaFinder -d /dev/sdd
============ PandaFinder 0.1 ===========
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Bricked device will appear to device node /dev/sdd
ARE YOU SURE?
CTRL+C if not, ENTER to continue
Realnode is /dev/sdd12
Ready to go.
(1) Remove MicroSD card from phone
(2) Connect bricked EVO 4G LTE to usb
Press ENTER when ready
*** Do NOT remove usb cable during process
*** Do NOT press any buttons until PandaFinder requests you to do that!!
******** Press ENTER when you understand this!! Really ********
Lets try unbricking once, before we run it really
Press ENTER to start test
Waiting for device.
- found /dev/ttyUSB1 - OK
Waiting device /dev/sdd12.......
[/QUOTE]
dmesg output
[QUOTE][ 208.362070] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 208.362094] qcserial 1-1:1.0: device disconnected
[ 242.659408] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 242.802505] usb 1-1: New USB device found, idVendor=05c6, idProduct=9008
[ 242.802511] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 242.802514] usb 1-1: Product: QHSUSB_DLOAD
[ 242.802517] usb 1-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 242.805254] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 242.805492] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[/QUOTE]
And here it gets stucked forever, previously when the reset command was being sent to the phone, it shows Qualcomm Inc in lsusb output and after some 7-10sec it swtich to Qualcomm QDL. But it only gets stucked onto Qualcomm QDL now.

Please post in the proper sections. This belongs in Q&A not development...

Yep... MOVED to Q and A

Might be better asking here:
http://unlimited.io/support.htm
Sent from my HTC One X using xda app-developers app

Can any1 provide any info on jtag pinouts of this device? It seems that i m not ableto recover the phone unless i jtag it. The riff box supports ressurection for all the msm8960 snapdragon s4 based phones so i think it will be able to recover evo lte also. I asked dexter @ thr irc channel and he said that screwed things up and hence will not be able to recover the device using thr provided method
Sent from my LG-LS840 using Tapatalk 2

You might find something here, these guys are trying to map everything. MSM8960 Info

The NRST pad location is shown in this picture of evo 4g lte motherboard. It would be really appreciated if some1 can help in location the remaining pads as well.
Full size image
http://img221.imageshack.us/img221/1503/cam00068.jpg

Bump, now since the phone is completely dead, m trying to locate the jtag pads on this phone. here is a rough idea for jtag pads. Let me known if any1 is willing to help.
https://www.dropbox.com/s/gbfyaf5aouc27ee/htcevo4glte2.jpg
The pad locations are just assumptions on the basis of regular jtag allocations on various htc phones.

Below are some of the voltage readings which are observed with Riff Box Voltage probe.
https://www.dropbox.com/s/reipjimu8toola4/CAM00068.jpg
http://pastebin.com/ZBw8TFcg
+C= Cable attached.
+B= Battery attached.

funkym0nk3y said:
Below are some of the voltage readings which are observed with Riff Box Voltage probe.
https://www.dropbox.com/s/reipjimu8toola4/CAM00068.jpg
http://pastebin.com/ZBw8TFcg
+C= Cable attached.
+B= Battery attached.
Click to expand...
Click to collapse
which adapter are you using? riff? ort? I was searching for just this because I have a very difficult HTC One xl brick. your thread was the first Google result, and this was the second:
http://www.cdmahosting.com/showthread.php?p=1491
I hope that helps!
at $200, the ort-jtag is a tempting buy, esp. When you see so many tough bricks lately. too bad I don't even know where to start with it... lol

=JKT= said:
which adapter are you using? riff? ort? I was searching for just this because I have a very difficult HTC One xl brick. your thread was the first Google result, and this was the second:
http://www.cdmahosting.com/showthread.php?p=1491
I hope that helps!
at $200, the ort-jtag is a tempting buy, esp. When you see so many tough bricks lately. too bad I don't even know where to start with it... lol
Click to expand...
Click to collapse
I know, in my country i got it for around 100$ (RIFFBOX, thanks to a known person). Riff box new update also supports MSM8960 chipset and so i think once we are able to locate jtag pads, thr isnt going to be any problem.

so in the case of, say, jewel and evita, the soft part of the jtag will be the same (using the right imgs of course) since they are both msm8960, but the connection points will be different because the board layout is different? but, on the other hand, the correct pins will show similar behaviour re: voltage as another msm8960, correct? Hopefully they will not be in the set that seems to hover around 1.8v...
One last question. will the pin voltage behaviour be more or less consistent between chip sets? I'm specifically thinking of the pins that have unique behaviour like 25, 26, 29 on your pastebin.com chart. If so, we might get lucky referring to a somewhat similar, but known chip set.

Hopefully yes, and that might provide help in locating possible known behavior and voltages on other similar phones. But i think this totally depends on the pull up resistors being used by manufacturers? I might be wrong here, maybe more and older hardcore junkies can shed some light on this.

funkym0nk3y said:
Hopefully yes, and that might provide help in locating possible known behavior and voltages on other similar phones. But i think this totally depends on the pull up resistors being used by manufacturers? I might be wrong here, maybe more and older hardcore junkies can shed some light on this.
Click to expand...
Click to collapse
yeah. this seems like an esoteric topic, and google isn't yielding results too easily. perhaps I'm just searching for the wrong thing. jtag is a really broad topic, and I'm unsure what the crucial variables are to narrow the search.
edit: this method seems helpful. take a look, if you haven't already seen it.

Success
Finally able to find all the necessary pinouts.
Thanks to htc unbrick team.

funkym0nk3y said:
Finally able to find all the necessary pinouts.
Thanks to htc unbrick team.
Click to expand...
Click to collapse
did you share these somewhere, or was it like a "for your eyes only" type thing?

At the moment its only for my eyes thing, will update the pinout pic and post here

Update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy.

funkym0nk3y said:
Update
View attachment 1471313
Enjoy.
Click to expand...
Click to collapse
You rock. Hopefully this will help us Evita people out with JTAGing some stubborn bricks.

Evita is already jtagged
Sent from my EVO using Tapatalk 2

[Q] Any way to recover files from S4 with dead screen?

I have an old Canadian Bell based Galaxy s4, with a dead screen. I'd like to try to get files off it, but did not enable usb debugging mode prior to the screen breaking.
Is there any way to access the file system on the phone in this situation? I've done a bit of looking around and can see that I should be able to access it via adb if I have usb debugging turned on, but debugging isn't on in this case.
I have usb connected the phone to my fedora machine and can see via dmesg that it does get detected. I can hear the thing start up, but beyond that I can't see anything else.
Googling around it sounds like I should be able to load a recover kernel, with debugging turned on if I use the right process, but I can't find enough into to get me going.
dmesg output is below just in case it helps...
.....................................................................................
[ 4104.343749] usb 2-2: USB disconnect, device number 6
[ 4180.261104] usb 2-2: new high-speed USB device number 7 using ehci-pci
[ 4180.376385] usb 2-2: New USB device found, idVendor=04e8, idProduct=6860
[ 4180.376390] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4180.376394] usb 2-2: Product: SAMSUNG_Android
[ 4180.376396] usb 2-2: Manufacturer: SAMSUNG
[ 4180.376399] usb 2-2: SerialNumber: ........
Any help is much appreciated!

If you can get a custom recovery on you can use adb without use debugging on. I assume you have an i337m. Try this with twrp http://galaxys4root.com/clockworkmodtwrp-recoveries/
Sent from my Nexus 9 using XDA Free mobile app

If you have a custom recovery plug it up to hdmi thru HML and use the TV for the screen. Hopefully the touchscreen still works. This worked for mine. No lcd but the digitizer was still good.

[HOW TO] Unbrick Kindle Fire HDX (QHUSB_BULK) with firmware <=1314.3.2.6

First of all - this is works only if you bricked on firmware <=1314.3.2.6.
So it don't works for "rollbacked 3.2.8(7)" bricks(
Sorry but need leak of newest version of flash programmer for higher sw.
I understand that there is not many people with this type of bricks but it is better that nothing=)
Of course you can try - you can not do worse=) I test this method on 13.3.2.3 and 13.3.2.4.
Apollo users should read post to the end before doing anything!
Manual in progress. Additions and comments are appreciated.
Logs of flasher to examine errors locates at C:\Program Files(X86)\Xiaomi\MiPhone\
My English isn't perfect) - PM me with OP corrections.
​
1. Download archive - https://drive.google.com/file/d/0B2twXJIOgv-UR0dZTVJUeFFsVU0/view?usp=sharing and unpack it. Two folders inside - fw and tools.
2. Install ./tools/MiPhone2015731.exe
2a. For x64 system you need disable drivers signature verification before installing. Google it.
3. Start and setup Miflash:
3a. Press 'Browse' and select folder "fw" from archive. Press OK.
3b. Press down arrow on this button, Press "Advanced" and fill fields with files in folder 'fw' by "Browse" :
- flashprogrammer - .\fw\prog_emmc_firehose_8974.mbn
- raw xml file - .\fw\rawprogram0.xml
- patch xml file - .\fw\patch0.xml
- other fields no need to touch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Ok. Now you need put your device in QHSUSB Bulk - mode and install Drivers.
4a. Your device can be in this state already. Just connect it to PC.
4b. If you have working adb (who knows) - type "adb reboot oem-2" or "adb reboot emergency" in cmd (i suppose you know that is adb drivers and adb). This is reboot kindle into emergency mode Qdloader 9008.
4c. Your device is stucked at greylogo or bootlooping without adb access. You need fastboot cable. Reboot device with plugged fastboot-cable.
5. Navigate to device manager and check for new device named QHSUSB_BULK . Drivers will install automatically or you need install it manually from .\tools\QualcommDrv.
In device manager at COM-Ports section you must obtain HS-USB Qdloader 9008 (COMx) without exclamation!
6. Go to Miflash , press Refresh, you should see your com port and empty bar under "progress" section.
7. Press "Flash". You should see messages like "WriteFile position 0x00000000840000, size 131072"
8. If all gone successfully disconnect kindle from PC and reboot it by holding power+vol up.
8a. If unsuccessful - reboot device and start over. In this mode for reboot sometimes needs above 5 min holding of power button.
If you get "Opening port" after some loading - you probably have > 1314.3.2.6 fw version.
9. Grats. You are in TWRP. You could flash stock 1314.3.2.3 firmware renaming bin to zip. Do not forget to block OTA immediately!
10. BTW you aboot partition is 13.3.2.3 version so you can do procedure of unlock without downgrading to 13.3.2.3 - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Apollo users !!! - you need to replace recovery.img and emmc_appsboot.mbn with these (rename twrp and aboot_vuln).
CREdits:
bournezhang - for leaked programmer.
FSmp - for testing at 13.3.2.4
For advanced users - this works with any unlocked devices too (aboot<= 13.2.3.2).
By filling "filename" at rawprogram0.xml you can flash any partition to your device. Big partition like system.img must be sparsed I assume and rawprogram0 need to correct.
Of course all of it could be done with dd or maybe with fastboot. But just FYI.
ps. Anyone who knows something about newest version of emmcbld.mbn or lab126 insiders =) feel free to send anonymous e-mail to 2457678atgmaildotcom. Thank you.

Reserved

sorry，I don't have the newest version.
i think we can only get it from lab126 or amazon.
by the way, in factory ,they have to flash the device to a special mode， and then reflash all the system images.

ONYXis said:
Reserved
Click to expand...
Click to collapse
Hope these files can help you. they are old version

bournezhang said:
Hope these files can help you. they are old version
Click to expand...
Click to collapse
Thank you. I already have it. Nothing interesting.

bournezhang said:
by the way, in factory ,they have to flash the device to a special mode， and then reflash all the system images.
Click to expand...
Click to collapse
there is no any difference, i use same protocol as Amazon. i can make fullflash instructions with system, cache, userdata, but I see no sense of this. just bigger download size - approx 2.5 GB.
With twrp you can flash what you want by yourself.

But most user's version is 4.5.2 or higher now .
Look forward this issue be solved.

really nice job

@FotixChiang , thanks. btw maybe "our friend" with that dev 4.1.1 firmare has this file for 4.x ?

I just followed your steps, but when I flashed the program failed. I then reset my device, but it no longer recognizes it as QHUSB BULK. All it says is "Unknown USB Device (Descriptor Request Failed)". Any ideas on how to get it back into QDLoader mode for another shot at flashing?

Hold power button long. Above 5 min sometimes. It always works.

ONYXis said:
First of all - this is works only if you bricked on firmware <=1314.3.2.6.
So it don't works for "rolbacked 3.2.8(7)" bricks(
Sorry but need leak of newest version of flash programmer for higher sw.
I understand that there is not many people with this type of bricks but it is better that nothing=)
Of course you can try - you can not do worse=) I test this method on 13.3.2.3 and 13.3.2.4.
Apollo users should read post to the end before doing anything!
Manual in progress. Additions and comments are appreciated.
Logs of flasher to examine errors locates at C:\Program Files(X86)\Xiaomi\MiPhone\
My English isn't perfect) - PM me with OP corrections.
​
1. Download archive - https://drive.google.com/file/d/0B2twXJIOgv-UR0dZTVJUeFFsVU0/view?usp=sharing and unpack it. Two folders inside - fw and tools.
2. Install ./tools/MiPhone2015731.exe
2a. For x64 system you need disable drivers signature verification before installing. Google it.
3. Start and setup Miflash:
3a. Press 'Browse' and select folder "fw" from archive. Press OK.
3b. Press down arrow on this button, Press "Advanced" and fill fields with files in folder 'fw' by "Browse" :
- flashprogrammer - .\fw\prog_emmc_firehose_8974.mbn
- raw xml file - .\fw\rawprogram0.xml
- patch xml file - .\fw\patch0.xml
- other fields no need to touch
4. Ok. Now you need put your device in QHSUSB Bulk - mode and install Drivers.
4a. Your device can be in this state already. Just connect it to PC.
4b. If you have working adb (who knows) - type "adb reboot oem-2" or "adb reboot emergency" in cmd (i suppose you know that is adb drivers and adb). This is reboot kindle into emergency mode Qdloader 9008.
4c. Your device is stucked at greylogo or bootlooping without adb access. You need fastboot cable. Reboot device with plugged fastboot-cable.
5. Navigate to device manager and check for new device named QHSUSB_BULK . Drivers will install automatically or you need install it manually from .\tools\QualcommDrv.
In device manager at COM-Ports section you must obtain HS-USB Qdloader 9008 (COMx) without exclamation!
6. Go to Miflash , press Refresh, you should see your com port and empty bar under "progress" section.
7. Press "Flash". You should see messages like "WriteFile position 0x00000000840000, size 131072"
8. If all gone successfully disconnect kindle from PC and reboot it by holding power+vol up.
8a. If unsuccessful - reboot device and start over. In this mode for reboot sometimes needs above 5 min holding of power button.
If you get "Opening port" after some loading - you probably have > 1314.3.2.6 fw version.
9. Grats. You are in TWRP. You could flash this stock 1314.4.5.5 image - http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914
10. BTW you aboot partition is 13.3.2.3 version so you can do procedure of unlock without downgrading to 13.3.2.3 - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Apollo users !!! - you need to replace recovery.img at folder "fw" with this one - https://drive.google.com/file/d/0B2twXJIOgv-UYzhORVczQ3E3cWM/view?usp=sharing
CREdits:
bournezhang - for leaked programmer.
FSmp - for testing at 13.3.2.4
For advanced users - this works with any unlocked devices too (aboot<= 13.2.3.2).
By filling "filename" at rawprogram0.xml you can flash any partition to your device. Big partition like system.img must be sparsed I assume and rawprogram0 need to correct.
Of course all of it could be done with dd or maybe with fastboot. But just FYI.
ps. Anyone who knows something about newest version of emmcbld.mbn or lab126 insiders =) feel free to send anonymous e-mail to 2457678atgmaildotcom. Thank you.
Click to expand...
Click to collapse
Great job bro. About one year ago I was reading many posts on this forum to get enough information to unbrick my Kindle Fire HDX (stuck on grey logo). by reading most of the posts related to Kindle Fire HDX I found out that the only way to unbrick it was a FactoryCable/ FastbootCable. so I made a factory cable and got my Kindle be recognised by my PC as Qdloader 9008 or Qcomm HS-USB Bulk or something like that. but after that I did not know how to flash files on it so my KFHDX was taking rest till today
thanks to you that I am able to revive it now thanks again. I have a lot of usefull files and information including some interesting drivers which might help you create tools or find other methods to unbrick the KFHDX. if you need some help or files just drop me a message to my inbox. I will be checking it frequently thank you

it's really worked method!
I restored gray logo (QHUSB_BULK) 3rd HDX 8.9 Apollo. I have been waiting this for 2 years))
the only thing I have not load the firmware http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914 - it's not loaded
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199 - it's work
BIG THX!

Thanks for response. I'll edit manual soon.

ONYXis said:
Thanks for response. I'll edit manual soon.
Click to expand...
Click to collapse
I congratulate you for your work and effort.
you are very good

need help.. I did the roll back, re-installed 4.5.2. 4.5.2 is now rooted. I followed the disable OTA instructions in the forum, (rename the file etc...)..
However that information may not be totally correct, because as soon as I connected to Wi Fi , kindle fire stated downloading 4.5.4. I shut the Wi Fi off, found another tutorial on disabling OTA updates. This one worked. However, I have a 100% downloaded update, and I'm fearful it will try to install itself. I need to know where to go with ES File Explorer to Delete this update file, so it does not install itself.
Thanks to all who can help.

why are you posted this here?
anyway, update file locates in /cache. need root to navigate there.
please do not offtop in this thread. thank you.

rlkellyjr said:
need help.. I did the roll back, re-installed 4.5.2. 4.5.2 is now rooted. I followed the disable OTA instructions in the forum, (rename the file etc...)..
However that information may not be totally correct, because as soon as I connected to Wi Fi , kindle fire stated downloading 4.5.4. I shut the Wi Fi off, found another tutorial on disabling OTA updates. This one worked. However, I have a 100% downloaded update, and I'm fearful it will try to install itself. I need to know where to go with ES File Explorer to Delete this update file, so it does not install itself.
Thanks to all who can help.
Click to expand...
Click to collapse
Third duplicate post in as many threads. Great way NOT to get noticed next time you need help.

I guess I should say thanks for the point in the right direction, but you coming across and telling me in different areas is not a way to get help. I posted in the wrong area to start with, and was told so. So thanks for the help.
---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------
[/COLOR]
Davey126 said:
Third duplicate post in as many threads. Great way NOT to get noticed next time you need help.
Click to expand...
Click to collapse

Ali Ejea Mc said:
Great job bro. About one year ago I was reading many posts on this forum to get enough information to unbrick my Kindle Fire HDX (stuck on grey logo). by reading most of the posts related to Kindle Fire HDX I found out that the only way to unbrick it was a FactoryCable/ FastbootCable. so I made a factory cable and got my Kindle be recognised by my PC as Qdloader 9008 or Qcomm HS-USB Bulk or something like that. but after that I did not know how to flash files on it so my KFHDX was taking rest till today
thanks to you that I am able to revive it now thanks again. I have a lot of usefull files and information including some interesting drivers which might help you create tools or find other methods to unbrick the KFHDX. if you need some help or files just drop me a message to my inbox. I will be checking it frequently thank you
Click to expand...
Click to collapse
Good evening: I have an Apollo HDX that is an continuous gray and yellow splash screen when booted.
I have no idea what OS version it is running since it has been a long while setting in my junk pile.
I also do not know the history of the HDX since I acquired the unit second hand.
It sounds like there is some hope for recovery?
Can someone point me in the right direction for getting this unit resurrected?
On my LINUX workstation I do not see any logging when plugged in using a standard USB cable:
However, when a Kindle fire HD factory cable (2012 HD Fastboot cable) is used to connect to the HDX, I receive this logging:
Jan 31 20:38:43 me-9100 kernel: [193518.636064] usb 1-4: new high-speed USB device number 12 using ehci-pci
Jan 31 20:38:43 me-9100 kernel: [193518.768771] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
Jan 31 20:38:43 me-9100 kernel: [193518.768779] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 31 20:38:43 me-9100 kernel: [193518.768784] usb 1-4: Product: QHSUSB__BULK
Jan 31 20:38:43 me-9100 kernel: [193518.768789] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
Jan 31 20:38:43 me-9100 kernel: [193518.769693] qcserial 1-4:1.0: Qualcomm USB modem converter detected
Jan 31 20:38:43 me-9100 kernel: [193518.769908] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Jan 31 20:38:43 me-9100 mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-4"
Jan 31 20:38:43 me-9100 mtp-probe: bus: 1, device: 12 was not an MTP device
Jan 31 20:38:43 me-9100 kernel: [193518.636064] usb 1-4: new high-speed USB device number 12 using ehci-pci
Jan 31 20:38:43 me-9100 kernel: [193518.768771] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
Jan 31 20:38:43 me-9100 kernel: [193518.768779] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 31 20:38:43 me-9100 kernel: [193518.768784] usb 1-4: Product: QHSUSB__BULK
Jan 31 20:38:43 me-9100 kernel: [193518.768789] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
Jan 31 20:38:43 me-9100 kernel: [193518.769693] qcserial 1-4:1.0: Qualcomm USB modem converter detected
Jan 31 20:38:43 me-9100 kernel: [193518.769908] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Jan 31 20:38:43 me-9100 mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-4"
Jan 31 20:38:43 me-9100 mtp-probe: bus: 1, device: 12 was not an MTP device
When USB is disconnected:
Jan 31 20:40:16 me-9100 kernel: [193612.201809] usb 1-4: USB disconnect, device number 12
Jan 31 20:40:16 me-9100 kernel: [193612.202101] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Jan 31 20:40:16 me-9100 kernel: [193612.202128] qcserial 1-4:1.0: device disconnected
Is the factory cable mentioned in this post the same factory cable used on the 2012 Kindle Fire HD?
I have worked on hundreds of the 2012 HD fires but, don't do anything with the HDX devices since they can't be bootloader unlocked. However, I would like to bring the HDX back to life it is possible. The tools for the HDX I see in this and other posts are for windows I presume and not LINUX?
Any help and direction would be helpful:::
Regards

adb devices does not see phone on linux

Hi Everyone:
I am sorry if someone asked this question before, but I could not find an answer that works for me. I just got my phone today and I want to root it. I am planning to use my laptop running Linux FC21. I have used adb on this machine before and it has work flawlessly. Here is what I have done:
- became a developer on the phone
- enabled usb debugging
- enabled OEM unlocking
- connected the phone to my computer.
- I get a notification on the phone saying "USB debugging connected"​- typed 'sudo adb devices'
- The list is empty.​
I have tried stopping and starting the sever with no effect. I have tried multiple USB ports and cables (USB-A to USB-C). That did not help. I have looked at dmesg and it sees the phone.
Code:
[email protected] ~] dmesg | tail
[ 1650.391982] usb 1-3: Product: PH-1
[ 1650.391984] usb 1-3: Manufacturer: Essential Products
[ 1650.391985] usb 1-3: SerialNumber: PM1LHMA792600274
[ 2128.638511] usb 1-3: USB disconnect, device number 16
[ 2133.666971] usb 1-3: new high-speed USB device number 17 using xhci_hcd
[ 2133.835601] usb 1-3: New USB device found, idVendor=2e17, idProduct=c032
[ 2133.835614] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2133.835617] usb 1-3: Product: PH-1
[ 2133.835618] usb 1-3: Manufacturer: Essential Products
[ 2133.835620] usb 1-3: SerialNumber: PM1LHMA792600274
Finally I have downloaded 51-android.rules from the web and added the line:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0600", OWNER="hal"
This did not help either.
So, HELP!
Thanks
----
EDIT: I tried both my Galaxy Note4 and my Zenwatch3 and they both worked.
----
EDIT: The phone never shows the popup asking if I want to authorize my computer.

Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.

NaterTots said:
Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, this did not work for me.

Have you tried leading your commands with ./?
This is required on Mac: ./adb devices

Airwolf79 said:
Have you tried leading your commands with ./?
This is required on Mac: ./adb devices
Click to expand...
Click to collapse
No, that will not make a difference. The $path is set correctly on the machine. If what you suggested was an issue, I would get "adb: Command not found" when I tried to execute it.
Thanks for the suggestion!

Do you have lastest ADB?
Sent from my PH-1 using XDA Labs

avd said:
Do you have lastest ADB?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Well, I have been working this and I think that you identified the problem. I have the most up-to-date for my OS, but it is old and I can't get newer versions to work. I had to move on to Windows :crying:

The instructions I found suggested creating a user group and adding myself to it:
Code:
sudo groupadd androiddev
sudo usermod -aG androiddev your_login_name
Then grant the permissions to that group rather than directly to my user account:
Code:
sudo sh -c "echo 'SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="androiddev"' >> /etc/udev/rules.d/51-android.rules"
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.

bjs339 said:
The instructions I found suggested creating a user group and adding myself to it:
Then grant the permissions to that group rather than directly to my user account:
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.
Click to expand...
Click to collapse
When you run fastboot run it as super user.
Modify the flashall and prepend sudo in front of every line
Sent from my PH-1 using XDA Labs

Mine has never seen my device when running adb devices,however commands to give write permission still worked
Sent from my Essential Phone using XDA Labs

Pixel 4 bootloader issue

Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?

burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the factory Google image back to the phone?
burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the Google stock factory image?

I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel

burntpuppy said:
I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel
Click to expand...
Click to collapse
If it's detecting the device your fine. Go here, https://flash.android.com/build/7005429?target=flame-user&signed. and re-flash the firmware and you will be good to go.

I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working

burntpuppy said:
I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working
Click to expand...
Click to collapse
You need to re-flash everything. It should do all the work for you. Maybe you flashed the wrong boot.img? Here is the main page for all devices. https://developers.google.com/android/images Select your device, you can choose flash and it will do it all for you or you can download the image, extract it all to your adb folder, double click flash-all and it should flash everything on its own.