Database Info

[HOW TO] Root Nextbook8 Premium (and install market app) [UPDATED 1-17-12]

PLEASE BE ADVISED: THE AUTHOR OF THIS POST NO LONGER PROVIDES SUPPORT FOR THIS THREAD. HOWEVER YOU ARE MORE THAN WELCOMED TO CONTINUE USING THE FILES AND METHODS AT YOUR OWN DISCRETION. GOOD LUCK!!
INTRO: For all those searching the internet trying to find answers as to how to gain root on your Nextbook8 Premium and also gain access to the wonderful android market from which we were greatly deprived (as is the case with many low-priced tablets these days), the wait is over thanks to a certain someone who goes by the name of DEVMONKEY. Of course I take absolutely NO CREDIT for this and only took the liberty to re-write it thus adding a little more detail to the process. Enjoy!!!
DISCLAIMER​***I HAVE NOT TESTED THIS PARTICULAR ROM WITH MY N8 WHEN I HAD IT BUT AS THE PROCEDURE TO FLASH IS STILL THE SAME ALL SHOULD GO WELL. HOWEVER, I AM NOT RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN IF YOU USE THIS AND DAMAGE YOUR DEVICE. PLEASE FOLLOW ALL STEPS CAREFULLY***​
[HOW TO] Root and install Market on your Nextbook8 Premium​
UPDATE: This is post has been updated with a new rom to replace old one. Method of flashing is still the same so no worries. All those who want to upgrade to this rom from the one I previously posted in this guide when I first wrote it can just repeat the steps over again with the new rom package.​
This rom is based on Samhain's release: SamDroid v1.13
Modifications (mostly GUI / cosmetic tweaks):
1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.
2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)
A couple of things to note once you have installed the rom:
- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.
- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.
- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.
- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).
- You can also grab Adobe Flash 11 from the market and it'll work correctly.
- This release boots MUCH faster, and is even more responsive than before.
- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.
VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.
​Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.
NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.
Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.
NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.
{
"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"
}
Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.
Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:
Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)

Thanks! worked great.

I signed up, so i can say thank you. this worked perfectly.. i was skeptical and scared i'd ruin this tablet, as i got it as a gift, and was obviously disappointed to see no market on it, but this worked. thank you.

How about Nextbook Premium 7?

Thank you!
This worked great, I was able to get the android market installed and working.

Android version?
What version of Android does this install?
Cheers, Greg.

It's work, your are wonderful,thank you Sunnyboy167

Great job! Good to have root and Market working. But anyone else get FC when opening Camera app?

Perfect! I have rooted many Android devices and this is one of the easiest ones. Just read the directions carefully and you'll do fine.
Hopefully someone will release an ICS update for this device soon..after using my Galaxy Nexus, Gingerbread seems so...obsolete.

I'm glad you enjoyed this info just as much as i did
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!

THANK YOU!!!!
I was about to throw this tablet out the window!!! Followed the instructions and it works perfectly!!!! Thanks SO SO much!!!

Thanks to you I had a very Merry Christmas haha thank button has been pushed repeatedly!

Hi Sunnyboy,
Just want to say a big thank you for the detail post. I was about to give up on on this tablet when I came across your post.
Chris

help help!!!
hi sunny boy,
i just got my nextbook8 yesterday... come across this website and trying to root my nextbook last night at home...
I encounter this problem...when i plug in my nextbook into the PC USB ..it turn on from the off mode. and the pc started to scan the driver and it actually install successfully. I am running on win7. after that i cant install the driver required.. can anyone help me out here cos i try to run exe. file. it cant root my nextbook... i am helpless now...

I am also having problem with the camera. I'll have this error:
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.

HELP HELP HELP...not able to on the device after updated the driver....PC shows device found after plug in USB, which shows the device is working but just cannot on it.. a total IT dummy and not sure what's going on..someone said the ROM is damaged which cause this.....any way to recover the tablet..i just bought it for less than a week. HELP HELP HELP!!!!!! (tried reset but still no response)

Sunnyboy167 said:
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
Click to expand...
Click to collapse
I have already been to this website and successfully added the market to my Next7. I do want to root it and flash a custom ROM, but I have not found anything useful. Thanks though.

Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??

eybarra2 said:
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
Click to expand...
Click to collapse
u can reboot the device by using a paperclip and press in the reset button.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Thanks for the detailed guide Sunnyboy167~ Anyway devmonkey just release a newer mod which works better than the previous. Do check it out

hi all,
I rooted my new nextbook8 ...and it works just nice...
just need some help on whether possible to use my iphone as a modem for my nextbook? as i realized it cant detect my wifi network from my iphone. While my colleague 's motorola zoom works fine with my iphone...any solution on this?
Caduser from singapore...

Fuhu Nabi2 Backup - Recovery - Root - Gapps on Ubuntu Linux

Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"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"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img

Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!

Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex

Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!

Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.

I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.

Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A

Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2

Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse

Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.

Glad it worked for you! I would love to see some JB action on here.

Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:

Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?

caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.

t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse

DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674

ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...

DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd

DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.

Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html

[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing

This is an update to the TWRP recovery for the Nabi 2.
​
{
"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. Have a good backup moved to your computer from the previous recovery.
Before starting this your Nabi should be updated to 1.9.37. 2 people that have 1.9.34 - (Madagascar Bundle) and 1.9.35 or 1.9.36 - (UK Versions) were having issues.
Please check your version in Settings-About Tablet-Product version, it needs to be 1.9.37 currently, other tablet versions besides 1.9.37 are experimental see below.
This is for Nabi 2
Nabi JR 4GB is HERE
NabiXD is HERE
Nabi JR 16GB is HERE
If you have Nick/Disney read up about different build for those.
Updates
Mar 15th 2015
TWRP 2.8.5.0 KK and JB http://forum.xda-developers.com/showpost.php?p=59452953&postcount=2592
2.7.1.0 http://forum.xda-developers.com/showpost.php?p=54972620&postcount=105
Jan 9th 2013
-Change to symlinked partition structure in recovery.fstab as we have found some Nabi's may have different structure
-Added Nabi Kernel version to TWRP screen for easier troubleshooting
-Added Nabi logo in place of Android(just for fun)
Initial
-Latest TWRP 2.3.3.0
-Changed to the prebuilt kernel from Nabi 1.9.37
-Fixed touch issues with some tablets with previous recovery(still testing this)
For more information on TWRP and change log see the TeamWin Website
Download
There are 5 downloads provided. The first is an installer for those less comfortable with the command line, it can install either version of TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second two are for people that just want TWRP 2.3.3.0 and can do a manual install. The final two are the last 2.3.3.0 with static partitions should you need to revert.
Auto Installer
Recovery Installer for Nabi(Recovery installer for both old and new kernel TWRP 2.3.3.0, TWRP 2.2.2.1, and STOCK recovery) Use install method 1
Current recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Older recovery recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Installation
-Method 1 (Recommended install , guided installer)
-Download "Recovery Installer for Nabi" from above
-Extract TWRPinstaller.zip
-Run RecoveryUpdater.bat
Code:
Select option 1 for a Nabi on 1.9.37 and follow directions
Select option 2 for a Nabi not 1.9.37 (UK 1.9.35 or 1.9.36 or Madagascar 1.9.34)
Select option 3 to go back to 2.2.2.1 recovery if option 1 or 2 do not work
Select option 4 to return your Nabi to stock recovery after restoring stock ROM
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 2.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).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.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).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_mt799
TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/
Credits
TeamWin team for TWRP.
Dees_Troy for build tutorials.
jmztaylor for the device code to work from.

aicjofs said:
Anyone want to guinea pig a TWRP build I made?
It's version 2.3.3.0 with the latest Nabi kernel. I don't think it will fix touchscreen issues but worth a try. EDIT: Some early results are indicating it is fixing touchscreen issues.
You can try it without installing it permanently
extract recovery.img from TWRPrecovery.zip to your adb directory
adb reboot-bootloader
fastboot boot recovery.img
That won't put it on the device just boot it to ram and you will maintain your current TWRP after a reboot. To make it survive reboot obviously you would need to
fastboot flash recovery recovery.img
http://home.comcast.net/~aicjofs/TWRPrecovery.zip
Click to expand...
Click to collapse
Tried your recovery, all I could say it's perfect. Touch screen in TWRP recovery is 100%. Have ben plagued with the touch screen error in recovery prior to aicjofs latest 2.3.3.0 TWRP recovery.
jmztaylor, aicjofs, t499user, e2950 deserve the XDA Nabi 2 award. Have owned the tablet maybe 3 weeks, in that time was able to restore from soft brick, get a working gapps witout 'Android Upgrading", and new updated 2.3.3.0 TWRP recovery. Got to Love XDA community.
All we need now is our own forum :laugh:
Sent from my GT-I9300

+ 1 on all that above
+ i wanted a updated version -
+ thank you
ps: *MY* nabi box says "ages 4-to 40" i think no matter what the age is
they all going to be happy with all this cool stuff.

good job
Glad to see people are happy u made this
:good:

Great to see more development starting to happen for the Nabi 2, thanks!

maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?

I have 2 responses from people where this version has touchscreen issues. It is for a 1.9.36(UK Version) and what I believe is a 1.9.34(Madagascar version) I updated the OP but it looks like you should only be using this on 1.9.37 right now.
Eric Karz said:
maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?
Click to expand...
Click to collapse
I always have usb plugged in so I never noticed.

CWM
aicjofs are you doing a CWM recovery for the nabi 2?

Eric Karz said:
aicjofs are you doing a CWM recovery for the nabi 2?
Click to expand...
Click to collapse
I did a CWM for the Nabi. Everything worked except I was having a hard time mounting the /sdcard properly. The internal sdcard as we know it is actually in /data/media(so it's on the data partition), I was able to manually "mount" it(symlink) through shell, but I couldn't make it auto mount. I'm sure it's something simple through init.rc or something but I couldn't get it working right to mount at boot time. On a side note to that, since it's on the data partition care has to be made that if the data partition is wiped that the sdcard is moved off and then back. I'm not sure if CWM does that with a loop device or something, just moves it or what, but it's dangerous. Lot's of devices have it set up this way so I think it would be accounted for, but I know TWRP accounts for it. I'm not sure extendcommand was working correctly either, it appeared to, but log was complaining about it. As it was I had early feedback that new TWRP was fixing touchscreen issues so I put it on back burner, as part of the reason for even building CWM was for those that had touchscreen issues. Only real change was to the BoardConfig.mk for BOARD_HAS_NO_SELECT_BUTTON to make CWM "function" less mounting problems.
Now I'm trying to decide if we are better using /dev/block/platform/sdhci-tegra.3/by-name in the recovery.fstab for those Nabi's with different partition structure. jmztaylor was kind enough to give me his ear and I think we should do tegra by name. No reason we shouldn't have one TWRP version, 2 at most. Once I get TWRP working for all Nabi versions for sure, I will probably revisit it.

Updated to symlink partitions for Nabi's that have been found that might contain a different partition structure.
Nabi kernel version added for easier troubleshooting
Nabi logo

Test Report
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks

Eric Karz said:
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks
Click to expand...
Click to collapse
Ok I really need to make a thread for Nabi Lab. Was that a hint? haha. Excellent feedback as always.
1. Yes you are correct that it should be added. I will add it.
:Main_7
adb\adb.exe kill-server
EXIT
2. What version of windows are you using? Also 32bit or 64bit? I had no issues with 7 and 8 64 bit after disabling windows driver signature enforcement, are you sure it took the "disable driver signature enforcement" after the reboot? That's the only thing that I know that would cause that. XP worked but I did manual mode as you did while testing. It's a modified Samsung driver so it might display that.
3. Also possibly related to the above. However I don't think so... It's possible that installing PDA net doesn't remove driver store/inf(depending on windows version). For example on Windows 7 open /windows/system32/driverstore/filerepository and search for "android" there is likely extra ones. So it just reinstalled the PDA net one. It should say Fuhu Nabi 2, so I think you are using the old driver. Both drivers are so you see the option for Nabi labelled one. You would have to unisntall in device manager and then remove all of android infs. Then reinstall.
4. Useful feature. That's not too hard to add since it detects the mode based off of it can run the getprop command. Give me an example when you would want it to do this so I can add it logically. Just really adding "fastboot reboot" and detecting. Are you thinking automatic detection like refreshing on it own?
Thanks for the feedback. You were already credited in the readme, but maybe you need some more credit

before i forget http://forum.xda-developers.com/showthread.php?t=1905674&page=131&highlight=nabi post 1302.
i was thinking
after the driver install
something like
1) test 1- Action > adb.exe reboot-bootloader
@echo Do you see the pretty green word "Bootloader" ? lol sorry i am tired

nabilab.bat
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .

Eric Karz said:
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .
Click to expand...
Click to collapse
Will that even be necessary if we go with the driver.bat you posted integrated in to the main bat file? I have been busy with my job last few days but I was able to run it in a few environments and it was working. The driver works, Im just working for an experience where anyone that can click a mouse/use a keyboard can install it. I think the PDAnet one is messy, that program even installs the apk to your tablet. Nonetheless the driver from a fundemental standpoint is the most important part, even if most people already have some functional driver. I want to get the driver cleaned up and the 2 known typos(although the 2nd might not be necessary if the driver install changes)
If I get those fixed make a Nabi Lab thread and work on ideas people have or want to see. Since you have been over the code what do you think of my hack job? Haha. Just notepad, not even notepad++, let alone a proper sciprting editor, I just kept adding stuff, it started as a simple recovery installer and then I got sloppy, and my variables and calls are a mess and named ridiculous. Kind of embarrassing. I haven't written that much code from scratch in 20 years, most of the time you have a base and can just work from there. That driver you linked gave me an idea of adding color to highlight errors and important parts, mostly cosmetic. For line by line color changes I have to use chgcolor and echoj. Easy enough to add to the download but changing all the echos is a tone of work.
I hope you know I appreciate your contributions.

opps my bad - forgetting the part about adding it to the main bat file .
just getting nabi lab to work for every one that uses it is the main goal.
code always has to start some place - i am sure as time goes on people will recommend things to to it.
the color in the Install bat was just to wake you up and watch what you are doing.
here is a example of something my brain skips over - Even though its proper and must be read in order to achive the goal
“Then hit VOL - until Recovery Kernel is selected
My brain only wants to hit vol 1 time haha
my brain should tell me to keep pressing Vol - until I see “Recovery Kernel” selected.

I see that Twrp is up to 2.4.0.0
Is there anything that nabi 2 users would benifit from it ?

Re: [recovery][nabi2] twrp 2.3.3.0
I too am wondering this!
Sent from my EVO using xda app-developers app

Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements
Click to expand...
Click to collapse
Seems interesting, I'll see about making a test build sometime this week unless someone beats me to it.

I'm short on time these days. Here is a build that boots. I tested an install. You can try and put through paces. fastboot boot recovery.img to test and not replace current.
Download TWRP 2.4.0.0

[GUIDE] Rooting the Moann inkPalm 5

Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
EDIT: You can find an extended guide at https://github.com/qwerty12/inkPalm-5-EPD105-root with steps for installing microG.

qwerty12 said:
Follow anything in this guide at your own risk. I will not accept any responsibility if you are left with a bricked device, and/or a device that is damaged or impaired in some way. These steps are a reconstruction of what I was doing - I haven't actually tested the exact files attached, which should be more cleaner than the ones I was working with.
The inkPalm 5 is a 5.2" eReader with an Allwinner 32-bit ARM B300 CPU and 1GB RAM running Android 8.1 sold in China under Xiaomi's Moaan brand.
This involves writing a file to /system, which may prevent you from installing future OTAs. Be warned that the firmware for this device cannot be downloaded, so you could end up with an unrepairable brick!
Make sure ADB is setup first.
Download dump_kernel_to_system_signed.zip
Reboot the inkPalm into recovery mode :
Code:
reboot recovery
Use the touch screen and/or volume + power buttons to choose the "Apply update from ADB" option
On the computer, run
Code:
adb sideload path\to\dump_kernel_to_system_signed.zip
(making the obvious substitution)
When it's done, choose the first option in the recovery (reboot system now) to boot back into Android
Back in an adb shell, run
Code:
cp /system/bimg.img /sdcard/
Install the Magisk APK
Open Magisk, tap install
I don't think the AVB/dm-verity option needs to be checked, so I left it unchecked. YMMV. The inkPalm doesn't encrypt itself even if you enable a PIN.
Choose bimg.img from your storage and let Magisk do its thing
Transfer the magisk_patched*.img file in your Downloads folder onto the PC
Flashing the patched kernel image with recovery
Rename your magisk_patched.img file to boot.img
Using your favourite archive manager, add your boot.img to the root folder of kernel_flashing_template.zip
In a command prompt, run
Code:
java -jar signapk-1.0.jar -w testkey.x509.pem testkey.pk8 kernel_flashing_template.zip kernel_flashing_template_signed.zip
(If you run into problems, make sure you have JRE 8 installed.)
Reboot back into recovery and
Code:
adb sideload
kernel_flashing_template_signed.zip
Reboot back into Android and hopefully you should have a rooted inkPalm with Magisk
(Flashing with fastboot should work, but I've not tested that.)
Click to expand...
Click to collapse
As far as I could gather, with both USB connection and developper mode on, ADB conncection is explicitely rejected. Besides, there is, on InkPalm, below the usuals USB checks, one that reads "...ADB/ADT..." which cannot be checked. The connetion request by wireless ADB, supplying the correct address, is also rejected.... As though the device needed be rooted first !

I haven't tested using ADB over Wi-Fi, but I can honestly say I have had no issues using ADB over USB on the inkPalm. ADB was enabled by default on mine, and not to mention the security of it has been weakened - you don't even need to approve ADB connections for the first time...

So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ? I cannot find any reference to the manufacturer that would eventually grant me permissions-- step ?
So long,
Sixto Quesada

Bis -- I forget to mention that my primary goal is merely to be able to change the language to English, as I think that there are already many possibilities in-built as to the configuration, including the shell !

squsqu6 said:
So, since mine seems to reject ADB on both USB and WI-FI, what would you suggest to try as next --and desperate ?
Click to expand...
Click to collapse
Is debugging mode actually on? Open the settings, go to the highlighted page and
{
"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"
}
turn the highlighted setting on (make sure the setting above it is on too - it will let you install external APKs)
You can follow these steps to show the Developer Settings, that's up to you: https://github.com/epodegrid/epd106-ADB#step-1-install-adb
squsqu6 said:
Bis -- I forget to mention that my primary goal is merely to be able to change the language to English
Click to expand...
Click to collapse
If you really can't get ADB to work, then there might be another way. Install the APK of my launcher fork (how you do that is up to you - you can try using the built-in browser or transferring the APK over MTP and using the file manager [which I've never opened] to install it).
In the new launcher, tap-and-hold the Settings icon (the one with a dark background),
choose Additional Settings and tap Locale. Then follow the instructions here: https://github.com/philips/inkpalm-5-adb-english#change-the-language

ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.

This worked great for me thanks a lot. I have a quick question if you know it. Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)? The stuff you can do with the home button/logo button in settings is pretty limited.

Thanks.
reaverclan said:
Is there anyway to get the old style android soft nav bar on the bottom (home, back, open apps)?
Click to expand...
Click to collapse
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button

qwerty12 said:
Thanks.
I think it may have removed entirely to save space. That's just a guess though. I tried two Magisk modules to enable it - one sets that qemu property and the other uses an Android resource overlay - and both didn't work. The only workaround I can suggest, untested, would be this: https://github.com/epodegrid/epd106-ADB#step-4-naviation-button
Click to expand...
Click to collapse
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible. So I guess it's for another xiaomi device or base android version. I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.

reaverclan said:
Yeah I tried step 4 and adb said the file was to old so rejected it and I tired it in the file manager anyways to see what would happen and it says it's not a working package or not compatible.
Click to expand...
Click to collapse
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
I also noticed only the stock file manager can actually invoke the package installer, root explorer gets the prompt to install but never then sends it to the Manger to load it and give the option for an install.
Click to expand...
Click to collapse
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).

qwerty12 said:
It's actually because the modified launcher mentioned in this thread uses the package name com.moan.moanwm (credits to whoever found that out; doing that allows the original Settings to be launched), which actually belongs to those navball buttons... I was originally going to suggest to just get rid of the launcher, so you can install the navball buttons, but they're really crashy and useless anyway. Sorry, I don't know what else to suggest - given other "QOL" changes by Moann (see below), I strongly suspect the navigation button code was ripped out entirely to save RAM.
Give Total Commander a try.
Moann really did a number on this device's Android build and messed it up, presumably in the name of "security". Only certain programs can show the original Settings, which messes up other applications' ability to show the app info of programs; the only thing that can force stop programs is Settings (which messes up Titanium Backup) and Root Explorer probably tries to invoke the Android installer directly (if that's a thing).
Click to expand...
Click to collapse
Ah I see that's clever. It's not the end of the world and yeah I think it's cause root explorer does what you said about invoking the thing directly. I just use the stock app to only install and that's it. My journey so far is shown here and regardless of the jank it has been a great device. https://www.mobileread.com/forums/showpost.php?p=4140508&postcount=155
Thanks again for the time to make it even greater. Only thing that sucks is no stock img to un brick if something goes to far. Hopefully someone leaks that at some point. This device seems pretty new to the market still.

squsqu6 said:
ADB is definit[iv]ely unavailable. But your launcher fork --that I already had, but did not know what to do with-- works, I now have most of the menu in English.
Thank you so much.
Click to expand...
Click to collapse
I now have a new, but old !, trouble : battery life. I have enforced all saving possibilities available --from standard menu, from E-Ink Launcher, and, from RomToolBox, processors speed slowing--, and, yet, after 8 hours of use, InkPalm battery is totally empty, even though being totally user-idle --not a single user application being active according to linux 'top' request. Conversely, Kobo reader battery lasts for days in reading mode.
My question : would it be thinkable any possible trick of triggering the sleeping function without pushing the red button, so as to keep the screen as it is --allowing the reading of actual page until next (not a book, a musical partion, which takes longer !)--. Bypassing by script the red button action, or other ? --Note : the screensaver option allows for user-image, like a screenshot, but it requires to move it to the proper place and to renew it at every page...
Sorry for being so long, I am far from being familiar wich Linux (Android).
Greetings,
S. Quesada

LineagOS - Jingpad

Has anyone looked into compiling / porting LineagOS for the Jingpad A1? They released the source code. Why use LineagOS and not their released because theirs is in Chinese and it's lacking features available in LineagOS. I understand that the company has stopped developing their default OS and everyone with them now kind of has a dead product. I someone ported UBports to it, but Ubports lacks somethings that LineagOS / Android brings to the usefulness for a tablet. I know they had android app support that you could install on their default OS, but it has bugs and some apps were slow or errored out upon launch.
jingpad-bsp
jingpad-bsp has 421 repositories available. Follow their code on GitHub.
github.com
Android ROM source code for JingPad A1
The source code has been zipped into the 8 packages below, you have to download them all before you compile. How to compile Full compilation (take the userdebug version as an example, if you are editing the user version, just change the ud710_3h10_native-userdebug-native in the instruction to...
forum.jingos.com

[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS

Excellent thank you for this. I am trying to flash my system with the image in the post. The process worked, thank you for showing me the post.
How to change to english
edit the following file in the source code
/source/device/sprd/roc1/ud710_2h10u/jingos/device.mk
edit the following lines.
persist.sys.language=en
persist.sys.country=US
persist.sys.timezone=America/New_York
persist.sys.locale=en-US
ro.product.locale.language=en
ro.product.locale.region=US
and compile
cd /source/vendor/sprd/release/IDH/Script
./build_pac.sh -a ud710_3h10u_native-user-native -b all 2>&1 | tee build.log
​

Have there been any new developments for the JingPad? I have one and I would consider putting Lineage OS on it. However, I'm not competent enough to build it from scratch. Is anyone developing AOSP for this tablet?
I am presently running UBPorts (Ubuntu Touch) and it is certainly less than stellar. I can't get WayDroid to run. Things might change when UT upgrades from 16.04 to 20.04 in the near future. But for now, I am checking everything before I stick it in the closet.

Hmm, I guess no one has mirrored the instructions?
Because all jingos.com links are now dead.
Maybe someone who has copied the instructions or the original author could add them to this thread?

I have a lot of the files for this tablet including the flashing application Research Download, the .pac file from January 2022, and USB drivers for Windows. I have the .docx file with the Research Download instructions.
I am leary to reinstall the JingOS without clear instructions on how to do it since I now have UBPorts installed.

LoTo62 said:
[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS
Click to expand...
Click to collapse
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.

r3d10tu5 said:
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.
Click to expand...
Click to collapse
No. Sorry. The only files I have are the original files distributed with the JingPad.

I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007

r3d10tu5 said:
I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007
Click to expand...
Click to collapse
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.

jmd8800 said:
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.
Click to expand...
Click to collapse
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
How did you install the gapps?
I tried again today, and finally found how I was able to use gapps before.
You should have booted to the system once, before you boot to recovery and flash gapps.
“open_gapps-arm64-10.0-pico-20220215.zip” and “open_gapps-arm64-10.0-nano-20220215.zip” are probably the only two available version that work.
After reboot, you should get an error like “This device isn’t Play Protect certified” which keeps popping up, not “There is a problem contacting with google server”.
Steps:
Go to play store, click sign in;
It said “This device isn’t Play Protect certified”, click that green link “g.co/AndroidCertifiedDevice”;
Follow Google’s instructions to register your device;
Go to Settings, try your best to force stop gms & play store and clean their data;
(But do NOT clean gsf’s data! Clean cache is enough)
Go to play store and sign in before gms know it.
Click to expand...
Click to collapse

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to ask that you properly clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
Looks like I have some work cut out for me. If I can get this to work and cover my needs I'll be happy. If not .... back in the closet it goes and I will buy an Apple or Samsung next week as I need something for travel.
Thanks

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?

jmd8800 said:
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?
Click to expand...
Click to collapse
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears

r3d10tu5 said:
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears
Click to expand...
Click to collapse
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again

jmd8800 said:
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again
Click to expand...
Click to collapse
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

r3d10tu5 said:
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
Click to expand...
Click to collapse
Thanks. I was just about to try again when I saw your post. Using this method I got better results but I cannot install because 'my driver version is too low'. I'll have to dig into this. But it appears to contact the JingPad and even errored out in the status bar. Progress!
I don't use Windows so I don't have a legitimate Windows OS working. It says it is test mode as I've not registered it. I can source the BIOS to find the key and hopefully that will let me get to a point where I can update the driver required to connect the PC and the JingPad.
Thanks again

Success! Thanks for all of your help @r3d10tu5
Well.... Success installing the pac file. I'm still working on the gapps. the adb command said it was a successful instal but Google software is not on the screens.

Just a thought as I was playing with this. Has anyone tried to use microG instead of going through all the hoops to get Google services running?