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.)
Related
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?
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
mrgygar said:
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
Click to expand...
Click to collapse
Sad, no one wants to reply. Or perhaps no one knows.
Did a backup, and experimented. I couldn't update directly, so I wiped back to a stock ROM, and upgraded to 1.2.1. Rooted with ManualNooter, and the market worked. So I have no idea what was going on, but it works now. Sadly, a computer accident made me lose my backups (including unrooted images). But at least I've got something functional.
I am currently in the same boat with my NST (BNRV300) running rooted 1.1.2. I last installed and/or updated some Market apps successfully perhaps about a year ago, and have not made any other change to the Nook, so I am at a lost as to what might be the cause. Any pointers would be greatly appreciated.
For now, my workaround this problem is to download the desired app's apk file from an alternate source (e.g., APKPure) then side-load it onto the NST.
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Sent from my NST
nmyshkin said:
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Click to expand...
Click to collapse
I think you are right -- my NST credential with the Playstore must have expired or more likely become invalid when I changed my password on my Gmail account.
If so I can't figure out how to re-validate the credential: I recall entering my Google login/password via the YouTube app during the course of rooting my NST using the MinimalTouch tool's 2-phase process, but now I can't even get the YouTube app to start (error message: ... problem starting up, please check your network connection and system time).
Look here
I responded to a related issue awhile back. Not sure if the info at the link might kick-start the signing in process.
Thanks for the pointer.
I decided to go the route of "factory reset, upgrade to 1.2.1 and re-root using Nook Manager", as simply re-rooting 1.1.2 using the old tool (Minimal Touch) is tedious & somewhat error-prone -- plus I'd like to try out 1.2.1.
That was what I would usually suggest but the farther I have gotten from that "day 1", the less likely I am to take/offer the same advice. I've made so many modifications at this point I don't think I'd ever get it back to its present state! Back up early and often...and, apparently, access the Market every so often, even if you don't want anything.
Good luck!
"Service Unavailable - Software update is temporarily unavailable. Try again later."
I swear every phone I've had, at one point or another, gets this message when I try to update. Nothing fixes it, I've tried it all. Only way I've gotten 93% of updates since my Eris is manually installing. In fact I think my first XDA post was how to resolve this, and I just had to do it myself.
So I found the stock KK ROM and, once again, will use Odin to install it and re-root, but why does this always happen? A few times, whatever. Almost all the time, thank God for XDA. Every time....ok what's going on? I backup and FDR before every update to be sure it's as clean as possible.
I've always rooted, but otherwise don't do anything. Is this just me? Does this happen a lot to other people? Is it purely coincidence? I can't find hardly any threads about it for the Note 3...
Basically....WTH?!?!
Last I checked, OTA isn't supposed to work when you're rooted...
ShadowLea said:
Last I checked, OTA isn't supposed to work when you're rooted...
Click to expand...
Click to collapse
The thing with that is I have gotten OTA's when rooted, even ones that removed root. That may have been a phone or two ago though. But the majority of the time I get this. I just don't get it, does everyone else with root only install updates manually? Maybe I should try one of those apps that temporarily unroots so you can install an update...
k1ng r4t said:
"Service Unavailable - Software update is temporarily unavailable. Try again later."
I swear every phone I've had, at one point or another, gets this message when I try to update. Nothing fixes it, I've tried it all. Only way I've gotten 93% of updates since my Eris is manually installing. In fact I think my first XDA post was how to resolve this, and I just had to do it myself.
So I found the stock KK ROM and, once again, will use Odin to install it and re-root, but why does this always happen? A few times, whatever. Almost all the time, thank God for XDA. Every time....ok what's going on? I backup and FDR before every update to be sure it's as clean as possible.
I've always rooted, but otherwise don't do anything. Is this just me? Does this happen a lot to other people? Is it purely coincidence? I can't find hardly any threads about it for the Note 3...
Basically....WTH?!?!
Click to expand...
Click to collapse
OTA is not working when phone is rooted, unroot your phone and try to update.
Sent from my SM-N900 using XDA Premium 4 mobile app
k1ng r4t said:
The thing with that is I have gotten OTA's when rooted, even ones that removed root. That may have been a phone or two ago though. But the majority of the time I get this. I just don't get it, does everyone else with root only install updates manually? Maybe I should try one of those apps that temporarily unroots so you can install an update...
Click to expand...
Click to collapse
These days, Root = No OTA.
The old method was : Enable survival mode in SuperSU (Pro needed) --> Disable Superuser --> Reboot --> Install OTA --> Reboot --> Re-enable Superuser --> Disable survivor mode.
Not sure if it still works though.
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.
I got a message this morning about a system update on my YT3-X50F
(YT3-X50F_S000022_160606_ROW_TO_YT3-X50F_S000023_161201_ROW) -
Downloaded and the install failed.
I googled and it seems this is happening to others. however the "Resolution" was to download from some Russian site
(https://forums.lenovo.com/t5/Androi...x50f-dec-2016-update-fail/td-p/3523775/page/3)
I'm not even clear on what the resolution steps are.
I'm asking here because I've used XDA as my go to forums for years (my third tablet). You guys are always helpful and able to explain stuff anyone can understand.
I had rooted my tablet, but went ahead and unrooted. I also pulled the "nuclear" option and factory reset. I was already on the verge of needing to do so anyhow since it was having a bunch of annoying freezing and rebooting issues. Its in the process of reinstalling all my apps now