Ok, I am MAD. This is unsolvable. I can't figure it out.
When I plug the Transformer into the PC, the PC won't detect it. It did a couple of days ago. I plugged it in to move some files over. It showed up as a drive before, but not anymore. The TF is brand new from Christmas, and it actually worked just fine Christmas day (I was able to transfer over some photos).
Two things happened between then and now that I can think of:
1. I used a System Restore to go back a few days because of a bluescreen issue that is unrelated and that I solved. It only went back literally one day, though.
2. I tried to delete some of the stock apps installed on the transformer. Not through root trickery or whatnot (I'm not even rooted or modified in any way). Just by going to the app market and trying to remove some crap (of course I couldn't).
I plug it in. Windows says "detecting driver," then it says it failed. USB debug mode is on. So I went into device manager. It shows up as "MTP Device" or maybe just "MTP," and Device manager gives it a question mark. So I went to Asus's site, downloaded the USB drivers, and installed those. No go. So I turned off Debug mode. No go. If I have debug mode on and plug it in and go to Windows Update, it shows an update for "Asus MTP Device" or something like that. I do the update and it gives me an error, saying the device is not connected. It is.
I've even installed the stupid Asus Sync Suite. It decided I wanted like five different startup programs. Revo Uninstaller made quick work of them, stupid bloatware.
So I've made no progress. Not sure why I could do it before, but I can't anymore. One thing that was weird when it WAS working was that my computer didn't get USB 2.0 transfer speeds from the device. Music copied agonizingly slow and my PC told me that "this device can perform faster if plugged into USB 2.0," even though all my ports are 2.0.
Currently, all that happens when I plug it in is Device Manager shows "MTP Device." HOWEVER, something interesting. When it's plugged in, the "safely remove hardware" icon shows up in the tray. If I click it, I see "Eee Pad Transformer." So the PC DOES detect the device, it just can't access its storage.
I'm on a Win7 PC that I built. I'm totally updated. The Eeepad is totally updated.
Oh, one last thing... I *might* have gone into the filesystem explorer app that came preinstalled to the device. I noticed that there were some folders from apps that I had installed but then uninstalled, and that bugged me, because if I uninstall a program I don't want that folder laying around. So I deleted some. But none were preinstalled apps. Things like Angry Birds, apps that I installed.
I read some thread in my google searches about something like UMDF or whatever. I tried that, but it seemed to only work for people with Vista or XP. The exe wouldn't even run on my system.
if anyone can figure this out, they'd have my eternal thanks.
You guys are awesome,
wontstoptalkng
ps,
I read through this thread a bajillion times:
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
I tried the method used in post 12, which is what worked for the OP. It didn't work for me, either because that method doesn't work on Win7 or it doesn't work on a 64bit os.
Hi,
First of all, great site you've got there, been checking it ever since I laid my hands on my first htc g1.
Secondly, and I hope I'm not double-posting about an issue already raised, as I've screened the threads quite thoroughly.
Here's the issue I have with my MK808B.
I've tried to start it with a USB ubuntu pendrive plugged into the USB OTG (I had saved some files I wanted to transfer, didn't realize it would mess things up).
Regular start up with this hdmi key is Google tv screen > android screen > home screen.
I get stuck at android screen, no matter how long I wait.
Out of nowhere, I tried to use another 2A power supply, as this had been advertised on other threads, no sucess... I also tried to start it with a paperclip pressing the reset button, didn't work...
Honestly, I don't know what to do exactly, I think it might have tried to boot ubuntu out of the usb stick...
I think I have no option left but to flash it (thus losing all that is installed already on it).
Is there any trick that could restore things the way they were? Any suggestion welcome.
Thanks for your time and help.
Solved by flashing
Hi,
Since no mgic trick happened to save the day, I was left with no choice but to flash it.
Used rockchip batch tools, crossed my finger so the stick wasn't a clone with the mediatek chip, flashed stock plus goodies rom, waited 10-15 minutes, and voila!
good as new, got rid of the chinese apps I couldn't even log on, but got a full wipe of my data.
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage
Hello All.
So the other day I paid a visit to the local skip, as you do, and I found a Flytouch Superpad 7 in its' box, so I took it home.
Plugged it in and it started to boot up, first screen had "Tablet PC powered by...." then the next screen was of the Android Droid with its' arms folded, it usually freezes here. Sometimes it will go onto a screen with "Android" in the centre, but no further.
So I have tried various combination of pressing buttons to no avail. Cannot access a recovery anything.
I took it apart and found it is a Yones Top Tech BC1003, so have been searching and searching for information and roms etc for days.
What I would like to know is, do you think this tablet is saveable?
I have plugged it into my laptop but it doesn't recognise it, but wouldn't the tablet have to boot to be recognised?
I have read thread upon thread, but still do not understand how I could get a rom onto this tablet if it is not recognised by the laptop and it doesn't show a recovery section where I could boot from a SD Card.
Any advice gratefully accepted. Just trying to save something from the landfill.
Just an update to say I managed to get the tablet up and running.
I ended up going to a lot of foreign language website through Google Translate and found some firmware for this board at the Koncaso site. Burned the .img file and put it in the tablet, which now works again.
So few years ago I bought a Windows tablet to serve as a second Windows portable device. It served its purpose and now I am upgrading the WT8-A to an Android. So far, I am close. But there seems to be one last major hurdle preventing this from being a success and I would love to be pointed in the right direction for some help.
What I have achieved so far: I installed android fully and it is/was fully functional. However a few major issues have sprung up.
1) I can not reboot the tablet back into Android. The only way possible is to run it "live" (but then I can't save anything) or re-install it. How do I get around the boot issue and where do I start?
2) At first, the entire platform seemed to work perfectly except for a few minor glitches. I couldn't get Bluetooth to work (no biggie, I never use Bluetooth on this tablet anyway) and the camera wouldn't work (also not a biggie, the camera stopped working in a Windows 10 upgrade so no loss there).
3) I left the tablet on and after a few hours the touch screen stopped responding. I could still access everything if I used mouse and keyboard through USB. So I did. Then Android loaded the "Android loading screen" and things went back to normal for a short while. The same thing has continued to happen over and over. The touch screen stops responding, eventually and somehow (still unsure how) Android seems to reload and it all works again.
4) WiFi has stopped working. WiFi worked perfectly in the first day and then by the second day no WiFi networks are being found.
So, I am left with a semi working, non-WiFi capable, non-rebootable ex-Windows now Android tablet and I admit I am stuck at this point.
What is the very first thing I can do at this point to take it one step further and closer to being a success?