Rikomagic MK802IV Forum Thread - Android Stick & Console RockChip based Computers

Does this page look too large / unorganized on your xda app? If so open it in the browser.
Dear xda users. Since this devices is fairly unpopular I don't expect xda to ever add a forum for this device so this thread is meant to act like a Forum for the Rikomagic MK802IV (uses Rockchip 3188t) where I will post any links to ROMs, Recoveries and Custom kernels.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Custom ROMs
Neomode ROM + Kernel by Neomode from Freaktab
Download it from here
Custom Recoveries
TWRP 2.7.0.0 by abdul_pt from Freaktab
- Download the TWRP 1280x800 rk3188 KitKat version from here
Instructions to install (LINUX) :
Code:
. Download TWRP (1280x800 KitKat)
. Rename the downloaded file to twrp.img
. Make sure you have ADB set up for RK3188 (set up udev/usb rules for rk3188 devices : http://linux-rockchip.info/mw/index.php?title=ADB_shell_with_RK3066 ).
. Boot up your device and make sure "Connect to PC" and "USB debugging" is ON
. Plug a usb cable into the OTG port and your pc
. Open the terminal and type : adb shell
. Now type : mount -o remount rw /system
. Now open a 2nd terminal window and CD into the location where you saved your twrp.img
. In the 2nd terminal now type : adb push twrp.img /system
. Go back to the 1st terminal and to make sure twrp.img is on your device type : ls /system
. !!!WARNING THIS WILL REMOVE YOUR OLD RECOVERY FOREVER UNLESS YOU HAVE A BACKUP OF IT!!! If you see twrp.img in the list type into the 1st terminal : flash_image recovery /system/twrp.img
. Then type into the 1st terminal reboot recovery or just power off your device and enter recovery via the recovery button.
. TWRP should be installed. Use a mouse via the usb Port or use the OTG adapter that you got with your device. If the mouse gets glitchy you need to use a cable mouse!
Instructions to Install (WINDOWS) :
Code:
.Download TWRP (1280x800 KitKat)
. rename the downloaded file to twrp.img and save it into the ADB foler of your Windows PC
. Make sure you have ADB set up for Windows with the ADB drivers for your device
. Boot up your device and make sure "Connect to PC" and "USB debugging" is ON
. Plug a usb cable into the OTG port and your pc
. Open the ADB shell
. Now type : mount -o remount rw /system
. Now type : adb push twrp.img /system
. Make sure twrp.img is on your device type : ls /system
. !!!WARNING THIS WILL REMOVE YOUR OLD RECOVERY FOREVER UNLESS YOU HAVE A BACKUP OF IT!!! If you see twrp.img in the list type : flash_image recovery /system/twrp.img
. Then type reboot recovery or just power off your device and enter recovery via the recovery button.
. TWRP should be installed. Use a mouse via the usb Port or use the OTG adapter that you got with your device. If the mouse gets glitchy you need to use a cable mouse!
I have tested this on my mk802IV and I can confirm that it works
DISCLAIMER: I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG (EX. THE DEVICE GETS BRICKED) NOR IS THE DEV OF THIS RECOVERY RESPONSIBLE. THIS RECOVERY MAY NOT RUN FLAWLESS SINCE IT HAS BEEN BUILD FOR THE RK3188 AND NOT SPECIFICITY ONLY FOR THIS DEVICE. ALSO I AM NOT RESPONSIBLE IF YOU START THE 3RD WORLD WAR BECAUSE YOU THINK TWRP LOOKS UGLY!
Custom Kernels
KitKat kernel for most rk3188 devices (including MK802IV)
Check it out here

Tools
If you plan to develop for this current device you may always check out my media fire folder that contains all useful for developing on this device.
https://www.mediafire.com/folder/hc3dv1rlh9hl1/MK802IV
Also check my github for sources
https://github.com/CTXz

Reserved

Good news! I managed to compile a CM12.1 ROM for this device. Now I haven't yet flashed it but I will tell you results as soon as possible
Sadly I couldn't convert it into a flashable image because a not completed builld.

I am locking at it the first time and it looks interesting.
On Amazon.de the price is at the moment EUR 82,99
On our local marketplace the Version 3 is still to buy .
About Ricomagic V4. On her website Version5 is out .

mike2nl said:
I am locking at it the first time and it looks interesting.
On Amazon.de the price is at the moment EUR 82,99
On our local marketplace the Version 3 is still to buy .
About Ricomagic V4. On her website Version5 is out .
Click to expand...
Click to collapse
Cool. I chose 4 because its the most dev friendly and currently the device has common crashes etc. This is why I want to build a custom ROM for it. I sadly always get some terrible errors during compiling that make me scratch my had all day so if you have any experience with custom ROMs and you do decide to buy the device help would be apriciated

USB to ethernet adapter
Hi Guys,
First time here, so please accept my apologies if this is not the right place to ask this.
I have Riko and the WiFi performs poorly, i understand the best way to insure good quality is a direct connection.
How do i know witch USB to Ethernet adapter i should buy ( that would have android drivers)?
Thanks!!
Dror

Related

2.37 has been rooted!

I have tested it on my phone, it works perfect!
SORRY FOR MY BAD ENGLISH. I HAVE THE CHINESE WORDS ON MY PHONE, SO I DO NOT KNOW WHAT THE ENGLISH EXACTLY IS. I TRANSLATED THEM ON MYSELF, IF YOU DONOT UNDERSTAND MESSAGE ME.
1, you should FLASH RECOVERY TO YOUR PHONE, and that will not be talked here. lots of threads can tell you how to do it.(I HAVE PLACED ONE WAY TO DO IT ON THE SECOND PAGE)
2, unpack "root.rar" into your DISK C, and the folder must be "root"
3, now mark the "debug mode"( you can find it in application Settings) , connect your phone to your computer( just CHARGING MODE)
4, press win+R on your PC keyboard, and type in "cmd".
5, now we can see dos commond, you should type in the following commond one by one.
CD C:\root
adb shell
reboot recovery
6, now your phone should reboot into recovery. select mounts and storage. there select 3 items( mount /system, mount /data, mount /sdcard)
7, disconnect your phone, and connect it again. then type the following commonds into your PC. NOTE THE SPACE
adb push su /sdcard/su
adb push superuser.apk /sdcard/superuser.apk
adb push psneuter /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
8, if you can see "~#" on your screen, you have made it. I have encountered a error on the 5th commond but it seems like ok, afterall I have been rooted.
9, you still have some commond to type.
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
ln -s /system/bin/su /system/xbin/su
chmod 06555 /system/bin/su
10, now on your phone you should still have the recovery, unmount the /system, data, sdcard.
11, reboot your phone, and enjoy it!
Thanks very much for the help of pxw816, without him I still in dark.
is this for real? :\
adkz said:
is this for real? :\
Click to expand...
Click to collapse
Sorry for forgeting to upload the file. It works on the chinese rom, I think all rom can be rooted this way...
Anyone willing to see if this would work on a Telus Desire HD with 2.43?
Anyone tried this ?
I'm quite sure this only works on the Chinese ROM. But I might give it a try
I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.
torkaberry said:
I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.
Click to expand...
Click to collapse
Same problem, booting into recovery just shows this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think this is the second method posted that only works in China
CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Seems like the chinese OTA's have an unpatched exploit, maybe one of the mods would like to change the title of this thread.
hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help
CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Hey guys, you cannot use the official recovery, flash a recovery that is usually used to install a rom...My recovery is 3.0, I don't know if 2.0 is ok....
evanbigfan said:
hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help
Click to expand...
Click to collapse
I'm not quite sure about that, for people who do not have a recovery may place the following file on your TF card( DO NOT PLACE IT INTO ANY FOLDER!), and shut down your phone(I MEAN COMPLETELY OFF, OR YOU CAN PULL OUT YOUR BATTERY). Then try to press the volume down button and the switch button at the same time to start your phone. See if the recovery can be installed automatically or not. if not, I'm afraid you have to downgrade to root and get a S-Off. If you do not know how to downgrade, post here, and see if i can give you any help or not.
This will never work, you will need Root and S-OFF to flash recovery. (thanks hawks556 for pointing that out)
closed.

The best guide to rooting and installing roms

[Under construction]
Hello,
Since I see that a lot of people are having trouble with rooting and installing roms, and since their isn’t a guide for everything I decided I’d write thing.
Table of contents
Intros
-I.1: Intro
-I.2 Support list
-l.3 What is rooting?
--Pre rooting:
1.1 Downloading our utils
1.2 Prepare our transformer
--Rooting
2.1 Rooting
--Recovery Installation
3.1 Recovery and roms
3.2 Different roms
--what to do with root
4.1 WTFWR
________________________________________________________________________
I: intro
This guide is presented in the easiest way. If you follow each and every step you should be fine. With that said I cannot be held responsible if you mess up your device in any way
I.2 Support list
This guide is meant to be universal as possible. I can guarantee this will work with original us transformer. I’m not yet sure of the slider, 3g or ww models. Please confirm them working below in the comments. Keep in mind you should always check the support of the rom you want to use by looking at by checking the thread.
l.3 What is rooting?
Rooting a great thing. With it you can install roms, ,make backups and overall great backups. Below is a article on it:
http://www.tomsguide.com/us/Root-Your-Android-Phone,review-1688.html
________________________________________________________________________
1.1 Downloading our utils
STOP: If you have a device running .19 or below use razor claw for rooting. Then, afterwords if you want to install recovery the a rom jump to 3.1 Razorclaw doesn’t require you to have a computer.
Before we begin we will need to get our computer ready to root with nacho root. Head over to
http://developer.android.com/sdk/index.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to download the android sdk. Get the zip it’s easier. Once you download it and unzip it. Place the folder in the root of your C: drive (just trust me)
Now double click SDK Manager
Check the box next to “android sdk platform-tools” then click install X packages. Accept any terms that come up. The sdk is now installing. Ignore any errors. Wait till it’s done
Cool, now to get your asus usb drivers. This will help our computer recognize our device. Go to
http://support.asus.com/Download/ModelList.aspx?SLanguage=en&keyword=eee pad&type=1
Select your device, The for the OS dropdown box choose “OTHERS” Then hit the plus next to “UTILITIES (1)”. Under that click Global (DLM). Wait till it downloads then install it.
Finally to get our rooting software. We will be using nacho root from:
http://forum.xda-developers.com/showthread.php?t=1427838&page=1
Download Nacho root and SU
Pic 6
Go back to your android SDK folder we download earlier. Put both of the files in the “Platform-tools”
Pic 7
1.2: prepare our transformer.
Go into the settings. On the left click application. Make sure “Unknown sources” Is checked. Then click development. Make sure “Usb debugging” is checked.
2.1 rooting. It is rooting time. Make sure your device has a good charge on it. Then hook it up to your computer.
Go to your computer and open cmd by hitting the start button then typing in cmd. In the windows type in:
Cd C:\android-sdk-windows\platform-tools
Make sure you have the space between cd and C: If an error returns you didn’t follow the tutorial and put the folder in the correct path. If that is case use the right path.
Pic 8
Hit enter.
Now type in:
Adb devices
A random string of number should appear, if not your don’t have your asus usb drivers installed correctly.
Here is the instruction for you to type in to root from the dev. Do it one line at a time. Do not type in any of the <wait for boot> things.
Code:
adb push nachoroot.bin /data/local/
adb shell chmod 777 /data/local/nachoroot.bin
adb shell /data/local/nachoroot.bin --stage1
adb reboot
<wait for boot>
adb shell /data/local/nachoroot.bin --stage2
adb reboot
<wait for boot>
adb shell id
<if id is 0 / root then continue, else start over>
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell /data/local/nachoroot.bin --undo
adb reboot
If you did it right an your device didn’t turn into an ipad you should be ok. Go to the market. Get super user. If all goes well you have root.
STOP: Now if you don’t want to install recovery and get a rom (which I HIGHLY recommend) this concludes the end of the tutorial. Feel free to view the information after the recovery and rom section.
3.1 Recovery Installation and roms.
THIS REQUIRES A MICRO SD CARD
If you are here you must want to get recovery, install a rom, and make your tf 1000% times better.
To begin go to http://forum.xda-developers.com/showthread.php?t=1346180
Get the app either on your computer OR your transformer. Install it, and click the giant button. Let it do it’s thing. Now you have recovery, which allows you to install roms.
Time to boot in recovery. Get this app:
http://forum.xda-developers.com/showthread.php?t=1173434
and click the oversized button to boot into recovery. (Yes you can do the other method by turning of your tf and holding both power button and bottom volume at the same time then clicking vol up when you see text, but that requires more then one finger.
There you go. You’ll see a recovery screen.
NOW pay careful attention. Once you are there we need to make a backup. Use your vol keys to scroll down to “Backup and restore”. Select it with the power key. Now make a backup by clicking backup (With the vol and power keys from now on obviously). Now you have a backup. To install a rom simply get the rom from the xda section (check comp. and don’t get nflash) and put it on your micro sd card. Boot into recovery. Scroll down to “install zip from sd card”. Then choose zip from sd card. Find the rom you put on the micro sd card. It should install. If this was to difficult view this kind man’s vid tutorial:
http://www.youtube.com/watch?v=fWdfce9wBjs&feature=related
May be wondering what rom you should pick. I recommend revolver, because the dev is offering me a large some of many to say that (Just kidding ). But really revolver is great.
Others include:
Prime
Revolution
And many more at: http://forum.xda-developers.com/forumdisplay.php?f=1107.
I wonder why there has been no one at least thanking you for your effort in writing this reference,
However i followed your instructions and have been successfully able to root my Transformer,
Thank you very much
keep it up
o_0
10 char
Thanks mate I am now rooted
i'll use the software when I get my Asus Transformer Prime
Question: Does the rooting tool work on the ICS Firmware?
Sent from my NexusHD2 using xda premium
andyabc said:
i'll use the software when I get my Asus Transformer Prime
Question: Does the rooting tool work on the ICS Firmware?
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
No, for ICS on the prime there is another method. I thought the name is mempodroid.
Look in the prime forum.
O.k then I'll root with this tool then use OTA Root keeper so I can be rooted on ICS
Sent from my NexusHD2 using xda premium
Thanks for the great post... always love having pictures along with instructions
andyabc said:
i'll use the software when I get my Asus Transformer Prime
Question: Does the rooting tool work on the ICS Firmware?
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
My answer is NO. I just push to ICS 4.0.3 and it does not work on ICS.

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

Root Nexus 4 on Linux

I just rooted my Nexus 4 using Ubuntu 12.04.
The instructions I found weren't quite what I'd liked them to be, none of them were for Linux and I had to do quite a bit of trial and error.
I know that a few years ago I wouldn't have been able to do it with those instructions.
So I thought I'd write down what I did so others can do it easier and faster than me.
To be able to easily understand this guide you need to know the basics about using a terminal, but other than that I'm trying to not to require the reader to know anything.
If you use another Linux distro everything should work pretty much exactly the same, but for the additional packages I had to install, but their name should be easy to guess because they are usually similar across distributions and how you install them should be explained in the documentation of your distro.
Connect your Nexus 4 to your computer using an USB cable.
First I downloaded the ADT Bundle from there developer.android.com/sdk/index.html and unpacked it into a new folder. Doesn't matter where, I'll use ~/androidSDK in those instructions. The tools which you need to root your phone are ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb and ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/fastboot
"x86" means I downloaded the 32bit version and "20130514" is the date of when the version I'm using was published, that will most likely be different for other people.
Now most likely adb and fastboot won't run yet (if you run them it will tell you something like "~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"). To fix this you need to install the packages "lib32ncurses5" and "lib32stdc++6". You can run the following command to do that:
Code:
sudo apt-get install lib32ncurses5 lib32stdc++6
(got that from there: stackoverflow.com/questions/10005907/eclipse-android-plugin-libncurses-so-5)
For adb to work you also need to activate USB debugging: Go to Settings->About phone and tap "Build Number" until it says you are developer. Then a new entry will appear in "Settings", called "{ } Developer options". Check the box next to "USB debugging", confirm with ok.
Now you need to backup everything on your Nexus 4 because it will be wiped while rooting. You can do this by running:
Code:
cd ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools
(in the future I'll assume you stayed inside that directory)
Code:
./adb backup -apk -shared -all -system
Before this command can finish you need to confirm on your Nexus 4 that it's okay to do that backup (just do what it says on it's screen).
This will put a file named backup.ab in the current directory. You can change the name and location of that file using the -f paramter, if you want.
Run
Code:
./adb reboot bootloader
to boot into the bootloader. After a moment the Nexus 4 should display something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(image stolen from reviews.cnet.co.uk/mobile-phones/how-to-root-your-google-nexus-4-50010361/)
Now the actual unlocking happens: Enter
Code:
sudo ./fastboot oem unlock
Maybe try without sudo first (just leave it out), but it only worked with sudo for me; without sudo it displayed "waiting for device" forever and I needed to abort with Ctrl+C.
Download SuperSU from there http://download.chainfire.eu/supersu (at the moment "CWM-SuperSU-v0.98.zip").
Put that file on your Nexus 4 any way you want, one possible way is to do:
Code:
./adb push ~/CWM-SuperSU-v0.98.zip /sdcard/
That assumes you downloaded SuperSU to your home directory. For that to work you need to activate USB debugging again (it was deactivated during unlocking).
Download the Nexus 4 "Touch Recovery" from www.clockworkmod.com/rommanager.
I guess you shouldn't need the touch version, but it's more comfortable for sure. When I downloaded it the file was named "recovery-clockwork-touch-6.0.4.7-mako.img" and that's what I'm going to use when I give you commands to run.
This "Touch Recovery" needs to be installed to the Nexus 4. To do this first boot into the bootloader again:
Code:
./adb reboot bootloader
And then flash the file using the fastboot utility:
Code:
sudo ./fastboot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
(if it needed sudo the last time it will need it again, if not, not)
Now go to the recovery mode (use volume buttons to navigate and power to confirm).
Tap "install zip from sdcard"
Tap "choose zip from sdcard"
Tap "0/"
Find the SuperSU .zip file you put on the phone earlier (tip: scrolling works as usual by swiping or if you want with the volume buttons) and tap on it.
Confirm that you really want to install it.
Boot into Android again and restore the backup you made earlier (if you made one).
Code:
./adb restore backup.ab
You need to confirm that command on the Nexus 4.
As you are now finished you can of course disconnect your Nexus 4 from your computer.
You should be finished now. Unless I remembered something wrongly when writing this because I mostly wrote this from memory, after rooting my Nexus 4. If something doesn't work as I claim then please tell me and I'll fix it (possibly eventually).
I myself followed those instructions http://forum.xda-developers.com/showthread.php?t=2018179 as far as possible and then googled what didn't work or just tried around for a bit.
Edit: As of now (18.8.14), those instructions should still work.

[Root Guide] INSTALL ROOT / WITHOUT RECOVERY / ADB-FASTBOOT / MAGISK

Hello, first of all I apologize for my English if you don't understand me somewhere, I'm learning English. Greetings from Peru.
Files and programs you need to download​THIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
In the computer​1- Lenovo Rescue and Smart Assistant, will help you in 2 things: In case your device is frozen or in a loop, there you can recover it and right there you can find and download the ROM of your device for free.
As you can see in this image my device is already selected and the ROM is already downloaded (just follow the steps and your device will be fine again)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here you will find the ROM
as you can see, location, folder and files of the ROM (it is necessary that you know where it is since you will need some files later)
2-You need to have ADB/FASTBOOT installed to be able to install the ROOT (remember that this is the safe way, there is no risk of your device freezing or in a loop, but everything is possible).
Link : https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
on device​1- First of all, you have to have the bootloader unlocked, here I leave the guide since it is somewhat long to read
Link : https://www.mobilewithdrivers.com/download/unlock-bootloader/lenovo-tab-m10-fhd-plus-tb-x606f
2- After unlocking the bootloader, you have to have Magisk.apk installed on your device
Link : https://github.com/topjohnwu/Magisk/releases
3- After installing Magisk, on the main screen you have to see if Ramdisk is "yes" or "no".
It says "si" because my native language is Spanish.
4- Go back to the computer and in the ROM folder you have to find the file "boot.img" and copy it to your device
5- within Magisk where it says "install", they give it to install and something similar to this will come out:
6- They only give the following next "siguiente " and select the option of Select file "seleccionar y parchar un archivo" (I repeat again ignore if it comes out in Spanish, you in English)
7- from there the explorer will open and they will look for where they copied the "boot.img" and select it.
Once the selector is given to start or let's start "comencemos"
the process has to be something similar to the image that I will post below, you can several certain lines but at the end it has to say "done!" without any error.
8- Now to finish the process on your device, copy the file that appears in your magisk "the patched file". Copy and paste it into the ADB/FASTBOOT folder
we return to the computer​
1- First of all, you have to enable "usb debugging" on your device
Link : https://www.embarcadero.com/starthe...bling_usb_debugging_on_an_android_device.html
2- Now go to your ADB/FASTBOOT folder and in a blank part open "powershell",
Now go to your ADB/FASTBOOT folder and in a blank part open "powershell" .
Holding SHIFT and right clicking open POWERSHELL
now they write "cmd" without quotes so that inside PowerShell you can use it as cmd
3- Here I will explain it in a long but correct way without errors, do not turn off the computer and leave it on since you will write an ADB command to order the device to enter Fastboot mode.
By typing "adb devices" you will find out if the drivers are correctly installed and your computer, cmd and adb/fastboot should recognize it.
now type "adb reboot-bootloader" , this will command your device to reboot into "bootloader" mode
Now this part is important that you pay attention as some people make mistakes.
Once your device has rebooted and you get to the "fastboot mode" screen, you will type the following in powershell :
fastboot devices
If the following appears, it is because your computer detects your device in fastboot mode.
Now comes almost the end of this guide, to install root do the following.
To root your device they usually tell you to type the following "fastboot flash boot boot.img", but sometimes there are errors.
what you will do is the following :
once you have written the following
you are going to drag the "magisk patches" file to the poweshell
and you will have to leave the path where the saved file is (this is a safe way so that you do not get errors)
now you just hit "enter" and it will be installed on your device
Now to finish, restart the device, install "root checker" and you will realize that you have it activated.
attached image of my device "Tab M10 FHD 2nd TB-x606x" with the latest ROM installed, having ROOT, MAGISK and modules installed
THIS PROCESS WORKS WITH ALMOST ALL DEVICES, ONLY IF THEY HAVE THE BOOTLOADER CORRECTLY UNLOCKED WITHOUT THE NEED OF A TWRP.
If the guide helped you, please comment, if it didn't work for you, please comment as I will try to help you solve the problem.
Currently I will not be contributing more to the community since I do not have my own computer, the computer I use will only be there for a few days, after that they will take it away.
when I have a new computer, I will be sharing RecoveryTWRP for some devices modified by me or some other help that I am able to carry out and finish as a project.
I thank XDA for creating this space to help, guide and for everyone to learn in the process.
I send you greetings from Peru.
Nice, thank you very much, sir.

Categories

Resources