Develop Bugs

[Q] OTG Host cable USB not being recognised, 4.3 issue?

Our brand new nexus 7 is not recognising any usb drives attached to it via an otg cable (which works elsewhere) , one of the main reasons that it was purchased
I have heard that it is an issue with android 4.3, and the only solution is apparently to reset it, and this might not be a permanent fix
So to cut a long story short, does anyone know about any potential fixes for this that may be coming out soon?

I am running CM 10.2 nightly and as of 8/24, USB OTG has been supported. Dunno that stock ever had or ever will have this without running some apps.

Smithy2997 said:
Our brand new nexus 7 is not recognising any usb drives attached to it via an otg cable (which works elsewhere) , one of the main reasons that it was purchased
I have heard that it is an issue with android 4.3, and the only solution is apparently to reset it, and this might not be a permanent fix
So to cut a long story short, does anyone know about any potential fixes for this that may be coming out soon?
Click to expand...
Click to collapse
You need stickmount or similar app.

Smithy2997 said:
Our brand new nexus 7 is not recognising any usb drives attached to it via an otg cable (which works elsewhere) , one of the main reasons that it was purchased
I have heard that it is an issue with android 4.3, and the only solution is apparently to reset it, and this might not be a permanent fix
So to cut a long story short, does anyone know about any potential fixes for this that may be coming out soon?
Click to expand...
Click to collapse
You need nexus media importer if you're not rooted. To use stickmount, you need to be rooted.

I have the same problem on my new nexus even with media importer.
This app http://goo.gl/7zBgYx claims to work on the new nexus 7 and ive tried the lite version which it indeed does at least show my files on a otg connected usb and lets me view pictures unlike Nexus Media Importer however you need the pro version to play/view files over 30mb, I havent got the time to check right now but if anyone does have successful results please let me know
Sent from my GT-N7100 using Tapatalk 2

Tried it and got Android 4.3 Issue 58277 Detected with Nexus Media Importer.
Had a look at this:
https://code.google.com/p/android/issues/detail?id=58277
Not going to do a hard reset but someone else has and it still didn't work.
Hope they fix it soon.

I've got same problem.
Is there any kernals I can flash that may fix it? I can't really root as it breaks support in apps I need to use.

There's an issue in Android 4.3 where it makes some incorrect assumptions about when certain mounts become available, a fix for it was committed to the AOSP repo a couple of days back and should make the next OTA, whenever that is.

It can be made to work on existing ROMs.

sfhub said:
It can be made to work on existing ROMs.
Click to expand...
Click to collapse
It can?
How? I'm desperate for a working fix, nothing I have tried works.

I have an idea how to get it working but my test units all have it working now so I can no longer test it because I can't reproduce the broken situation.
So I know it is possible to get it working and possibly how to fix it, but have no way of testing it.

sfhub said:
I have an idea how to get it working but my test units all have it working now so I can no longer test it because I can't reproduce the broken situation.
So I know it is possible to get it working and possibly how to fix it, but have no way of testing it.
Click to expand...
Click to collapse
Someone has posted a libusbhost.so file in the below thread (Post 72) which apparently fixes it (Compiled from official Google source.)but I'm not entirely sure what to do with it.
https://code.google.com/p/android/issues/detail?id=58277

kitch9 said:
Someone has posted a libusbhost.so file in the below thread (Post 72) which apparently fixes it (Compiled from official Google source.)but I'm not entirely sure what to do with it.
https://code.google.com/p/android/issues/detail?id=58277
Click to expand...
Click to collapse
rename /system/lib/libusbhost.so to /system/lib/libusbhost.so-backup
then copy the new one into /system/lib
change permissions to root.root 0644
reboot
I am not using that library and my units are working, so it possibly does fix it in a more reliable way, but isn't absolutely necessary to get it working on current ROMs. I believe there is a race condition in the code that can be resolved.

sfhub said:
rename /system/lib/libusbhost.so to /system/lib/libusbhost.so-backup
then copy the new one into /system/lib
change permissions to root.root 0644
reboot
I am not using that library and my units are working, so it possibly does fix it in a more reliable way, but isn't absolutely necessary to get it working on current ROMs. I believe there is a race condition in the code that can be resolved.
Click to expand...
Click to collapse
Just tried it.
Didn't work.
Gah.

[GUIDE][ROOT][CWM] ARCHOS 97b Platinum HD

I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!

thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site

Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.

Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?

i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved

ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you

Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.

Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?

Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.

Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards

Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.

Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested

please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.

Nexus 7 not getting recognised no matter what I do (no adb, no fastboot)

Hi!
I hope you nice guys could help me out getting my Nexus 7 recognised on a PC, after 2 days of hard work (googling and pulling my hair, literally), no matter what I did, all went in vain. Installed several drivers from google, samsung, htc etc but absolutely nothing happened. Things that I already have tried include
Turned USB debugging on/off
MTP/Camera
Reset my Nexus 7
Tried Windows/Mac/Linux
Tried different cables
My Nexus 6 and LG G2 have no such problem, they get identified for file transfer, fastboot or adb easily, but Nexus 7 is a nightmare. I want to flash 5.0.2 manually because I have TWRP installed. When I connect to a PC it just charges itself and doesn't give a single hint that its connected to a PC, please help me out. What could be the possible problem.
Thank you very much.
Best regards.

I been in this situation before on other device. You need to uninstall all other drivers and restart you computer.
plug in your nexus 7 and let the device driver install itself

Done that already. I tried on 5 different machines 2 macs, 2 Windows and a linux. 1 Windows and one Mac machine was absolutely fresh. Thanks for your reply.
Any other ideas.

rat170 said:
Done that already. I tried on 5 different machines 2 macs, 2 Windows and a linux. 1 Windows and one Mac machine was absolutely fresh. Thanks for your reply.
Any other ideas.
Click to expand...
Click to collapse
Why can't you use OTG and flash or transfer the rom from a thumb drive? If OTG won't work, it tells you that the USB port is somehow damaged. Its contact points to the board have been known to disconnect on their own due to shoddy soldering.

Hi,
I have exactly the same problem : have tried to connect my tablet to several computers (windows, linux), on different USB ports and with differents USB cables, but I can't get the computer to recognize the tablet (even in fastboot mode). But wharging the devices works without problems.
I'm starting to think that the microUSB port on the nexus is damaged, even if I've always been cautious with it. The worst part is that Asus is telling me that the tablet is only under 1 year warranty whereas the booklet inside the box says 24 or 36 months... (i am past the first year).
I am considering a serious conception flaw because of other similar posts.

Thanks graphdarnell and luna. I think this is the problem. I tried on several other machines of work and friends, and the broken USB port seems the only reasonable explanation.
So now that I have a nexus 7 with broken USB port, how can I update my nexus 7. Can I revert to stock recovery and install the ota update, or do I have to live with 5.0 with a permanent notification of 5.0.2 update for the rest of its life?

rat170 said:
Thanks graphdarnell and luna. I think this is the problem. I tried on several other machines of work and friends, and the broken USB port seems the only reasonable explanation.
So now that I have a nexus 7 with broken USB port, how can I update my nexus 7. Can I revert to stock recovery and install the ota update, or do I have to live with 5.0 with a permanent notification of 5.0.2 update for the rest of its life?
Click to expand...
Click to collapse
FWIW, I have never been able to get any of my computers to connect to my Nexus 7 in anything other than fastboot mode. I have installed/uninstalled drivers hundreds of times. Eventually just gave up and started using usb-otg.

rat170 said:
Thanks graphdarnell and luna. I think this is the problem. I tried on several other machines of work and friends, and the broken USB port seems the only reasonable explanation.
So now that I have a nexus 7 with broken USB port, how can I update my nexus 7. Can I revert to stock recovery and install the ota update, or do I have to live with 5.0 with a permanent notification of 5.0.2 update for the rest of its life?
Click to expand...
Click to collapse
Did you try OTG? If yes, and it doesn't work, the solution would be to re-flow the usb port. It's no big deal, but you need a little patience, some soldering skills, and the right soldering tip. I could have helped you if you were nearby.
CM 12 has ADB through wi-fi (if I remember correctly), but it's pointless in your situation. Airdroid in Playstore allows you to transfer files through wi-fi from PC to tablet. And there are other apps functioning similarly too.
A word of caution: you want to be careful with the official Lollipop (which has been pulled off the shelf by Google). Lots have found out the hard way how it might brick your tab without warning. Use one of those custom roms (Clean Rom 5.1 or CM12) that is Lollipop-based instead.

graphdarnell said:
Did you try OTG? If yes, and it doesn't work, the solution would be to re-flow the usb port. It's no big deal, but you need a little patience, some soldering skills, and the right soldering tip. I could have helped you if you were nearby.
CM 12 has ADB through wi-fi (if I remember correctly), but it's pointless in your situation. Airdroid in Playstore allows you to transfer files through wi-fi from PC to tablet. And there are other apps functioning similarly too.
A word of caution: you want to be careful with the official Lollipop (which has been pulled off the shelf by Google). Lots have found out the hard way how it might brick your tab without warning. Use one of those custom roms (Clean Rom 5.1 or CM12) that is Lollipop-based instead.
Click to expand...
Click to collapse
OTG also is not working, so I think it's safe to assume that its broken. I tried flashify to flash the stock recovery instead of TWRP, but after that I have got nothing, no TWRP no stock recovery. Whenever I try to start recovery it shows a dead android bot with "No command" written over it, and OTA update is giving some kind of error. I am not sure what to do next. All I can do is transfer as much files as I need to my Nexus 7 over wi-fi.

Any help please..... I just want to flash 5.0.2 with broken USB port and apparently no recovery installed.

You could try the nexus root toolkit:
http://forum.xda-developers.com/showthread.php?t=2389107
It has a very nice windows driver installation and troubleshoot section.

mulperi said:
You could try the nexus root toolkit:
http://forum.xda-developers.com/showthread.php?t=2389107
It has a very nice windows driver installation and troubleshoot section.
Click to expand...
Click to collapse
My nexus 7's USB port is broken, so I doubt that its going to help.

Need help with custom rom about root

Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal

At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......

Samsung Galaxy S9... Help Me!

Hi everyone, I'm here today to avoid going crazy altogether, I know I should most likely give up this time, but I don't want to lose this match. I have been applying root permissions to my devices for 8/9 years now, in the last year I am using only custom roms, so I know the steps to take. This time I want to revive my old S9 exynos, the problem? The usb port is unusable because "there is moisture" plus it does not have root permissions.
I tried everything; Wireless ADB, horrible apps like Kingroot and so on and so forth. I therefore came to the conclusion that to have the root you need the twrp or the pc, to have the twrp you need the root or the pc. For me that I can not use the USB port means that consequently I have to say goodbye to the PC. In other words, I create a paradox, without root I can not have the twrp and without twrp I can not have the root.
someone to give me a good idea? I know I should give up, but really, I don't want to.!
p.s. having the usb port repaired is not an option hahahah