For Droid 2's on Gingerbread, click link below to find info to Root your phone
http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
One Click Root Version for Linux and Works for Mac, too!
This is still a work in progress! Gonna call it 3.3 (I went through 3 previous versions). It takes the 2.2.1 version and adds a user interface. Nice, easy, clean. In order to run this script, you need to chmod (change permission) of the .sh file, and then execute it.
Download the file here: http://kimete.com/droid/beta/dorootv3.sh
It is good for both Linux and Mac. All you have to do is execute it and the script will download all the appropriate files for you!
How to run this in Ubuntu/Linux
How-to video here: http://www.youtube.com/watch?v=gvlB3e_UE8I
Note: General idea. You no longer need to update android-sdk, though.
1. Download the file.
2. Right-click the file, choose properties, choose the permission tab, and check executing file as program, close window
3. Double-click the file, choose Run in Terminal, and it'll start.
4. Choose 1 for install and root. Choose 2 for root process only. Only good if you've rooted using this method before, or you need to reroot your phone. Choose 3 to unroot. Choose 4 for credits/donation information. Choose 5 to exit. Choosing other numbers...
How-to for Mac
How-to video here: http://www.youtube.com/watch?v=d7s8dtfYyHI
Note: General idea. You no longer need to download and install android-sdk anymore.
1. Download dorootv3.sh. Best to put it on your desktop.
2. Open a terminal. Go to the magnifying glass and type in terminal, and then select it.
3. Next, you need to change permissions. Type in the terminal chmod 0755 followed with a single space. Then drag the dorootv3.sh into terminal.
You should see something like this chmod 0755 /user/(file path)/dorootv3.sh. Press enter.
4. Now run your file by dragging the file into the terminal again and pressing enter!
5. Now choose and option...
New version of rooting for Linux and Mac! Version 2.2.1!
Linux 2.2.1: http://www.kimete.com/droid/beta/DoRootLinux_221.zip
Mac 2.2.1: http://www.kimete.com/droid/beta/DoRootMac_221.zip
General Instructions:
1. Extract the files.
2. Change the permissions on the doroot.sh file
3. Run doroot.sh file.
Instructions for Linux and Mac
1. Extract the respective files to somewhere accessible. Your home directory or desktop is idea. The file comes in a .zip file. Just open it up and drag and drop the DoRootMac or DoRootLinux folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the folder in terminal.
example: [cd /DoRootMac or cd /DoRootLinux]
4. enter [chmod 0755 doroot.sh] then run it [./doroot.sh]
5. Let it run.
6. That's it, you are done.
One Click Root for Windows
Here's the Windows version. Facelessuser pushed this through and worked his magic. Give it a try. Very exciting stuff. I haven't used it yet, but according to him, it should work!
Download here, Ver. 2.1.4:
http://www.kimete.com/droid/beta/DoRootWin_2.1.4.zip
Instruction for Windows:
How-to video here: http://www.youtube.com/watch?v=B7RGVikpQ8o
1. Extract the folder from the DORoot zip file to your desktop. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom righ, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot.bat
5. Let it run.
6. That's it, you are done.
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Many thanks to facelessuser for working his magic!
====
====
How-to Videos
Video of the Rooting Process for D2 and DX by [email protected]
For Windows/Mac/Linux
http://www.youtube.com/watch?v=u5l3MDomDSc
Video of the Rooting Process for D2 and DX by DarkOnion
For Windows
New: http://www.youtube.com/watch?v=B7RGVikpQ8o
Old: http://www.youtube.com/watch?v=gzlg9a-H42w
How to use the ADBDL.sh file by DarkOnion
For Mac and Linux
http://www.youtube.com/watch?v=9cHpGXfEudM
=====
=====
Frequently Asked Questions
Why does my anti-virus tell me that the files contain Trojan's?
The files are exploits and hack your phone. Don't worry, they are clean. However, to be safe, do not download from any other source than the ones linked in this post.
I've gotten countless hate mail and comments on Youtube users about rageagainstthecage-arm5.bin being detected as a trojan. It is an EXPLOIT. If you are scared that the files I hosted are going to give your computer a virus. Look else where, like Z4Root, though, my understanding is that Z4Root also uses rage.
http://forum.xda-developers.com/showthread.php?t=853704
What is do these files/programs/scripts do?
These scripts will root your Droid 2 or Droid X phone with the least amount of user input as possible.
Why should we use this method and not another method?
All the methods are based off the same process/procedure. If you feel like doing MORE work, we can't stop you. The reason why we wrote all these scripts is to expedite the process, make the procedure easier, and to reduce human input which reduces the chance of human error.
Is there anything I need to know in order to successfully root my phone?
Yes. READ THE DIRECTIONS. Read the directions first. A lot of people make errors because they don't read the directions. I've also provided links to my video and another video which outlines the root process. Both are only a few minutes long.
Root failed! What do I do?
Run the script again! Most people succeed on the first or second try. Usually the rest by the third try.
Do I have to install Android SDK and update it?
It depends. The new Linux/Mac version does not require you to. The windows one, we are still working on.
Does this work on other phones?
I can't answer that. I know it works for Droid 2 and Droid X.
Wait a minute, this isn't really one-click! What's the deal?
Deal with it. Don't like it, try the 25+ step process.
When I open up the Superuser app, I get a blank screen.
That is NORMAL. Superuser lists the processes/applications that you've allowed superuser access to. If you haven't allowed anything, then it will be blank.
How do I test if I have root or not?
Try downloading an app like Wireless Tether (published by Google), and running it.
What USB connection mode do I set my phone to?
PC Mode or Charge Only. Choose the one that comes up with USB Debugging.
I am not very good with computers. Is this something I can do?
Oh yes! The key to success is following the directions.
How do I update Android SDK?
On Windows, you just need to double click the SDK Manager.exe. On Linux/Mac, you need to go into terminal, navigate to the tools folder in the android sdk folder, and run this command ./android update sdk. More information can be found in the SDK Readme text file. On Windows, double-click and run the SDK Manager.
I am getting stuck at the "daemon not found/daemon is starting" part. What do I do?
You need to fumble with the settings on your phone. You don't need to close the terminal. Change between PC Mode and Charge Only mode until it starts to continue. If that still doesn't work, also try disabling then enabling USB debugging for each mode.
=====
=====
Reporting an Error or a Problem
You can report errors right here in this thread. Make sure you give us as much information as possible. List what operating system you are on, what phone you have, at what part of the script you had errors, and anything else you may have tried or done. The more information you provide us, the better we understand situations. Posting up pics or logs of the terminal is extremely helpful.
=====
=====
Change log for 1-2-3 Root
Version 0.0 - 25+ step tutorial on how to root D2 on Windows and Mac
Version 1.0 - Initial scripts to streamline processes and reduce user error in Ver. 0.0.
Version 2.0 - Streamline of multiple scripts into 1 script. Minimal commands. Minimal work. With error checking and reporting.
Version 2.1 - addressed issue where remnants of a previous root would not allow root to complete
Version 2.1.1 -
-Cleanup code.
-Address issue where I thought I was killing a hanging rage, but I wasn't (It was a syntax thing)
-Fix for ERROR6 or ERROR5 (this was drastically different than what I did in windows. I wasn't returning exactly a string in format I thought when doing the check, so I had to do some ridiculous stuff to process it.)
-Better error resolution. (more error checking)
-Refined unroot.
-Reboot if you had files from a previous root
-Now the script will automagically download needed root files if they are not in your folder. (If you are behind a proxy, make sure your mac or linux has curl or wget configured for proxies respectively)
-Longer wait before remount (I had it not remount because it was busy once)
Version 2.1.2 -
Linux and Mac
Contains everything windows 2.1.1
Unroots non bootstrapped phones too
All
Contains option to unroot
Version 2.1.3 - Added dounroot.bat
Vesion 2.1.4 -
-Fix bug where people were getting a false ERROR5 because they already had Superuser.apk
-Hide killing of busybox before unroot
Version 2.1.4 - Files are standalone. No need to download Android SDK anymore.
Version 2.2.0 -
-adb included, no SDK needed
-abort if cannot find adb
-remove alternate busybox at /system/xbin and /system/bin when unrooting
-remove alternate busybox at /system/xbin when rooting and installing busybox at /system/bin
-No more hang in exploit...I hope
-Clean up code
Version 2.2.1 - minor revision to code (curl related)
DarkOnion's DoRootv3
Version 3.0 - set-up menu's, added error checking, will detect which OS you are on
Version 3.1 - fixed issues with ADB SDK User interfaces
Version 3.2 - adapted to DoRoot 2.2.1
Version 3.3 - edited code for easier understanding and modifications
=====
=====
References:
Original procedure produced by Sebastian Krahmer
http://forum.xda-developers.com/showpost.php?p=7838000&postcount=1
Tutorial/How-to Root Droid 2 on Windows by DarkOnion
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
Tutorial/How-to Root Droid 2 on Linux/Mac by DarkOnion
http://forum.xda-developers.com/showpost.php?p=8103311&postcount=340
====
====
Appreciate my work and/or help, feel free to send donations my way! Poor college student here who just got a speeding ticket! Doh!
This is outdated information and should be used as a reference only! All updated versions have moved to POST #1.
Hi all. Made it to the front page of XDA Developers.
http://www.xda-developers.com/android/easy-rooting-method-for-droid-2/
I just want to make sure credit is given where due. First of all, the original procedure was produced Sebastian Krahmer. From there I wrote an indepth tutorial to root the Droid 2. I took a vague instruction set and help it grown into something that the average person could understand. Understanding the need to simplify the process, I decided to write scripts to further streamline the process. What started out as a 3 part script that involved 8 or 9 commands eventually became a two part script that involved 3 or 4 commands. I have no programming background, by the way. Having trouble getting the process down into one part, facelessuser volunteered to take my work, and put a bunch of neat things into it to get it to work as one thing with error checking! So, with that said, I'd like to thank everyone that had a part in the project, especially facelessuser for his dark magic arts that made the script run, matt4542 for constantly testing my various scripts, and everyone who directly or indirectly ran the scripts!
We are moving forward!
===
Hi all.
We (me), facelessuser, and a few others are working furiously to get an easy one step program out for you guys. In the mean-time, I have a pretty safe, and clean, and easy 2 step method for Windows, Mac, and Linux. I am still cleaning stuff up, but for the most part, it all runs well.
What you need:
Android-SDK for your operating system which can be found here:
http://developer.android.com/sdk/index.html
Motorola Drivers (if you are using Windows) which can be found here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
And the files/scripts/programs to root for your OS:
Want to try the one step process, go down to post #2!
Windows [1.0]: http://www.kimete.com/droid/DORootforD2Windows.zip
Mac/Linux [1.0]: http://www.kimete.com/droid/DORootforD2Linux.zip
Instruction for Windows:
GO DOWN TO POST #2 AND DOWNLOAD THE ONE STEP
1. Extract and Update Android SDK package to your computer. The file comes in a zip file. Just open it up and drag and drop the android-sdk-windows folder to your C drive. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Install Motorola Drivers
(Tip, to stop the launching of the Verizon/Motorola site, go to the MotoConnect icon in the bottom right, right click, when phone connects, nothing.)
3. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
4. Double-click and run doroot1.bat
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes before it boots you out.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthecage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to DOS, enter or double click doroot2.bat
8. That's it, you are done.
Instruction for Linux and Mac:
GO DOWN TO POST #2 AND DOWNLOAD THE 1-STEP!
1. Extract and Update Android SDK package to your computer. The file comes in a .tar.gz file. Just open it up and drag and drop the android-sdk-linux folder to your home directory or desktop. Next, extract the files from the DORoot zip file to the tools folder of Android SDK. You should be moving 7 or 8 files into the tools folder.
2. Make sure you phone is in PC Mode with USB Debugging enabled
PC Mode: Notification blind -> USB connection -> PC Mode
USB Debugging: Settings -> Applications -> Development -> USB debugging
You need USB debugging icon showing in notifications. Try Charge Only if you can't get PC Mode to show USB debugging.
3. Navigate to the tools folder of your android-sdk
[cd /android-sdk-linux_x86/tools]
4. enter [chmod 0755 doroot1.sh] then run it [./doroot1.sh]
5. Follow the instructions. You will enter into the shell and be prompted with a $.
6. enter [./data/local/tmp/rageagainstthecage-arm5.bin] and let it run. Can take up to 15 minutes.
6a. To check if rageagainstthecage worked it's magic, enter the shell with adb shell. You should see a # sign. If you don't, you need to run rageagainstthe cage again by entering the command from step six.
6b. If you see the #, exit the shell by typing exit.
7. After being booted from shell and back to command prompt, [./doroot2.sh]
8. That's it, you are done.
Enjoy my works? Want to show your gratitude? Just want to help a poor college student out, donate via PayPal to: [email protected]. All donations are greatly appreciated. Money will be spent on escorts, food, adult beverages, higher education and its bs fees, paying off my phone, and the wonderful speeding ticket I got this week!
Hey Thanks alot for writing this! I just tried it out and ran until completion.
A few things I found.
In the dos prompt, part2 the program asks user to input a few commands. Commands 2 and 3 should end in .sh. The program dosent mention this.
Thanks again
Typo in the 3rd step. You forgot to add '.sh'.
lockdownx1x said:
Typo in the 3rd step. You forgot to add '.sh'.
Click to expand...
Click to collapse
Doh. Good catch y'all. I will take care of that now!
Problem
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
The " ./ " before doroot.sh tells linux to look in the current directory for the file to run. Make sure you in the tools directory of the sdk and that the script is there as well.
Sent from my DROID2 using XDA App
Yep i definitaly made sure of that but same error. It doesnt matter though i have rooted my droid 2 through the manual proccess
NiteSite said:
Everytime i type: $ ./doroot2.sh
i get:
./doroot2.sh
./doroot2.sh: not found
thank for the help!
Click to expand...
Click to collapse
Did you do cd data/local/tmp in adb shell before doing the chmod and ./doroot2.sh?
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
NiteSite said:
Yeah the chmod doroot2.sh worked without a problem. ./doroot2.sh did not tried it several times though
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Weird. I am going to send you a PM. Hit me up on Google Talk.
-Kevin
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
mjones1052 said:
Should turn this in to a one click root app for D2. Couldn't you essentially do some modifications and run it from the phone?
Click to expand...
Click to collapse
I am working on it. Hahaha. I don't have any programming background. So I am learning on the fly, but progress is being made.
Though, I have to say that the process is much much much easier than what it originally began as. So... moving in the right direction.
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Kenny Strife said:
I'm not much of a programmer. I'm on Windows. Do I need to chmod the files, and if so, how would I do that?
Click to expand...
Click to collapse
Just follow the instructions. Launch the doroot1.bat file. The .bat file will launch you into ADB shell. chmod the doroot2.sh file, then run it. adb shell again. chmod the doroot3.sh file and run that. Hope that helps. I am on google talk if you need help.
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
please help!
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
chrismouro said:
i rooted manually and when i try to open superuser permissions icon i get a black screen...should i follow your steps to root now and will that work ??
Click to expand...
Click to collapse
You are okay. Superuser lists the program you've allowed superuser access to. You haven't given any apps access, therefore blank!
Kenny Strife said:
I'm stuck on the second step. Attempting to contact you through Google Talk...
Thanks, by the way.
Click to expand...
Click to collapse
Kenny, did you get this resolved? I am experiencing the same issue.
I'm getting kicked the ./doroot2.sh: not found as well. Anyone get past this point?
I bartered for a cheap chinese tablet this past weekend. It is an Ematic EGM003BL with Jellybean 4.2.2. I got it with the intention of trying to install the google play store and other related apps.
I have a tiny bit of experience with hacking android, mainly I managed to install Cyanogenmod on my wife's old Nook Color.
So at this point I have the tablet with a barebones install of 4.2.2.
I used SRSroot to root the tablet but it said that the tablet was already rooted. If I tried to click on the build number in the About tablet setttings, it told me that I'm already a developer.
I also installed Rom Manager, clockwork on the tablet (side loaded I think).
I downloaded the appropriate Gapps package from the goo link. I copied the gapps package to the device and that is where I'm at.
I really can't use Rom Manager to doanything because the tablet is an unsupported device.
I searched for info on installing the Google Play store and related apps on unsupported devices and the main results show how to install it on a rooted kindle fire.
The key that those instructions show is to put the tablet into recovery mode but I can't seem to do that.
When I turn on the tablet while holding the volume down button, I get a display on the screen shown in the attached picture.
use cmw or twrp to installing gapps from recovery
iwjosi said:
use cmw or twrp to installing gapps from recovery
Click to expand...
Click to collapse
I have the clockwordmod rom manager program installed on the tablet but because its an unsupported device, it won't allow me to make a recovery. So I'm not sure where to go from there.
Were you able to find any solution for this. I have chinese tabled and want to install Google Apps on it. What is the process and/or way to do that.
Have a good root but no Gapps
anshumangoyal said:
Were you able to find any solution for this. I have chinese tabled and want to install Google Apps on it. What is the process and/or way to do that.
Click to expand...
Click to collapse
After many hours of searching and trying different solutions I have actually got mine rooted and booted up with the procedure below:
thanks DVD2955
Forum thread: Is the Ematic Genesis tablet from Walmart rootable?
Update: The following is for your information I can not be held liable if you "Brick" your tablet as this worked for me, but try at your own risk!!
Read this page: Universal Root
Use this utility: Root_with_Restore
Then download the GAPPS from the above link and extract and find the folder "SYSTEM"
Open a dos command prompt window.
Now connect your tablet via USB and be sure that you have it set for USB DEBUGGING in the system / development
DO NOT TURN IN USB STORAGE.
Go to the folder where you extracted the download "Root_with_Restore" go to the folder 'STUFF' and from the command box type " adb device " you should see your tablet connected.
Run the "BAT" file from "Root_with_Restore" [I do not remember for sure but I know that "Other" did not work so I choose the option above it.]
Then find where you extracted the GAPPS system folder and type: adb push <if needed type in the full drive+folder listing>system /system : now wait.. you should see allot of screen messages. till you get a message saying complete.
Unplug the USB cable and turn off your tablet.
Turn on your tablet... this may take longer than in the past.. but you should have a working "GOOGLE PLAY STORE" once your system comes up.
It fails at the push for GAPPS
From my folder where ADB is located I run this command in the CMD window:
adb push C:\gapps\system /system
it returns this:
Push: c:\gapps\system/addon.d/70-gapps.sh -> /system/addon.d/70-gapps.sh
failed to copy 'c:\gapps\system/addon.d/70-gapps.sh -> /system/addon.d/70-gapps.sh' : Read only file system.
Need clarification whether mounting the sysem folder and setting permissions to rw will correct the failure. I am not the expert and have only rooted and modded Coby Kyros, Craig and Pandigital tablets.
adb Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android (On 32-bit Linux)
Xperia Z5 Compact E5823, Android 6.0.1, 32.2.A.0.224
Installed adb to explore my old (ST15i/Gingerbread) phone. Seems to work ok.
Thought would plug in new Z5 and make backup -
Enabled developer mode, usb debug enabled.
adb_usb.ini is ok
51-android-rules is ok
phone is recognised, adb device shows phone connected, can execute shell command etc.
but when I execute
Code:
adb backup --all
I get the following prompt
Code:
Now unlock your device and confirm the backup operation.
But no prompt appears on phone (or not at least in any obvious place)
have tried restarting adb daemon, rebooted linux, rebooted phone etc to no avail.
Searching via google hasn't thrown up much except two sites, one that says Z5 does not support adb backup while the other says it works perfectly.
Comments and suggestions welcome
Use helium app from play store for backup.
Adil Tariq said:
Use helium app from play store for backup.
Click to expand...
Click to collapse
Ok, but what I'm really looking for is to find out about this specific issue.
thanks
TVPad 4 is fourth in a series of Android-based IPTV settop boxes targeting the worldwide Chinese communities at large, although it seems to work well as a basic Android TV box. Support for all its predecessors (TVPad 1-3) have been discontinued. This guide will only focus on TVPad 4, model M418. Also this device have been banned from US and upgrading it may "brick" it - more on this later.
The method I used below is gathered from various sources elsewhere but not much on rooting and ADB. This is a compilation of all the most important info in one place. I am not sure if its bootloader is locked or not, but the Android 4.4 kernel sources can be found at openlinux.amlogic.com.
Physical specs:
AmLogic S805 SoC: ARM Cortex-A5, quad-core 1.5Ghz, Mali450 graphics, 1080p H.265 support
~1GB RAM
microSD card slot
HDMI out
USB-A port
Hardware needed:
To fully complete the process you'll need:
Monitor/TV with HDMI port
USB hub
microSD card
USB drive (optional)
USB keyboard
USB mouse
The remote that came with your box
Files needed:
* TVPad 4 5.054 firmware + TWRP 2.8.1.0: https://tvpadtalk.ca/discussion/1071/downgrading-tvpad-4-to-5-054/p1
The TWRP seems to be the modified from the one for AmLogic k200. Only the one from above work; the one from TWRP themselves do not.
* TVPad 4 5.066 OTA update: http://www.phoneunlock.com/forum/viewtopic.php?f=5&t=590
If you have this box and are in the US, do NOT do 5.066 update; your box is going to be banned. Might as well go all out and repurpose it into a general purpose Android TV box; but for the rest of the world, this update directs your box to different servers where it's mostly business as usual. You should be able to go direct from 5.054 to 5.066 following this guide, despite what others say.
* Root zip: http://www.freak-tab.de/finless/s89_root_update.zip
* APK install hint file:
Create a file named batchinstall.banana with contents below:
Code:
directory=
checkapp=no
Preparation
1. Download the 5.054 firmware and unzip into root of your microSD card. You should have recovery.img and TWRP folder. They are the TWRP recovery and a 5.054 TWRP backup respectively. Devices boots from recovery.img on root of microSD card if detected.
2. NON-US ONLY: Download the 5.066 OTA update to microSD root.
3. Download root zip to microSD root.
4. Put batchinstall.banana and any APKs you want to install on your USB drive or microSD. There is a APK pack of 23 apps for Cantonese speakers or 29 apps for Manadarin speakers available out there, but I haven't bothered. I included an updated SuperSU, ES File Explorer (preferably an older version; I used 4.0.4.9; newer ones are heavily loaded with ads), VLC, Firefox, AdAway, Terminal Emulator (by Jack Palevich). The last 4 being open source should also be available from F-Droid. Substitutions can be made to taste but Terminal Emulator is required to enable ADB (see below).
Enter Recovery
You will need to use stock recovery for OTA update AND TWRP for 5.054 firmware and root.
1. Connect HDMI monitor and USB hub to device. Connect USB keyboard and mouse to the hub. Leave power disconnected.
2. Look for a hole on the underside. If you have one, stick an iPhone/iPad SIM ejector pin in it and feel for a button. If able, this is the recovery button and you may skip to step 6.
3. Pull off the 4 rubber feet on the bottom and remove 4 screws under them.
4. Pry around the seams and lift the bottom cover off.
5. You either have a recovery button on the PCB or an empty spot for it. If no button, you'll have to short the bottom two contacts where the button is supposed to be (with all ports on the top edge).
6. Insert microSD card into "TF" slot. IMPORTANT: Leave popped out to enter stock recovery; fully insert to enter TWRP.
7. Press and hold the recovery button (or short the contacts) while plugging it in. Keep it pressed (or contacts shorted) until the recovery or TWRP appears.
8. Operate stock recovery with keyboard and TWRP with mouse.
Re-flash 5.054 - Downgrade/Unbrick
People do this to recover from "use restricted" or some other server errors after this thing is sued out of the States. I have also used it to recover from a soft brick situation.
1. Fully insert microSD card. Enter TWRP.
2. Select Restore. Choose External SD for storage.
3. Select the only available package to restore.
4. Swipe to Restore.
5. When complete, do not reboot yet. Return to main menu and select Wipe. Swipe to Factory Reset.
6. US ONLY: Remain in TWRP and proceed to step 2 of rooting.
7. NON-US ONLY: Return to main menu and select Reboot, Recovery. Immediately after screen go blank, push the microSD card again to eject it. It will pop out half way. Leave it hanging there. Proceed to update 5.066 next.
Update to 5.066 - NON-US ONLY! New server and Play Store support.
1. Enter stock recovery.
2. Fully insert microSD card.
3. Select Apply update from EXT and press Enter.
4. Select your 5.066 update file and press Enter.
5. When update complete, unplug power. Proceed to rooting.
Rooting
This is too easy with TWRP.
1. Fully insert microSD card. Enter TWRP.
2. Select Install, then the root zip file. Swipe to install.
3. Reboot into system and proceed with initial setup.
Kingroot also works but leaves some very persistent crap and questionable apps on the system so I do not recommend rooting using it.
Sideload apps
Plug the USB drive with your apps and batchinstall.banana file into the device or hub. Batch installer will appear. Select Batch Install and check that all apps you are installing are there and checked, then select Install.
Enable ADB
TVPad 4 does not have a USB slave port so ADB is only through TCP/IP. Steps below assume you have adb working on your computer.
1. Connect a USB mouse if not already.
2. Move mouse to right half of top of screen then drag down. Click on the gear to enter regular Android Settings app.
3. Enable Developer Options - About Mediabox, click Build Number 7 times.
4. Enable USB Debugging in Developer Options.
5. Open Terminal Emulator (sideload it if you haven't already).
6. Type in the following:
Code:
$ su
(Grant root if prompted)
# setprop service.adb.tcp.port 5555
# mount -o remount,rw /system
(Make the same setprop change in /system/build.prop - uncomment or add the line)
# stop adbd
# start adbd
7. Find the IP address of your TVPad from its own over-simplified settings page.
8. Open a command prompt/terminal on your computer and do this:
Code:
> adb connect <TVPAD IP ADDRESS>
(Authorize your computer on the TVPad.)
> adb devices
(confirm its IP is listed and not "unauthorized")
> adb shell
$ su
(grant root if prompted)
#
(success!)
# chmod 660 /data/misc/adb/adb_keys
(Double check permissions the public key file of authorized ADB clients)
9. Reboot and check that the change stays.
You're done! Now you have full control of this little TV box even after its server go under for good.
Additional apps
Kodi 15.2 seems to work on this box. 16.1 is untested. 17.x will not work since it requires Lollipop. Download from kodi.tv.
If all you want out of TVPad is TVB programming, the official app TVBAnywhere works on this box. About US$100/yr subscription for its own original programming only. Oh and it doesn't serve the States either. Go figure.
The gapps framework added with 5.066 is very minimal and doesn't work for eg. maps. You'll need to get it from apkpure. Use version 11.0.38-030-155006848.
I'm still looking for a decent launcher.
Credits:
https://www.youtube.com/watch?v=6evvWebosnU
https://www.youtube.com/watch?v=ZtY_qdYzmPs
https://www.youtube.com/watch?v=W2heIbUdZVE
can we flash any other rom on TVPad 4 since we can install TWRP??
I rooted easily with kingroot apk. to get shell, I just used my laptop as proxy between wifi and lan, created a meterpreter reverse_tcp metaploit payload, connected back to my laptop, shell and then su...
3vilhomer said:
can we flash any other rom on TVPad 4 since we can install TWRP??
Click to expand...
Click to collapse
To be honest, I'm more interested in if we can get Lollipop on this thing, for that is required for Kodi 17.
For whatever reason I can't boot into the TWRP. I have all the recovery.img and TWRP folder located in the root directory of the SDcard and my SDcard is FAT32 formatted. What did I do wrong?
Suppport has been officially terminated for this box so, it will only be a normal TVbox.
I'm kinda wondering if the SoC supports at least lollipop. A custom rom would be cool to run Leanback apps with a few modifications
ya, is there anything we can do with this box now since most live tv apps doesnt work on it anymore
Do you know where I can grab the file for TVPAD1? I am not sure which model I have, is only written TVPAD on top and there is no 2S, Plus or anything else.
TvChina, a subsidiary pay TV app after TvPad 4 ceased operating on June 1st. TvPad, the parent company, together with its Blue TV etc, have gone bust due to lack of funds from global dwindling sales. Now that the box is useless, can someone upload a root file so we can wipe then reuse it for other purposes? Found a related message on Google but it's has been blocked. Thanks in advance. Wonder if someone can get hold of firmwares for UnBlock or evPad etc so we can tune this into other sites.
did anyone ever put a different android OS on this and got the IR blaster to work too??
3vilhomer said:
did anyone ever put a different android OS on this and got the IR blaster to work too??
Click to expand...
Click to collapse
They were able to upgrade to android lollipop here:
tvpad.ca/discussion/1993/tvpad4-upgrade-to-android-lollipop-5-1
The root file "s89_root_update.zip" link is not working anymore. Does anyone has a copy > please post it here.
Hello,
I have an Android TV that forbids me doing almost anything, except installing apps by inserting usb disk.
System information: Android 4.4.2 Linux version 3.10.0_s5([email protected])(gcc version 4.4.1 (Hisilicon_v200(gcc4.4-290+glibc-2.11+eabi+nptl)))#1 SMP Tue Jul 30 11:29:05 CST 2019 ARMv7 Processor rev3(v71)
Settings is stripped that only simple TV related items left. I cannot enable developer options by tapping multiple times on some item. Also I don't see any WiFi-direct related settings that I want to use Miracast on my phone. I tried install settings.apk exported from another Android 4.2 tablet and failed.
Adb is not possible, not only that developer options is not enabled, but also adbd is not running (seen from ps command in terminal emulator app). "start adbd" have no effect -- maybe no permission with userID like 10045.
Computer has no response when connecting to its USB port (male to male), no new device found.
There is no /mnt/sdcard, instead there is /mnt/mmcblk1/mmcblk1p1, with only one folder named Android that I cannot access. If I insert a usb disk, it will be /mnt/sda/sda1. And it seems I cannot execute from sda1, e.g. su binary, even it shows r_x permission (I have corresponding SuperSu apk installed first).
Google apps are stripped, which is normal for chinese system; but while most system allow you install by yourself, this TV failed installing Google Account Manager app (Google Play Services and Store apps could be installed, all exported from another Android 4.2 armv7 tablet).
Tried a bunch of rooting apps and none of them work. Frama, Towel, Magisk, Kingroot, Kingoroot, etc...
I am confused. Hope people here could give some help.