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?
Related
First things first...
Credits:
Mast3rpyr0 - Original creator of a simple one click root. Most the code used here is based on his work with some tweeks. [ Link ]
webs05 - For the outstanding help he has provided to those who were having issues using Simple Root!!! Thanks!
toastcfh - For root and nand unlock. [ Link ]
Koush - Recovery image [ Link ]
maejrep - For helping with the code to remove sendkeys!! Thanks alot!!
If I forgot anyone that I should have mention, let me know....
{
"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"
}
Automatic updates and create update patches with wyBuild.
After hours of trying to figure out a way to make Mast3rpyr0's batch files work correctly, I noticed it had problems sending certain commands. So I decided to use some of his batch file codes, and create a VB.NET application along with batch files. I have unrooted and rooted my personal phone multiple times trying to get this to work. I tested the app 3times!! Each time Unrooting my phone! All three times its has been successful!
What exactly does this do?
Exactly what it say, Root your EVO in 3 Steps.
How do you use it?
Make sure your phone is on USB Debug mode. (MENU > Settings > Applications > Developement > USB debugging = Checked ) Click the buttons starting from Step 1.
Why the large file size?
This includes all the .img and .zip files that are needed to root. (2 PC36IMG.zip @ ~ 170MB = 340mb) and a couple of other smaller files. I decided to add them to make things more simple and avoid having to explain where to get these files.
Youtube Example
sorry for all the video splits...not my fault, blame youtube.
Video quality might be bad, give them a few to process 720p version
Part 1-1 - http://www.youtube.com/watch?v=GAqTEAWxh7U
Part 1-2 - http://www.youtube.com/watch?v=578jDEJ6M_c
Part 2-1 - http://www.youtube.com/watch?v=I-FbYqPOrpg
Part 2-2+3 - http://www.youtube.com/watch?v=qk7lBDpSp-A
AndroidPolice.com Review + Tips
Download:
Megaupload - had to put this up, account suspended due to the amount of downloads =( they want my to go dedicated smh...
Official Page | Full (Download this if you never used this program before)
If you have downloaded this program before, please read this
Note: Its recommended to flash a custom ROM. Reason I say this is because for whatever reason, the eng-image doesnt allow proper SU permission!!
Requires: Dot Net Framework 4 and HTC SYNC
I would try it if I didn't fully root yesterday. But props to you guys for putting that together. Seems like a one step jailbreak. Very nice.
WOW! Great work. This will unlock NAND too? If so you might want to update your thread title....
jiqqaman said:
First things first...
FOLLOW THE DIRECTIONS!! IF IT SAYS DONT MOVE YOUR MOUSE, DONT CLICK ANYTHING, DONT TOUCH YOUR KEYBOARD... THEN DONT!!!!
The reason for this is because for some reason a batch file cant send the command
Code:
adb shell cat sdcard/flash_image > /data/flash_image
The only way I found to get around that was using Sendkeys. I know, send keys is lame, and poor programming, but its the only way that I could get this to work.
Basically, Sendkeys sends keystokes to a targeted window, as if you were typing. You might see your keyboard NumLock, Caps light blink while this is being used, which is perfectly normal. (Enjoy the light show)
Click to expand...
Click to collapse
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
this is amazing. too bad noobs like myself could not wait to root and unlock nand. but the process was well worth it. great job, i hope this save someone a headache
Re: [Program] SimpleRoot .1 ---- 3 Click Root!!
smw6180 said:
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
Click to expand...
Click to collapse
Thanks, I'll see how that works later on, and if it works ill just upload a zip file with the updated code. Don't like the whole sendkeys thing,...I'd like to figure out on making it work without batch files... but I no pro code lol
Sent from my HTC EVO using Tapatalk
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
It wont hurt to re-root just run the whole thing. make sure you backup of course
thanks OP great work I'm sure it will get even better and easier once you get rid of key presses
STICKY!!!!
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Damn after I followed the 50 step-by-step and wish I had seen this earlier nice work might try this on my older bros in a few days
Sent from my Sprint HTC EVO 4G. via tapatalk
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
Yes, but you must run on the pushfiles.bat file before you goto step 2.
CYBERxNUKE said:
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N6GV5NNP - no .img or .zip files
make sure you have the first PC36IMG.zip from the first root tutorial and the 2nd PC36IMG.zip from the nand unlock rename it eng-PC36IMG.zip or else you'll break it =(
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
OP theres an updates restore image much better options from armon .02 works for people who have bad sectors ALLOT of us have
but 01 is for those who dont try that first
http://forum.xda-developers.com/showthread.php?t=705026
ken987 said:
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
Click to expand...
Click to collapse
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
great job on making this easy guys.... To bad I couldnt wait longer than a week to root.
jiqqaman said:
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
Click to expand...
Click to collapse
Thanks for the quick reply. No, I am a new EVO owner and this is my first android phone. I was an iPhone user but I have come over to the Android side. No regrets. I have basically a new EVO with the OTA update installed. So my goal would be to run your one click method and then learn how to load roms. I also read that people have some kind of rom loader on their phone that sounded pretty easy so I need to do more searching on the forums here so I can learn.
Ken
This would have saved me 3 hours....
Thanks dude though this seems awesome.
Videos are titled "Hero 4g" btw.
Part 1 worked for me but part 2 doesn't. When I click yes on part 2 I get a screen that says "Unhandled exceptin has occured" and it gives me a option to continue or quit and I click continue and it closes out.
Does this method work if I already have the .6 stock rom on my device?
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
DISCONTINUED - Left for research and archive purposes.
After much hardwork @codelover and I are pleased to release both stock rom as well as TWRP 2.8.6.0
for the 2 known variants v31 and v38. Please make sure you download and flash for your specific variant. Check faq if you do not know which variant you have.
REQUIRED FOR BOTH VARIANTS:
Windows XP/Vista/7/8/8.1/10TP 32bit or 64bit
SPFT (Windows Version) “linux version coming soon”
Correct Scatter File
Preloader Drivers (if you do not know how to install manually go here)
ADB
A Brain
Usage:
For flashing either pre-rooted Rom and/or TWRP you will need spft+scatter file. It is imperative that you make sure that if you got a v31 you only uses v31 files not v38. Same for the v38 users only use v38 files. You have been warned.
Click to expand...
Click to collapse
Flashing Rom:
Make sure
Run the file flash_tool.exe
Click on scatter-loading and select your MT8127_Android_scatter_RCA_Vx.txt file
Make sure all listed files are checked and if any isn't double click on it and select the appropriate file
Leave settings as Download Only “if working tab Format All + Download "if wont boot' then hit the Download button
Make sure your tablet is completely switched off then connect it to your PC and the flashing process will commence immediately.
Once it's done, you'll see the tick sign below and that's all. Reboot your device and setup your device afresh.
{
"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"
}
Flashing TWRP:
Same as above except only check mark recovery and select “recovery_twrp2860_vXX.img” and nothing else then proceed.
How to ROOT:
*With stock recovery: Kingo
*With TWRP: SuperSu
DOWNLOADS:
(V31.0 USERS ONLY)
Pre-Rooted Stock ROM (scatter file included in zip and attached below)
TWRP 2.8.6.0 (scatter file included in zip and attached below)
EDIT: TOUCH FOR v31 TWRP IS MISALIGNED FIX IN PROGRESS. LINK REMOVED UNTIL THEN
(V38-V1.8.0 USERS ONLY)
Pre-Rooted Stock ROM (scatter file included in zip and attached below) (Currently being fixed sorry for the issues)
TWRP 2.8.6.0 (scatter file included in zip and attached below) (Currently being fixed sorry for the issues)
NOTICE:
Please keep thread clean and DO NOT ask things others have asked already as you will be ignored. If you do have a honest question and have a working knowledge of android. I would be glad to assist you the best I can. If you are noob and messed something up DO NOT ask for help. Meaning basics of knowing adb,logcat, installing drivers, and so forth. Sorry if you are a noob but please try to understand that things we may ask of your will require this and becomes too much of a slow down if we have to guide you thur everything.
Click to expand...
Click to collapse
CREDITS:
http://twrp.me/ – @Dees_Troy & his team mates, for TWRP Recovery
@codelover - For being an awesome programmer, dev and person!
@TripFX - For being an awesome Tester, v38 rom dump and Dev Machine Hoster
@synius - For v31 rom dump and tester
@nathanski - Tester
@acejay3200 – Being a nice lab rat with knowing i may not be able to make a recovery for you or even brick your working device and not being rude..
Others I may have missed
Discontinued
Faq:
Question: How do I know which variant I have?
Ansere:
Method #1
From a booted android, goto Settings > About > Build number
You should see something like this.
RCT6773W22-ANDROID4.4.2-3101-V38-V1.8.0
Method #2 (Better & more accurate)
For this your device must be rooted & already have USB Debugging Mode enabled.
Make sure adb.exe has been installed on your system (computer).
Execute the following adb command:
Code:
adb shell
su
cat /proc/cmdline
then search for ‘lcm’ text in the output:
If lcm=cpt_clap070wp03xg_lvds < you need to use v31 files
If lcm=1-lxjc070whm270_18a_rgb < you need to use v38 files
Question: What if I dont remember which variant I have and can’t access adb?
Ansere: If this is the case we will need to use SP Flash Tool to help identify your variant.
Open SF Flash Tool, load V38 scatter and switch to ‘Read Back’ tab. Clear all then click Add,
Click the new item & change the output file name from ROM_0 to ROM.txt,
edit the readback address as below:
Start Address: 0x9000000 / Length: 0x1000
Then press “Read back” button, now connect the tab while powered off.
When it’s done, open the file with wordpad and check if you have “ANDROID” at the beginning of the file, if your answer is yes then you have V38, otherwise use V31.
'pleas take with a lol"
edited off bs bulk
Is anyone else having problems with DL link.
nathanski said:
but if you cant test and flash the wrong one re-flash other,,,
because if its not one its the other ....
Click to expand...
Click to collapse
read full faq
leetree2001 said:
Is anyone else having problems with DL link.
Click to expand...
Click to collapse
just test download links in on my pc all download fine Firefox 37.0.1 Win7 x64 all work
no touch in twrp volume keys do nothing power button shuts off tablet boot into android tablet works fine i am trying to make a backup so i dont have to flash everything again
edited off more bloat
i flashed twrp with its own scatter had no touch then with the 4.3 scatter that fixed my tablet now touch works but the buttons dont lineup
acejay3200 said:
i flashed twrp with its own scatter had no touch then with the 4.3 scatter that fixed my tablet now touch works but the buttons dont lineup
Click to expand...
Click to collapse
A correction to V31 in on its way
V38 has good reply on touch working well, small snag regarding to internal storage reported,,,
Well I got it downloaded, and it worked great for me, touch Worked great for me. I did a ful
I backup and all buttons seem to respond to touch. I used twrp easy magic's unpack, repack to install it, thanks you guys, and girl's for you're hard work.
gr8 t2o hear good results, thank you,,,
nathanski said:
Great to hear good results, what file are you reporting success with, if I may ask,,,
I stay on my tablet like most of my time when I'm not working or ect,ect when I stop using it as heavily I am going to install twrp I guess, just haven't made time as the tablet is basically my main device
Click to expand...
Click to collapse
Twrp 2.8.6 v38,the only problem I found is internal sdcard not showing up in file manager. But external sdcard does,
twrp. installer.exe http://forum.xda-developers.com/devdb/project/dl/?id=10082,, its a option
TripFX said:
Faq:
Question: How do I know which variant I have?
Method #2 (Better & more accurate)
For this your device must be rooted & already have USB Debugging Mode enabled.
Make sure adb.exe has been installed on your system (computer).
Execute the following adb command:
Code:
adb shell
su
cat /proc/cmdline
then search for ‘lcm’ text in the output:
If lcm=cpt_clap070wp03xg_lvds < you need to use v31 files
If lcm=1-lxjc070whm270_18a_rgb < you need to use v38 files
Click to expand...
Click to collapse
Note: Watch your tablet as you're doing this. You may have to grant su permissions on the tablet after executing the "su" command in adb.
I tryed using sp flash tool to flash but I couldn't get it to work is there another flash tool I could use thx
edited off bulk,
Edited.
nathanski said:
Yeah there is, in the link I have up showing time stamp 3:23
---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------
Did you have to copy the whole FAQ in a simple reply
Click to expand...
Click to collapse
Thx for the help it won't boot into recovery it comes on I just can't get into recovery
mike9976 said:
Thx for the help it won't boot into recovery it comes on I just can't get into recovery
Click to expand...
Click to collapse
I can't say as to why but you do need the self education one can learn about how to use spflash tool,, seeing as that's the way that I know that's the first info I could offer ,,, you should get your version information first, then download your ROM because the scatter file that had reports of best results are in the full firmware, and you then need to know that the reset button will bring up a driver install but it happens fast to catch this you need the device manager in windows open, plug the rct in then press reset with a tothpick or other small pin ect,, the device shows up with a sound chimes on windows, right click the new device in the USB group and install using the hosted driver,,, now to the spflash tool its self load the scatter in the full ROM related to the vershion you have and then only check recovery,,, and find the twrp.IMG in you downloads and use only the download option in the spflashtools,, and click download then Right after hit reset on the back of the tablet,,, it can be done ,,,, even for the new people wanting to learn,,, regarding the twrp,installer.exe I linked to, I have no knowledge it was only reported to be a full success by another user before you so I wanted to offer a fast way for others to find it ,, so I linked to the .exe,,, and lastly ON MY TABLET I HAVE TO BE ON A CHARGER TO LAUNCH RECOVERY AT BOOT USING VOLUME KEY,..and you can download a root reboot apk that will boot from inside android directly into recovery,, maybe I helped,,,, p.s. another great thing the full ROM offers is the original OEM recovery.. Pleas do try to learn. As always i do wish every one the best
---------- Post added at 02:45 AM ---------- Previous post was at 02:38 AM ----------
best regards to you @TigerG8
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
{
"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"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:
Probably a lot of stuff ...
What you need:
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:
Spoiler
Method 1, Micro-SDCard
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin
How to get TWRP log files:recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage
Changelogv2.00.1-alpha
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha
added drivers for himax touch screens.
v1.02.1-alpha
added drivers for novatek touch screens.
v1.01.2-alpha
added patch with improved multidisabler
v1.01.1-alpha
update multidisabler
v1.01.0-alpha
fix permission for mkbootimg
v1.00.0-alpha
Initial Release
This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.
Yes, it runs on my A22 5G.
Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?
Is the A226BZH3AUL1 suitable？
a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Thank you! Going to test asap.
lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?
koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.
Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?
The model of a22 5G available in my country does not have nfc.