Saturday, March 24th, 2018

darkoshi: (Default)
Trying to get the Android SDK to work, so I can root my phone. It requires Java, though it doesn't tell me what version.

On the following Oracle JDK 8 page, when I click the radio button to accept the license agreement, and click any of the download links, I get the error "We're sorry, the page you requested was not found."

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

I even tried the pages for the Java 9 and Java 10 JDKs. All of the download links get the same error. I tried with different browsers. I even logged in to the site, as is sometimes required for downloading older versions of the files. What is going on? Are the links working for anyone else? Is it a temporary outage? How can the world go on, if the JDK can't be downloaded anymore? Did everyone switch over to using non-Oracle JDKs? AAAAAHHHHH.

Now I thought to search Twitter. It's not just me; other people are having the same problem:
https://twitter.com/search?q=oracle%20jdk&src=typd
Well, that's a relief, sort of. But is the world going to end?

So I decided to try downloading OpenJDK instead. Apparently that's made by Oracle too. But why does the main download page say that JDK 9 and 10 are "ready for use", while JDK 8 (Updates???) are "early access"? Eh? At least I found a working download link there.

Update, 2:21pm:
The Oracle downloads are working again now. An Oracle employee posted on this reddit thread that the temporary outage was resolved about an hour ago. That's the only semi-official notice I found about it. No mention of it on Oracle's twitter feed, even though I counted about 20 tweets directed at @Oracle about the problem. Based on the posts on twitter and elsewhere from people getting the 404s, the outage was from around midnight to 2pm (EDT).

unlockable

Saturday, March 24th, 2018 11:17 pm
darkoshi: (Default)
I'm ready to unlock my phone's bootloader, as the first step for rooting it. I have the unlock code, though I haven't actually used it yet. To get the code from Motorola, they make you accept a legal agreement, which states that unlocking the bootloader will void the warranty, and all kinds of other scary things, such as it may lead to DEATH. ::eep! goes hide under a rock for a bit::

That's like saying that loading custom software onto your computer could lead to death. Perhaps so, if you got some really bad software that made your CPU overheat and purposely disabled the fans and any normal safety shut-down mechanisms from working. Or various other highly unlikely things that could be imagined.

I also backed up my phone apps and contacts as well as I could, as unlocking the bootloader will delete it all. Unfortunately, some of the best backup apps can't be used unless the the phone is already rooted.

But based on some things I read, maybe I should delay rooting the phone, as it could prevent the phone from upgrading from Marshmallow to Nougat. Per this page, the Moto G4 got the Nougat update a year ago. But per this page, the Moto G4 Play (which I have), just started getting the update in February - but only the Verizon and international unlocked versions. Mine is a local unlocked version. But maybe the update will come to my phone soon too.

Oh! The whole reason I started writing this post: The word "unlockable" can mean 2 things. I keep reading it as "unable to be locked", whereas in this context it instead means "able to be unlocked".

.

Now, a note about the Android SDK Tools. The adb (Android Debug Bridge) and fastboot utilities are required for unlocking the bootloader. Most of the instructions I found tell you to download the command-line (non-Android Studio) version of the tools (which are available at the very bottom of the above page), and then to run "sdkmanager.exe" (a GUI app) to get the other tools. But that exe is no longer included in the command-line tools. Now they only include "sdkmanager.bat" which is a non-GUI version. To use this batch program to download adb & fastboot, do the following.

1. You should have the Java JDK installed (version 8 worked for me), and your JAVA_HOME environment variable should point to the JDK folder. Otherwise you'll get an error that JAVA_HOME is not defined.
2. Open a command prompt to the downloaded Android SDK's tools\bin folder.
3. Run this command to get a list of the installed and installable packages:
sdkmanager --verbose --list
4. The list should include an entry for "platform-tools". This is the one that includes adb and fastboot.
5. Run this command to install that package:
sdkmanager --verbose "platform-tools"
6. Enter "y" to accept the license agreement.
7. The \platform-tools folder will be created with adb.exe and fastboot.exe.

Or, this may be a simpler method.

July 2025

S M T W T F S
  1234 5
6 789101112
13 141516171819
20212223242526
2728293031  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Monday, July 14th, 2025 10:52 am
Powered by Dreamwidth Studios