So this seems to be a common thread in several areas, so I am asking for a simple answer.
First, I am not an Android app creater but I am familiar with programming in several languages.
Can anyone create an app that without root, computer program, or adb instructions that reliably (works on big and little named devices) can do the following:
(permission already granted)
: "Platform.xml is already modifed to allow read/write for external media."
: "Remove external read/write permissions [Yes/No(default)]?"
(permission not granted)
: "Platform.xml is not modified to allow read/write to external media."
: "Apply external read/write permissions [Yes(default)/No]?"
This is the main reason that I need to root any android device, and is the biggest headache to do on devices that are not big name (ie not a mainline manufacturer/major carrier Samsung, LG, Motorola, etc.). I have tried several methods (oneclick, towelroot, kingroot, etc.) and most of my devices remain unrooted (Craig, RCA).
Realized how some of this reads so clarification:
Method must work without rooting - as rooting is rarely supported on less popular devices especially on non-phone devices, some of us have purchasing issues (can't pay $500-$2000 for the latest/greatest android devices).
Must be as universal as possible (any manufacturer and carrier, not just the big names), list Android versions and alternate instructions/commands/apps as needed:
KitKat sub-thread, Marshmallow sub-thread, Lollipop sub-thread
Can use a computer (Linux/Mac, Windows) with ADB, Android app, or a combo of both
SD Card/Flash drive must remain portable - no "encryption to work with this device's memory" (the current manufacturer solution which removes portability).
If using ADB, include all instructions/commands (make no assumptions other than ADB is loaded, could say "Load ADB by following <i>this</i> guide" as the first line) from "adb devices" to completion.
Related
hi. i can't believe i'm the first person to ask this but i've searched as best i can through these forums, and on google, and cannot find a definitive answer. there are lots of pages giving high level descriptions of rooting a phone like "gives admin access", "allows access to the root filesystem", etc. but, when you root a phone, what actually happens ? does it simply make the "su" binary available so that apps can call it to access the root user ? eg. i've got a samsung galaxy s2, if i install an insecure kernel, then add su to /system/xbin, and then reinstall a stock kernel, is that technically a rooted phone ? this is actually what i did on my phone, although i installed superuser and busybox from the market after adding su. i am aware that there are various threads in the sgs2 forums on how to root, i'm just using my phone as an example, i'm just trying to understand generically what is meant when someone says a phone has been rooted. cheers.
Full control over your system
Ability to alter system files. You can replace many parts of the "Android Core" with this including:
Themes
Core apps (maps, calendar, clock etc)
Recovery image
Bootloader
Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
Boot images
Add linux binaries
Run special apps that need more control over the system
SuperUser (lets you approve or deny the use of root access to any program)
Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
<there are more but I cannot think of any right now>
Backup your system
You can make a folder on your sdcard and backup all of your .apk files to your sdcard (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
Relocate your (browser/maps/market) cache to your /sdcard
Relocate your installed applications to your /sdcard
Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Copied and pasted from google... it is your friend.
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Carrot Cruncher said:
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Click to expand...
Click to collapse
Unrooted phone is like logging on as user in a computer. By rooting you have "administrative" rights, just like using sudo command in Ubuntu. Some binaries which are important in gaining administrative rights are installed in the phone.
sent from my nokia 3210
If you come from Windows, you're familiar with the Administrator account. A user that can do everything on the system, as opposed to other users than only have limited privileges. In Linux, that account is called "root". That's all there is to it. It's a user that can do everything on the system.
@Panos_dm: Actually, it's *not* like using sudo. Sudo gives elevated privileges to your existing user account, whereas "root" is a whole separate account.
Nope, sudo actually switches users
i'm a linux user and have been a linux admin in the past so understand the difference between su and sudo. sorry to sound pedantic but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
It opens your phone to a whole new array of possibilities.
Sent from my HTC Sensation 4G using xda premium
Carrot Cruncher said:
but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
Click to expand...
Click to collapse
In a gist? The "su" binary and the Superuser.apk app get installed. Sometimes doing so requires exploiting a vulnerability via a trigger. Rageagainstthecage is a common trigger. I once had a link that explained what exactly rageagainstthecage does, but I don't have it anymore.
If you really want to know all the details, here's the script I used to root my Defy: http://pastebin.com/G3m9v4FQ
Hmm, I see the script contains a link to the explanation of what rageagainstthecage does. Cool.
many thanks for confirming my understanding of the process.
Please notice that this is a minimal rooting procedure of the 1GB RAM / 16GB internal storage version only. It is not an end-user "kitchen sink" procedure, nor does it block future OTA updates from B&N. This procedure provides rooting. In addition, I include:
The "su" binary (command-line interface), but not the "SuperSu" (recommended) or "Superuser" app. You can easily get either app from the Android Market; that has the advantage that you will get notified of updates!
The "busybox" binary (common Linux command-line tools).
The "sqlite3" binary (command-line interface to the SQLite library).
A reference to a minimal set of "Gapps", including the Android Market (which is needed to easily proceed after rooting).
I don't solve problems that are unrelated to rooting, like "side-loading" (the installation of "unknown sources"; this is apparently a B&N v1.4.x issue). There are possible solutions to such issues elsewhere on these forums.
Here is the procedure: http://www.mailpen.com/download/NT16-1.4.x-Root_1.07.zip (1.1MB)
Unzip the file onto your (Windows or Linux) PC (everything is in the "rooting" subdirectory), and view the ReadMe.txt file. Note that I may occasionally make minor revisions to the ReadMe.txt file without changing the version number of the .ZIP file, but any procedural improvements will result in a new version number.
Caveats:
Don't use this procedure on the 512MB RAM / 8GB internal storage version !!!
You must have a sense of total personal responsibility (ie, there is no warranty).
You must understand command-line operations and utilities in Linux and Windows. In particular, that means you should ALREADY know how to cut lines from the ReadMe.txt file document and paste them into the command line for your PC (in order to save typing and mistakes).
You must have a basic understand how the Nook Tablet works. That means, don't try to root it within 24 hours of getting it; you need to know how to navigate the device and its settings.
You must have ALREADY installed on your PC, a command-line version of ADB that has ALREADY established an ADB/USB connection to your Nook Tablet. The XDA-developers forum has plenty of help and expertise in this area. Although this procedure does not use QtADB (a GUI add-on to ADB), I heartily recommend it: http://www.addictivetips.com/mobile/qtadb-adb-android-debug-bridge-beginners-gui/
You must be willing (and know how), if all else fails, to revert to stock B&N v1.4.x unrooted.
Questions or comments that reveal a sense of entitlement (eg, "when are you going to do xxx", as opposed to "are you going to do xxx") will be ignored or worse.
Questions or comments that copy most or all of the contents of this message (lack of forum protocol) will be ignored or worse. Note that copying the link above in a message is really, really dumb, as I will be changing it with revisions.
Remaining issues (hopefully eventually resolved):
If you use the "n" button to access the Nook-specific screens, you may find that it is not obvious how to get back to the Zeam (or other) launcher. You can get back to the Android launcher by using the Nook "Search" screen to search for the name ("Zeam" in this case) of the launcher (this is what I do for the very few times I need to), or you can side-load and install the "HomeCatcher" application (see http://forum.xda-developers.com/showthread.php?t=1357175).
For sideloading, you can either use ADB (that's what I do), QtADB (see above), or you can install a newer copy of "NT Hidden Settings" (see http://forum.xda-developers.com/showthread.php?t=1400615). If the latter does not work, contact the author of that app, not me (I rarely use sideloading); that is his area of expertise.
Revision history:
2011-12-27 v0.1 EXPERIMENTAL: Original (experimental).
2011-12-28 v0.2 EXPERIMENTAL: Added missing zergRush.
2011-12-28 v0.3 BETA: Fixed missing "/". Extensive ReadMe.txt (manual procedure) revisions.
2011-12-29 v0.4 BETA: Added scripts (beta) for a semi-automated approach. The manual procedure is now documented in "ReadMe.old".
2011-12-29 v0.5 BETA: Updated to include new "Nt Hidden Settings" app. Cosmetic revisions to file "ReadMe.old". Text files (including scripts) converted to DOS format for Windows weenies ...
2011-12-30 v0.6 BETA: Script files split and updated to reflect testing results. File "ReadMe.txt" updated, file "ReadMe.old" removed.
2011-12-31 v0.7 BETA: Script files split, so that rooting v1.4.0 is separate. This allows those who have already rooted 1.4.0, to skip that step and proceed directly to upgrading to v1.4.1 while preserving root.
2011-12-31 v0.8 RELEASE CANDIDATE: Error in script file "AdbUpdate.cmd" fixed.
2012-01-01 v0.9 RELEASE CANDIDATE: Split the script file "AdbUpdate.cmd" (and updated "ReadMe.txt") to support those who are already rooted v1.4.0. Due to the variation in v1.4.0 rooting procedures by others, this latter option is experimental. That means you are on your own if you don't start with (or revert to) a stock (unrooted) v1.4.0.
2012-01-02 v0.10 (skipped to avoid confusion).
2012-01-02 v0.11 RELEASE CANDIDATE: Convert the script files back to Unix text file format (they now run on Linux as well as Windows).
2012-01-05 v0.12 RELEASE CANDIDATE: Minor script simplifications.
2012-01-08 v1.00 RELEASED: Minor "ReadMe.txt" additions.
2012-01-13 v1.01 RELEASED: Added "busybox" installation.
2012-01-16 v1.02 RELEASED: Fixed typo in script comment; other cosmetic changes.
2012-01-31 v1.03 RELEASED: Added options for installing/fixing Google Calendar, and other (minor) options.
2012-02-21 v1.04 RELEASED: Added support for rooting B&N v1.4.2.
2012-03-12 v1.05 RELEASED: Work around ADB command line parsing bug.
2012-06-27 v1.06 RELEASED: Added support for rooting B&N v1.4.3.
2013-01-03 v1.07 RELEASED: Bug fix: Forgot to add new files referenced in updated scripts!
You may copy my work into other works, but please give credit. Similarly, let me know if I have not given adequate credit for the work of others.
Notes:
Don't use this procedure on the 512MB RAM / 8GB internal storage version !!! The problem is not with this procedure per se, but with the fact that reverting to v1.4.0 will install boot software that assumes that your NT has 1GB of RAM.
There is now a general/universal capability for "sidebooting" an NT from an SDcard (see http://forum.xda-developers.com/showthread.php?t=1466583 ), that is virtually guaranteed to work with all future revisions of NT firmware from B&N. While my procedure above is well-tested by me (and it's what I use), those having problems with it, may be well-advised to try the bootable SDcard solution.
Not to be overly dense, but I assume this would allow side loading as well. It's not clear if this root simply re-enables the "simple" side loading we currently enjoy in 1.4.0.
Sideloading ???
nooknut said:
... I assume this would allow side loading as well.
Click to expand...
Click to collapse
Valid question; YES, via ADB/USB. You can also just use ADB/USB once to install a newer version of "NTHiddenSettings", and that should fix it permanently. I'm looking at adding that to my .ZIP file.
New version !!!
Added missing file "zergRush" to .ZIP file (see OP); extensive revisions to ReadMe.txt.
Still requires downgrade to 1.4.0 first...
I was really hoping this would root 1.4.1 directly, but it looks like from the instructions that I still need to downgrade to 1.4.0 first.
Are there any changes in 1.4.1 that makes it advantageous over 1.4.0?
Congrats on this breakthru !
Question: I have a rooted NT that was upgraded to 1.4.1 after rooting. Could I start your procedure from step 6, that is Root of 1.4.1 after upgrade ?
Regards,
DipDog3 said:
I was really hoping this would root 1.4.1 directly, but it looks like from the instructions that I still need to downgrade to 1.4.0 first.
Are there any changes in 1.4.1 that makes it advantageous over 1.4.0?
Click to expand...
Click to collapse
Yes, you need to be on 1.4.0 first.
See the B&N forums for some discussions of the differences. Over 100 files were changed in the update, and some bugs that were important to some were fixed.
so its not really a 1.4.1 hack, it's a 1.4.0 upgrade hack.
Dean, may I make a suggestion? place all binaries into a separate folder in the zip file...
Windows:
Code:
cd \location\of\my\files
adb push .\separateFolder /data/local/tmp
adb remount
linux/mac:
Code:
cd /location/of/my/files
adb push ./separateFolder /data/local/tmp
adb remount
and in that separate folder you can have a script
Code:
#! /bin/sh
cd /data/local/tmp
chmod 755 zergRush
./zergRush
cat /data/local/tmp/su.upd > /system/bin/su
chmod 6755 /system/bin/su
cat /data/local/tmp/local.prop >/data/local.save
cat /data/local/local.root >/data/local.proprm
#blabla---- put as much crap here as you can without rebooting.
exit 0
which will be executed with
Code:
adb shell
/data/local/tmp/script.sh
I'm suggesting this because even myself, a very experienced linux vet... I would never go through that whole procedure more than once.
Can one assume that since the tablet will be rooted 1.4.1 there is no need to block the OTA to 1.4.1?
Have to start over.
gsoriano said:
Congrats on this breakthru !
Question: I have a rooted NT that was upgraded to 1.4.1 after rooting. Could I start your procedure from step 6, that is Root of 1.4.1 after upgrade ?
Click to expand...
Click to collapse
Unless you did something similar to that in step 5, you lost root. Step 5 is the key to keeping root.
Sorry! I got to the same point as you (without root), and had to go back to step 3.
OTA blocking
miniblue said:
Can one assume that since the tablet will be rooted 1.4.1 there is no need to block the OTA to 1.4.1?
Click to expand...
Click to collapse
That would be my assumption as well.
I keep getting this error when doing step (adb push nooktablet_1_4_1_update.zip /media):
failed to copy 'nooktablet_1_4_1_update.zip' to '/media': Is a directory
Scripting ...
AdamOutler said:
So its not really a 1.4.1 hack, it's a 1.4.0 upgrade hack.
Click to expand...
Click to collapse
Yep, just like for a lot of Android devices (eg, my Droid, my Acer A500 ...), where you have to revert to an easily hackable version first, and then upgrade.
AdamOutler said:
... I'm suggesting this because even myself, a very experienced linux vet... I would never go through that whole procedure more than once.
Click to expand...
Click to collapse
Gee; I've gone through it several times , cutting and pasting one line at a time from the ReadMe.txt file to the command line ... Actually, it's pretty quick if you do that, but I am looking at better ways to script it. However, I'd like to see some others run through the procedure (where they can see the consequences of individual commands if there are problems) before I "automate" it.
Notes:
While Microsoft has never advertized it, their C/C++ compiler libraries have from the beginning supported both "/" and "\" as a path separator on Windows. A quick test of ADB supports that as well. So, it may be possible to create just one set of scripts (note that running zergRush drops the ADB shell connection).
I use individual "adb push" statements for the files, because that preserves the date/time of the original file (I DESPISE the use of "cat" to copy files for this reason). I know using "cat" is a common Android script practice, but it makes it very difficult to determine the age of installed files (WHEN they were installed is not of interest to me). Of course, either usage is easily scriptable.
Oops ...
mfleigle said:
I keep getting this error when doing step (adb push nooktablet_1_4_1_update.zip /media):
failed to copy 'nooktablet_1_4_1_update.zip' to '/media': Is a directory
Click to expand...
Click to collapse
Try "/media/" at the end (missing "/").
.ZIP file has been updated (v0.3).
I used B&N's method. Copying the zip to "MyNook" from: barnesandnoble.c om/u/Software-Updates-NOOK-Tablet/379003187
And You might want to change the wording of step 6.5. I thought you mean to unzip using the cmd window. I ended up using the apks from nookandzergy and modifying its script to install Gapps
Requirement 1.2
mfleigle said:
I used B&N's method. Copying the zip to "MyNook" from: barnesandnoble.c om/u/Software-Updates-NOOK-Tablet/379003187
And step 6.5 I get: 'unzip' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
OK, you have to have unzip on your computer or an equivalent unzip program. While "unzip" is not included in Windows distributions, it's an almost universally available program (you can use a GUI version to accomplish the same thing).
DeanGibson said:
OK, you have to have unzip on your computer or an equivalent unzip program. While "unzip" is not included in Windows distributions, it's an almost universally available program (you can use a GUI version to accomplish the same thing.
Click to expand...
Click to collapse
I updated my earlier post, since I relized after posting that that step was for linux. Thanks for the instructions. I am now on a rooted 1.4.1, lol
Use "unzip" or an equivalent
mfleigle said:
I thought you mean to unzip using the cmd window.
Click to expand...
Click to collapse
I did. However, I will change the ReadMe.txt file to note this issue.
mfleigle said:
I ended up using the apks from nookandzergy and modifying its script to install Gapps
Click to expand...
Click to collapse
If that does the job, good!
miniblue said:
Can one assume that since the tablet will be rooted 1.4.1 there is no need to block the OTA to 1.4.1?
Click to expand...
Click to collapse
I would still block OTA's since 1.4.2 might remove rooting altogether.
Did anyone else read the NT's TOS? It says sideloading is allowed (even in the 1.4.1's TOS)
Im sorry is this method for windows or linux? being 1.4.1 i suppose that still have all the fixes? can someone confirm no strange behavior with apps, fc's?
A great guide for newcommers and others alike, all credit goes to the original poster (appdroid)
Originally Posted by appdroid
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word. The idea came from here. I may have took some of his work. SO credit him and Pirateghost for the information about Android.
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
ASOP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
Click to expand...
Click to collapse
thanks.. there were a few in there I didn't know!
FYI, I'm fairly certain appdroid kanged this from the CyanogenMod wiki.
I have a question, and if possible the answer should be as wide as possible to work on as many systems as possible. While I am not fully conversed in Android functions, syntax, and interfaces, I have been programing various computers since the mid 80's and have applied rooting/jailbreaking methods to several systems (if it functions like a computer, I want my Admin rights, much thanks to each and all authors of these). I know that someone somewhere out there may have asked and already found a solution to this very annoying problem.
Thanks to the Google's decision to increase security in the Android OSes (KitKat and higher) by removing write access to the SD Card (as I call it a very 'bonehead' and brute force decision), most of the older apps do not work properly anymore with the user added SD Cards and most are not being updated with some form of support (create a folder on SD Card). The solution for most persons is to root the system then either run an app that corrects the problem or install a new LRAM image (Lockable RAM: 'unlock' the RAM and overwrite its data with a new image then re-lock it. I don't like the term 'ROM' for this as it has been incorrectly used since the late 80's). I have found at least 2 file managers that say they have a (in-app) solution, but these solutions don't extend to all of your other apps (ie "Root Explorer" or "B1" solution doesn't help your File server/uTorrent/Photo Gallery app).
But what of the owners that for one reason or another can't root their system (unable to root, not authorized or allowed to root, etc.) but want/need to have write access to the user added cards (mainly because their internal storage is just too small)? Example, in my case my personal phone has several apps that require it to remain in an unrooted state for certain work related programs (security issues).
So here is my question:
Is it possible, on an unrooted and stock LRAM android device, using ADB to PULL the "platform.xml" file, add the line '<group gid=”media_rw” />' to it, then PUSH the edited file back to the android device?
I realize this may require entering (various name versions) Recovery or Update mode which is specific to each device (I think Samsung calls their ODIN). But I think the ADB commands and computer side instructions should be the same. So if it is possible, please list all ADB instructions (I know the text editor used will depend on the PC/MAC OS used).
Thank you one and all that give any advice or assistance.
Well it looks like there have been a lot of lookers since I first posted this but still no reply by anyone that knows Android OS inside and out. Most of you are probably thinking "tl:dr" to all of it.
I know there has to be a way to update/upgrade system files that doesn't require rooting or a way to find the manufacturer's or cellular vender's access path or password.
Hello,
I recently got a hand on Yuntab K107, ARM MT8752, Android 5.12 Bootloader unlocked. Everything worked fine until factory reset, after that Google play store and other gapps stopped working (play store checking info, then goes black and freezes for a while).
Tablet is rooted from factory by kingroot, I tried finding TWRP/CWM for this tablet to reflash gapps but I failed. I also tried Magic TWRP installer and MTK droid tools. Magic TWRP installer acts like it's working but no results. MTK droid tools refuses to find my device even if i tried every driver possible and cleared wrong drivers with USBDeview.
I also tried flashing gapps manually thru root explorer by unpacking gapps files and matching system file structure also no luck.
Then I backed up the stock recovery and tried flashing few custom TWRP's that some post suggested may work (you guessed it - it didn't work) It just hangs on the first booting screen then it surrenders after a while and reboots back into android.
Do you know about any TWRP/CWM that might work on this tablet or any other way to repair gapps if recovery is not necessary?
Thanks
I also rooted it with kingroot but havnt any custom recovery but i doing some experiment. Let se what it will result
I should be able to compile TWRP for you
I have one of these K107 tablets but it is running Android 7 and so far I have been unable to root it. Because you guys have root you should be able to download adbd Insecure by chainfire and follow this guide to Fetch the boot.img file by Extracting the boot.img directly from the device:
you will first have to determine the (sadly device-specific) path to the storage device where boot.img's content can be retrieved. I know two methods for this:
ls /dev/block/platform/*/by-name/ (where * covers yet another device-specific folder name, chances are it is the only directory below platform/), the exact name to search is also platform dependent but makes usual sense (some examples: boot, LNX (acronym for "Linux")). The files in this directory are actually symbolic links and some people bother to manually go to the target, but I recommend sticking with the higher level name based path which, while longer, remains less error prone. So you will end-up with a path like /dev/block/platform/sdhci-tegra.3/by-name/LNX.
On some (older?) devices, the right device could be found by investigating the output of cat /proc/mtd. If you see the device mtd2 associated to the "boot" label, then you will use the path /dev/mtd2.
Now:
From the phone's developer menu:
Enable debugging on your phone,
Allow root access to ADB (this step applies to phones running CynogenMod, other devices may require some potentially more complex procedure),
Connect it to your computer (and from there to the VM guest if you are running Android tools from within a virtual machine).
If this is not already done, I recommend to manually start the ADB server on the computer's side, this will allow you to directly validate the RSA key on device's side without affecting the behavior of the following ADB commands:
adb start-server
Then switch ADB in root mode:
adb root
Finally, you should be able to directly extract the boot.img file from the device using such command (the source and destination path and names are given as examples, adapt them to your needs and preferences):
adb pull /dev/block/platform/sdhci-tegra.3/by-name/LNX ./boot.img
The command will copy the whole partition, both used and free space, so don't be surprised that the resulting boot.img file will be larger than the original boot.img file coming with the stock ROM .zip file, the content itself remains similar.
Once the transfer is finished, disconnect the phone and don't forget to disable both debugging and root access from the developer menu.
Then upload the boot.img and I will build TWRP and test it on my tablet for you