Hey everyone, I'm new here , and I thought I'd start with a quick question.
My HTC Universal is a bit handicapped (bought it off a friend who said it was broken, apparently the USB plug terminals weren't fully soldered, but I couldn't connect all of them and it will only charge through USB and nothing else.)
If someone has an HTC schematic or a high-res image of the motherboard, I could possibly try to revive USB transfer capabilities (but that area is a bit damaged from not having a small enough soldering iron ), *OR*, if there is a way to reflash from within the OS using a SD card, that would be great.
Hope someone knows the answer to this, thanks!
Edit: And if it's of any possibility, how much would a replacement board be? Enough to satisfy a 100% working USB connection?
No ideas? If someone can at least give me a schematic or a high-res pictures of both sides of the board then I could possibly fix the USB to 100% functionality.
If you check the WIKI for the Universal you shoul be able to find a link for downloading the Service Manual. It shows the total un-assembly-re-assembly process step by step. You may also find instructions for SD flashing there as well. I have never flashed my Uni by SD, but I have don other phones like that. Most of the HTC's are capable. There is even info in the Service manual telling you what to have on the SD and wht to name the files from proper use. Give it a search.
Thanks! I have the manual already so I'll give it a look over. I wasn't entirely sure and I thought I wouldn't see anything but I'll look more in-depth .
Just a side note, does anyone know where I can get a replacement motherboard and how much it will be? Just curious, as that option might be available if it isn't too expensive.
I managed to get 2 of my HP Veers bricked while trying to update the modem firmware. This happened while trying to test a release for the community with an update from WebOS 2.1.2 (latest official release, to 2.2.3 (latest available leaked version)).
The devices still power on (HP Logo), but there's no way to get them recognized via USB anymore or to get them into recovery mode.
It looks like the only option to get them working again would be via JTAG flashing.
It uses the Qualcomm MSM7230 chipset, pictures of the boards can be found here:
Google for "Veer disassembly" since I cannot post links yet.
Anyone got any suggestions about how to revive it, what tools to use, what JTAG pin-layout might be etc?
Thanks in advance
Probably an answer...
As a fromer HW developper I would avoid opening a device if it comes back under warranty repair. JTAG needs five pins: TDI, TDO, TMS, TCK and TRST
The magnetic Veer port has five pins. The magnetic Veer port can attach an USB as well as a headset. So these pins are multifunctional.
Probably there is also some sort of voltage reference that is able to detect JTAG on those pins.
I also bricked my veer due to simple stupidity ;-) Anyhow I think it is a good chance for a hands-on. Do you have any USB/JTAG cable and appropriate SW?
Probably we need to kill a magnetic USB-cable to get proper contact...
what's your intension, could that be worth a try?
cheers Win07
Hi Win07,
Sorry for the late reply, I wasn't around here for a while. I currently don't have a JTAG interface available but was looking at the RIFF Box which seems to support the MSM7230 chipset and would be able to do probing of the pads.
I'm just not sure if it's any good. I'm happy to invest in this device if it would give us some degree of certainty it might work?
I used a multi-meter to measure the voltages of the different pads, see in the picture. I suspect this should be JTAG pads. Anyone who has any clues, any help is highly appreciated!
its easy to brick a veer?
rpadula said:
its easy to brick a veer?
Click to expand...
Click to collapse
Not by an end-user, no. Stick to Preware and you'll never brick it.
-- Rod
Herrie82 said:
Anyone got any suggestions about how to revive it, what tools to use, what JTAG pin-layout might be etc?
Thanks in advance
Click to expand...
Click to collapse
Maybe check this post over at WebOSNation
forums.webosnation.com/hp-veer/310041-disassembled-veer-circuit-board-chips.html
good luck
Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730
OK, will do. Thanks!
try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
As far as I can tell, the title says what the tablet's model is although I'm not 100% sure as it doesn't have any stickers or decals giving any clues as what it's exact model is other than it has 8GB of storage.
My brother found it in a house he was remodeling for someone. The last occupants of the house were long since gone and the owner (who my brother was doing the work for) said he could keep it and since he already has a tablet, he gave it to me.
The downsides to this are;
1. It has no SD card. But I can easily go out and buy one.
2. It's locked with a passcode and since it's original owners are long gone, there's no way to get the code.
The passcode can range from a single digit and above so guessing was obviously out of the question.
I tried looking up the recovery button sequence and after trying countless different ones that I've found, I've had no luck.
Windows 7 recognizes it as a USB Composite Device, I've tried the instuctions found in google to get it to recognize it as a tablet, but so far no luck there either. The tablet doesn't even show a prompt for USB Mass Storage when it's plugged in. It simply displays the passcode number pad.
I've considered flashing it but LiveSuite is a joke. After trying to decipher all the broken english, it wont even recognize the tablet. I found the firmware on the MaPan website after digging through all their tablet models and comparing the pictures until I found the exact match of the one I have.
Any idea how I can make this tablet usable? I have Ubuntu 12.04 in virtualbox as well if using that will make it easier.
Also, if anyone asks for pictures, I'm sorry as I don't have a camera. I have a cheap phone but it doesn't have one.
So I was given 5 phones recently. After testing each one I found that the LG K30 (or at least I believe it to be this model) does not function. When plugging it into my computer I see QHSUSB_BLUK appear on my PC. From what I have searched I believe this device may be bricked but I am not sure why or by what. I don't believe the person to have owner this before me would try to do anything to it but I am unsure. I am wondering if anyone else has had this issue and if anyone may know a fix to this.