I just bought a galaxy tab 10.1 last night. I rooted right away and put a custom rom on (overcome rom). I went to push an .apk from the removed apps .zip and it says my device can't be recognized. I've tried everything (Uninstalling/reinstalling drivers, rebooting device and laptop, switching usb ports). I've been searching google for some answers so that I didn't have to start a new topic, but I'm still stuck. If anyone can help it'd be great. And I thank you if you can.
p.s. I'm not new to adb. I have a Rezound that is rooted and I use adb all the time. I'm using Windows 7.
Did you enable USB debugging in the settings?
He is right.. I have noticed this on my Galaxy Tab 10.1, my Acer Iconia A500, and my Asus Transformer Prime. All 3 its the same story... I am far from new to rooted devices and using ADB. Ive got 7 Android phones and 3 Tabs, so rooting and using ADB is close to becoming second language for me.
I've had issues with adb as well. I'm not certain but i think it may be related to kies. It seemed to start after doing one of the kies client updates. Adb now won't list the tab under devices. I can get it back if i uninstall all android drivers from device manager and uninstall kies then reinstall just the tab drivers.
I got it working right after I posted this. I uninstalled the sdk and reinstalled it and my tab came right up under devices. Thanks for the replies. My issue may have been caused by the kindle fire I had right before I bought this. I had to add some lines and stuff to some sdk files to get the kindle to come up in adb.
FWIW I've successfully connected through adb wireless. If you're having issues maybe try that market app?
Related
*FIXED* So i've been running pda net on this pc for 2 months and today when I come in it decides to not see my phone. So I reinstall and everything goes smoothly until it gets to "installing pdanet to phone" where it just hangs. I tried uninstalling the app on my phone, reinstalling from the market and titanium and still the same thing. Any suggestions? Running the new kernel from the 3.30 leak.
I also tried wired tether and all it does is force close on me
Well I decided to flash Net 4.1.9.1 and everything works again. The new HTC kernel didnt play well with pdanet for me
If the problem exists even with another app then you might have something more serious on your device. I'd backup and factory reset and try again. If it does not fix it then it could be hardware related. Can you connect via ADB? If so, how about adb install app?
I put my phone into recovery and the PC and pdanet recognized it, however being in recovery i couldn't start the app on the phone.
But when booted up I got nothing.
Sent from my PC36100 using XDA App
I got pdanet to install and recognize my phone, but now it hangs on connecting.
Android phone and adb all show up in device manager as installed and working. My only guess left is the kernel. I recall reading about a kernel having issues, I don't remember which one though.
Sent from my PC36100 using XDA App
I've downloaded the drivers several times and tried on two Windows 7 machines. Every time the installation fails. I've downloaded from the Samsung site, from Koush's Helium site, and from a couple posts in these threads.
Is there another way to install the drivers?
I'm trying to update to 4.4.4, and I have a Chromebook available, is there a way to use that?
Sent from my iPad using Tapatalk HD
Solved!
As seems to always be the case, This bugs me for weeks, then I post about it, and then I solve it.
The solution for me was to connect the phone, set it to MDM mode, and then run Windows Update. It found one update, which didn't help, but after that there were two more updates that did. (Before you ask, before I did this I had already done all updates that applied to my laptop.)
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.
So some backstory, I just tried installing xposed framework earlier in the day. Got an error about app_process64 or whatever so I looked it up and posts said to delete it so I tried. X-plore file app wouldn't delete it and I tried to download es file manager whatever but it wouldn't download from the play store. So I rebooted my fire and it's stuck on the fire logo now. Factory reset it but it not work. I've researched the crap out of this and from what I can see, since adb can't find my device my only option is the update from adb option from recovery mode since I did get that to see my fire.
So with all this buzz about how downgrading will brick my device I'm unsure what version to use. I don't know what version my fire is but it should be the latest I imagine since I just got the thing last week and it downloaded updates when I started it up the first time.
Any help would be much appreciated cause I'm all confused. I looked at https://forum.xda-developers.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443 and it lists firmware up to 5.6.3.0 but the update at the top says we're now on 5.6.3.4? So where do I find that at?
Update: K nevermind I got it. I took a chance and went to that page I listed and sideloaded the 5.6.3.0 suez file. Rebooted and fire booted up like new. Go me!
tl;dr -- How do I restore my original FireTabletSettings.apk to /system/priv-app/FireTabletSettings without adb? --or-- How do I enable adb without the settings panel?
Hi all. I'm reaching out to the amazing braintrust here on xda-d in hopes that maybe someone has some guidance. My most recent adventure has been de-amazon-ing my kids new HD10. And for the most part, I have been quite successful thanks to the wealth of knowledge here in this forum. I've managed to get it rooted, de-bloated, replaced the launcher, and even re-enabled a critical feature not found in the Amazon version of Android (screen pinning, essential for 2 year olds!).
But..... (there's always a 'but'..)..... but.. I have discovered I have somehow managed to lock myself out of adb on this particular device. I did search the forum first, finding nothing helpful for this. In order to get screen-pinning back I rolled the dice and used DragonFire1024's rewritten FireTabletSettings.apk, against the recommendation to avoid it with OS versions after 5.6.2.0 (I'm unfortunately running 5.3.7). I accept full responsibility, it was my gamble. The result is screenpinning resurrected (yay!), but also my settings panel is a mine field of broken links. Apparently much has changed in the settings after 5.6.2. Including how they refer to adb. So tapping on the enable box for USB debugging (here called 'enable adb') crashes the settings panel.
The situation is far from hopeless though, because I am rooted, and I had backed up the original FireTabletSettings.apk to the downloads folder on the tablet. However, when I try to copy it to the /system/priv-app/FireTabletSettings folder, CX tells me it's read-only and can't copy it over. I have it in root mode, and even tried enabling adbd insecure for good measure. But no joy. I do not currently have a recovery (twrp or other) installed.
So I need guidance on how to either enable write permissions (temporarily) on the settings folder or on how to install a recovery, all without adb. Or if there's some backdoor way to enable adb, that would work too.
Thanks for any advice.
UPDATE: Hey friends, I just wanted to update this thread with my progress (albeit negative progress, unfortunately). It seems my gamble with this ill-advised mod has failed pretty hard. I'm updating as a cautionary tale to others considering modding their settings file outside the recommended OS versions. I can say pretty confidently: DON'T DO IT.
EDIT: After initially getting stuck after a hard reset, I was able to manually flash an Amazon rom using adb sideload. This did the trick. It is now full factory stock, including the settings panel. I have to do everything over again (except messing with the settings panel), but I have control of my tablet again. The moral of the story is, unless your os version is supported, don't mess with the settings panel. It will rob hours of your life you'll never get back.