NABI LAB GUI
{
"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"
}
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
I abandon this project a long time ago, as the NabiLab command line program was working with very few issues besides getting the drivers working. That program was entirely for the Nabi 2 product. As I worked on rooting the Nabi XD and compiling TWRP for it, I took a condensed version of NabiLab and made it into NabiRootXD program. I never owned the Nabi JR 4GB model(Tegra2) and never bothered creating an auto installer for it, or for TWRP for that matter. Recently I came on to the new Nabi JR 16GB(Tegra3) after rooting and creating TWRP for it I wondered if I should re-use the tried and true NabiLab. That's when I remembered my initial attempts at a VB .NET app for the Nabi2. It seemed like with 4 different Nabi projects out there it might be in at least my best interest to maintain them all in one program.
Overview
The goal was to provide a program for the current crop of Fuhu Nabi devices. It should have similar function to the stable working NabiLab commandline program but expand support to the other Nabi products. I also want the user to be able to see and or edit the commands being sent to the device without having to compile the windows app, so this program sets out to simply start the similar batch files that original NabiLab used. At this point all functionality of NabiLab isn't restored to this newer program, so in some respects NabiLab original is still a superior program. In the NabiLabGUI's corner it has the latest TWRP (2.6.0.0 as of this writing), and some common adb/fastboot commands at your finger tips. At this point we can call this ALPHA testing. Despite the NabiLab commandline roots here it is bound to have some bugs. I will put it here, and down below: using the unlock bootloader feature in NabiJR 16GB will wipe your data
You Tube video description :http://www.youtube.com/watch?v=_h7ZiWp2B7Q
-Devices
Nabi 2 (NV-7A)
Nabi JR 4GB (NV-5A)
Nabi XD (NV-10A)
Nabi JR 16GB (NV-5B)
-Functions
Install TWRP 2.6.0.0
Install stock recovery
Install root
Install Gapps(Google Play, Play Store, etc)
Perform initial backup of device
For NabiJR 16GB: unlock/lock the bootloader
Send simple/common ADB and fastboot commands
Auto updating via Microsoft ClickOnce
Installation in the start menu as NabiLab
Removal via control panel
-What it doesn't do that NabiLab original did...yet
Auto restore a device back to stock
Edit lockscreen image
Display devices stats
Prerequisites
.NET framework 3.5 (Sorry)
The program has to be initially installed in Internet Explorer(double sorry)
ADB/Fastboot drivers installed. PDAnet drivers have had the most sucess. Use the tools menu on the right side to check and see if you can control Nabi with ADB and Fastboot before starting the scripts.
Device updated to it's latest firmware. While older firmware may work it is best to be on the latest.
Download
NabiLabGUI installer You have to launch this link in Internet Explorer, there is an extension for google chrome called ClickOnce but I have had little luck getting it to work. Here is the copy and paste link if you are currently in a different browser.
Code:
http://home.comcast.net/~aicjofs/NabiLabGUI/publish.htm
Since I am just hosting this on Comcast, they don't serve the proper MIME types, you may have to toggle the "compatibility mode" button in IE. If the bar is blue on the web page it likely wont work, if it's orange it will. If you are seeing xml after clicking install you need to toggle compatibility. See the video for an example.
Usage
Main Menu
Have device on, and powered up to TWRP or Android. Launch program from start menu.
The program has tool tip enabled which you can hover the mouse over to get general information. In this screen you can issue the ADB/Fastboot commands by selecting the radio button and pressing button. The CMD prompt button will open a command window where you can issue commands within the $PATH, fastboot, and adb. On the left side you select the device you have plugged in to issue device specific auto scripts.
Deivce Menu
Root, Recovery, Gapps, Backup - This option is best used if you have a brand new Nabi. A new window will open. Follow directions, start by pressing the etner key, and don't hit enter button rapidly, be patient. Most sticking points are pressing the volume keys on the device, in the correct order and quickly enough. After its complete you should have TWRP recovery installed, a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Gapps only - Installs Gapps only. You must first have TWRP installed.
Root only - Installs root/superuser. You must have TWRP installed.
Install TWRP x.x.x.x - Install TWRP and nothing else
Install stock recovery - Install stock for OTA, or selling, etc
Bootloader unlock(only on NabiJR 16GB) - UNLOCKING WILL DESTROY YOUR DATA. IT WILL WIPE IT CLEAN. WARNING!! WARNING Now that is out of the way....Before you do anything on the NabiJR 16GB you will have to unlock the bootloader. During the script you will need to OK the unlock on the Nabi itself. You have to be quick, the timeout is 3 to 5 seconds maybe. You will get a prompt when its unlocked. Did I mention...IT WIPES YOUR DATA!
Example of Script Window
You need to have the blinking cursor in the small white bar at bottom. The window opens this way but if you leave focus and comeback you can have the cursor in the upper grey area, and press any key won't work
Other & Links
Install location XP C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx or Vista/7/8 C:\Users\username\appdata\local\apps\2.0\xxx\xxx\
Nabi JR 4GB TWRP
Nabi XD TWRP
Nabi 2 TWRP
NabiLab commandline version
Main Nabi2 thread
aicjofs said:
NABI LAB GUI
I abandon this project a long time ago, as the NabiLab command line program was working with very few issues besides getting the drivers working. That program was entirely for the Nabi 2 product. As I worked on rooting the Nabi XD and compiling TWRP for it, I took a condensed version of NabiLab and made it into NabiRootXD program. I never owned the Nabi JR 4GB model(Tegra2) and never bothered creating an auto installer for it, or for TWRP for that matter. Recently I came on to the new Nabi JR 16GB(Tegra3) after rooting and creating TWRP for it I wondered if I should re-use the tried and true NabiLab. That's when I remembered my initial attempts at a VB .NET app for the Nabi2. It seemed like with 4 different Nabi projects out there it might be in at least my best interest to maintain them all in one program.
Overview
The goal was to provide a program for the current crop of Fuhu Nabi devices. It should have similar function to the stable working NabiLab commandline program but expand support to the other Nabi products. I also want the user to be able to see and or edit the commands being sent to the device without having to compile the windows app, so this program sets out to simply start the similar batch files that original NabiLab used. At this point all functionality of NabiLab isn't restored to this newer program, so in some respects NabiLab original is still a superior program. In the NabiLabGUI's corner it has the latest TWRP (2.6.0.0 as of this writing), and some common adb/fastboot commands at your finger tips. At this point we can call this ALPHA testing. Despite the NabiLab commandline roots here it is bound to have some bugs. I will put it here, and down below: using the unlock bootloader feature in NabiJR 16GB will wipe your data
-Devices
Nabi 2 (NV-7A)
Nabi JR 4GB (NV-5A)
Nabi XD (NV-10A)
Nabi JR 16GB (NV-5B)
-Functions
Install TWRP 2.6.0.0
Install stock recovery
Install root
Install Gapps(Google Play, Play Store, etc)
Perform initial backup of device
For NabiJR 16GB: unlock/lock the bootloader
Send simple/common ADB and fastboot commands
Auto updating via Microsoft ClickOnce
Installation in the start menu as NabiLab
Removal via control panel
-What it doesn't do that NabiLab original did...yet
Auto restore a device back to stock
Edit lockscreen image
Display devices stats
Prerequisites
.NET framework 3.5 (Sorry)
The program has to be initially installed in Internet Explorer(double sorry)
ADB/Fastboot drivers installed
Device updated to it's latest firmware. While older firmware may work it is best to be on the latest.
Download
NabiLabGUI installer You have to launch this link in Internet Explorer, there is an extension for google chrome called ClickOnce but I have had little luck getting it to work.
Usage
Main Menu
Have device on, and powered up to TWRP or Android. Launch program from start menu.
The program has tool tip enabled which you can hover the mouse over to get general information. In this screen you can issue the ADB/Fastboot commands by selecting the radio button and pressing button. The CMD prompt button will open a command window where you can issue commands within the $PATH, fastboot, and adb. On the left side you select the device you have plugged in to issue device specific auto scripts.
Deivce Menu
Root, Recovery, Gapps, Backup - This option is best used if you have a brand new Nabi. A new window will open. Follow directions, start by pressing the etner key, and don't hit enter button rapidly, be patient. Most sticking points are pressing the volume keys on the device, in the correct order and quickly enough. After its complete you should have TWRP recovery installed, a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Gapps only - Installs Gapps only. You must first have TWRP installed.
Root only - Installs root/superuser. You must have TWRP installed.
Install TWRP x.x.x.x - Install TWRP and nothing else
Install stock recovery - Install stock for OTA, or selling, etc
Bootloader unlock(only on NabiJR 16GB) - UNLOCKING WILL DESTROY YOUR DATA. IT WILL WIPE IT CLEAN. WARNING!! WARNING Now that is out of the way....Before you do anything on the NabiJR 16GB you will have to unlock the bootloader. During the script you will need to OK the unlock on the Nabi itself. You have to be quick, the timeout is 3 to 5 seconds maybe. You will get a prompt when its unlocked. Did I mention...IT WIPES YOUR DATA!
Example of Script Window
You need to have the blinking cursor in the small white bar at bottom. The window opens this way but if you leave focus and comeback you can have the cursor in the upper grey area, and press any key won't work
Other & Links
Install location XP C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx or Vista/7/8 C:\Users\username\appdata\local\apps\2.0\xxx\xxx\
Nabi JR 4GB TWRP
Nabi XD TWRP
Nabi 2 TWRP
NabiLab commandline version
Main Nabi2 thread
Click to expand...
Click to collapse
going to give this a whirl on my daughters now
:good:
So no way to root and install gapps on the 16gb nabiJR without unlocking the bootloader and installing the custom recovery?
Sent from my Xperia Tablet Z
Spectre51 said:
So no way to root and install gapps on the 16gb nabiJR without unlocking the bootloader and installing the custom recovery?
Sent from my Xperia Tablet Z
Click to expand...
Click to collapse
I have not tried it, but in theory you could use motochooper root method. Then manually transfer su, superuser.apk, set permissions, then install gapps manually. No need to unlock bootloader, of course without doing it you have no recovery to fall back upon.
Just used this on both my Nabi Jr 4GB and Nabi2, worked wonderfully! A couple bugs that cause software crash, but nothing that restarting it back up didn't hurt. I think the scripting for the all-at-once Recovery/Backup/Root/GApps needs some work, as they both got hung up for me on each one...so I just did each step individually.
Also, I downloaded it using Chrome and installed it from that way as well, and it worked just fine...and I didn't have to use any extension
Thank you very much!!!
I'm looking to do my nephews nabo but I don't know what nabi it is. The model number on the back is Nabi-A. If anyone could enlighten me that would be great. I just don't want the kid mode on there. He doesn't use it anymore so my mom is going to use the Nabi so I would like to get as close to a normal android tablet as possible (custom Rom, Google play store, etc) Thanks ahead of time for any help.
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
I'm looking to do my nephews nabo but I don't know what nabi it is. The model number on the back is Nabi-A. If anyone could enlighten me that would be great. I just don't want the kid mode on there. He doesn't use it anymore so my mom is going to use the Nabi so I would like to get as close to a normal android tablet as possible (custom Rom, Google play store, etc) Thanks ahead of time for any help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Nabi-A is the original Nabi, this program doesn't support it. I haven't followed much about that tablet. It is rootable, you could at least remove some of the kids programs. I doubt there is a custom ROM.
I have nabi Jr 16 gb, to install twrp then need to unlock boatloader. If I do that then I Will lose that, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
ipskang said:
I have nabi Jr 16 gb, to install twrp then I need to unlock boatloader. If I do that then I Will lose data, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire using Tapatalk
ipskang said:
I have nabi Jr 16 gb, to install twrp then need to unlock boatloader. If I do that then I Will lose that, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
You just loose everything on internal SD(data/media), and all saved settings, games, etc. Everything you put on the device. After a reboot the device will put all your apps back from the backup on the addon partition. Basically it is a factory reset.
In your first post, its mentioned that gapps cannot be installed on 2.1.27 but I have product version 1 of Nabi Jr 16gb nick edition . Can I install gapps ? How do i check system memory?
Sent from my Amazon Kindle Fire using Tapatalk
I used the nabilab tool and did the all in one step. Everything went through.but the touch feature in TWRP is not working. I found another version that says it fixes this problem but don't know how to flash it with TWRP not working. Can anyone help?
marcran75 said:
I used the nabilab tool and did the all in one step. Everything went through.but the touch feature in TWRP is not working. I found another version that says it fixes this problem but don't know how to flash it with TWRP not working. Can anyone help?
Click to expand...
Click to collapse
not sure what nabi you have here--
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
I use for all my nabis- POST 1
Test method 2 for temp install
I put the Recovery I want to install in the same folder the adb files are in.
once you figured out that its the recovery you want use method 3 to make it stick.
HTH
Stock ROm 1.03
Can anyone send me a stock rom 1.03 please, I desperately need it.
DeathMetalSquad8790 said:
Can anyone send me a stock rom 1.03 please, I desperately need it.
Click to expand...
Click to collapse
what problems are you having updating?
mjw2k11 said:
what problems are you having updating?
Click to expand...
Click to collapse
Well i got TWRP flashed however accidentally wiped rom without backup. So i have a flashed recovery with no Android OS to boot into. I just need the stock rom so i can flash it back and boot into Android, then im gonna finish rooting.
DeathMetalSquad8790 said:
Well i got TWRP flashed however accidentally wiped rom without backup. So i have a flashed recovery with no Android OS to boot into. I just need the stock rom so i can flash it back and boot into Android, then im gonna finish rooting.
Click to expand...
Click to collapse
best thing to do is follow the tutorials on here, use the nabi lab full, it contains stock rom, should be easy enough,and then just use OTA until you get to JB, most files are available here - http://forum.xda-developers.com/wiki/Fuhu_nabi_2let us know where you get stuck!
mjw2k11 said:
best thing to do is follow the tutorials on here, use the nabi lab full, it contains stock rom, should be easy enough,and then just use OTA until you get to JB, most files are available here - http://forum.xda-developers.com/wiki/Fuhu_nabi_2let us know where you get stuck!
Click to expand...
Click to collapse
Just a note that at this time of post the wiki link only has NAbi 2 content
DeathMetalSquad8790 said:
Can anyone send me a stock rom 1.03 please, I desperately need it.
Click to expand...
Click to collapse
I can't remember all the numbers which is that for the Nabi JR 4GB? JR 16GB? Something else?
I'm having the following issue when using NabiLab to back up
# Pushing gapps and root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
any help?
have you got the nabi installed and connected correctly? what are using to push gapps and root? if your on JB now (Nabi 2.3) then the filing structure is different and nabi lab wont work
Irish Cream said:
I'm having the following issue when using NabiLab to back up
# Pushing gapps and root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
any help?
Click to expand...
Click to collapse
Related
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"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"
}
TWRP recovery for the Nabi JR. (NABIJR-NV5A)
{
"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"
}
At this point this recovery is still considered in testing. The normal disclaimers apply. 2 forum members have tested as working. After flashing to recovery partition sometimes the device would hang and need power button reset and then device works normally.
This is for Nabi JR 4GB
Nabi2 is HERE
NabiXD is HERE
NabiJR 16GB is HERE
Updates
Auto Installer for 2.6.0.0 in NabiLabGUI http://forum.xda-developers.com/showthread.php?p=44258583#post44258583
Initial
-Latest TWRP 2.4.4.0
For more information on TWRP and change log see the TeamWin Website
Download
There are 2 downloads provided. The first is an installer for those less comfortable with the command line, it can install TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second are for people that just want TWRP 2.4.4.0 and can do a manual install.
Auto Installer
Recovery Installer for Nabi(Recovery installer for TWRP 2.4.4.0 and STOCK recovery) Use install method 1
Current recovery.img
TWRP 2.4.4.0 for Nabi(Only TWRP 2.4.4.0, manual install) Use install method 2 or 3
Installation
Start with Nabi booted to android, ADB debugging enabled, windows adb and fastboot drivers installed. (PDAnet drivers are popular)
-Method 1 (Recommended install , guided installer)
-Download "Recovery Installer for Nabi" from above
-Extract TWRPupdaterjr.zip
-Run RecoveryUpdater.bat
Code:
Select option 1 for a Nabi on v1.0.3 and follow directions
Select option 2 to return your Nabi to stock recovery after restoring stock ROM
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 2.4.4.0 for Nabi"
-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 2.4.4.0 for Nabi"
-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_junior
TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/
Credits
TeamWin team for TWRP.
Dees_Troy for build tutorials.
Eric Karz and his hours of testing.
just think, now you don't have to do a factory reset any time you have a problem with JR. thank you aicjofs for contributing such useful items to help make the nabi family experience so much better .
TWRP 2.5.0.0 for NabiJR
What's new in TWRP 2.5.0.0
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
Nabi specific: Theme change required for 2.5.0.0
Download
This is awesome, thank you so much for this.
Just flashed gapps using this recovery on the Nabi Jr with ICS. Fantastic. Thank you. Now it's not a useless POS anymore.
are there any stock roms or anything i can do if i wiped the original rom that comes from the factory
juanfernandez77 said:
are there any stock roms or anything i can do if i wiped the original rom that comes from the factory
Click to expand...
Click to collapse
I replied to you in the Root for Nabijr thread. I don't have a NabiJr or I would. I know Eric should have a backup, someone needs to make a stock system image.
I've been attempting to flash the recovery, but my Nabi Jr keeps getting stuck on a screen that says, "Checking for RCK.. press key <volume up> in 1 sec to enter RCK" It has options to continue, reboot-bootloader, reboot, or power off. I have tried manually installing using the adb command lines and I've tried the automatic installer. Both get stuck on this screen. Any idea what's going on?
Anybody able to help?
is it the 4 or 16 GB tablet ?
My kid broke the 4GB Tegra 2 ICS Nabi Jr, and I got the 16GB Tegra 3 JB Nabi Jr as a replacement.
Any idea if it will work on that model?
Edit: I can't even test because this Nabi variant shows this screen after reboot-bootloader: http://i.imgur.com/I1rRMgI.jpg, and fastboot is saying waiting for device. Not sure how to proceed.
aicjofs would be able to say better
but I wouldn't use the the one built for 4 gig on the 16 gig version
4 gig is ics and 16 is jelly bean - using it could result in a foobard tablet
Send aicjofs a PM and see if he has time to look in to a recovery for 16 gig version of the nabi jr
Archon810 said:
My kid broke the 4GB Tegra 2 ICS Nabi Jr, and I got the 16GB Tegra 3 JB Nabi Jr as a replacement.
Any idea if it will work on that model?
Edit: I can't even test because this Nabi variant shows this screen after reboot-bootloader: http://i.imgur.com/I1rRMgI.jpg, and fastboot is saying waiting for device. Not sure how to proceed.
Click to expand...
Click to collapse
No way this particular recovery will work. It is Tegra2 based, and the new tablet is Tegra3 based. If anything you could try the Nabi2, or NabiXD recovery they are at least Tegra3, although if it works at all the screen will be completely off because of resolution differences. Be aware that you could damage using those recoveries, although I don't think it will and it just wont boot....anyway... for whatever that is worth... I'm just telling you. Based on what Fuhu did for XD(jelly bean) I'm not sure the Bin4ry root script will work. You can read about that adventure here http://forum.xda-developers.com/showthread.php?t=2207499
As for the fastboot thing. Make sure it is showing the fastboot/bootloader driver in device manager, the menu is definitely different what is that saying above the menu?
I did try Bin4ry, but I don't think it worked. There was an odd message in the process, and even though the script said it was done, I am not sure it was.
As for the custom recovery, I'm willing to work with you or whoever is interested, to test and get it working for the new Jr. For starters, it'd be great to know how to dump the current recovery. The next step is to figure out why I can't fastboot, and then try other recoveries from XD or custom if someone is testing with me.
The bootloader message says something about RCK - not sure what it means.
Archon810 said:
I did try Bin4ry, but I don't think it worked. There was an odd message in the process, and even though the script said it was done, I am not sure it was.
As for the custom recovery, I'm willing to work with you or whoever is interested, to test and get it working for the new Jr. For starters, it'd be great to know how to dump the current recovery. The next step is to figure out why I can't fastboot, and then try other recoveries from XD or custom if someone is testing with me.
The bootloader message says something about RCK - not sure what it means.
Click to expand...
Click to collapse
What did script say something about "cannot mount are you root"?
I'm not sure why fastboot isn't there. Do you get a different menu if you manually boot with Power and vol+ key. Maybe this new bootloader wants a key input within a few seconds of boot to enter recovery or fastboot?
I'm guessing RCK is recovery kernel.
One way or another you need to get fastboot, as you said, to try a custom recovery. So it's best to concentrate on that.
I don't remember what the script said, but it wasn't that. In fact, it could have worked for all I know, because it thought it did, but there was a "not found" message halfway through the process about something. I can repeat if this is needed.
This is the menu that comes up with adb reboot-bootloader, or by holding Vol-Up and Power. Same menu.
Do you want to connect on gTalk to try to debug this further?
Archon810 said:
I don't remember what the script said, but it wasn't that. In fact, it could have worked for all I know, because it thought it did, but there was a "not found" message halfway through the process about something. I can repeat if this is needed.
This is the menu that comes up with adb reboot-bootloader, or by holding Vol-Up and Power. Same menu.
Do you want to connect on gTalk to try to debug this further?
Click to expand...
Click to collapse
I'm mobile right now. Watching my kiddoz playing at park. I can try Gtalk later today.
So I'm looking at the image and 2 things come to mind. The USB icon
1) it's in fastboot now which is why icon is there. Open device manager as you have it plugged in and then power it up and see if there is any activity. Yellow exclamation, bootloader/fastboot driver showing up. Anything to show there is life on tablet side
2) can you use the volume keys to go down and "select" the USB icon. Or is it a touch icon, doesn't look like it but worth a shot.
OK, I'll pm you my gTalk.
The USB icon is not selectable. It just cycles back to Continue after Poweroff.
This shows up in the device manager when it's hooked up, including when it's in this bootloader mode: http://i.imgur.com/SVMzw8v.png. The Unknown Device isn't related as it's there when the Nabi Jr is unplugged too - I think it's a fingerprint reader, I'm not even sure what it is.
Archon810 said:
OK, I'll pm you my gTalk.
The USB icon is not selectable. It just cycles back to Continue after Poweroff.
This shows up in the device manager when it's hooked up, including when it's in this bootloader mode: http://i.imgur.com/SVMzw8v.png. The Unknown Device isn't related as it's there when the Nabi Jr is unplugged too - I think it's a fingerprint reader, I'm not even sure what it is.
Click to expand...
Click to collapse
Strange that its showing the ADB interface, instead of bootloader one in that task manager screenshot. I'm not thinking of many avenues here less some button pressing sequence we don't know. I tried a quick google search the other day and didn't come up with anything enlightening. You don't actually need fastboot/TWRP to root it but it would make it easier, plus I almost consider it a necessity for the backup purpose alone. It might be wise to post this is a general section and see if anyone else has seen a similar bootloader screen.
Ok here is the story on the 16GB Nabijr.
Fastboot commands need to be issued with "fastboot -i 0x0489"
The bootloader is locked on this Nabi. There is good news and bad news. Good news it can be unlocked. The bad news is that it wipes the Nabi to do so.
I was able to gain temp root in adb with motochopper. With this I was able to dd the recovery partition and extract the kernel. I was only interested in temp root, so I don't know if the program can be used as is for permanent root, or if you need to copy su and superuser.apk yourself. You can root with TWRP anyway. With this I was able to build a TWRP for the 16GB junior. Unfortunately the touch screen was very buggy. Hard to get presses to take and especially to swipe. I'm not sure if its just mine or they are all like this. This devices looks quickly thrown together. It's version 1.0, not 1.0.2, or 1.2.3, just 1.0, the build.prop looks like they never even touched it. Maybe it can be fixed with software update(touchscreen firmware update), no kernel source so that route won't work, maybe I don't have the module bound right in TWRP. I'm not sure the recovery is entirely usable with this bad of touch response but let's see what other devices are like.
If you wish to use TWRP for Nabi Jr 16GB this would be the instructions. USE AT OWN RISK!
1) Enter fastboot mode
With the Nabi powered off press and hold power and volume down.
2) Unlock the bootloader. This will erase everything on the device.
Code:
fastboot -i 0x0489 oem unlock
after issuing the above look at the Nabi screen and use volume keys to OK the unlock.
3) Enter fastboot mode (as described above)
4) Test and/or flash TWRP to your device.
Extract the TWRP download and place recovery.img in the same folder as your fastboot.exe
Run the command to test out TWRP
Code:
fastboot -i 0x0489 boot recovery.img
or this command to make it permanent
Code:
fastboot -i 0x0489 flash recovery recovery.img
5) To boot TWRP from power off. Press and hold power and vol up(different then fastboot and vol down)
6) MAKE A BACKUP! If it's like mine the swiping will be hard to start the backup, but just do it. The Nabijr should be in an unmolested(unrooted) condition with your personal info erased if you followed this. I can guarantee one of your fellow Nabi JR owners will at some point needs this so help them and help yourself. Now put a copy of that backup on your computer.
7) When TWRP exits it will ask if you want to root the device. It is hard to swipe on mine, but you can do this instead of the motochopper. We had some trouble with the Gapps for 4.1.2 on XD, will be interesting to see if it works here.
TWRP 2.6 for Nabi JR 16GB
To get your recovery back to stock if you flash TWRP:
Stock Recovery for Nabi JR 16GB
device tree source: https://github.com/aicjofs/android_device_fuhu_juniorb
TWRP source: https://github.com/TeamWin/Team-Win-Recovery-Project/
If it works for everyone I will try and build an auto installer type script at some point, but no promises, I barely had free time to figure this out.
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
This will also work for the PLT1065G but you need to use different recovery/parameters. The kernel is different (looks like a different touchscreen).
Thanks for this. Got one for $50 at Loblaws today. Will attempt rooting.
Got it for my 6 yr old
Edit: Fixed boot issue
protectivedad said:
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
Click to expand...
Click to collapse
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Friko said:
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Click to expand...
Click to collapse
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
protectivedad said:
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
Click to expand...
Click to collapse
I've been fiddling with it and it seems to be completely random. So I guess it's something we'll have to live with.
I bought it for my 6 year old who's dying to play Pokemon Go. The app runs okay on it. It's just the 'GPS' (or lack of a proper GPS chip) that's a bit slow/inaccurate
Hello I to bought this tablet in Canada I successfully rooted it but is there a reason why no other cameras can be downloaded or Music players or Instagram.
Is thee any chance to unbrick this tablet?
I have one stuck in the boot logo, hard reset wont solve, is there any flash file?
Hellooooo !!
anybody here ?
---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------
ANYONE TEIED THIS FIRMWARE?
https://mega.nz/#!TVFX0CiZ!6CaGOSGZM47PQAd9KZDuKcPJaXsCL3n3JJQBtXPRHJo
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
yurais said:
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
Click to expand...
Click to collapse
There is a way to create an SDCARD and it will run from the SDCARD. I've forgotten how . I'm looking at one of my kids cracked ones right now. The touchscreen is cracked so I'm looking at build Ubuntu for it. I'll post when I figure out the SDCARD again.
Reset tablet to factory
I was able to use the factory irmware to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Let me know here as soon as you just remember anything related to this.
I got another tab like this, screen cracked and I could read off its firmware, so I now have a working firmware waiting to be written...
Enviado desde mi SM-N920T mediante Tapatalk
Thanks so much for this guide. I picked one of these up for $6 when HHGREGG was closing.
Proscan PLT7650G
Good day is there a guide and firmware for a Proscan PLT7650G
Technician
protectivedad said:
I was able to use the factory irmware[/URL] to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Click to expand...
Click to collapse
How did you flash the image? what software did you use,
Thanks.
it's not possible to change the rom or custom image of the tablet to another operating system like ubuntu or linux. It has allow OEM bootloader unlocked in the settings in developer section greyed out and it doesn't allow oem bootloader unlocking 'enabled'. You cannot enable it.
What you are doing is just resetting the factory image. or rom. you can just push the reset button with pin after charging the tablet for 3 hours.
These tablets are not 'cheap' to make and google, cell phone companies subsidize these 'cheap' tablets. so you have to use and pay them when you subscribe to their cell phone 'service' or google advertisements when you use their 'service'.
Lots of vaporware being pushed saying they can unlock something for $40 or downloading tools etc. wasted of time as it's impossible to unlock oem BOOTLOADER if the manufacture has locked it, you cannot install another operating system in the tablet, or smart phone. so don't waste your time.
Only some phones allow oem unlocking bootloader and those are the higher end phones costing $400-$600 for a tablet that are not 'subsidized' by google or you cell phone company as with 'cheap' phone or tablet.
the firmware is not available for download at the manufacture website that should raise alarms about the firmware. I've factory reset the device and now it's having reboot issues, either the firmware is defective or corrupt bootloader etc. The manufacture proscan seems to be selling the devices yet no technical support or even a direct download from the manufacture, downloading firmware from thirdparty servers is security risk. it seems like today lots bogus websites and no technical support from manufacturers in tech devices they sell. and people have to sites like XDA for 'free' technical support. Even Microsoft which makes billions in profits fail to provide proper technical support for some reason. and have to rely on 'free' technical support for bugs and issues with their software and hardware and lots vaporware apps etc.. bogus apps. that don't work.
Rooting gives the user the ability to install and change OEM software. from what i gather so don't waste your time, to root a device, allows the user to delete operating system files. if the manufacture doesn't allow changing the oem software there is nothing you can do. about so don't waste time trying root it or try to install ubuntu or linux on the tablet or smartphone if it's oem LOCKED. bootloader. you cannot unlock it. it's much harder to unlock oem software.
the method to 'restore' factory image or known as 'flashing the rom'
there is no reason to flash the rom etc.
1. just hold the power button and esc button at the same time
2. release the power button wait 2 seconds
and then release the esc button
you should now be in boot up mode.
this unit doesn't allow you to be in bootloader mode. so you CANNOT install another firmware or install linux etc. other than the proscan firmware.
3. press esc to select restore the factory settings
4. press the power button to select
this the easiest way to restore stuck in browser or need to flash the rom
again if the rom is 'corrupt' which is not likely
if that is the case
the option to "apply update from external storage" doesn't seem to work as you cannot mount to flash the rom and reinstall the .img file from the .zip file
"apply update from external storage"
where you saved your .zip doesn't work
the apply updated from ADB works you need a usb computer hooked up to you computer and terminal command to ADB to your table to rinstall the .imge file
update ,this no longer seems to work in installing the .zip file method to install the firmware.
lot of software and hardware that have no technical support or documentation and the stuff just doesn't seem to work and high security risk with no updates from manufacture as it cost them money to resolve issues. selling disposable technology tablets. that is not meant to last. basically toys. for kids.
This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin
Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub
Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)
@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.
MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo
marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!
the firmware is
A83T_N106_N1061L6BC_20160309
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit
stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test
Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)
I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.
NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"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"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?
UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"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 have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks
@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks
Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks
Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.
How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.
adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"
Would love to see some break throughs with this device aswell. Cheers to any one working in it.
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk
Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it