NVIDIA Shield Pro rooted using wget to download Dropbox file - Shield Android TV Q&A, Help & Troubleshooting

Sorry, but probabely I am blind, or lost the track. I have rooted a NVIDIA Shield Pro 2019 running now Lineage OS 17.1.
I have installed BusyBox v1.34.1-meefik. I am trying to download a file from my Dropbox account by using:
Code:
wget -O /storage/self/primary/XXX/XXX.7z "https://www.dropbox.com/s/XXXX/XXX.7z";
Yesterday this piece of code was working as expected. Today (after I have rooted the device again, because I wanted to have a clean installation after trying different tools and things) it is not working anymore.
I am getting this message:
Code:
wget: note: TLS certificate validation not implemented
All files (tried different) I am loading from Dropbox having around 800kb, even if the Original file on Dropbox is smaller, or bigger. On my Linux PC the same command is working, so the files on Dropbox are okay.
With the "?dl=1" I am getting the message
Code:
wget: note: TLS certificate validation not implemented
wget: server returned error: HTTP/1.1 400 Bad Request
Also
Code:
--no-check-cert
does not work/have a effect.
I also have tried to download with curl. Same ****, but I think the files are 1kb.
What am I doind wrong? I mean Yesterday it was working on the same device. I just rerooted it for having a clean installation. And now I am stuck. Spend several hours on google.
Don`t know and understand if it has something to do with TLS, or SSL.
Really appreciate your help.
Thanks in advance.
Stefan

Related

[Q] "adb server didn't ack * failed to start daemon"

okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.
*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?
dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.
Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.
No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though
Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.
Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App
I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809

need help installing Ubuntu 13.04 on nexus 7.

for the past couple of days i have been trying to install Ubuntu 13.04 on my nexus 7 but unfortunately, i keep running into problems. i have a laptop with Ubuntu 13.04 installed on it, but when i run the desktop installer it gives mean error for checksum validation. then i found a way that you could do it on a windows PC however when i go to download the cd images it bring me to a 404 (page not found) website. i would give the link but i am not allowed due to my account restrictions. if anyone could call me via Skype or team-viewer and could help me or perhaps provide an alternate way of installing Ubuntu or even tell me what i am doing wrong it would be much appreciated.
thanks in advanced, Kevin.
http://cdimage.ubuntu.com/releases/...3.04-preinstalled-desktop-armhf+nexus7.img.gz
dont i also need the boot img?
kevinperyea said:
dont i also need the boot img?
Click to expand...
Click to collapse
If you are installing it as the lone system, than yes, you will need the boot image. If you are using multirom to multiboot, than no, you wont need the boot image.
Sent from my Nexus 7 using xda premium
Its not very hard actually..First decide that do you want to remove android and replace it with android or yoou want to keep android untouched while multibooting ubuntu on your device as a secondary OPERATING system...
If you want me to I can write a full guide describing both procedures....I RECOMMEND MULTIBOOTING....
I need some help too
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
Thank's in advance,
GGgamer16
* one more thing ,i saw someting about multibooting, does it work like in windows(when you boot up it's asking you which os to run) or how does it work, and tell me hwo do i do it.
Ubuntu 13.04 on Nexus 7 2012
Posting in wrong spot... couldn't delete :/

[Q] Sideloading apps from Mac

I can't find instructions on how to side load apps from OS X to my Nook Simple Touch. I rooted it using these instructions. I also installed NTGAppsAttack but it took me a while before I could log into Google and get it working. Now that it's working it doesn't seem to do much since I can't search the Google Market (probably because I can't side load apps).
First, I'm trying to install the Kindle App that I got from here. I downloaded the Android tools, but when I try to run ADB, it seems that the device isn't connected:
$ ./adb install ~/Downloads/Kindle_3.3.1.1.apk
error: device not found
- waiting for device -
I thought maybe I could load the .apk file in the Finder. There isn't enough room for me to load it onto the NookManager partition (only 8 MB free) so I put it in the My Files/Documents folder of the NOOK partition. However I can't seem to find that location using the ReLaunch app. It won't let me out of the sdcard directory.
I also tried launching ADB Konnect on the device and it tells me "Root Access Denied!"
Is it possible to install apps via SSH? I can't figure out how to get SSH running.
I'd appreciate any help. Thanks.
No idea about Macs, but for USB you will have to modify ~/.android/adb_usb.ini
Nook is not a "known" Android.
Code:
0x2080
If your root uses ADB over WiFi that would work too.

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.
WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?
For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.
The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?
Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.
Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards
Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards

Need help installing a ROM, any ROM

UPDATE: I'll leave this post for the moment. But I am going to start a new one for getting help on the first step in the installing a custom ROM process that is failing. Please ignore this post for now.
I have an old S4 (Model SPH-L720) that I originally obtained through FreedomPop (Sprint network). I haven't used the service in years and actually do not intend to ever attach it to a network. But I would find it useful to be able to connect to the internet via WiFi, download apps from the Play Store, and use them. Unfortunately, I have been unable to even get TWRP installed. I have tried multiple methods and applications, but no luck. I don't know if FreedomPop has the phone locked down, the phone is broken, or I'm simply doing something wrong. I just know that I've wasted a good 8 hours and I'm going to toss the phone in the trash if I can't get something going quickly. I'd appreciate any help.
Notes:
I was able to use Odin to re-install the original Samsung build, but that didn't fix any of the issues. The device seems dependent upon connecting to FreedomPop. It will not allow use of the Play Store.
I have been unable to get fastboot to connect. Depending on the app I use, I get either the error "adb server version (32) doesn't match this client (39); killing..." or "adb server version (32) doesn't match this client (41); killing..." I have not been able to find client version 32 anywhere.
I have been unable to use the adb sideload function. I get the error, "cannot read 'twrp-3.6.2_9-0-serranoltespr.img'" or
adb server version (31) doesn't match this client (39); killing...* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I'm not a developer. I'm lost.

Categories

Resources