Hello everyone, I have been reading and respecting you for a long time.
They gave me a Mediacom tablet with Android to repair or throw away as a favor, I'm not asking for money and I'm not a professional, just self-taught. It basically had half the screen where the touch screen didn't work, so in addition to trying with the "pizoelectric" lighter as seen on youtube and various apps, I decided to try replacing the touch screen as well. Once done, the problem remained as it was. I tried to do the factory reset and now I'm stuck in the installation because I can't click on the buttons to finish the installation. I used to at least rotate the screen and run it on the good half. But now I'm stuck in the installation. I also tried to take a usb dongle to attach a mouse to it, but it doesn't see it, also tried on the smartphone, but it doesn't see it anyway. 1. Confirmed that it is not damage to the touch screen. Can I finish installation via adb shell? What do you think is the problem? is it software? Any advice is greatly appreciated.
Thank you
It's hard to advise anything without writing the model name of the device. Adb host will not work when it is not enabled in the device.
ze7zez said:
It's hard to advise anything without writing the model name of the device. Adb host will not work when it is not enabled in the device.
Click to expand...
Click to collapse
The model is smarpad iyo 10, but I doubt it serves as information, since it is probably an Android 9 problem. I thought it was possible at boot to enable a shell and complete the installation or maybe rotate the screen.
Thank you for answering.
The Rockchip A55 RK3566 processor in the Mediacom IYO 10, supports USB OTG, so a mouse connected to an OTG adapter should work.
Which adapter did you use?
The touch screen for the Mediacom IYO 10 is not outstandingly complicated and has no chipset in it. So the touch is controlled by the mother or daughter board electronics, which you probably did not replace when you replaced the screen.
ze7zez said:
The Rockchip A55 RK3566 processor in the Mediacom IYO 10, supports USB OTG, so a mouse connected to an OTG adapter should work.
Which adapter did you use?
The touch screen for the Mediacom IYO 10 is not outstandingly complicated and has no chipset in it. So the touch is controlled by the mother or daughter board electronics, which you probably did not replace when you replaced the screen.
Click to expand...
Click to collapse
The Otg adapter is from Tek-one to-g-15, it may be that it doesn't work, in fact it doesn't work on the mobile either, I try to change it.
As you said, the touch had no chip, just a connector to the motherboard.
An information that I have omitted may be useful, at the beginning the tablet also had another problem, in some circumstances that I have not explored, the screen or the resolution was resized in half, presumably in the working half. Almost immediately the scaling issue was fixed by randomly activating a gui option in hidden developer mode.
Now, excluding the Otg that I'm going to change, do I have any possibility of continuing the installation via shell?
Thanks for the precious information.
You probably don't have TWRP so you won't do anything with the build.prop file.
The lack of a shell is the result of not enabling debugging in the developer options, available only after starting android.
Look for a working OTG adapter.
Maybe this thread will help you.
Is there any emulator for Amazon fire stick?
If i develop an app for amazon fire stick but I don't have a Fire stick so how can I check my app? Is there any emulator for Amazon fire stick ?
stackoverflow.com
Related
Backstory:
My buddy bought 3 ASUS tf300t tablets online with broken screens. Unbeknownst to us they have this weird firmware issue because ASUS is lame and doesn't care about backwards compatibility. I've been trying to fix these tablets for a few weeks now and I'm just spinning myself in circles and getting frustrated. 1 of them is rooted with CWM recovery so that's the one I'm working on.
The issue:
According to http://forum.xda-developers.com/showthread.php?t=2091233&page=11 I can simply adb into the device copy the proper firmware to it's set directory, delete the old firmware, run the firmware update command and touch will be restored.
So how does one use adb without usb debugging enabled?
I tried through CWM, adb worked, but I can't get superuser to work, nor could I get the touch_firmware_update command to work.
So I downloaded the http://forum.xda-developers.com/showthread.php?t=1893714&highlight=root stock rom with usb debugging enabled. I flashed that rom and my computer brings up the normal TF300t drivers for MTP.
ADB doesn't see any devices...
I tried manually replacing those drivers with the ADB drivers from google because I'm a touch retarded and I thought it would work. My mom says that I'm super smart and really handsome, but I feel like she lies to me.
There's just so many new terms and I've spent so many hours on it that frankly, if search did bring up the answer, I would miss it.
I'd appreciate any help, and if you help me fix it, I'll make a youtube video thanking you in the creepiest way possible.
-Thanks
duffskeeze said:
Backstory:
My buddy bought 3 ASUS tf300t tablets online with broken screens. Unbeknownst to us they have this weird firmware issue because ASUS is lame and doesn't care about backwards compatibility. I've been trying to fix these tablets for a few weeks now and I'm just spinning myself in circles and getting frustrated. 1 of them is rooted with CWM recovery so that's the one I'm working on.
The issue:
According to http://forum.xda-developers.com/showthread.php?t=2091233&page=11 I can simply adb into the device copy the proper firmware to it's set directory, delete the old firmware, run the firmware update command and touch will be restored.
So how does one use adb without usb debugging enabled?
I tried through CWM, adb worked, but I can't get superuser to work, nor could I get the touch_firmware_update command to work.
So I downloaded the http://forum.xda-developers.com/showthread.php?t=1893714&highlight=root stock rom with usb debugging enabled. I flashed that rom and my computer brings up the normal TF300t drivers for MTP.
ADB doesn't see any devices...
I tried manually replacing those drivers with the ADB drivers from google because I'm a touch retarded and I thought it would work. My mom says that I'm super smart and really handsome, but I feel like she lies to me.
There's just so many new terms and I've spent so many hours on it that frankly, if search did bring up the answer, I would miss it.
I'd appreciate any help, and if you help me fix it, I'll make a youtube video thanking you in the creepiest way possible.
-Thanks
Click to expand...
Click to collapse
Short of investing 60 bucks on a docking keyboard, your best bet would be to get a usb dongle that allows you to plug in a keyboard so you can be sure debugging is ticked. Otherwise, if it's enabled and you've installed the proper drivers, Windows should see your device. From there, it's a breeze, if the hardware is good. You don't have to do Youtube. Just stop crying, Gives me the creeps.
graphdarnell said:
Short of investing 60 bucks on a docking keyboard, your best bet would be to get a usb dongle that allows you to plug in a keyboard so you can be sure debugging is ticked. Otherwise, if it's enabled and you've installed the proper drivers, Windows should see your device. From there, it's a breeze, if the hardware is good. You don't have to do Youtube. Just stop crying, Gives me the creeps.
Click to expand...
Click to collapse
Yep, your only for sure way would be a USB OTG adapter or a dock. Heres the adapter in the US for 10 bucks shipped on eBay. This will let you use any regular USB mouse instead of the touch screen
http://www.ebay.com/itm/USB-to-OTG-...ablet_eReader_Accessories&hash=item41700957d7
Heres another for 4 more bucks that gives you Two USB ports :
http://www.ebay.com/itm/Dual-40-Pin...ablet_eReader_Accessories&hash=item3cce7dd4c8
Also you can try giving this a shot ....http://code.google.com/p/androidscreencast/
Its an app that pushes your phones screen to your desktop so you can use a keyboard and mouse on it. Not sure if it will work for you since im sure it needs debugging on, but also worth a shot. I use MyMobiler on mine but it needs to be set up on the device itself first. This looks plug and play but says it has slow refresh rates.
As far as the ADB drivers, Im using the universal drivers found here : http://forum.xda-developers.com/showthread.php?t=2139767 and everything works as it should . Try those out
Oh and one more thing.. You might be able to use fastboot to push a touchpanel firmware zip. This is a different device, but you could try it :
http://forum.xda-developers.com/showthread.php?t=2159863
pyraxiate said:
Yep, your only for sure way would be a USB OTG adapter or a dock. Heres the adapter in the US for 10 bucks shipped on eBay. This will let you use any regular USB mouse instead of the touch screen
http://www.ebay.com/itm/USB-to-OTG-...ablet_eReader_Accessories&hash=item41700957d7
Heres another for 4 more bucks that gives you Two USB ports :
http://www.ebay.com/itm/Dual-40-Pin...ablet_eReader_Accessories&hash=item3cce7dd4c8
Also you can try giving this a shot ....http://code.google.com/p/androidscreencast/
Its an app that pushes your phones screen to your desktop so you can use a keyboard and mouse on it. Not sure if it will work for you since im sure it needs debugging on, but also worth a shot. I use MyMobiler on mine but it needs to be set up on the device itself first. This looks plug and play but says it has slow refresh rates.
As far as the ADB drivers, Im using the universal drivers found here : http://forum.xda-developers.com/showthread.php?t=2139767 and everything works as it should . Try those out
Oh and one more thing.. You might be able to use fastboot to push a touchpanel firmware zip. This is a different device, but you could try it :
http://forum.xda-developers.com/showthread.php?t=2159863
Click to expand...
Click to collapse
I gave up, but, I appreciate it. I even ended up buying the adapter, ended up bricking the tablets.
Hi,
I'm trying to learn about serial communication with devices from an Android tablet via USB host mode. I have a tablet, I have the devices, I have the apps... they just won't talk. It's most likely something to do with the firmware on my odd tablet, or maybe I'm just missing something stupid.
The tablet:
SUPERPAD FLYTOUCH
10.2" >24GB< ANDROID 4.0 TABLET A10 1.5Ghz CPU | 1GB RAM
"About this Tablet" says:
Model: BC1003
Android 4.04
Baseband ver 1.5rc4
Kernel 3.0.8 [email protected] #2 Mon Aug 6 15:23:31 CST 2012
There are 2 USB-A ports on this device. One has a physical switch that goes from device to host mode, comes with a male-male cable for attaching to a PC. The other port is host only. I can connect a USB thumb drive and it mounts just fine, shows up in the file manager, no problems. Same for a USB keyboard. It powers any USB device I've plugged into it.
The problem:
It works well enough for most things. But, I've now run into two applications that won't use the host USB port on the thing. Both seem to want to do basic serial communication. At this point, those 2 apps are about the only things I actually want to do with it, so I'm willing to experiment.
I have a USB oscilloscope that comes with an Android app. The app installs and runs fine, but it won't recognize the hardware usb device I've plugged in. Annoying, but I don't really need it. I've recently purchased some digital scales(DROs) for my lathe/mill. There's an Android app that interfaces these scales to an Arduino device via USB. Installs fine, won't connect to the Arduino. Okay, now this is starting to get annoying. Also, for what it's worth, the Android app for doing general Arduino stuff didn't work either.
So, the USB hardware works enough to connect a USB thumb drive or keyboard but the firmware won't use said hardware to do what I want.
The questions:
Am I doing something wrong? Is there an app I can install that enables serial communication over USB host mode? Am I missing something stupid?
Is there any other firmware I can run that will allow this communication? I think I've got the Windows utility that will allow me to flash the rom. I've watched the youtube vids on dis-assembly so I can pull the internal tf/sdcard and make a full dd backup. I'm assuming it contains the roms and everything else. Actually, I'm thinking about just pulling said card and replacing it with a smaller one for experimenting. Will I still be able to flash it using the windows LiveSuite utility even with a blank card inserted?
At this point, I'm willing to play. I mean, it's still useful enough to be careful, but I'm willing to take some chances and put a little work into it. If I can get it running with the DRO software while talking over USB to the Arduino, I'd sacrifice everything else. GPS, battery life, wifi, screen rotation, sound, whatever. I'd just bolt the thing next to the mill and that's that. Failing that, I'll put it back to stock and stick it on the fridge for my wife to look up recipes, Yeah, poor tablet... motor oil and metal swarf or cooking oil and flour. No happy retirement for this tablet, sitting in a drawer gathering dust.
Any hints, links, recommendations, or directions appreciated.
David...
Good evening guys, I'm starting this post since this is the only issue preventing me to buy an Nvidia SHIELD Tablet at the moment. As the thread title suggests, it's about the charging the device while using the MicroUSB port as a Host in a USB OTG (for example, to be able to Gamestream at 1080p using a USB Ethernet card). I tried to find another thread in here about this, but maybe it just hid from me (in which case, I apologize, and please, refer me to that thread before closing this one). I can link you to some outside-XDA forum threads about this, but I'm not doing it by now since I don't know if outer links are allowed.
Anyway, back to the topic, I don't own a SHIELD (yet),only waiting for this issue to be solved. I'm so sorry but in my opinion, the SHIELD Controller is not even close to the 60 USD worth point as a controller, so I'm using another one, and one of the features that made me decide for the SHIELD Tablet is the Gamestream possibility, but with Keyboard + Mouse, not only with controller, feature that I want to use my PC peripherals with. Also, I'd be using a USB Ethernet card for 1080p Gamestream.
Considering the previous points, plus it's by all known that the battery life of the SHIELD is not specially awesome when it comes to gaming, I consider being able to charge the device while gaming (in any condition, including using some devices through the USB OTG HUB feature) a must.
Wondering around, I came to think about two hypothesis:
1) SHIELD's kernel has not the USB host + charging feature implemented, which, as someone around here said, it'd be a serious case of false advertising.
2) SHIELD's kernel actually has the USB host + charging feature implemented, but somehow, it's not activated on the build.prop, in which case, the solution would be as simple as modifying the root/system/build.prop file, adding the following line: # support USB Host rp.usb_host = 1 (you need root permissions to do so. Be sure you make a backup file!)
I'd greatly appreciate if anyone in the forums could test it, so I'll be able to purchase my brand new SHIELD Tablet without the fear of having it only as a regular tablet until Nvidia decides to offer the features they claimed they will (which honestly, is pretty sad...)
Noct27 said:
Good evening guys, I'm starting this post since this is the only issue preventing me to buy an Nvidia SHIELD Tablet at the moment. As the thread title suggests, it's about the charging the device while using the MicroUSB port as a Host in a USB OTG (for example, to be able to Gamestream at 1080p using a USB Ethernet card). I tried to find another thread in here about this, but maybe it just hid from me (in which case, I apologize, and please, refer me to that thread before closing this one). I can link you to some outside-XDA forum threads about this, but I'm not doing it by now since I don't know if outer links are allowed.
Anyway, back to the topic, I don't own a SHIELD (yet),only waiting for this issue to be solved. I'm so sorry but in my opinion, the SHIELD Controller is not even close to the 60 USD worth point as a controller, so I'm using another one, and one of the features that made me decide for the SHIELD Tablet is the Gamestream possibility, but with Keyboard + Mouse, not only with controller, feature that I want to use my PC peripherals with. Also, I'd be using a USB Ethernet card for 1080p Gamestream.
Considering the previous points, plus it's by all known that the battery life of the SHIELD is not specially awesome when it comes to gaming, I consider being able to charge the device while gaming (in any condition, including using some devices through the USB OTG HUB feature) a must.
Wondering around, I came to think about two hypothesis:
1) SHIELD's kernel has not the USB host + charging feature implemented, which, as someone around here said, it'd be a serious case of false advertising.
2) SHIELD's kernel actually has the USB host + charging feature implemented, but somehow, it's not activated on the build.prop, in which case, the solution would be as simple as modifying the root/system/build.prop file, adding the following line: # support USB Host rp.usb_host = 1 (you need root permissions to do so. Be sure you make a backup file!)
I'd greatly appreciate if anyone in the forums could test it, so I'll be able to purchase my brand new SHIELD Tablet without the fear of having it only as a regular tablet until Nvidia decides to offer the features they claimed they will (which honestly, is pretty sad...)
Click to expand...
Click to collapse
Just FYI, if you are going to copy/paste the same info between forums make sure you typed out commands correctly.
should be:
ro.usb_host = 1
NOT rp
EDIT:
Seems saving the file errors out even rooted...Not sure what to do.
EDIT 2:
Doesn't work. Tried it with a Build.prop editor.
Side note: When it is "charging" the AndroidOS doesn't see it charging but the port lights up orange. Doesn't look like it puts out full amps.
LVNeptune8 said:
Just FYI, if you are going to copy/paste the same info between forums make sure you typed out commands correctly.
should be:
ro.usb_host = 1
NOT rp
EDIT:
Seems saving the file errors out even rooted...Not sure what to do.
EDIT 2:
Doesn't work. Tried it with a Build.prop editor.
Side note: When it is "charging" the AndroidOS doesn't see it charging but the port lights up orange. Doesn't look like it puts out full amps.
Click to expand...
Click to collapse
TYVM for the attempt... then it's just that Nvidia totally made this feature out of nowhere... Well, let's have hope in the Android Development comunity...
Oh! And thanks for the correction! OMG I misstyped it... Gonna correct it on the GeForce forum ATM.
So, does a USB hub works with the Shield? Charging while using wired peripherals..
Hi
I have Galaxy Ace 4 (kitkat 4.4) with broken lcd. The screen is blank but touch should work. Earlier something was visible on screen and as I remember touch was working.
Moreover, the system had some failure due to permanent "application xxx stopped working" and factory reset should be made.
I would like to use this phone as wifi hotspot. Is there any way to access the phone after factory reset? I have found application like Visor to control android via usb on pc. But developer mode has to be enabled and I'm not sure if system should be rooted.
Thank you for any help
If you can still see the screen, but the touch screen does not work:
Buy a cheap USB adapter so you can connect a PC keyboard or mouse (probably a USB C to USB A adapter). You can buy these adapters from China on eBay for $ 1 (but you may have to wait a month until they arrive in the mail. In this case, buy from a seller in your own country). I suppose you have a keyboard or just use the keyboard and use the arrows to move and select things, so I think the Windows button will become the home button. Press Enter to select and Escape to return. Or you can simply point and click with the mouse. The problem is that not all phones support "OTG", so you may not be able to read the adapter. If so, then I think you have no other choice. . But most of the stores themselves definitely support 100% OTG, so it should work normally. The problem with Bluetooth is that you need to pair it first, which requires touching the screen. Therefore, if you cannot touch the screen, using a Bluetooth mouse or keyboard may not work
If you can't see the screen, but the touch screen works normally:
Unless you change the screen, don't think that there are many things you can do. Android phones that were previously compatible with MHL allow you to use a dongle to connect it directly to HDMI. But the cell phone no longer has that function. If you have a Samsung phone, I think you can buy a Samsung Dex docking station, which will allow you to connect it to the screen via HDMI. If you can install applications on your phone, you may be able to control your phone from your computer using a screen mirroring application (there are thousands of different software that can do this, but you need to install applications on your phone). Same as Google Chromecast screen mirroring. .You need to access the application on your phone to perform this operation. Therefore, there is nothing you can do except replace the screen. If you are lucky and your smartphone supports some type of HDMI dongle adapter or some type of desktop docking station with HDMI output, you can view the phone's screen and access it.
My Samsung A30 has a broken screen, I’m attempting to transfer all my files unfortunately the phone does not have the file transfer mode enabled so when I plug it in to my PC it’s recognised as a modem.
I’ve attempted to use https://github.com/Genymobile/scrcpy to display my phone so I can perform transfer operations unfortunately it requires USB debugging enabled which I don’t have.
I’ve also attempted connecting my phone to my TV via a USB hub though the phone model does not support HDMI output.
The phone is running as it is receiving calls with it vibrating.
Any thoughts on anything else I can attempt? I’ve already bought a new phone so not too keen on getting the screen replaced especially given there could be other issues.
AHuss123 said:
My Samsung A30 has a broken screen, I’m attempting to transfer all my files unfortunately the phone does not have the file transfer mode enabled so when I plug it in to my PC it’s recognised as a modem.
I’ve attempted to use https://github.com/Genymobile/scrcpy to display my phone so I can perform transfer operations unfortunately it requires USB debugging enabled which I don’t have.
I’ve also attempted connecting my phone to my TV via a USB hub though the phone model does not support HDMI output.
The phone is running as it is receiving calls with it vibrating.
Any thoughts on anything else I can attempt? I’ve already bought a new phone so not too keen on getting the screen replaced especially given there could be other issues.
Click to expand...
Click to collapse
If the screen is broken and you did not have USB debugging enabled before it was broken, there is nothing you can do to retrieve your data except repair the screen or find a tech shop that has the tools and the knowledge to pull your data directly from the hardware chip itself.
You will not solve this yourself using only software.
Use a USB Type C to HDMI cable to your TV.
The Samsung A30 apparently supports it.
HDMI Alt Mode doesn't go through a hub.
Enable ADB and download.
@Droidriven thanks, fair enough, I've ordered a screen and will attempt to replace it myself.
@Renate To enable ADB I need to enable USB debugging. Also doesn't seem like Samsung A30 supports HDMI output https://www.samsung.com/au/support/mobile-devices/connect-samsung-device-to-tv-via-hdmi/
Oh, sorry, my bad. The internet will give you an answer to any question, usually wrong.
Is there any chance that you can find the hardware serial console on internal test points?
Then you just need to:
Code:
# settings put global adb_enabled 1
If your ADB was previously enabled, then you won't have to deal with the invisible acceptance screen.
If not you'll have to echo the public key into /data/misc/adb/adb_keys
(I just did this on my B&N Glow '21 when it factory reset and it blocked me with a mandatory OOBE setup.)
Renate said:
Oh, sorry, my bad. The internet will give you an answer to any question, usually wrong.
Is there any chance that you can find the hardware serial console on internal test points?
Then you just need to:
Code:
# settings put global adb_enabled 1
If your ADB was previously enabled, then you won't have to deal with the invisible acceptance screen.
If not you'll have to echo the public key into /data/misc/adb/adb_keys
(I just did this on my B&N Glow '21 when it factory reset and it blocked me with a mandatory OOBE setup.)
Click to expand...
Click to collapse
For one, your solution is not a software solution, which is what I said, that they would not solve this with software alone. That is true and that is all I was saying.
Second, this solution is a hardware approach that the typical user has no experience with, which is why I didn't present them with an option that I am certain they are not comfortable with or experienced enough to attempt, as demonstrated by their attempts with software and unsupported HDMI and then stopping there to ask for help. An answer that more than likely seems more like a risk to them than a solution, isn't really helpful to them. I've helped with users dealing with this issue for years, I've learned that the vast majority of them are not comfortable with resorting to solutions that people like you and I would. With most of them, you may as well be telling them that they can solve their issue by biting a tiger on his ear, they are afraid of the solution. But, I understand, you have a proven, working solution, so you posted it, that is actually good, thank you.
That is why I said to repair the screen or take the device to a tech shop that has the experience and the tools(which requires opening the device to implement a hardware solution, as your posted solution also requires opening the device to implement a hardware solution) to retrieve the data for them(if repairing the screen is not their preferred solution, which obviously isn't). Also, Samsung isn't as simple as B&N hardware, Samsung has some tricky stuff when it comes to hardware, especially their Qcom versions, such as Qfuse(on some nodeld)and other tricky hardware designed to make tampering a real pain or even kill the device with built in components intended to kill the device if triggered. Their bootloader is pretty hard to get past without breaking into the hardware itself also.
Yeah, I know about Samsung, which is why I don't buy it.
In any case, if it's booted to Android, then Android generic solutions will work.
I don't have any idea if a serial port is accessible, but if it were, that would be an easy option.
thanks for the advice guys, @Renate your solution is probably probably beyond my expertise though thanks for your comment, hopefully I can understand it better in future. I'm hoping to use this screen replacement as an entry point into mobile phone repair.