Related
i've seen numerous posts about this all over the place and couldn't find a fix anywhere
after providing logs to jcsullins he managed to solve my issue and now have a fully working TP again
heres the thread i created over at rootzwiki http://rootzwiki.com/topic/37804-battery-question-mark-issue/
and heres the link to the irc post for jcsullins to guide people through it
only created this here as i know a lot don't go on rootzwiki but many have this issue
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__310#entry1068329
hopefully this will help someone out and resurrect your thought to be dead TP
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Thanks
Thanks, it helped me a lot!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
I was able to fix my touchpad with this rootzwiki guide above. My touchpad had JB installed, after a battery drain it was completly dead. I was able to charge it by cutting down an old USB cable and charging the battery alone (touchpad had to be opened).
FYI (Tried ubuntu 12.04.2 in 2 different machines, the tpdebrick only worked on my alienware on the Dell with 1GB of ram it did not worked. The alienware has 2GB of RAM.)
The battery took almost 50% charge, then tried booting it up and nothing (only got question mark).
Theres a small button inside the unit in the charging module, I pressed it, and the unit turned off (it was the only way I could get it to shut down.
Did the debrick process, after that the touchpad would not charg via the USB port and only via the touchstone, so I did the ACMEUninstaller to remove android and it's good as new again. The problem for me was caused by the JB android installed. I had no problems when it had ICS.
Followed the instructions in the link from the first post. And it works!
Was skeptical as instructions seems very complex, but I thought I got nothing to lose. In summary, it was straight forward and you just need to:
1. Download Ubuntu 12.04 LTS and burn the iso to a CD/DVD.
2. Boot up your PC with the Ubuntu Installation CD.
3. Select Try Ubuntu rather than Install.
4. Follow the listed steps/instructions. PS: If you see a "space" for the terminal command, there is a "space" required when you key in the terminal command. And when the script is running, its working, even though you see nothing on the touchpad screen. When "All Done", the touchpad simply rebooted by itself, and ran through the usual boot-up sequence.
Good luck.
Its fixed!!!! Thanks!!!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
Thanks so much!!! I am so far from knowing how to fix a computer or tablet and my daughters HP touchpad did all of the things mentioned and I did the debrick and It is up and working. I was nervous to try this debrick thing since I have no clue how to do computer stuff but all the directions were clear and easy. Thanks!! I have a happy daughter
sudo ./tpdebrick command not found
hi dude, thank you for the post but i always got the message sudo ./tpdebrick command not found, could you help me?
note: the tpdebrick file is into the folder u.u
dfu-util and fastboot missing
[email protected]:~$ cd downloads
bash: cd: downloads: No such file or directory
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip tpdebrick-v004
Archive: tpdebrick-v004.zip
replace tpdebrick-v004/tp16.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: n
replace tpdebrick-v004/ebr16.bin? [y]es, [n]o, [A]ll, [N]one, [r]ename: N
[email protected]:~/Downloads$ cd tpdebrick-v004
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$
why is this coming up? i cant find any links to where i would find dfu-util or fastboot or where it needs to be.
What version of Ubuntu are you using? Is it 32 or 64 bit?
gtallmadge said:
What version of Ubuntu are you using? Is it 32 or 64 bit?
Click to expand...
Click to collapse
I used this particular file and made it into a bootable usb stick
releases.ubuntu.com/12.04/ubuntu-12.04.4-desktop-i386.iso
ubuntu.com/download/desktop/create-a-usb-stick-on-windows
It was a lot easier than I thought, just did the tpdebrick today :good::good:
fixed for the right links
Glad it worked for you. I knew the directions said to use Ubuntu 12.04 which is still available so it is good to know 14.04 which is
the current Long term release of Ubuntu works as well.
I'm sorry, but it was this one that I used
releases.ubuntu.com/12.04/
Thanks for the info..I obviously misread your post.
Questionmark of Death on TP
First problem I ran into, couldn't find a working link for the webos doctor, after an hour of searching, came across a link but xda won't let me post since I don't have 10 posts.
w w w . adbtoolkit.com /rooting/devices/hp/tenderloin/webOS-Doctor/wifi/#.VGYTS9YghCW
Next issue, when it told me to hold my power+vol down+home button down, it would time out with some error( I think it said qdl not found something like that). Tried a few times, then tried a samsung cable for my phone instead of the original touchpad cable, and that worked. Thanks to the guy at rootzwiki for the information.
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
ractar28 said:
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
Click to expand...
Click to collapse
It's not deleted. You have to log into rootzwiki from the error screen, and the link will load.
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Gamedays said:
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Click to expand...
Click to collapse
Do you happen to have the guide as well, or am I missing it somewhere? I was also unable to get the registration process to work... the step I am on specifically:
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
Thanks!
Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970
Soulace1970 said:
Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970
Click to expand...
Click to collapse
If you've made it this far after running all of those Novaterm commands, you're in for a treat. Just turn off your HP Touchpad, run the WebOSDoctor 3.0.0 by double clicking it on your desktop (if you can't run it, you need to install java, see java.com) Once the dialog box tells you to connect your Touchpad, make sure to hold the up power button when you plug it in, this will boot you to the USB symbol, which is Webos Recovery. Click next button on the dialog box on your computer. It will do the rest. Make sure to charge the unit for awhile with it off if possible (hold home+power for 10-20 seconds after the HP symbol shows up to force it to turn off), as it's a good idea to have at least 30% battery when you do. I've done this process many times to reset my TP when I tried out Ubuntu.
Edit: By the way, you need to extract that zip file prior to running the .jar file (which is the WebOSDoctor program)
fixed
I got my brothers... tried everything... saw this...
http://rootzwiki.com/topic/38786-tpdebrick-v004/
downloaded ubuntu like it suggested... ran it as a live cd... downloaded the stuff... followed the directions (Spelling is CaSe sensitive in ubuntu) and holy crap... it worked!!!
Was hoping someone has the tpdebrick zip package, it's unavailable on goo.im right now as they migrate/move equipment. If I could get a mirror for it that would be great.
lmt1979 said:
Was hoping someone has the tpdebrick zip package, it's unavailable on goo.im right now as they migrate/move equipment. If I could get a mirror for it that would be great.
Click to expand...
Click to collapse
I can't post the URL as a link, but this should get it ://d-h.st/users/jcsullins
HP TOUCHPAD DEBRICK Linux Live CD
I have created an Ubuntu Live CD with all the necessary files to Debrick the Tablet from TP Debrick v005 by jcsullins.
If there is any Tablet that did not finished the flash process, run this Live CD and perform the Debrick again.
If you do not know the Tablet model do the following:
Flash using the 16 GB, then connect to charger. If the home LED does not come on after some time then.
Flash using the 32 GB, then connect to charger. If no LED light then
Flash using the 64 GB.
All process must finish in " ALL DONE "
Click HERE for the HP TOUCHPAD DEBRICK LIVE CD
For information about charging a Tablet after been store for 9 years go here:
https://forums.webosnation.com/hp-touchpad/332615-hp-touchpad-won-t-turn-brand-new-never-opened.html
How To UnBrick A Hard Bricked Moto X
Hii , First of all I wanna thanks to this awesome scrpit by @s5610 who brought my phone from dead to alive , I think i am the first guy to unbricked the hardbricked phone using this script lol , My phone was hardbricked because i was testing my kernel and entered wrong path in partition due to which i got hard bricked i was worried for my phone , Service Center was asking for 7k in Indian Rupees , i was hopeless then i gave a try to this method , followed all steps written here and then finally i entered to fastboot menu of 30.B7 Kitkat As i was using 30.B7 Bootloader earlier and then i flashed My gpt.bin and S-partition and flashed my stock rom voilla !! and my phone booted the aim was to share this post was this method was on page 42 and only less guys have seen this post , so i created a new thread regarding this
All Credits Goes to - @s5610
s5610 said:
Unbricking Guide for any Moto X Gen 1 (wire trick)
Download, and unpack supplied zip to any disk, C: or D:, in root folder. Install driver by launching Qusb.drv.inst.msi, then open Windows' Device Manager, and see if you got "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
If yes, you see it, go to software part below. If it's not there, a full disassemble of the phone is needed to get close to back side of motherboard (google for "iFixit Teardown Moto X Guide" for step-by-step instruction).
So, when you are inside, disconnect the battery first. No need to pull it out, it's glued. Now get to back side of motherboard, and very very gently gain access to the lower left corner of ARM+DRAM shield (see picture). I've done it with Stanley knife. Also you can use miniature nippers - but very carefuly! Once you get access to inner space of shield, use tiny wire to short special pin to the ground (see picture), then connect USB cable, and in the moment when you see "QHSUSB_DLOAD" device (or "Qualcomm HS-USB QDLoader 9008" if driver is installed) pop out in Windows' Device Manager, quickly remove the wire. The goal is to have "Qualcomm HS-USB QDLoader 9008" in "COM & LPT ports" section of Device Manager. If it is achieved, we are done with hardware, and move on to soft part.
Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat
(if you got error like "No data read from USB..." etc, just skip to next step)
Next launch either
- .Boot_KK_4.4.2_B4.exe,
or .Boot_KK_4.4.4_B7.exe,
or .Boot_LP_5.0.2_BC.exe,
or .Boot_LP_5.1.0_BD.exe,
or .Boot_LP_5.1.0_BE.exe
- depends on Android version your phone has last time. If you don't know what you need, begin with first one.
Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat
Phone should go into fastboot mode! If it doesn't, repeat previous step trying higher version. But don't try to flash BC, BD, and BE, if you didn't install Lollipop on this phone!
OK. Disconnect the USB cable, connect the battery, connect again USB cable (fastboot don't work, if don't see battery). Launch next bat-file:
RUN_gpt.bin_flash.bat
The phone will get in fastboot, ready to be flashed by appropriate firmware. If it is official RSD (SBF), delete from xml strings consisting gpt.bin and motoboot.img for safe flashing.
...
Download link: http://www.mediafire.com/download/3e38rr3wy28s071/Moto.X.Unbrick.zip
This guide was brought to you by s5610
Links that this guide is based on (where I took files and general idea):
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
http://forum.xda-developers.com/mot...-moto-x-t2629057[/url[/QUOTE][/QUOTE][/QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Not sure if additional thread is necessary )
UPDATED
The best resurrection method for Moto X is here.
Can Someone re-upload that file? Thanx!
Please upload the mediafire link...
Plz plz.. I have bricked my phone. It seems that this procedure will work for me. Please upload and save my life.
even i have bricked my moto x...need a working download link..please.
https://drive.google.com/file/d/0B3EDzuzDCakzdWxHa2RWVDJhRXc/view?usp=sharing
Cannot install qsub.drv.inst.msi on my windows 10...says failed to attribute and failed to delete qcusbser.sys.
Thanks
Can we write the full firmware through Qload 9008 mode ???
HI I have a question. I bricked my gf's phone while trying to unlock the bootloader and I am not able to turn the phone on. Only positive feedback is that when I plug it in to the computer, I can hear a notification on my computer. I followed your guide. I can see the "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
Then I followed your software instructions. When I run the RUN_blank_bootloader_flash.bat, I get the following
Code:
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
qflash - com3 is an invalid port
Invalid COM port enteredBlank flashing successful
Device will now enumerate in fastboot mode
Then, I followed the rest of the instructions by trying each .Boot .exe and waitng 10 seconds and finally with RUN_moto_x_bootloader_flash
but I am getting the following error.
Code:
C:\Users\cxx\Desktop\Python27>python qdload.py MPRG8960.bin -ptf _boot\partiti
ons.txt -pt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com3
Traceback (most recent call last):
File "qdload.py", line 815, in <module>
main()
File "qdload.py", line 762, in main
tty = openTTY(args.ttyPort)
File "qdload.py", line 174, in openTTY
tty = serial.Serial(port=tty_path, baudrate=115200)
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 38, in __init
__
SerialBase.__init__(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\serial\serialutil.py", line 282, in __init
__
self.open()
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 66, in open
raise SerialException("could not open port %r: %r" % (self.portstr, ctypes.W
inError()))
serial.serialutil.SerialException: could not open port 'com3': WindowsError(2, '
The system cannot find the file specified.')
C:\Users\cxx\Desktop\Python27>pause
Press any key to continue . . .
please help.
Thanks.
Device Shows As USB Input
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
shengslogar said:
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
Click to expand...
Click to collapse
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
liveroy said:
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
Click to expand...
Click to collapse
Will do! I think I did try charging it awhile ago, but I'll give it another shot.
can my phone be unbricked?? here is the error log:
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
een reset back to blank flash mode. Usually this is caused by power supply issu
s. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries
I am trying to install the drivers and it will show up as qhsusb_dload for about 5 seconds then reverts back to Relink HS USB QDloader 9008. Should i try the wire trick? It will say that the Qhsusb drivers are installed but always changes.
Ok so I installed Ubuntu 16.04 onto a fladhdrive and booted it.
I downloaded the files debrick005 and webdoc.jar files. I put them in my home folder. This is where I having problem. I can see the files in the visual part, but ls in terminal sees them but they are listed in red? Not sure if that's normal. I tried to unzip the folder in terminal with no luck. I was able to extract clicked the visual folder and clicking extract.
Everything seem ok even thought I couldn't unzip in terminal. When I run ./debrick 16 it checks the script and says it can't find the webdoctor.jar. it's in tpdebrick folder visually...
I'm kind of a linux noob . Surprised I got this far. Not really sure what's going on. The .jar file is in there and the file names match.
Anybelp from you guys would be awesome. My tp has sat with questionmark battery error for years....
Ok so I moved the .jar to the home folder. The script ran. It seemed like it was working til it gets to copying A6 files. It's spits "unable to negotiate with 192.168.7.7 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-shal. Lost connection. Copy failed aborted.
I'm not sure why the edit to my sshd_config isn't working as described.
I tried to modded tpdebrick script posted a few posts back with dellie-hellman support, Moved it to the tpdebrick folder and renamed it and replaced with the original tpdebrick script. Still same error when trying A6 firmware.
Edit: when I open sshd_config in gedit, it's blank except for the code changes I made. Pretty stuck at this point and don't know what should be there to begin with.
So I solved the problem. I ran the script in ubuntu 14. No modifications to the sshd_config needed. Scripts ran and said charge for a while. Couple hours later, my touchpad, which has sat unusable for 2yrs, is not operational. Hope this helps someone else who runs across this problem.
HP TOUCHPAD DEBRICK Linux Live CD
I have created an Ubuntu Live CD with all the necessary files to Debrick the Tablet from TP Debrick v005 by jcsullins.
If there is any Tablet that did not finished the flash process, run this Live CD and perform the Debrick again.
If you do not know the Tablet model do the following:
Flash using the 16 GB, then connect to charger. If the home LED does not come on after some time then.
Flash using the 32 GB, then connect to charger. If no LED light then
Flash using the 64 GB.
All process must finish in " ALL DONE "
Click HERE for the HP TOUCHPAD DEBRICK LIVE CD
For information about charging a Tablet after been store for 9 years go here:
https://forums.webosnation.com/hp-touchpad/332615-hp-touchpad-won-t-turn-brand-new-never-opened.html