Install ADB & Fastboot on Ubuntu 18.04 / Linux Mint 19 ...

The Nuclear Option for No-Surf Lifestyle (Android Users)

The Nuclear Option for Android Users

This guide is my attempt to create the ultimate no-surf lifestyle change for repeat offender internet addicts. This is a nuclear bomb, scorched earth policy that will make your house a surf-free zone, with NO workarounds. These steps will block all possibility of using your phone or your PC to surf, and there won't be anything you can do about it in a moment of weakness. By the time you complete this guide, you will have performed some fairly extreme measures to block yourself from surfing, measures which border on absurdity. In my experience, they are necessary. (Note: This guide is for Android users, but if I had an iPhone and couldn’t figure out a similar method for the iPhone OS, I would switch to Android just to be able to pull this off. It’s that important for me.)
There are a few key features of the nuclear option:
I’m going to assume you are already sold on the fact that you need to get off the internet. If not, go read the top posts on this subreddit (the irony), then come back here. There is a ton of very thoughtful writing on here by people more articulate than myself. I’m only going to try to sell you on why you should go full-blown ape on your internet access (instead of half-ape), and how to do it.

Why Half Measures Don’t Work

I am a 5-year No-Surf failure. This is a long-term project of mine that has failed at each attempt. I’ve tried app blockers, timers, exercising discipline and self control, etc., but nothing has stuck for more than a few weeks. The draw of porn, Youtube, social media, and worst of all, Reddit, have always tempted me to find workarounds. Every roadblock I’ve erected has been too easily removed when temptation presents itself. We are dealing with technology that has been engineered for easy access and addictive content. Like probably 99% of us on this subreddit, I’ve considered desperate measures, including asking the question...
...Why not switch to a dumbphone? Well, there honestly are legitimate reasons not to do this. My career prevents me from switching to a dumbphone. I need access to email, and my company uses an annoying security app for two-factor authentication each time my company laptop connects to an external wireless connection. There are also very real benefits that come with a smartphone that are limited or unavailable with most dumbphones: a high quality camera, music, Google Maps, Google Drive, Wikipedia, Weather, online banking, Venmo, looking up a phone number, etc. These tools are hard to abuse because they’re boring. The key is throwing out the bathwater but not the baby.
Why not just install app-blockers or usage timers for distracting apps? I believe this is like telling a crackhead to take his crack and put it in a little box on his kitchen table, lock the box, then hide the key from himself somewhere in the house. This may seem like a good solution to someone who has never met a crackhead. What we want to do is more like telling the crackhead to lock his crack in a box, drive four states over, ride a horse into the wilderness, get off the horse and walk over two mountains, then dig a hole and bury the box. Yes, in theory, he could go get his crack, but it’s going to be pretty inconvenient. In the real world, here’s what I’ve experienced with app-blockers:
Why not just use some discipline? This is by far the worst way to attempt no-surf. You will cave at the first moment you get horny, lonely, or just bored. I have proven to myself time and time again that this approach is completely ineffective for those of us with a real problem. Since you’re browsing No Surf and probably a Reddit user, I bet you know what I mean.
The only guaranteed no-surf solution is a scorched earth policy. There is no discipline required if you follow these steps, because it is extremely annoying to reverse. The only workaround for this method is a two-hour process that requires leaving my house: I have to take my phone and a laptop to a public place with a wifi connection, download android developer tools again, and tediously reverse all of the steps in this guide. This is great, because I have never been horny enough to justify driving to a coffee shop and spending two hours fucking around with PowerShell commands just to re-enable the ability to look at titties on a three inch screen.
This method leaves you with no choice but to adopt healthier lifestyle habits. The internet has always been an irresistible temptation for me, and it has consumed basically all of my downtime at the house for about a decade. In the weeks after I pulled the pin on this grenade, I was amazed by the lifestyle changes that occurred. Within hours of completing the process, I picked up a book for the first time in months. There was literally nothing better to do in my whole damn house. My sleep schedule went from 6-7 hours per night to 8-9 hours, because honestly, it’s boring to stay up late without the internet. To me, this was amazing, and I’m sure many of you can relate. I started to exercise more consistently. I started back up with an old meditation habit I had dropped a year or two ago. I’ve never been happier to be this bored.

The Nuclear Option

Disclaimer: Many of the following steps related to removing system apps are strongly plagiarized from this guide. Huge thanks to the original author.
  1. Cancel your Internet subscription at home. If you really have a problem with internet use, this is when your brain will start listing reasons why this is a horrible idea. What about Netflix? What about streaming music? What about when I need to search for a recipe? How is my refrigerator gonna reorder from Walmart when I run out of nutterbutter?? What about my boo Alexa?!?!!? You got to stay strong fam, we need tough love here. Aspects of this are going to be a little painful, but that's kind of the point. Nuclear Option, baby. Treat yourself to something nice with the $75/mo you save on your internet bill. And go get a library card.
  2. Uninstall all social media and other distracting apps on your phone. Again, your brain may protest this. How am I gonna know what’s happening with my friends if I don’t have Facebook, Snapchat, Instagram, Twitter, blah blah blah? I can’t uninstall Youtube, I use it to learn useful things sometimes! Nuclear Option, baby. If you want to know what your friends are doing, call them and talk to them. I did make one exception for myself: I kept Facebook Messenger Lite because a) you can’t use it to browse your FB feed, and b) some of my friends still use it instead of text messaging. Once this process is complete, you will be logging into Facebook very infrequently, and I didn’t want to accidentally ignore their messages. (Side note, I know there are privacy issues with the Messager app, so if that bothers you, don’t install it.) If you have any browsers installed in addition to Chrome, delete them now.
  3. Try to uninstall the Chrome android app. You will notice that there is no uninstall option, since it’s considered a system app on the Android platform. There is a way around this (without needing to root your phone) which we will be covering shortly. This also applies to other system apps we want to delete, such as Google Play Store.
  4. Install the Android apps “MacroDroid” and “App Lock”. You will need these later on.
  5. This is the point where you need to install any useful apps you think you may eventually want on your phone. Suggestions with high usefulness and low abuse potential include the Wikipedia app, Venmo, Google Podcasts, Audible, a good weather app, etc. This is your last chance to install these as we will be deleting the Google Play Store app shortly.
  6. Download the ADB binary for your particular OS (Windows, Mac, Linux)
  7. Extract the Zip File into a folder you can quickly access.
  8. On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
  9. Now in your phone’s settings, enter Developer Options and find USB Debugging. Enable it.
  10. Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
  11. On your computer, browse to the directory where you extracted the ADB binary.
  12. Launch a Command Prompt in your ADB folder. For Windows users, this can be done by holding Shift and Right-clicking then selecting the “Open Powershell window here” option.
  13. Once you’re in the command prompt/terminal, enter the following command: “adb devices” (if that produces an error, try “.\adb devices” (omit the quotation marks))
  14. You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
  15. Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
  16. Enter the following command: “adb shell” (if that produces an error, try “.\adb shell”)
  17. Execute the “pm list packages” command (without quotes) to find package names.
  18. ALTERNATIVELY: You can also easily find the package name of an installed system application by installing the App Inspector app on your phone. I prefer doing it this way so you know exactly what the app name is of the application that you are about to uninstall.
  19. Execute the “pm uninstall -k --user 0 command (without quotes) to uninstall a specific system application. It is critical that you remove all surfing temptations here, so please be honest with yourself. Mathew 5:30: “And if thy right hand offend thee, cut it off, and cast it from thee: for it is profitable for thee that one of thy members should perish, and not that thy whole body should be cast into hell.”
  20. e.g., for Chrome, you will use “pm uninstall -k --user 0 <com.android.chrome>”
  21. If memory serves, Youtube is also a system app and will need to be deleted this way too.
  22. Repeat for any other app you were unable to remove in step 2.
  23. Delete the Google Play Store app to block yourself from reinstalling a browser or social media app in a moment of weakness. *CAUTION: THIS IS YOUR LAST CHANCE TO INSTALL ANY USEFUL APPS YOU MISSED IN STEP 5\*
  24. Use “pm uninstall -k --user 0 ” to uninstall the google play app.
  25. Now, delete the ADB binary tools from your PC. This is critical, because the goal is to intentionally create a catch-22 for yourself. You will not be able to reverse the steps above without ADB binary tools, and since you have no wifi in your house (see step 1) and no browser on your phone, there’s no way to download ADB binary tools without leaving your house and going somewhere with wifi. For me, this is inconvenient enough that I won’t do it. You have now blocked all surfing capabilities on your phone and deleted the tools you would need to re-enable it. This does leave one work-around that we want to fire bomb next, which is hotspot/tethering.
  26. Disable the hotspot feature on your phone, so you can’t provide a connection to another device. I’ve spent a lot of time trying to figure out an ADB command to accomplish this, with no luck. But I am not a developer; I’m just a guy, so who knows. I have managed to come up with a workaround using an automation app that accomplishes what I need. You will use the MacroDroid app you downloaded in step 4 to make a simple macro that blocks tethering. In basic terms, we want a program that executes the following logic: “If hotspot is turned on, turn off hotspot”. If you try to turn on hotspot with this macro active, it will immediately toggle back off. It’s clumsy but it’s effective.
  27. Open the MacroDroid app and select “Add Macro”.
  28. Next you will select a trigger for the macro. Select “connectivity” to see available triggers in this category.
  29. Select the “Hotspot Enabled/Disabled” trigger and select the “Hotspot Enabled” option.
  30. Now that we have a trigger defined, we want to select an action. Select the “Actions” tab towards the top of the screen.
  31. Select “Connectivity” again, and then “HotSpot On/Off”.
  32. Select the “Disable HotSpot” option and hit OK.
  33. Hit the check mark in the bottom right corner of the screen to save your macro.
  34. Create a similar macro for USB or bluetooth tethering if that feature is available on your phone.
  35. Now you want to use the other app you downloaded in step 4, “App Lock” to prevent you from disabling this macro (and using the hotspot feature in a moment of weakness). This is what I meant in the intro by the phrase “measures which border on absurdity”.
  36. Open App Lock. I like App Lock because you can create a numerical password of arbitrary length. On a piece of paper, write down a random string of numbers 9 to 12 digits long, like “893619412876” or "368597241" and make this the password for App Lock. *[*Alternatively, If you want to, literally use on of the exact strings above, and don’t write it down on a sheet of paper. If you ever need to unblock this feature, you will have to leave the house, find a place with public wifi, pull up this reddit post on your laptop, and get the key off of it. It’s absurd, I know.]
  37. In App Lock, scroll down the list of apps until you find the MacroDroid app, and lock it. You have now blocked hotspot and removed the possibility of unblocking.
  38. If you wrote your password on a piece of paper in step 36, GET YOUR PASSWORD OUT OF THE HOUSE. Take it to your mom’s house, or go to the park and bury it in a bottle next to a tree. Yes, that's absurd. Do it.

Congratulations, You’ve Fucked Yourself!

You now have Amish level internet access! As a measure of comfort, these steps are reversible, but I’m going to leave it to you to figure out how. Better yet, don’t even try.
Let’s recap:
From this point on, if you need to look for a job, or learn how to make a mimosa, or look at cute cat pics, you will have to go to a library or a coffee shop with a laptop, because you cannot access anything at home. What this means is this: if something really is important enough, like searching for a job, you will go to a library, which is actually a great place to focus on important stuff like searching for a job. What you probably won't do is go to the library just to look at cute cat pics for hours on end. Which is a good thing.
I would strongly encourage you to extend your firebombing campaign to offline games, any downloaded porn you have saved locally on your phone/PC, etc. In my opinion, the most entertaining thing in your house should be a book. YMMV
The world is your oyster now. Go to the Library. Try meditation. Start exercising for fucks sake. Cook some good food. Good Luck!
submitted by nuclear_no_surf to nosurf [link] [comments]

[TOOL] Mirror your Android phone to your computer over ADB

Just wanted to let this awesome community know of a simple app I came across recently. It's called scrcpy. It's available for all platforms, Linux, Windows and MacOS. Moreover, it's completely free and easy to set up. Please bear with me for this long post.

Download:

Download scrcpy from GitHub

Requirements:

You'll have to ensure you have USB Debugging enabled in Developer Options. If you're running Linux, ensure that you have the required ADB binaries on your PC.
Enable ADB debugging in your device

Installation:

The instructions for Linux and MacOS are pretty straightforward. On Windows, I'd suggest you to extract the contents of the zip file to an easily accessible directory, say C:\scrcpy, then add the directory to your PATH environment variable. If you already know how to, skip the steps below.
To add the directory to the environment variables, follow the steps below (Applicable to Windows 10. It differs slightly on older versions of Windows.) :
Adding the C:\scrcpy directory makes it easy to launch scrcpy from anywhere. All you need to do is plug in your Android phone (with USB debugging enabled), open a command prompt (or PowerShell, whatever you prefer) and run:
scrcpy
If you're connecting your Android phone for the first time after enabling USB debugging, I suggest you to run adb devices. A dialog should show up on your Android phone, asking you to allow USB debugging. Check "Always allow from this computer" and tap on "OK". If you now run adb devices again, it should list your device's serial number along with "device".

What's better is that with a recent update, you can mirror your phone even with the display off. You can do this by pressing Ctrl + O or even start mirroring with screen off by running the scrcpy -S command.
More info on scrcpy shortcuts

Thanks for reading! Sorry for the extremely long post.
submitted by buffonism to kustom [link] [comments]

How to temp-root the nokia 3.1 Plus

First of all, i must credit the user diplomatic on XDA for finding the exploit and making this possible. His thread link.
REQUIREMENTS A Nokia 3.1 Plus and
Either:
Familiarity with ADB (if using PC) and basic Linux shell commands You agree to post the model name of any unconfirmed device which ran mtk-su successfully Familiarity with the Thanks button under XDA posts
INSTRUCTIONS FOR ADB
  1. Make sure you meet all the requirements listed above, especially the last 2.
  2. Download the current mtk-su zip file to your PC and unzip it. Inside will be 2 directories: 'arm' & 'arm64' with an 'mtk-su' binary in each. Pick the arm64 one.
  3. Connect your device to ADB and push mtk-su to your /data/local/tmp folder: push path/to/mtk-su /data/local/tmp/
  4. Open an adb shell: adb shell
  5. Change to your tmp directory: cd /data/local/tmp
  6. Add executable permissions to the binary: chmod 755 mtk-su
  7. At this point keep your device screen on and don't let it go to sleep. Run the command: ./mtk-su
  8. It should only take a second or two. If the program gets stuck for more than a few seconds and your device is awake, press Ctrl+C to close it. The -v option turns on verbose printing, which is necessary for me to debug any problems. The output of ./mtk-su -v is similar to this: $ ./mtk-su -v param1: 0x3000, param2: 0x18040, type: 2 Building symbol table kallsyms_addresses pa 0x40bdd500 kallsyms_num_syms 70337, addr_count 70337 kallsyms_names pa 0x40c66d00, size 862960 kallsyms_markers pa 0x40d39800 kallsyms_token_table pa 0x40d3a100 kallsyms_token_index pa 0x40d3a500 Patching credentials Parsing current_is_single_threaded ffffffc000354868+50: ADRP x0, 0xffffffc000fa2000 ffffffc000354868+54: ADD xd, x0, 2592 init_task VA: 0xffffffc000fa2a20 Potential list_head tasks at offset 0x340 comm swappe0 at offset 0x5c0 Found own task_struct at node 1 cred VA: 0xffffffc0358ac0c0 Parsing avc_denied ffffffc0002f13bc+24: ADRP x0, 0xffffffc001113000 ffffffc0002f13bc+28: LDR [x0, 404] selinux_enforcing VA: 0xffffffc001113194 Setting selinux_enforcing Switched selinux to permissive starting /system/bin/sh UID: 0 cap: 3fffffffff selinux: permissive #
  9. Now, we got the temp-root, but we can't use it, what we should do? We must integrate it within magisk.
  10. Download and install the init.d scripts support app. (Support the developer.)
  11. Make a folder named 'init.d' on your internal storage. Also make a 'bin' folder inside 'init.d'. Set up the init.d app up like this:
  1. Download and install the Magisk Manager apk. For Android 9, the highest version that will work is 7.1.1. The latest version should be usable for Android 8.x and lower, but 7.1.1 may be better in all cases.
  2. In MM, go to Settings, Update Channel, Custom, and enter this URL: https://raw.githubusercontent.com/topjohnwu/magisk\_files/841e978604f989d04549013cd4dcc7e34aea5288/stable.json . This will freeze the update version of Magisk at 18.1. That's necessary for MM to create the right environment for Magisk modules to work.
  3. Download the current su-boot script, unzip it, and put suboot.sh inside your /sdcard/init.d folder.
  4. Download the current mtk-su zip and put your appropriate mtk-su file in your /sdcard/init.d/bin folder.
  5. Download the Magisk 18.1 zip (not 19.x or higher). Extract the arm/magiskinit file and move it to your /sdcard/init.d/bin folder. That is the only file you will need from that zip. (Support the developer.)
  6. Now you should be ready to launch the Magisk backend. Either reboot or tap 'Run scripts now'. The process will take a few seconds before telling you that 1 script has finished. If it ran successfully, last execution result will show something like this: Code:UID: 0 cap: 3fffffffff selinux: permissive source type magisk does not exist Error in: allow magisk (null) (null) (null) client: launching new main daemon process That output was made by the latest mtk-su & suboot script. If you get a different result, then something may have gone wrong.
  7. At this point, you should be able to run 'su' or do a root request from an app and get a prompt.
  8. When you open Magisk Manager, it will prompt you with Requires Additional Setup. On this window, you can tap Yes. This is safe. Make sure that you have done step 5 before doing this.
  9. Turn off update checking in MM.
Never try to do a direct-install Magisk Update, this will brick our phone. Congratulations, if you did everything right, you must have now working temp-root. Use it whatever you like!
submitted by ach_renders to Nokia3_1Plus [link] [comments]

[Tutorial - Android] How to prevent FEH from stopping your music when launching. No root required!

Saw this on /pokemongo and instantly applied it to FEH. Works great!
https://www.xda-developers.com/pokemon-go-audio-focus/
For those unable to visit for some reason, here are the instructions:
cmd appops set com.nintendo.zaba TAKE_AUDIO_FOCUS ignore
Example image for pokemon go
submitted by wait99 to FireEmblemHeroes [link] [comments]

Pwntools v3.0 Released

Hey guys, Pwntools developer here!
If you haven't used it before, Pwntools is a Python library/framework developing exploits for Capture The Flag (CTF) competitions, like DEFCON CTF, picoCTF, and wargames like pwnable.kr.
Pwntools makes the exploit developer's life easier by providing a suite of easy and quick tools that do exactly what an exploit developer would want them to -- without the hassle of writing template code or dealing with various minor gotchas.
If you're a new user to pwntools, you can check out the Getting Started page on the documentation, available at docs.pwntools.com.
The v3.0 release is a big one for us, and our first in over eighteen months!
Both existing and new users can install Pwntools with a simple pip install --upgrade pwntools.
For those who just want to see what's new, you can check out the CHANGELOG.md here.
In particular, all of the changes which were made on the Binjitsu fork of Pwntools have been merged back into upstream Pwntools.
Everything below here is the changelog, for ease of reference.

3.0.0 (August 20 2016)

This was a large release (1305 commits since 2.2.0) with a lot of bugfixes and changes. The Binjitsu project, a fork of Pwntools, was merged back into Pwntools. As such, its features are now available here.
As always, the best source of information on specific features is the comprehensive docs at https://pwntools.readthedocs.org.
This list of changes is non-complete, but covers all of the significant changes which were appropriately documented.

Android

Android support via a new adb module, context.device, context.adb_host, and context.adb_port.

Assembly and Shellcode

Context Module

DynELF and MemLeak Module

Encoders Module

ELF Module

Format Strings

GDB Module

ROP Module

Tubes Process Module

Tubes SSH Module

Utilities

submitted by ebeip90 to netsec [link] [comments]

Chaos Rings Preservation Project

EDIT: Now updated for 2020! See new info below.

EDIT: Now updated for 2019! See new info below. EDIT: Now updated for 2018! See new info below.

Disclaimer:

So first off, let me make one thing quite clear: I cannot share any files for what I'm about to discuss due to the rules of this sub. My aim here is simply to draw attention to this series and encourage others to create playable archives for themselves before it's too late.

Info:

Now, backing up a bit: recently it occurred to me that I haven't touched a Chaos Rings game in quite some time, and that I missed the earlier games in the series. It also occurred to me how difficult it is becoming to play them considering Square Enix pulled support and removed the first three games from the App Store (both for Android and iOS). To be specific, this includes:
Chaos Rings III is a much newer game and still runs on modern devices just fine, so I'm less concerned about that one for the time being.
Chaos Rings is an important series to me considering the games are great JRPGs in their own right and still stand as some of the best original games made specifically for mobile devices to date. While anyone who purchased the games while they were available can still install them from their app history, you'll need a very old Android device to do so. I tried running them on my 2013 Xperia Z running Android 4.3 and they crashed immediately. In theory, anything older than Android Lollipop should work, but obviously your mileage will vary.
Basically, this is a very endangered series that could potentially become completely inaccessible without an official resurrection from Square Enix. At the moment, the only legal way to obtain the series for newcomers is to create a Japanese Playstation account, import the Japanese version of Chaos Rings III: The Prequel Trilogy for PS Vita, and use the included codes to download the oldest three games and their respective English patches digitally. No physical versions have ever existed.
Update: It is technically still possible to purchase the games on Amazon's app store (CR 1, CR O, CR 2), but they will not run on any current Amazon devices. The fact they haven't been pulled is likely an oversight. Still, if you intend to download the games through other, more compatible (but less official) means, purchasing here is your only option to show your support and obtain a legal license.

The Project:

Enter the Chaos Rings Preservation Project, my personal effort at creating a playable archive of the series that stands some chance at surviving the test of time. Since compatible real Android hardware is itself fast becoming extinct, PC emulation is the only way to go. And this too is harder than it sounds, as Android emulators tend to be very imperfect and have their own disadvantages. In the end, this is what I discovered:
Thus, I recommend using MEmu for Chaos Rings I and Omega, and AMI DuOS Lite Mumu/Nemu for Chaos Rings II and III unless MEmu is updated to correct its issues with the latter two games.

Backing things up:

Armed with the above knowledge, you should be able to set up the necessary emulators, log in to your Google Play or Amazon account, find the games in your app history, and install them to a runnable state. But this is only the first step. Next is ensuring the games remain playable for the foreseeable future.
The way I've done this is by backing up the virtual machines themselves, so the entire Android installation can be restored with the games preinstalled fresh. Since this saves all the necessary prerequisites too, I feel it is the safest and most likely way to keep the games alive.
MEmu makes this very simple: from the Multi-emu Manager application, use the arrow on the right to expand the VM options list and choose Export. This will create a .ova file of the entire virtual machine which is compatible with a number of other virtualization applications. For a preservation project, this is great.
Mumu makes things a bit more complicated, but it is still possible to backup virtual machines in a user-friendly way. There's no built-in interface for managing multiple virtual machines or creating new ones yourself, so instead you'll have to swap out one VM at a time if you'd like to keep the games separate. Mumu virtual machines are located under "C:\Program Files (x86)\Nemu\vms" (or your chosen installation directory). Backup the default VM ("myandrovm_vbox86"), then run Mumu and install Chaos Rings II. Exit, then backup the "myandrovm_vbox86" folder again. Then, restore the clean VM backup and repeat the process for Chaos Rings III. Once you've made backups, you can swap out which game to run by simply storing each VM in a different folder and renaming folders before launching Mumu. For power users, a simple batch file (like this one, for example) can automate the process--and even launch directly into the game! All in all it's not too difficult, but much less ideal than MEmu.
I would recommend creating both local and cloud copies of your backups for longevity.

Final thoughts:

After fighting an uphill battle with this all day, I finally have functioning backups of Chaos Rings, Chaos Rings Omega, Chaos Rings II, and Chaos Rings III which I can deploy to any PC. Since Chaos Rings II and III are not perfect yet I don't consider the project complete, so I eagerly anticipate seeing updates from the MEmu developers in hopes that they will solve the issues preventing those two games from being usable. Of course, most desirable would be for Square Enix to update the games for modern versions of Android and iOS or even port them to Steam for longevity, but for now the likelihood of that happening seems quite low.
Thus, it falls to the community to preserve this piece of JRPG and Android gaming history. I hope that my efforts to do so will inspire others to do the same!

2019 Update

A lot has happened in the last couple years since this project started for me, and unfortunately, certain changes to operating systems (especially regarding CPU execution) have apparently broken compatibility with the Chaos Rings I and Omega, which were only ever released as ARM apps. Chaos Rings II and III have native x86 binaries, which means they will still work in modern emulators as usual, but ARM apps required libhoudini, Android's ARM to x86 translation layer, to function... which they don't anymore. Also, as Android 4.x continues to age, support is vanishing fast even from emulators mentioned in this post. (Because Android switched from the Dalvik runtime to ART shortly after Chaos Rings, Android 5.x and future versions are not compatible.)
This led to a lot of fruitless searching for yet another replacement emulator. In the end, I concluded that x86-based virtual machines just aren't going to cut it. Chaos Rings requires real ARM emulation, and that led me all the way back to the humble Android Studio emulator. Google's emulator is definitely not designed for gaming or preservation, but it turns out it's actually quite portable when you strip away everything unnecessary for the task.
I began by firing up the full Studio application and setting up an Android 4.4 KitKat ARM image in the AVD manager. I then installed the same versions of the games listed above using adb and... it just worked.
From there I copied out just the Android SDK and .android folder in my user profile. To run in any arbitrary location, some paths need to be edited in .ini files and Windows needs an environment variable set to point the emulator to the new .android folder, but this was easily automated with a .bat file I wrote. I also deleted anything not required by the emulator to function, as it can be pretty bloated out of the box.
In the end, I managed to fit Chaos Rings I, Omega, and II into a single ARM-emulated VM and make it portable in only 7GB. That's more than other emulators, but also completely manageable, and this package should last long into the future. The Android Studio emulator is built on QEMU and in theory this version of the preservation project could be ported to Linux or Mac OS without much difficulty.
So, as it stands, Android Studio is now a valuable means of preserving this series. For as long as Google keeps providing KitKat system image downloads, you can build an emulator yourself. But keep it in a safe place so it'll still work once KitKat is dropped for good.

2020 Update

The Amazon listings for Chaos Rings have finally been taken down and PlayStation Vita is officially the last place you can purchase the series (only in Japanese). :(
Fortunately, there is some good news: for anyone feeling that Android Studio ARM emulation is too slow for their CPU, there is a fork of Nox emulator called XePlayer that is surprisingly great for Chaos Rings! Those who've seen my other comments on Android emulators know that I'm not a fan of Nox at all, but XePlayer seems to be the purest version of it and runs fast and offline--and better yet, is compatible with Chaos Rings I, Omega, and II all at once, which is a first for x86-based emulators. There is a quirk with Chaos Rings II touch emulation that requires every click to be a drag-and-release to register, but since most interactions are drag-and-release anyway, it's still plenty playable. XePlayer is now my top recommendation for an alternative to Google AVD.
submitted by LukeLC to AndroidGaming [link] [comments]

Chaos Rings Preservation Project (x-post /r/AndroidGaming)

EDIT: Now updated for 2020! See new info below.

EDIT: Now updated for 2019! See new info below. EDIT: Now updated for 2018! See new info below.

Disclaimer:

So first off, let me make one thing quite clear: I cannot share any files for what I'm about to discuss due to the rules of this sub. My aim here is simply to draw attention to this series and encourage others to create playable archives for themselves before it's too late.

Info:

Now, backing up a bit: recently it occurred to me that I haven't touched a Chaos Rings game in quite some time, and that I missed the earlier games in the series. It also occurred to me how difficult it is becoming to play them considering Square Enix pulled support and removed the first three games from the App Store (both for Android and iOS). To be specific, this includes:
Chaos Rings III is a much newer game and still runs on modern devices just fine, so I'm less concerned about that one for the time being.
Chaos Rings is an important series to me considering the games are great JRPGs in their own right and still stand as some of the best original games made specifically for mobile devices to date. While anyone who purchased the games while they were available can still install them from their app history, you'll need a very old Android device to do so. I tried running them on my 2013 Xperia Z running Android 4.3 and they crashed immediately. In theory, anything older than Android Lollipop should work, but obviously your mileage will vary.
Basically, this is a very endangered series that could potentially become completely inaccessible without an official resurrection from Square Enix. At the moment, the only legal way to obtain the series for newcomers is to create a Japanese Playstation account, import the Japanese version of Chaos Rings III: The Prequel Trilogy for PS Vita, and use the included codes to download the oldest three games and their respective English patches digitally. No physical versions have ever existed.
Update: It is technically still possible to purchase the games on Amazon's app store (CR 1, CR O, CR 2), but they will not run on any current Amazon devices. The fact they haven't been pulled is likely an oversight. Still, if you intend to download the games through other, more compatible (but less official) means, purchasing here is your only option to show your support and obtain a legal license.

The Project:

Enter the Chaos Rings Preservation Project, my personal effort at creating a playable archive of the series that stands some chance at surviving the test of time. Since compatible real Android hardware is itself fast becoming extinct, PC emulation is the only way to go. And this too is harder than it sounds, as Android emulators tend to be very imperfect and have their own disadvantages. In the end, this is what I discovered:
Thus, I recommend using MEmu for Chaos Rings I and Omega, and AMI DuOS Lite Mumu/Nemu for Chaos Rings II and III unless MEmu is updated to correct its issues with the latter two games.

Backing things up:

Armed with the above knowledge, you should be able to set up the necessary emulators, log in to your Google Play or Amazon account, find the games in your app history, and install them to a runnable state. But this is only the first step. Next is ensuring the games remain playable for the foreseeable future.
The way I've done this is by backing up the virtual machines themselves, so the entire Android installation can be restored with the games preinstalled fresh. Since this saves all the necessary prerequisites too, I feel it is the safest and most likely way to keep the games alive.
MEmu makes this very simple: from the Multi-emu Manager application, use the arrow on the right to expand the VM options list and choose Export. This will create a .ova file of the entire virtual machine which is compatible with a number of other virtualization applications. For a preservation project, this is great.
Mumu makes things a bit more complicated, but it is still possible to backup virtual machines in a user-friendly way. There's no built-in interface for managing multiple virtual machines or creating new ones yourself, so instead you'll have to swap out one VM at a time if you'd like to keep the games separate. Mumu virtual machines are located under "C:\Program Files (x86)\Nemu\vms" (or your chosen installation directory). Backup the default VM ("myandrovm_vbox86"), then run Mumu and install Chaos Rings II. Exit, then backup the "myandrovm_vbox86" folder again. Then, restore the clean VM backup and repeat the process for Chaos Rings III. Once you've made backups, you can swap out which game to run by simply storing each VM in a different folder and renaming folders before launching Mumu. For power users, a simple batch file (like this one, for example) can automate the process--and even launch directly into the game! All in all it's not too difficult, but much less ideal than MEmu.
I would recommend creating both local and cloud copies of your backups for longevity.

Final thoughts:

After fighting an uphill battle with this all day, I finally have functioning backups of Chaos Rings, Chaos Rings Omega, Chaos Rings II, and Chaos Rings III which I can deploy to any PC. Since Chaos Rings II and III are not perfect yet I don't consider the project complete, so I eagerly anticipate seeing updates from the MEmu developers in hopes that they will solve the issues preventing those two games from being usable. Of course, most desirable would be for Square Enix to update the games for modern versions of Android and iOS or even port them to Steam for longevity, but for now the likelihood of that happening seems quite low.
Thus, it falls to the community to preserve this piece of JRPG and Android gaming history. I hope that my efforts to do so will inspire others to do the same!

2019 Update

A lot has happened in the last couple years since this project started for me, and unfortunately, certain changes to operating systems (especially regarding CPU execution) have apparently broken compatibility with the Chaos Rings I and Omega, which were only ever released as ARM apps. Chaos Rings II and III have native x86 binaries, which means they will still work in modern emulators as usual, but ARM apps required libhoudini, Android's ARM to x86 translation layer, to function... which they don't anymore. Also, as Android 4.x continues to age, support is vanishing fast even from emulators mentioned in this post. (Because Android switched from the Dalvik runtime to ART shortly after Chaos Rings, Android 5.x and future versions are not compatible.)
This led to a lot of fruitless searching for yet another replacement emulator. In the end, I concluded that x86-based virtual machines just aren't going to cut it. Chaos Rings requires real ARM emulation, and that led me all the way back to the humble Android Studio emulator. Google's emulator is definitely not designed for gaming or preservation, but it turns out it's actually quite portable when you strip away everything unnecessary for the task.
I began by firing up the full Studio application and setting up an Android 4.4 KitKat ARM image in the AVD manager. I then installed the same versions of the games listed above using adb and... it just worked.
From there I copied out just the Android SDK and .android folder in my user profile. To run in any arbitrary location, some paths need to be edited in .ini files and Windows needs an environment variable set to point the emulator to the new .android folder, but this was easily automated with a .bat file I wrote. I also deleted anything not required by the emulator to function, as it can be pretty bloated out of the box.
In the end, I managed to fit Chaos Rings I, Omega, and II into a single ARM-emulated VM and make it portable in only 7GB. That's more than other emulators, but also completely manageable, and this package should last long into the future. The Android Studio emulator is built on QEMU and in theory this version of the preservation project could be ported to Linux or Mac OS without much difficulty.
So, as it stands, Android Studio is now a valuable means of preserving this series. For as long as Google keeps providing KitKat system image downloads, you can build an emulator yourself. But keep it in a safe place so it'll still work once KitKat is dropped for good.

2020 Update

The Amazon listings for Chaos Rings have finally been taken down and PlayStation Vita is officially the last place you can purchase the series (only in Japanese). :(
Fortunately, there is some good news: for anyone feeling that Android Studio ARM emulation is too slow for their CPU, there is a fork of Nox emulator called XePlayer that is surprisingly great for Chaos Rings! Those who've seen my other comments on Android emulators know that I'm not a fan of Nox at all, but XePlayer seems to be the purest version of it and runs fast and offline--and better yet, is compatible with Chaos Rings I, Omega, and II all at once, which is a first for x86-based emulators. There is a quirk with Chaos Rings II touch emulation that requires every click to be a drag-and-release to register, but since most interactions are drag-and-release anyway, it's still plenty playable. XePlayer is now my top recommendation for an alternative to Google AVD.
submitted by LukeLC to emulation [link] [comments]

How to compile rebase aeond/aeon-wallet-cli for Android

Someone asked in a seperate thread how I compile aeond for my Android Samsung Galaxy S6.
I replied there but thought it might be good to outline the process and provide some unofficial Android binaries if you want to test with care.
My build system is Ubuntu - if you are a Windows user you could spawn a free AWS t2.micro Ubuntu instance or VirtualBox and complete these steps on there.
Note this not to compile the GUI wallet. My use case is to have a node on a seperate device on USB power that I can call remotely.
If you know what you are doing with Docker and adb, grab the Dockerfile: https://github.com/stoffu/monero/blob/aeon-rebase-min/utils/build_scripts/android32.Dockerfile , edit it as per the "Edit The Dockerfile" section of this post, then follow the instructions here https://github.com/stoffu/monero/tree/aeon-rebase-min#on-linux-for-android-using-docker
If you want to skip building the binaries, grab this very unofficial zip file (25mb) that was created from writing this up: https://s3-ap-southeast-2.amazonaws.com/dddaeonandroid/aeon-rebase-android-binaries.zip (md5sum: c2b93b71ed2bb8d02da91b296e5fb84c) and move on to the "Copy To Device And Run"
Considering it's a daemon with no GUI there's no great screenshots or videos of it in action. Best I could do: https://asciinema.org/a/cofRrRo3tmZ0a8SgrsJ5y4Sgo
Build Requirements
Install Docker
sudo apt-get update sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" sudo apt-get update sudo apt-get install -y docker-ce 
Add user to docker group
sudo groupadd docker sudo usermod -aG docker $USER 
Log out and log back in (or restart)
Test docker works:
docker run hello-world 
If you get an error like this:
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///varun/docker.sock:
The docker group is not working properly, you can google for this solution or drop to root with sudo su
Install Git and adb
sudo apt install -y git adb 
Download Rebase Code
We will pull directly from stoffu 's repository:
git clone https://github.com/stoffu/monero.git 
Then swap to the aeon-rebase-min branch
cd monero git fetch git checkout aeon-rebase-min 
Edit The Dockerfile
We need to edit the utils/build_scripts/android32.Dockerfile file to build the rebase code, not the original Monero code:
vi utils/build_scripts/android32.Dockerfile #or nano utils/build_scripts/android32.Dockerfile 
Find these lines at the bottom of the file:
RUN git clone https://github.com/monero-project/monero.git \ && cd monero \ 
And change to:
RUN git clone https://github.com/stoffu/monero.git \ && cd monero \ && git fetch \ && git checkout aeon-rebase-min \ 
Save the file.
Build the Binaries
This can take some time and bandwidth as docker is downloading a small version of Debian, the entire Android NDK, the rebase code and is then compiling the binaries.
cd utils/build_scripts/ && docker build -f android32.Dockerfile -t monero-android . docker create -it --name monero-android monero-android bash cd ../../ docker cp monero-android:/opt/android/monero/build/release/bin . 
Check the binaries have copied out of the docker container:
ls bin/ 
You should see
aeon-blockchain-export aeon-blockchain-import aeond aeon-wallet-cli aeon-wallet-rpc
If you have built the binaries on a remote server, download the bin folder to your local machine that has adb installed on.
Copy To Device And Run
Plug your Android device in and make sure developer mode is enabled - https://www.digitaltrends.com/mobile/how-to-get-developer-options-on-android/
With adb installed, confirm you can see your device (you may need to authorise your computer on your Android screen):
adb devices 
If the device shows and no errors are reported, copy the binaries to the sdcard:
adb push ./bin /sdcard/0/aeon/ 
Run aeond
There are different ways of running cross compiled apps directly. My phone does not let me write to the init.d files so I can't set aeond to start on startup.
adb shell su cd /sdcard/0/aeon/ ./aeond --data-dir /sdcard/0/aeon/ 
You should now have aeond running succesfully on an Android device!
You can open another adb shell, change directory back to the aeon binaries and run the aeon-wallet-cli or aeon-wallet-rpc applicataions.
File Hashes
If you downloaded the zip at the top of the post and want to compare against your own compiled binaries:
58b529a1ec805d37be5bd3d7b62e695a aeon-blockchain-export
cf778e0b79637229639b4ca317d317d6 aeon-blockchain-import
81af340f2aaf3838bbd81e8ffaf8fb01 aeond
99965faca2e0de959b4f139d843fc290 aeon-wallet-cli
b2a9eb01424f83b921594f176cdc2068 aeon-wallet-rpc
Is it on the nose to say tips are welcome? Wmt8WofgiL8gjawsk4fiMf9vKcXPhhJgHijQs3bWxjctH49VLVHjrA7iUyfYT3Q8wG7ifuaAUmftSLN2yJguQYNW1HGAbKUEf
submitted by dddanmar to Aeon [link] [comments]

September OTA Failure to Install

I have an issue installing the September OTA.
EDIT: Temporary solution: Run adb sideload on MS Windows (I don't know why it doesn't work under linux)
What I've tried:
Updating from inside the system (has given be a generic "Couldn't update, Installation problem" error)

Downloading the fastboot version and flashing that (works, but no touchscreen, which makes the phone hard to use)

adb sideload (doesn't work for me)
Logcat for SystemUpdate (adb logcat SystemUpdate:I \*:S): https://vomitb.in/WMsLKUA1WD
Notes:
It looks like it is failing with error code "20" which is real helpful.

Logcat part that is "interesting":
09-06 14:04:19.414 3078 7141 I SystemUpdate: [Execution,SynchronizedUpdateEngine] start(aqch{url=file:///data/ota_package/update_s.zip, payload_binary_file.offset=7802, payload_binary_file.length=85348469, properties=[FILE_HASH=YKnoAmCcMnhFpJw4HZg211114GKh6AJLm+DHEKCWNjU=, FILE_SIZE=85348469, METADATA_HASH=3tt9HZHpLAh5Z4epXfxVnsrQpSHMbxTgFvdNwgVasF0=, METADATA_SIZE=412880]}, additionalProperties.size=0) 09-06 14:04:19.414 3078 7141 I SystemUpdate: [Execution,UpdateEngineDelegate] applyPayload() 09-06 14:04:19.475 3078 3496 I SystemUpdate: [Control,InstallationControl] Update engine status updated to 0x002. 09-06 14:04:19.512 3078 4794 I SystemUpdate: [Control,InstallationControl] Update engine status updated to 0x003. 09-06 14:04:19.643 3078 4794 I SystemUpdate: [Control,InstallationControl] Update engine status updated to 0x000. 09-06 14:04:19.672 3078 4794 I SystemUpdate: [Control,InstallationControl] Update engine status updated to 0x000. 09-06 14:04:19.703 3078 7141 E SystemUpdate: [Execution,NonStreamingAbApplyAction] Installation failed with error code: 20. 09-06 14:04:19.709 3078 7141 I SystemUpdate: [Control,InstallationControl] Installation progress updated to (0x412, -1.000). 

submitted by tsmock to essential [link] [comments]

[Guide] Updating your bootloader-unlocked Moto X to 4.4.4 via OTA

I've seen several posts over the last few days with people wondering how to upgrade their bootloader-unlocked Moto X to 4.4.4 using the over-the-air (OTA) update, so I figured I'd post a quick guide so that anyone in this situation can update their device with minimal hassle. The process is fairly straightforward, but some people may not have done it before, and even those who have may enjoy a refresher!
This post is for devices with unlocked bootloaders -- I don't really have experience with the root methods used on locked Moto Xs, so I can't help anyone with that. These exact steps are also specific to the Verizon update rolling out now, but the same general process should apply to other OTAs and other carriers.
I'm also assuming that you have a custom recovery and a rooted device and that you want to restore those after the upgrade -- if you haven't modified the recovery you can probably install the OTA as-is with no issues.
What do I need to install the OTA?
In order to install the OTA, your device needs to have the stock recovery and an unmodified /system partition. What does this mean?
Preparation
Before you get started, make sure you have the following files:
And one final note, make a backup of any important files on your phone. If everything goes correctly you should not lose any data, but since we're messing around with system files on the phone there's always the chance that something catastrophic could happen resulting in the need to wipe the device. Better to be safe than sorry!
The Process
If you're using Xposed, the first thing we need to do is disable it for the duration of the upgrade. To do this, boot into your recovery (probably TWRP), and install the 'Xposed-Recovery-Disabler.zip' file that you should find at the root of your storage. This file is created automatically during the Xposed installation process, and will disable the framework without removing any of your installed modules or settings.
If you don't have the disabler zip or you're otherwise unable to flash it, you can also just hit the 'uninstall' button within the Xposed installer app to do the same thing.
Next, reboot your phone into the bootloader. You can do this by shutting down the phone and then holding the power + volume down buttons to power it back up. (The bootloader screen may not actually show until you release the buttons, so if you don't see anything for ~10 seconds just let them go and it should pop up.) If you were already in TWRP after the previous step, you can also just reboot to the bootloader from there.
Once you're at the bootloader screen, plug your phone into your PC. Open a command prompt in the directory where your fastboot executable is located, and run the command 'fastboot devices'. The tool should print a line showing the serial number of your device and its current state, which is 'fastboot'. If you don't get any output from this command, then your drivers are probably not installed correctly -- check your device manager to see if you have any unrecognized devices, and try reinstalling the Moto device manager to get the proper drivers.
Assuming fastboot recognizes your device, the next step is to flash the stock recovery. You need to tell fastboot where the recovery.img file is -- the easiest way is just to copy it into the current directory; alternately you can provide the full path to the image instead of just specifying 'recovery.img'. The command you need to run is:
fastboot flash recovery recovery.img 
The phone will flash the stock recovery and let you know when it's done.
This step is optional, but recommended. The OTA installer is going to verify a number of files on your device's /system partition, and if any of those files have been modified, the update will refuse to install. If you don't feel that you've made major changes to your device aside from rooting and installing Xposed, you can skip this step and hope for the best. If it turns out that you do have changes that conflict with the update, the OTA will fail to install and you'll need to either manually restore the modified files or come back to this step and flash the stock system image before trying again.
If you want to be certain that the OTA will install without issues, I'd recommend flashing the stock system image now. Note that /system does not contain any user-space apps or data, so you shouldn't lose any information by resetting it.
Just like flashing the recovery.img, you need to have your phone at the bootloader screen with fastboot ready to go, and you need to have the system.img file handy. This time, however, you'll need to use the Motorola fastboot utility since the system.img image is too large for the stock fastboot tool. The the command to run is:
mfastboot flash system system.img 
The system image is fairly large (around a gigabyte) so it may take up to 10-15 minutes to completely install. Be patient!
Now your device is ready to accept the OTA upgrade. If your phone has already prompted you to install it, then you can boot back up into Android and begin that process from the notification, which will reboot the phone into recovery and start the upgrade automatically.
If you're using the downloaded .zip file instead, then select 'Recovery' from the bootloader menu to enter the stock recovery. (Remember that 'volume up' is the select key -- if you hit the power button instead your phone will just power off!) Now you should see a green android icon with a red triangle on it. This looks scary, but don't worry! If you press the power+volume up buttons, the actual recovery menu should pop up. Select the option to apply an update from your storage, then select the OTA zip file that you downloaded earlier. The install process should begin and will take several minutes.
Once the install process is complete, you'll be back at the recovery menu. Select the option to reboot the device, but hold down the power+volume down buttons as it restarts -- we're going straight back to the bootloader to flash our custom recovery.
In the bootloader, make sure that the phone is plugged into your PC and that you have the custom recovery .img file handy, then run the command to flash the new recovery file (I'll assume most people are using TWRP, but substitute the name of your own image file if necessary):
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img 
Assuming you want to root the device as well, go ahead and enter the custom recovery you just flashed and install the SuperSU package or whatever you normally use.
Now you're ready to boot the system up. It will take a little longer than normal, and you'll see the 'Optimizing apps' screen as the device rebuilds the dalvik cache files for each application. Once everything is up and running, head into the Settings -> About Phone menu and check your Android version. You should be on 4.4.4!
The final step is to re-enable any root applications that you have installed. For Xposed, just open up the Xposed installer app and hit the 'install framework' button. You'll need to reboot in order to activate the framework, but afterwards you should find all of your modules and settings exactly how you left them.
Other root apps may also need to be re-enabled or re-activated; check each one and make sure it's doing whatever it's supposed to do. For example, if you're using AdAway you'll need to re-apply the host file modifications.
You're done!
And that's it! The whole process should take no more than 20-30 minutes if you already have the files you need, and you shouldn't lose any data or settings during the upgrade. Now that you're on 4.4.4, check out the new dialer as well as the Motorola Alert app!
Good luck to anyone upgrading, and let me know if there are any changes/updates that need to be made to the guide.
submitted by chrismith85 to MotoX [link] [comments]

What does wiping 'system' in TWRP do ?

well .. i have a problem of sorts .
I am using Galaxy Mega I9152 , CM13 (downloaded from here ; https://forum.xda-developers.com/galaxy-mega/orig-development/rom-cyanogenmod-13-t3297678)
now problem is , it was running smooth as ever until a few hours ago :'( . my phone all of a sudden got stuck in bootloop and my attempts to recharge it did not work. the Os stayed on for a few seconds before giving up and restarting. this continued for sometime before i tried to google online
this is what i did
booted into the TWRP recovery and went for the 'fix permissions' option. and at the end of the procedure TWRP asked me if i wanted to root my phone (i had disabled root early on , through SuperSU , through the application's settings) . BY MISTAKE , i swiped and rooted my phone
then instead of going into bootloop , the phone just stuck on the booting animation
i tried to clear dalvik cache and cache but to no avail.
my SD card was encrypted (formatted as internal) so i tried to access it through adb and other methods , but in vain :'(
next i tried to use another SD card i had , and after inserting it into the phone , i was able to transfer the SAME custom ROM i had used before , into it , through adb . i tired to reflash that rom on TOP of my CURRENT ROM , but to no avail.
i got error message "error executing binary" while trying to install the rom and also a statement saying " cannot install on top of incompatible data"
now i am very confused and i just want to save my pics and data from my phone and my ENCRYPTED sd card which i can't seem to be able to use in any other device (even TWRP doesn't recognise the SD card , because it's formatted as internal :/)
please help me out , i just want to save my pics and stuff.
my FINAL question is , that if i remove the 'system' through TWRP and install the EXACT same ROM again , will the SD card , that was encrypted during the PREVIOUS 'life' of the ROM in my mobile , work on the 'new' iteration of the SAME Rom in my mobile. please help me out.
EDIT : i dont want to lose my data , even if i have to lose my OS , so be it but PLEASE help me retain my pics ! My pics are in the SD card which i have TAKEN OUT of the phone , as it is UNREADABLE and i cannot reflash the device using it. so i'm using another SD card
EDIT 2 : i have tried looking up how to DECRYPT the Adoptive Storage (internally formatted SD cards) and have come across this ; http://android.stackexchange.com/questions/135803/corrupt-sd-card-formatted-as-internal-storage
also here's what i get , after i fit the SD card into card reader and run the # fdisk -l command ;
OUTPUT http://pasteboard.co/POGvyBOxO.png
MASSIVE UPDATE : i was able to retrieve the key by going into the /data/misc/vold folder ... I CAN SEE THE .KEY FILE.BUT only after i browsed the folder when the SD card was loaded INTO the laptop's card reader while the phone was booted into TWRP. i DID NOT retrieve the .key file through Linux terminal.
NOW WHAT DO I DO ! i am very confused , since i don't know what to make of the Linux Output of reading my SD CARD.
please help !
also , there's this trick ;
https://forum.xda-developers.com/moto-e/general/trick-switching-roms-loosing-adopted-sd-t3314647
submitted by yaxir to AndroidQuestions [link] [comments]

LLSIF Launcher: multi-account manager/launcher (open-source)

Introduction

This is a little tool I made for School Idol Festival (android version) that allows you to easily manage your multiple accounts and log into the game with one of your accounts in a single click. I only tested this in the Bluestacks emulator, but it should also work on a real device.
NOTE: the binaries are packed with UPX to minimize the size, and some anti-viruses might give you a false positive (although it's very unlikely).

Requirements

Before you attempt using this tool, make sure you have the Visual C++ Redist 2013. Also, your emulator or device needs to be rooted. The program also relies on adb, but I have shipped adb with the binaries so it should be fine.

First time set-up

(you can ignore this if you already have xposed + rootcloak and skip to WiFi ADB)

Usage:

(note: this assumes that you already know how multi-accounting works and you have all your renamed GameEngineActivity.xml's in a folder)
(warning: this tool is designed not to erase your xml's but you should still make a back-up and save your transfer codes in case something goes wrong)

Advanced Users:

If for some reason you don't want to use WiFi ADB or you need to change the ip it connects to because you want to use it on a real device, you can change the ConnectCommand parameter in settings.ini

Troubleshooting:

If the tool can't seem to get the file list and you're 100% sure the path you provided is correct, try running fix_adb.bat and trying again. It will reset the adb connection. If it still doesn't work, restart bluestacks and terminate adb from your task manager. Also, make sure that you have no other android device connected to your computer.

Source code:

It's written in pure C + Win32API. The internal library I wrote to control LLSIF through adb is cross-platform and you can re-use it to make a linux frontend if you wish. If you wish to play around with the source code, you can grab it at: https://github.com/Francesco149/llsif_launcher

Legal stuff:

The copies of adb.exe, AdbWinApi.dll or AdbWinUsbApi.dll I shipped with this tool are made by Google and I do not own them.
Copyright 2014 Franc[e]sco ([email protected]) This file is part of llsif_launcher. llsif_launcher is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. llsif_launcher is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with llsif_launcher. If not, see http://www.gnu.org/licenses/.
submitted by lolisamurai to SchoolIdolFestival [link] [comments]

stuck in bootloop , Please help me out :'(

I am using Galaxy Mega I9152 , CM13 (downloaded from here ; https://forum.xda-developers.com/galaxy-mega/orig-development/rom-cyanogenmod-13-t3297678)
now problem is , it was running smooth as ever until a few hours ago :'( . my phone all of a sudden got stuck in bootloop and my attempts to recharge it did not work. the Os stayed on for a few seconds before giving up and restarting. this continued for sometime before i tried to google online
this is what i did
  1. booted into the TWRP recovery and went for the 'fix permissions' option. and at the end of the procedure TWRP asked me if i wanted to root my phone (i had disabled root early on , through SuperSU , through the application's settings) . BY MISTAKE , i swiped and rooted my phone
then instead of going into bootloop , the phone just stuck on the booting animation
  1. i tried to clear dalvik cache and cache but to no avail.
  2. my SD card was encrypted (formatted as internal) so i tried to access it through adb and other methods , but in vain :'(
next i tried to use another SD card i had , and after inserting it into the phone , i was able to transfer the SAME custom ROM i had used before , into it , through adb . i tired to reflash that rom on TOP of my CURRENT ROM , but to no avail.
i got error message "error executing binary" while trying to install the rom
now i am very confused and i just want to save my pics and data from my phone and my ENCRYPTED sd card which i can't seem to be able to use in any other device (even TWRP doesn't recognise the SD card , because it's formatted as internal :/)
please help me out , i just want to save my pics and stuff.
my FINAL question is , that if i remove the 'system' through TWRP and install the EXACT same ROM again , will the SD card , that was encrypted during the PREVIOUS 'life' of the ROM in my mobile , work on the 'new' iteration of the SAME Rom in my mobile. please help me out.
EDIT : i dont want to lose my data , even if i have to lose my OS , so be it but PLEASE help me retain my pics ! My pics are in the SD card which i have TAKEN OUT of the phone , as it is UNREADABLE and i cannot reflash the device using it. so i'm using another SD card
EDIT 2 : i have tried looking up how to DECRYPT the Adoptive Storage (internally formatted SD cards) and have come across this ; http://android.stackexchange.com/questions/135803/corrupt-sd-card-formatted-as-internal-storage
also here's what i get , after i fit the SD card into card reader and run the # fdisk -l command ;
OUTPUT http://pasteboard.co/POGvyBOxO.png
MASSIVE UPDATE : i was able to retrieve the key by going into the /data/misc/vold folder ... I CAN SEE THE .KEY FILE. BUT only after i browsed the folder when the SD card was loaded INTO the laptop's card reader while the phone was booted into TWRP. i DID NOT retrieve the .key file through Linux terminal.
NOW WHAT DO I DO ! i am very confused , since i don't know what to make of the Linux Output of reading my SD CARD.
please help !
also , there's this trick ;
https://forum.xda-developers.com/moto-e/general/trick-switching-roms-loosing-adopted-sd-t3314647
submitted by yaxir to androidroot [link] [comments]

Make Kobo 7 HD Great Again (Detailed instruction on how to root, recover and customize Kobo)

Kobo 7 HD (K7H) is probably the cheapest (so far) FHD tablet that you can get in the history of tablets, I bought mine (refurbished 16GB, but appears to be brand new) a couple days ago for around $40 CAD.
Here are the steps I took to make my K7H into a bookreader with full browsing capabilities with a superb battery life.
start of preparation
(you need to re-perform preparation if you screw up and brick your K7H at any time during this guide)
download mfastboot-v2.zip from here
https://androidfilehost.com/?fid=95916177934532795
if this link above expires, google mfastboot-v2.zip and i am sure you can find a valid one somewhere.
the zip is 1.36MB and should contain the following 7 files:
AdbWinApi.dll AdbWinUsbApi.dll linux-fastboot mfastboot.exe osx-fastboot aapt.exe adb.exe 
extract all contents to a new folder on your desktop, let's call this folder HOME folder from now on.
next, download
http://download2.kobobooks.com/apollohd/update-ota339.zip
if this link above expires, google update-ota339.zip and i am sure you can find a valid one somewhere. it is 382MB.
and copy/move it into HOME folder
fully charge your kobo
reset your kobo by pressing the power on (PO) button and then immediately pressing the volume down (VD) button, you should then be brought to K7H's system recovery interface, choose wipe data / factory reset by pressing VD twice, and then press PO. then pressing VD 7 times until you are at "Yes", then press PO again. then wait for it to finish.
next connect your kobo to your PC with the USB cable that came with K7H. on K7H, press VD once to select "apply update from ADB", press PO, and you are brought to a waiting screen, at the same time, the computer will install necessary drivers needed. on PC, hold down Shift key and right mouse click in HOME folder and select "Open command window here" (make sure you don't have any file highlighted), in the command window, type
adb sideload update-ota339.zip
this should bring you to this screen within the command window on your PC
https://i.imgur.com/WxsAxGH.jpg
one comment: feel free to disconnect and reconnect K7H to your PC a couple times if you encounter error messages such as "error: device not found" "daemon not running" etc after you type adb sideload update-ota339.zip
on K7h, it will install the firmware and a couple of yellow lines will appear and the final yellow line should say "Install from ADB complete."
https://i.imgur.com/JhWHt2U.jpg
next, reboot system now should be automatically selected, simply press PO to restart your K7H.
end of preparation
your K7H will be stuck at the Kobo screen for a while, be patient. once your tablet is booted up, you need to go through the whole registration/update process. this part doesn't require any guidance, although it may appear you can only do this with a kobo account, so register one on your PC.
once you are in, press the bottom right icon to go to apps, select settings, scroll to the bottom, select
"about kobo arc 7HD", tap on "build number" 7 times to activate developer options.
go back to settings by press the back-up key at the bottom left corner, scroll to bottom
select "developer options"
checkmark "USB debugging"
uncheck "verify apps over USB"
go back to settings by press the back-up key at the bottom left corner, scroll to bottom,
select "security"
checkmark "Unknown sources"
uncheck "verify apps"
now download tr_old.apk from here and save it into HOME folder.
https://forum.xda-developers.com/attachment.php?attachmentid=2843562&d=1404980556
if this link above expires, google tr_old.apk and i am sure you can find a valid one somewhere.
on pc, hold down Shift key and right mouse click in HOME folder and select "Open command window here"(make sure you don't have any file highlighted), in the command window, type
adb install tr_old.apk
again, feel free to disconnect and reconnect K7H to your PC a couple times if you encounter error messages such as "error: device not found" "daemon not running" etc. please note that, you can use this method to install WHATEVER app onto your K7H, even ones not meant for android 4.2.2, as long as you can download the apk of the app, you can get apk of apps by using google or from certain reputable sites like https://www.apkmirror.com/ or https://apkpure.com/ or https://www.apk4fun.com/ and etc.
now go to apps on K7H, open the new app towelroot, press the "make it rain" button and wait for K7H to reboot, now your K7H is rooted.
now on K7H, search for SuperSU by CodingCode from the google play store that you can access by going into apps (again, press the bottom right icon to go to apps), sign in using your google account, it should be the first result returned. please note that, your Kobo might restart on its own, as it is busy updating all kinds of softwares now that you signed into the playstore, as its CPU is quite slow and is easily overwhelmed. once things settle down, open SuperSU, press start, choose continue when it asks for binary needs update, choose normal when it asks the other question.
next, download recovery.img - [Click for QR Code] (6.54 MB) from here into HOME folder.
https://forum.xda-developers.com/showpost.php?p=47024957&postcount=4
assuming your K7H is still connected to your PC, on PC, hold down Shift key and right mouse click in HOME folder and select "Open command window here"(make sure you don't have any file highlighted), in the command window, type
adb push recovery.img /sdcard/
then type in the command window
adb shell
then type in the command window (make sure the screen of your K7H is turned on)
SU
a box will popup on K7H (i.e., look at your tablet), make sure you select "GRANT"
then type in the command window (by the way, you can always right click and select paste when you are in the command window)
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Next, in the command window press Ctrl key and C key as if you are copying something
then type in the command window
adb reboot recovery
now your K7H will restart
you will notice that the interface is different from earlier during the preparation step, "reboot system now" should be highlighted, press PO button, press VD 7 times to highlight
"Yes, disable recovery flash"
then press PO button.
now your K7H has the Recovery Mod.
next. search for nova launcher from the play store that you can access by going into apps
(again, press the bottom right icon to go to apps) and install the free one.
once it's installed, press the HOME folder button of your K7H (middle button of the three virtual buttons on bottom left), select Nova launcher and make sure you select Always.
now go to play store and search for titanium backup install it. run it and select "GRANT".
go through some menus where you always press "OK".
if you ever get stuck at the Kobo screen with three dots for a while, just connect K7H to your PC, hold down Shift key and right mouse click in HOME folder and select "Open command window here" (make sure you don't have any file highlighted), in the command window, type :
adb shell input keyevent KEYCODE_HOME
please note that the above command is case sensitive, i.e., KEYCODE_HOME must be capitalized
last thing, the screen is really bright at night, even when i adjust the brightness to minimum. so i figured out a way to adjust it further. install f.lux either through adb install or through app store, change the color driver to tegra and you are good to go.
if you are an advanced user, you can use titanium to uninstall A LOT of things.
i am not advanced, but through some trial and error, i managed to delete a lot of things, such as the drop down menu when you swipe at the top, and a lot of other things. doing this helped me extend the battery life to 10 days (2 day 14 hour * 4) with daily book reading and / or light browsing before bed, the standby battery life is around 20 days.
the system navigation bar also takes up a lot of screen real estate with its default status bar(top) and navigation bar(bottom), the difference is night and day, compare the following two images:
first is on a K7H where I got rid of both the top bar (no need for it really), and bottom bar (replaced system UI with this app)
second is on a regular K7H.
(don't pay attention to the large font, I set my text to large under accessibility)
https://i.imgur.com/WsH7IDC.png
https://i.imgur.com/HrcMsC7.png
the top bar and bottom bar together take up around 13% of screen real estate by my calculation.
btw, I learnt how to take SS of your tablet screen under adb (the above 2 SS are not taken with a camera like earlier), hold down Shift key and right mouse click in HOME folder and select "Open command window here"(make sure you don't have any file highlighted), in the command window, paste the following code and the screenshot should be under your HOME folder.
adb shell screencap -p /sdcard/screen.png adb pull /sdcard/screen.png adb shell rm /sdcard/screen.png 
here is a SS of K7H running Moon+ Reader Pro
https://i.imgur.com/YC9mX7t.png
submitted by Glancealot to kobo [link] [comments]

Decrypting a SD card on Ubuntu

well .. i have a problem of sorts .
I am using Galaxy Mega I9152 , CM13 (downloaded from here ; https://forum.xda-developers.com/galaxy-mega/orig-development/rom-cyanogenmod-13-t3297678)
now problem is , it was running smooth as ever until a few hours ago :'( . my phone all of a sudden got stuck in bootloop and my attempts to recharge it did not work. the Os stayed on for a few seconds before giving up and restarting. this continued for sometime before i tried to google online
this is what i did
booted into the TWRP recovery and went for the 'fix permissions' option. and at the end of the procedure TWRP asked me if i wanted to root my phone (i had disabled root early on , through SuperSU , through the application's settings) . BY MISTAKE , i swiped and rooted my phone
then instead of going into bootloop , the phone just stuck on the booting animation
i tried to clear dalvik cache and cache but to no avail.
my SD card was encrypted (formatted as internal) so i tried to access it through adb and other methods , but in vain :'(
next i tried to use another SD card i had , and after inserting it into the phone , i was able to transfer the SAME custom ROM i had used before , into it , through adb . i tired to reflash that rom on TOP of my CURRENT ROM , but to no avail.
i got error message "error executing binary" while trying to install the rom and also a statement saying " cannot install on top of incompatible data"
now i am very confused and i just want to save my pics and data from my phone and my ENCRYPTED sd card which i can't seem to be able to use in any other device (even TWRP doesn't recognise the SD card , because it's formatted as internal :/)
please help me out , i just want to save my pics and stuff.
my FINAL question is , that if i remove the 'system' through TWRP and install the EXACT same ROM again , will the SD card , that was encrypted during the PREVIOUS 'life' of the ROM in my mobile , work on the 'new' iteration of the SAME Rom in my mobile. please help me out.
EDIT : i dont want to lose my data , even if i have to lose my OS , so be it but PLEASE help me retain my pics ! My pics are in the SD card which i have TAKEN OUT of the phone , as it is UNREADABLE and i cannot reflash the device using it. so i'm using another SD card
EDIT 2 : i have tried looking up how to DECRYPT the Adoptive Storage (internally formatted SD cards) and have come across this ; http://android.stackexchange.com/questions/135803/corrupt-sd-card-formatted-as-internal-storage
also here's what i get , after i fit the SD card into card reader and run the # fdisk -l command ;
OUTPUT http://pasteboard.co/POGvyBOxO.png
MASSIVE UPDATE : i was able to retrieve the key by going into the /data/misc/vold folder ... I CAN SEE THE .KEY FILE.BUT only after i browsed the folder when the SD card was loaded INTO the laptop's card reader while the phone was booted into TWRP. i DID NOT retrieve the .key file through Linux terminal.
NOW WHAT DO I DO ! i am very confused , since i don't know what to make of the Linux Output of reading my SD CARD.
please help !
also , there's this trick ;
https://forum.xda-developers.com/moto-e/general/trick-switching-roms-loosing-adopted-sd-t3314647
P.S : in the end , all i know is that all Android OSes are JAVA Virtual Machines running on handheld computers (smartphones) so please , please help me out in decrypting the SD card and preserving my data. i'm a CIS engg student , so you can expect me to try anything you advise regarding this. please , PLEASE help me out !
submitted by yaxir to linuxquestions [link] [comments]

[Android] SM-G360V 5.1.1 (Galaxy Core Prime - Verizon US) Setup Wizard Crash Loop

After rooting with the KingRoot apk apps would start crashing randomly (no message, just every running app would exit and throw me to my home screen), so I decided to factory reset. I grabbed Titanium Backup, grabbed the app backups I needed, then did the reset. Phone booted up, but now the setup wizard just crashes every run through and restarts itself, leaving my phone useless.
All the steps I've taken are below. I don't want to give up hope because I can still get into download mode, but a phone upgrade would be nice.
WALL OF TEXT STARTS HERE
It may be important to know that after KingRoot, my boot screen had an unlocked lock with the text "custom" under it- I figure this means my bootloader is unlocked, but I could be wrong.
I've enabled USB Debugging through the recovery screen.
Setup Wizard (Without SIM): Connect to Wifi network -> Next -> Crash Skip connect to wifi -> Skip anyway -> Crash
Setup Wizard (With SIM): Properly IDs my number and connects to 4G -> Next -> Sometimes crash Skip Verizon Cloud -> Not Now -> Crash Setup Verizon Cloud -> Finished Setting up -> Crash
Installing TWRP via h00ps://twrp.me/devices/samsunggalaxycoreprimequalcomm.html Option 1 (TWRP) nogo, no previous TWRP installed Option 2 (Odin) nogo, tried both through the website on Linux/FF and through Windows (VirtualBox). The website asks me for the PIT, then when it tries to retrieve it from the device it fails. The app on Windows doesn't ask me for it, but when trying to install it it pops up "secure check fail: recovery" on the phone's screen (the app does nothing). Option 3 (dd) nogo, can't get an adb root shell
Rerooting through the KingRoot desktop app: It looks like it succeeds (it's all in Chinese). adb root gives "adbd cannot run as root in production builds" adb shell su gives "[-] Connection to ui timed out"
Trying to remove or disable the Setup Wizard app: ps | grep setup returns the following package names: com.android.setupwizard (pm disable -> Unknown package) com.google.android.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=11940, uid=2000, package uid=10014) com.google.android.partnersetup (pm disable -> Permission Denial: attempt to change component state from pid=11958, uid=2000, package uid=10030) com.sec.android.app.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=12180, uid=2000, package uid=1000) kill -> Operation not permitted) pm uninstall -> "Failure [DELETE_FAILED_INTERNAL_ERROR]"
pm path com.android.setupwizard -> nothing pm path com.google.android.setupwizard -> /system/priv-app/SetupWizard/SetupWizard.apk pm path com.google.android.partnersetup -> /system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk pm path com.sec.android.app.setupwizard -> /system/app/SamsungSetupWizard/SamsungSetupWizard.apk
I had also sideloaded gapps-lp-20150314 (for 5.1.X) in hopes that it would fix it up.
Anything else I should try? Any stock images so I can do a complete, fresh, reinstall? I know someone here was working on getting stock everything uploaded- will that be my best bet?
Thanks!
EDIT: Additional information
Download mode returns the following strings:
ODIN MODE PRODUCT NAME: SM-G360V CURRENT BINARY: Samsung Offical SYSTEM STATUS: Custom REACTIVATION LOCK: OFF QUALCOMM SECUREBOOT: ENABLE (CSB) RP SWREV: S1, T2, H1, R1, A3, P1 SECURE DOWNLOAD: ENABLE
When trying to flash TWRP with ODIN add line SECURE CHECK FAIL: recovery
submitted by A_Water_Fountain to techsupport [link] [comments]

Guide: Enabling built-in superuser (using official files only)

Note: This is for CM12S.
For those who are a bit paranoid and/or conscious of the risk in using magical "root my phone" programs...
(note: there's a .zip here that will do this for you; I've checked that the files used are the same you'd get by following this guide)
The first step is enabling a "debuggable" kernel. This will allow you to use root from ADB. To do so, download the boot-debuggable image (link in post), put the device in fastboot mode (adb reboot bootloader or hold volume-up while booting) and run
fastboot flash boot cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Now boot the phone normally, go to Settings -> About Phone. Tap a bunch on Build Number until it tells you that developer settings are active. Go back, enter "Developer options". Turn "Android debugging" on and set "Root access" to "Apps and ADB".
Make sure adb is working (device needs to show as "device" under adb devices). Restart adb with root privileges:
adb root
and make sure /system is mounted for write:
adb remount
Now, download a CM12 (not 12.1) nightly for the device. You'll need to convert the system.new.dat file (sparse filesystem image) to a mountable, standard filesystem. I used https://github.com/xpirt/sdat2img (python script). Run it like so:
sdat2img.py cm-12-20150414-NIGHTLY-bacon/system.transfer.list cm-12-20150414-NIGHTLY-bacon/system.new.dat system.img
Now the system image needs to be mounted; the right way to do this depends on your OS.
On Linux, this is trivial; mount it as any other device. (sudo mount system.img /mnt)
On Mac OS, install ext4-fuse (brew cask install osxfuse; brew install ext4-fuse) and run ext4fuse system.img /some/directory.
On Windows...well, find a way to do this. You might be better off with a Linux VM here.
Once it's mounted, navigate to the root of the image and copy xbin/su somewhere.
cp /mnt/xbin/su ~
Now, we just need to drop this su binary on the device.
adb push su /system/xbin/su
Now, you have to tell SELinux that this binary can act as su. To do so, open a shell:
adb shell
and set the context...
chcon u:object_r:su_exec:s0 /system/xbin/su
and set the right owner and permissions...
chown 0:0 /system/xbin/su
chmod 06755 /system/xbin/su
Close the shell. Reboot the device, and root should now be working (though do note - it's managed in Privacy Guard now, there is no preference pane for it).
Unlike CM11, you do not need to arrange for the su daemon to be run. /init.superuser.rc will do this for you.
submitted by xales to oneplus [link] [comments]

[UPDATED] How to setup Android SDK,ADB and Fastboot on ... SAMSUNG ADB ENABLE FILES FREE LETEST 2019 1000% TESTED How to check bootloader lock/unlock status using ADB - YouTube How to install ADB Driver of any device on PC  ADB DRIVER ... android debug bridge (adb) not detected in android studio ... Dump any Android eMMC Raw Binary Using ADB Interface Secure Download Enabled Solved  Secure Download Enabled ...

Microsoft Windows ADB Setup. Download the ADB ZIP file for Windows; Extract the contents of this ZIP file into an easily accessible folder (such as C:\adb) Open Windows explorer and browse to where you extracted the contents of this ZIP file; Then open up a Command Prompt from the same directory as this ADB binary. This can be done by holding ... How to Install ADB on Windows. Download the ADB ZIP file for Windows and extract the files into an easily accessible folder (like C:\adb) Open the Windows Explorer and navigate the folder where you had extracted the contents from the ADB ZIP file. Now, open Command Prompt on the same directory as ADB binary. Press the SHIFT key and right-click ... How to Install ADB on Windows, macOS, and Linux. Lately here at XDA we have been writing a number of tutorials to show you how to access certain features of the Android platform that simply are ... How to Install ADB & Fastboot on Ubuntu 18.04 / Linux Mint 19?. Android Debug Bridge (ADB) is a versatile command-line tool that enables you to communicate with a device from a client machine. With adb command, you can perform a variety of device actions, such as the installation of Applications, copying files, run shell commands, debug applications e.t.c. Tap on USB Debugging option to enable it. How to Setup ADB on Windows. Head over to the link and download the ADB zip file for Windows. → Download ADB; Extract the zip file into an easily accessible folder. Navigate to the folder where you extracted the ZIP file. In the folder containing the contents of the zip file, open up a Command Prompt. To open, hold Shift and Right-click within the ... Scroll down until you find the “USB debugging” option and switch ON the toggle. When prompted, select “ ... Install ADB on Linux. Download the platform tools package for Linux: Link; Extract the content of the downloaded “platform-tools-latest-linux.zip” file to a suitable location of your choice. We prefer the Desktop. So open a Terminal window and direct it to the folder where the ... Some Linux users should be aware that there can be an easier way to install ADB on their computer. The guide above will certainly work for you, but those own a Debian or Fedora/SUSE-based distro ...

[index] [11952] [19207] [11937] [16642] [26220] [20691] [706] [13299] [26400] [8321]

[UPDATED] How to setup Android SDK,ADB and Fastboot on ...

Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING! - Duration: 43:42. ... Miracle box 2.82 crack ADB Unauthorized Problem fix 2019 1000% working - Duration: 5:30. TECHNICAL ZONE ... Hey Guys, This is Aditya Prakash and in this video I'll be showing you How to ADB Driver of any android phone/tablet on Computer (Windows 7, 8, 8.1 & 10) wit... A detailed explanation on Android's updated SDK Manager,its command line tools and how to use them. Compatible with the latest version of Android SDK. Link t... See previous video here https://www.youtube.com/watch?v=zczjkcUEn60 Subscribe to my channel for more videos Odin Fail Auth Fix Odin Auth Fail Fix Flashing Sa... this video will guide you through the various steps involved in the solution of the problem adb not detected in android studio .the sample problem is in the ... Read eMMC raw binary boot1, boot2, main user area and extended csd using adb interface. Requirements: - Android phone with active usb debugging - Rooted andr... This video will help you know how to check status of bootloader and root status using adb mode. Also how to restart in fastboot mode.

http://binary-optiontrade.rockcontnallicho.cf