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.
Related
I was given an HTC Incredible the other day, and I quickly found out that the digitizer was non-functional, so I took it apart and found obvious liquid damage inside. Several areas of the board were crusted over with what I assume to be residue from the evaporated liquid. I remained hopeful that the only problem was a dead digitizer, but after carefully cleaning up the board, I noticed some scorched resistors near the digitizer's ribbon connector on the motherboard. On the off-chance that I misdiagnosed the cause of the dead touchscreen, I restored it to factory via recovery, but as I expected, still no go, of course.
It's frustrating, because the device is in beautiful shape in every other way. Screen looks great, not a single scratch on the phone itself, it boots into recovery perfectly as well as into Android.
I fully realize that I will never have this phone working as it was originally intended without swapping out the board, which I don't really plan on doing. I also have no interest in using this as a phone. I'd like to see this phone repurposed as a headless Linux box on my home WLAN. With its specs, it should be able to run Debian and Asterisk quite well (works great on my Seagate DockStar with 128MB RAM/700MHz ARM5-based SoC.) I just hate to see an otherwise perfectly good embedded computer go to waste because I can't enable debugging via the touchscreen.
Is it possible to use a breakout board attached to the microUSB connector to utilize any sort of external input so that I could jump into the phone and turn on debugging/root the device? Or would that require HID drivers to be installed on the device beforehand?
Another idea that I've considered is possibly reflashing it with a rooted ROM or maybe changing some settings on it via CDMA Workshop, I would still need to get into mode for that by pressing ##3424#, right? Argh. Is there another way?
Do either of these options sound viable? Any other suggestions? It should go without saying that I'm well aware that this could be a brick already, but it just seems as though there must be SOMETHING that can be done to at least give me rooted ADB access in the future.
Thanks in advance!
I'm guessing I'm out of luck? Either way, it's not a big deal. It's not as though it cost me anything, but it'd be nice to put it to work in some way. As a Linux geek, there's always a nagging feeling I get when I see a Linux-based device sitting in the corner being under- or non-utilized. Especially embedded.
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
HELLO,
i would like to try to replace the nand chip of my bricked tv box with a new chip
this because the original chip has been damaged shortening two pins trying to put the device in mask rom mode
my device is t-r42 based on rk3188
the price of the nand flash is about $4,
i can found it on some chinese online store
i hope that replacing the nand, my device will go to mask rom mode, enabling me to do the firmware loading through pc (rkbatchtool)
i know that this mode has been designed specifically to load the firmware the first time,
so i hope my device will go to this mode the first time i power on it after replacing it
any suggestion?
any hint?
i know this must be done with :microscopic` attention
thanks!!
Vicolodo said:
HELLO,
i would like to try to replace the nand chip of my bricked tv box with a new chip
this because the original chip has been damaged shortening two pins trying to put the device in mask rom mode
my device is t-r42 based on rk3188
the price of the nand flash is about $4,
i can found it on some chinese online store
i hope that replacing the nand, my device will go to mask rom mode, enabling me to do the firmware loading through pc (rkbatchtool)
i know that this mode has been designed specifically to load the firmware the first time,
so i hope my device will go to this mode the first time i power on it after replacing it
any suggestion?
any hint?
i know this must be done with :microscopic` attention
thanks!!
Click to expand...
Click to collapse
your going to have to find someone with a hot air rework station to unmount and or remount a new chip. the thing of it is, the pcb has to have perfect traces,,, 0 damage. even if that is met, unmounting and remounting a new chip in a perfect world takes a lot of skill and experience. will it get you into mask rom mode,,, I would guess yes. far as I understand it, thats a hardware thing not a os thing (os=firmware). Unless its something you just want to tinker with just to see if you can do it I wouldnt bother. Thats just me. I have crashed units over and over and got into mask rom mode doing the pin short, purposely trying different firmwares to see if they would work. I am not sure if mask rom mode will happen with out the pin short on a blank chip. maybe thats another question.
if you find someone local that does rework on surface chips, best bet would be ask them. Also a better answer here at least for me would be a close up picture of the chip you speak of, it would probly tell a thousand words. I have done rework, not in the past 5 years but I have. it takes a extremely steady hand and a good feel for when the solder is fluid. Theres tricks to it, do it wrong and theres no fixing the torn traces. Maybe craiglist would point you to someone who does this sort of work in your area. Possibly a local flat screen tv repair center may be able to direct you to someone local also, they are packed with sm chips.
Just some thoughts
stinkster said:
your going to have to find someone with a hot air rework station to unmount and or remount a new chip. the thing of it is, the pcb has to have perfect traces,,, 0 damage. even if that is met, unmounting and remounting a new chip in a perfect world takes a lot of skill and experience. will it get you into mask rom mode,,, I would guess yes. far as I understand it, thats a hardware thing not a os thing (os=firmware). Unless its something you just want to tinker with just to see if you can do it I wouldnt bother. Thats just me. I have crashed units over and over and got into mask rom mode doing the pin short, purposely trying different firmwares to see if they would work. I am not sure if mask rom mode will happen with out the pin short on a blank chip. maybe thats another question.
if you find someone local that does rework on surface chips, best bet would be ask them. Also a better answer here at least for me would be a close up picture of the chip you speak of, it would probly tell a thousand words. I have done rework, not in the past 5 years but I have. it takes a extremely steady hand and a good feel for when the solder is fluid. Theres tricks to it, do it wrong and theres no fixing the torn traces. Maybe craiglist would point you to someone who does this sort of work in your area. Possibly a local flat screen tv repair center may be able to direct you to someone local also, they are packed with sm chips.
Just some thoughts
Click to expand...
Click to collapse
thank you very much,
i will let you know!!
Vicolodo said:
thank you very much,
i will let you know!!
Click to expand...
Click to collapse
A quick alternative for establishing that it is only a faulty NAND is to try booting Linux from an SD card. If that works, then you could look around for someone who has created running Android from SD card for your device and you could at least still use your device in the interim.
HI
My wife's phone (i9300 galaxy S3) has gone wrong and it went off without battery.
I found a new battery, but it lasted only one day. I thus decided to take it for repair,
as I think that this is the charge connector that is broken, but actually, the tech told me that it was probably the motherboard,
as when it used a tool to plug it to the direct charge ports on the side, the phone only bootlooped.
Thing is:
My wife's phone wasn't using cloud or external SD,
it was not rooted.
I tried some android toolkits to connect it, but odin or adb don't detect it, so I have no chance to try and put some new kernel on it.
It has no recovery mode, and when in download mode (1st screen), it actually doesn't last long before it reboots anyway.
Choosing some option will also make it reboot.
So I think it is failed beyond software repair.
But if you have suggestion for this (the tech was at a small street stall and I don't expect him to be high level, no offense, but he seemed to only perform two repairs, screen and charge flex boards, so not much more able than me if he can't go beyond this), feel free?
So my second question is :
Does anyone know how to retrieve the internal storage of the phone without breaking it, and reinstall it in a working way on a new motherboard?
Or alternatively, on an emmc reader such as those used for raspberry cards and so on? (I don't want to put some link, I don't want my message to be filtered)
The photos on this chip are priceless for us, and I would even pay professional to retrieve these (I would prefer not having to, because money doesn't exactly come cheap to me, but I guess I won't be able to make it alone.
So if you know some repair service in Europe that would be able to perform such task, I would be grateful for your sharing of such knowledge.
I saw an alternative in malaysia, but it feels a little too far for being able to do something in case of problem.
Thanks for your attention and time.
UPDATE 24.11.20
I have recovered my HU by reading the whole night on this forum and TO THE AMAZING work of several people here.. especially GREAT GREAT thanks to marchnz and to scorillo_ro I build myself the USB cable and followed all the instructions I could find. With some moments of headache .. finally I flashed a new ROM and it booted up!!!
I have to go down on my knees to you guys for the super AMAZING work you have done. Wihtout you I woulld be now 180€ poorer. (new HU).
___________________________
When booting I get this errors...
I got a MTCE_LM PX5 unit (8Core A53 CPU 2GB RAM)
It is always very difficult to enter Recovery so I tried several times but it doesnt work. Either I just didnt mage it right or the recovery is broken.
In the pictures you can see 2 different messages. I have the feeling the long message version is when it normally tries to boot into the OS but fails.
The short message looks like when I managed to get into recovery reboot but it fails too.
Or its the same message .. it just blinks up for 10ms or something and dissapears and then blinks back after 5 secods ... I had to take like 20 photos to catch it. So maybe its the same actually.
Anyone has a clue what I can do from now on?
Great to hear another success story.
It took alot of effort to develop the method, for which was made possible by a member posting the schematic diagram to the forums for the benefit of all. Your post helps other too, so thanks!
Thanks again for the endless hours you put into developing the esiest method possible (for this SOM).
I am REALLY pissed at the Chinese somehow. They develop great stuff sometimes but fail to think over the edge. It is so easy to destroy your OS by small or stupid mistakes. And then there is no OTG to easily reflash the rom. I mean the hardware supports it. They could (and luckily and finally some new models support OTG on at least one USB port right away). But why was this not implemented right from the first designs for the headunits is puzzling me.
I would love to help anyone who needs help. But I have the PX5 HCT V4 SOM so you people wrote exactly how to do it for this specific SOM... I am not sure I can add anything of what wasnt said already.
I just had 2 main issues. The USB cable was found but not recognized at first.
So what I figured out was that you should not use more than 2 resistors to make the voltage division (thats what I did first) and I just had 2.8V on the division. I did it fast and not clean, means. No really good soldering connections.
Then I rebuild the whole thing used a good cable just 2 resistors (2kOhm and 3.3kOhm) and I soldered everything as clean and as compact as possible with least distanced to each part. So it gave me 3.1V on the division.
This was recognized immediately. Ahh.. and it helps too if you can use some contact spray for electronic parts. Because the pins sometimes do not sit well inside the SOM board.
Then the flashing of the ROM didnt want to work. It gave me an error on downloading the firmware.
Solution was to simply erease the flash memory.
But everyone who goes to your thread and reads at least the first 20 pages gets rather the clue on the minor issues. But its actually all written in there... just need to read it