I posted this over at SD, but not sure that gets the traffic that XDA does so I'm double posting...
*** Original post ***
I was upgrading from an old version of VeganTab to Brillant Corners. I NVFlashed to 1.1 3588 and made sure things worked. I then nvflashed to 1.2 4349 and let things boot up. Everything seemed to work. I then put the BC update.zip on the sdcard and rebooted to recovery which installed BC. I also installed the supplement. Everything worked although I noticed some instability in BC, I gave it a few days but it just didn't seem right so I nvflashed back to 4349.
I was going to reinstall BC but after I nvflashed 4349 I had some issues... I ended up getting a magic number mismatch and when I shut off the tablet and tried to start it again I no longer got any birds or any gtablet screen. It didn't seem like anything was happening. I panicked a little and started reading the recovery options over at the dummies site. I talked myself into cracking open the tab and trying the unplug the battery method of getting back into APX mode. After turning on and off the device a few times, I believe I also ended up hitting the reset button inside the case, I finally noticed that when I was powering on the tab it was going straight to APX mode without showing the birds.
I then nvflashed back to 4349 and booted up. I put the tab back together and when I got booted back up I noticed that I now had no touch screen. My buttons work (home, back, etc...). I could plug in a mouse and click around. But the screen didn't register any touches. I started reading about the touch screen and trying things. I flashed back to 1.1 different roms, flashed back to 1.2. Nothing fixed the screen. I ran the fix screen calibration from the 1.2 recovery and also by putting the file on the sdcard and external sdcard.
I also let the battery drain all the way dead and tried reflashing and recharging and still had no luck.
I also cracked the tab back open to check all the connections. I can't find any reference as to what cord is the connection for the touch screen. Everything internal looks plugged in and ok. I'm always careful with electronics, I have a desk for working on them and have been playing with them since modding PS1's back in the late 90's.
Does anybody have any ideas, anybody head of this. Did some hardware get ruined and do I have a broken tab. I have one of the original tabs, bought when they first appeared at Staples last fall.
*** Somebody suggested running the Code Detox from the dummies site ***
Well I did the detox, after wiping and using the format nvflash I ended up with a magic value mismatch. I used the internal reset button to get the device to connect in APX mode and successfully flashed back to 1.1 3588. Booted up normally but the touch screen is still not responsive. I'm not sure what else to try. I might have just borked the device. I may try completely disassembling the table and reassembling it to make sure nothing got disconnected. I'll also inspect the connections to make sure no wires look damaged.
Anybody else have any other ideas?
bmasephol said:
I posted this over at SD, but not sure that gets the traffic that XDA does so I'm double posting...
*** Original post ***
I was upgrading from an old version of VeganTab to Brillant Corners. I NVFlashed to 1.1 3588 and made sure things worked. I then nvflashed to 1.2 4349 and let things boot up. Everything seemed to work. I then put the BC update.zip on the sdcard and rebooted to recovery which installed BC. I also installed the supplement. Everything worked although I noticed some instability in BC, I gave it a few days but it just didn't seem right so I nvflashed back to 4349.
I was going to reinstall BC but after I nvflashed 4349 I had some issues... I ended up getting a magic number mismatch and when I shut off the tablet and tried to start it again I no longer got any birds or any gtablet screen. It didn't seem like anything was happening. I panicked a little and started reading the recovery options over at the dummies site. I talked myself into cracking open the tab and trying the unplug the battery method of getting back into APX mode. After turning on and off the device a few times, I believe I also ended up hitting the reset button inside the case, I finally noticed that when I was powering on the tab it was going straight to APX mode without showing the birds.
I then nvflashed back to 4349 and booted up. I put the tab back together and when I got booted back up I noticed that I now had no touch screen. My buttons work (home, back, etc...). I could plug in a mouse and click around. But the screen didn't register any touches. I started reading about the touch screen and trying things. I flashed back to 1.1 different roms, flashed back to 1.2. Nothing fixed the screen. I ran the fix screen calibration from the 1.2 recovery and also by putting the file on the sdcard and external sdcard.
I also let the battery drain all the way dead and tried reflashing and recharging and still had no luck.
I also cracked the tab back open to check all the connections. I can't find any reference as to what cord is the connection for the touch screen. Everything internal looks plugged in and ok. I'm always careful with electronics, I have a desk for working on them and have been playing with them since modding PS1's back in the late 90's.
Does anybody have any ideas, anybody head of this. Did some hardware get ruined and do I have a broken tab. I have one of the original tabs, bought when they first appeared at Staples last fall.
*** Somebody suggested running the Code Detox from the dummies site ***
Well I did the detox, after wiping and using the format nvflash I ended up with a magic value mismatch. I used the internal reset button to get the device to connect in APX mode and successfully flashed back to 1.1 3588. Booted up normally but the touch screen is still not responsive. I'm not sure what else to try. I might have just borked the device. I may try completely disassembling the table and reassembling it to make sure nothing got disconnected. I'll also inspect the connections to make sure no wires look damaged.
Anybody else have any other ideas?
Click to expand...
Click to collapse
Hey
Im also suffering from a similar problem. Everything works and my gtab boots up fine, but the touchscreen is unresponsive. Ive pulled the device apart and looked for any damaged connections especially the ribbon connection to the outer touch screen layer. Everything looked fine. After putting back together, i started and it booted up fine, but touchscreen still unresponsive.
Has anyone else been able to recover from this? What did you do?
Cheers
I ended up calling the support number and the device was under waranty so I got a RMA and sent it in. 2 weeks later I had it back working, same case but I think the guts were swapped. Only cost me the shipping. Pretty good deal. Just make sure you flash back to stock.
bmasephol said:
I ended up calling the support number and the device was under waranty so I got a RMA and sent it in. 2 weeks later I had it back working, same case but I think the guts were swapped. Only cost me the shipping. Pretty good deal. Just make sure you flash back to stock.
Click to expand...
Click to collapse
That sounds like what im going to have to try and do, although im in australia, so i dont know how kind they will be about replacing it.
I have another problem now after trying to flash back to original stock rom in this thread
Im not having a good couple of days lol.
Cheers.
Related
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
I'm brand spanking new to Android. Haven't dealt with sdk's andn loading rom's in ages and don't have the time to figure it out. Thought there might be some hard reset button combo that I was missing or something. Just heading to the Sprint store now with box in hand to have them switch it out or activate my Treo Pro again. Kinda need the phone for work and don't have a home phone so downtime is not a good thing.
darkenergy said:
hmm im kinda new to android, but if your stuck in fastboot cant you use the devkit to push a new recovery image like RA 1.2.3 and flash ?
i might be wrong tough
Click to expand...
Click to collapse
he won't be able to push that to do ADB tricks, nor do fastboot flashing with img files
Goldcard doesn't help as well
I hv got a G1 in same situation after pulling out the battery.
Stucked at first splash screen on next boot.
I assume that is a rom / system problem so I tried to boot into recovery but still freeze on 1st splash screen.
I tried to figure out the problem and I'd try to connect by usb and tried adb logcat but only waiting device return. And yep the screen goes black ( but still on ) likely in this situation.
And yea SPL enter was successful but can't connect to fastboot so no recovery can flash.
I notify the phone (seemingly) won't be able to charge as the notification do not turn on, or it does charge but problem with notification light (?), probably it is more likely a hardware problem due to removing the battery. Recently I take the G1 to a shop to figure out is that a hardware failure.
I'm all for troubleshooting and playing around with ROMs, but there's times when I just need to be up and running and have opted not to screw around with something I depend on for work. There's other toys to "play" with.
So after a way too long stay at the Sprint store I have a new Hero that's up and running just fine.
Wanted to say it was something I installed, but everything seemed to be approved by the masses as working well. Maybe it was something with the battery pull. I'm surprised no one has made a soft reset widget. Seems kinda basic coming from 13yrs of PalmOS and a bit of winMob.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
download htc sync and install it.
http://www.htc.com/us/supportdownloadlist.aspx?p_id=300&act=sd&cat=all
download sprint RUU and run it, it will wipe your phone, but it will work agian
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
thanks for that. Will keep that handy for next time or if I ever play around with it. I think I'm going to the Moment though when it hits next month. Better screen, processor and keyboard will be doing it for me.
fixing any android stuck in fastboot
If your stuck in fast boot this is what you do.
1. Remove the micro sd card and somehow connect it to your computer.
2. Download a rom that is made for your phone and put it in a easily accessible folder on the micro sd.
3. Reinsert the sd card in the phone and reboot, once in fast boot go to hboot.
4. After going into hboot select recovery.
5. After this is done you must go to "install zip from sd card" and choose the rom that you have downloaded, select install and wait until the installation is complete, if unsuccessful redownload and try the whole process again, if unsuccessful the second time try downloading another rom.
If you have any questions please personal message me so i can help you.
Download: cyanogenmod.com
Btw i had a HTC hero and had this problem many times and this had worked every time.
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
dbpaddler said:
So I just got done configuring chompSMS. Disabled notifications on the built in SMS app. Did a battery pull and got this screen and haven't been able to get out of it. Held down home & power and got a user memory wipe screen. Figure I'd give that a shot. Still stuck on the FASTBOOT screen and now have to redo the whole thing if I manage to get out of this screen.
Anyone else see this? Not much out there about Sprint's Hero, but there's a bit about Orange's Hero, rooting, flashing rom's and all that fun stuff. Nothing about getting it back to normal though.
and to add....after letting it sit connected to usb for a bit, the screen finally went dark but now won't turn back on. Really odd.
Click to expand...
Click to collapse
yurais said:
I have a similar situation
when i power on the phone it goes straight to fastboot mode.
I Checked volume keys and are not stuck.
If I connect phone via usb and run:
fastboot reboot
the phone will load normally the android OS and will work just fine until you power it off again.
\
I dismantled the phone just to be sure there is no hardware issues, I tried to power on the phone without the home button connected to the board and the phone will load the android OS without any issue.
I dismantled the button itself, it has some sort of touch IC inside and a normal key button downside.
I could not notice any dust or water tracks in the button, so
at this point and dont know where to go...
I dont have another button just to be sure if it is the button itself or a board issue.
Click to expand...
Click to collapse
People still use the Hero? There are so many better phones you can buy for dirt cheap. Heck, I got the Evo LTE for $80 on Craigslist. Even the Evo Shift, Design and 3D can be had cheap. I'd dump the Hero without blinking.
If your phone was bricked in any way, but still shows something on the screen when powered on or plugged in, try this.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen
IF the phone screen does show the battery charger or something else on the screen after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
When done properly, this will always get you into Download mode. After that you should be able to use Odin to revert to stock, tar and instructions here:
http://forum.xda-developers.com/showthread.php?t=734475
This fixed my 'odd' bricks. Over and over again.
I'd say it's impossible to truly brick this phone.
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
davbran said:
I have been researching this most of the day, due to some testing I was doing, and the one thing I have come to realize is that this phone recovers well from "brick" it's not a true brick it's just scary. One of the posts I read, here on xda, said that unless the blue progress bar started advancing while using Odin, you can unplug, pull battery fairly safely.
Click to expand...
Click to collapse
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
omg, i love you This totally fixed my problem XD
Everyone kept saying go to download mode, but no one ever said to "7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!"
super life saver... thanks alot
I actually did find someone else say to do that but it was out of luck as it was deeply buried. Don't remember where it was here lol
Its nice to have people who help us newbies
andershizzle said:
Haha well that's exactly what happened to me. I flashed wrong with Odin and it failed halfway through, and I had no choice but to reboot the phone.
And when I did I got a truly odd screen. All I could see was a picture of a phone connected to an exclamation point connected to a laptop. That's it. Lol.
And I fixed it by doing this.
Click to expand...
Click to collapse
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Maverick777 said:
Yea, last night I was messing around with the latest lag fix, but it ending up causing a lot of FC's, so I had to revert to stock a few times. I tried to make it work using ext2 and ext3, but it still wasn't stable enough. I didn't enjoy the noticeable speed increase, but it wasn't worth it since launcher pro was one of the programs that was FCing.
Anyways, so after I gave up for the 3rd time, I flashed stock using ODIN and it got stuck. I left it there for awhile with no progress and the phone's screen actually just went completely black. I pulled the battery and got the weird cell phone pointing to computer icon. I almost crapped my pants at that point. Very scary moment since I had not seen that screen before.
A quick google search for "bricked Vibrant" led me to this thread and voila! My Vibrant is alive and well again.
Thanks a bunch.
PS: After reflashing stock that many times, I still find it strange that after a fresh flash, I still get a noticeable speed boost by wiping the phone through the privacy setting. Not sure if it's a placebo effect, but I swear it makes a noticeable difference every time.
Click to expand...
Click to collapse
Glad I could help!
And that's intersting. I'll make sure to wipe the privacy settings. I actually haven't ever wiped them yet.
No go for me.
I used the stupid partition tool in rom manager. partitioned the internal memory not the sd card.
Saw a few others did this, and this worked for them, either right away or after flashing eugene's froyo rom then reverting back, but that rom just hangs on cache.fsd or something like that.
Trying to repartition through odin, with no download files selected right now. It does not appear to be doing anything, just set pit file, then do not turn off target in odin.
Will leave it for a bit, maybe try to flash this again, i think the issue might be deeper for me though. need kernel and everything else.
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Thank you so much for this, I received a replacement set 2 days ago and was playing around the the phone and I bricked it, it thought it was frozen so I pulled the batter and it bricked.
I followed your instructions and it works like a charm. What I did find though is that i can't seem you use odin on a mac even with a virtual machine. I had to use an actual PC.
tweezit said:
I did that but my phone locked up and now all I get is a picture of a yellow cation sign next to a little phone and pc pic.. anything I can do at this point or??
tried going into recovery and download mode but it wont let me past that screen.
Click to expand...
Click to collapse
This is exactly the screen I had. Follow my instructions exactly and you'll get into download mode (at least i did)
This should be made a sticky.
thank you thank you thank you
Sticky this thread.
Sent from my SGH-T959 using XDA App
Great find for all.
has anyone found a way to unbrick a flashed EU rom then the person flashed to US rom? and then the power wont come on? But the unit does get hot when plugged in?
Im trying to see if i need to jtag this thing. or if anyone had success?
Thanks
ok so my vibrant gave me the cell phone and computer screen i got it back in download mode. started odin to get it back to stock but no matter how long i let odin go nothing happens i got the files that i need for odin out of a thread on these forums and i have followed the directions to the letter and still nothing. any help some one can give would be great. thank you for your time.
How do I know if my phone is being picked up by Odin or being flashed?
did the same thing the clockwork partition wiped my internal memory
F**k!
woop guess im going to tmobile in the a.m. and playin the whole
idk what happened it wont turn on
thank god for the 14 day return policy!
I ran into "brick mode" myself 2 nights ago and could not get my phone into download mode. Any possible combo of volume key up/down and power had no effect. Just that phone exclamation point pc icon slowly blinking in the center of the screen. I did finally get it into download mode but it wasn't using any of the previously mentioned methods, so I'll add one more to the growing list to try. This one worked for me after almost 4 hours of experimenting.
BTW....my phone would never display the battery charging image when powered off and plugged in. Just this same annoying image.
Pull the battery. Put it back in. Hold the just the volume down button. Do not hold the power button. Plug in either a wall charger or USB cable. The cable will power up the phone and voila. I was in the download screen.
I also highly recommend the stock ROM from the thread
"[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)" In Vibrant > Vibrant Android Development
I tried another ROM found out on the internet and ended up with a shell that crashed and restarted every 60 seconds.
For those running into Odin stuck on a message about verifying the file system, I had no luck when the phone used COM3. I suggest moving your USB cable into different ports on your PC. Each new port will "install" a new instance of the phone using different COM ports. COM5 and COM6 both worked as I was reflashing the day away yesterday.
I tried installing CWM and somehow must have done it wrong. Gtab bricked, would not turn on at all. Let the battery run down, connected to DC, still nothing.
Plugged in the USB and my Windows 7 computer recognized the device, so I assumed it was in APX mode
Followed instructions for NVFlash, got it up and running. Shut it down, but it would not come back up with the power button.
Repeated the NVFlash, got it up and running again - shut it down and same thing - it would not come back up.
I then used the FORMAT routine to wipe the Gtab, then the NVFlash routine, same thing. It recovered but would not power back up after powering down.
I used two different NVFlash routines, one from this forum, one from another. One included the CWM, one did not.
I also ran update on the Gtab, downloaded 1.1-3588 successfully, however when installing, at the reboot stage, the Gtab again would not power up.
Present configuration shows Tap UI version 1.0-2638.
Common problem is inability to restart/power up after these steps.
Any ideas? Is this a hardware thing?
PS - I have spent quite a few hours looking for similar problem in the forums without luck - however if there is a thread that covers this please point me.
Im having the same problem, iv tried both nvflash techniques and nothing, also cant find anything helpful in forums
Hoping someone else on this forum has an answer... Are planning to return it? Got mine on woot and I think I have 30 days??
Sounds like some crickets are chirping on this one. I have continued to review other threads and can't find anything quite like what I am experiencing as described above. I continue to re-NVFlash the gtablet whenever I need to use it. It will go into "sleep" mode and recover with a short power button push but will not come back after fully powering down.
I've loaded three different NVFlash routines, one from this site and two from another. One has the clockwork mod built in. In all cases I can't get the power up cycle to work. When I plug in the USB cable it pings indicating it is in APX mode (boot looping??).
The only thing I can think of is cracking the case and hitting the reset button.
Since I can re-flash it I guess I could always return it??
Any ideas
My phone was working perfectly fine until yesterday, when I went to the pool and carelessly left my mobile phone near some humid/wet clothes. When I got my hands on it, it was /working/ or so it seemed yet I couldn't put the SIM code to unlock it. It then restarted and got stuck in a bootloop.
I removed the battery, checked the Water Damage stickies and everything seemed fine, but still wasn't working. Today I got home and dropped my phone in rice (I heard it's good in order to absord water and such) and after a while I removed it, put the baterry in but now it just gets stuck on the boot screen.
I tried going into recovery, was able to, but can't surf through the menu because volume keys don't seem to work.
Any ideas what is wrong with my device? Any suggestion for a new phone if my phone doesn't come back from the dead?
Technical data?:
Unlocked with HTCDev Unlocker, rooted, and flashed CM7.1 with no problems before.
Two year old device.
Bump and extra info about my problem.
I left my phone discharging it's battery and seeing if anything worked okay. This morning it was off and wouldn't turn on, so I put it to charge.
After some hours, I got it's LED green so I tried and turned it on. It did, but still didn't pass the Cyanogenmod bootscreen, so I tried going into Recovery, and it worked! Now I'll try to tinker it, and see if I can get it fixed.
So, if anyone out there has the same problem I have, they should try killing their battery and charging it to 100%. It seems the battery malfunctioned or is almost dead, but a man can wish and see if he can repair his gadgets.
Glad to hear it's fixed! I'm sure many others would feel the same way about your recommended remedy!
Sent from my Nexus 7 on the XDA app. GO CANADA GO
Thanks!
When I had access to the Recovery I backed up my phone and wiped dalvik and cache, then re-installed Cyanogenmod (now upgraded from 7.1 to 7.2) but I'm currently considering switching to another ROM, like an ICS'
Everything works fine, except the SIM, but I believe that's a problem on my own end (network not working)
If it ain't broke...see if it'll go faster. That's what I tried, BUT ended up
If it ain't broke...fix it 'til it is!
I posted this in XDA Assist, but as I suspected, I've well hosed this one, with probably no way up, but here goes. I promise, next time I won't be so wild. I know now that if you must burn your bridges, don't be standing on them!
Android 4.2.2
It's rooted with Vroot, has SuperSU and Titanium Backup Pro, shows rooted.
Had ADB working, tablet taking commands.
I first tried to put in CWM recovery for the HSG1279, supposed to be the same tablet, just bigger screen. I don't even know now whether THAT'S true or not.
Started in recovery mode, but was just stock, so I tried arctools to put in a generic Rockchip CWM 6.0.3.1. That's when things started going sideways. The install hung (imagine that!). The arctools had a forced restart of some kind, so I used that. When I got back to my home screen (whew!), I used Titanium backup to see what recovery mode looked like. The tablet went dark, and would not power on. I did the paper clip trick, which got it started, but did NOT wipe anything out, so not a hard reset. Any time after that when I tried to restart in recovery mode, the hard shutdown with the clip was required. Yesterday afternoon, I went off to work for about 3 hours, leaving the tablet on, but in standby. When I came back, the tablet was dark and no amount of paper clipping would help. It would not recognize a charge. Not being one to duck a fight, I opened the case and unsoldered the black (-) wire at the PC board. The battery measured some voltage, but I didn't notice how much, about 1/4 on the 25v. scale. I soldered it back on, put it back together without any further incident. It sill does just what it was doing...nothing. I have noticed that when it's plugged into my PC's USB port, and I reset with the clip, Unknown Device shows up in my PC's Devices And Printers list. When I unplug the cable, I get the stock Windows "be-boop" USB removal sound. When I plug it back in, I get a short "boo-boo-boop" sound. That's where it is now. Anyone have any ideas on getting it going again? For me, no more trying files that aren't made specifically for this oddball tablet. This has been a fairly expensive lesson in that.
Thanks for any help.
~Bob~