NABI LAB v2
{
"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"
}
NOTE: The program is becoming long in the tooth and not as useful with Jellybean on Nabi. For Jellybean TWRP installs check this repackaged version of Nabilab http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
This is a tool for performing various automated tasks on the Nabi 2. It's written as a windows command line batch file, and v1 has been tested by a few members of the forum with positive results. Hopefully this means all the bugs are worked out, most issues have been typos on my part. It's an attempt to include all recent developments in Nabi 2 rooting, Gapps install, recovery methods, and modding and provide and all in one experience. Alot of this is my own original work, and other parts are creations of others intact or modded for Nabi use. Using the latest known working methods, it hopefully prevents users from having to install, break things, uninstall, recover, try new method, ask forum questions, try another method, and all the while for those with kids having them ask why you broke their toy.
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
A test version of NabiLabGUI is here: http://forum.xda-developers.com/showthread.php?t=2391449
Overview
Video Overview of Nabi Lab v1 mostly the same as v2
-Install ADB/Fastboot digitally self-signed drivers.
-Root the Nabi 2
-Install Gapps(Play Store, etc)
-Fix Android is upgrading message
-Make a stock backup of unrooted device
-Install a stock 1.9.37 in the event of loss of backup.
-Install stock, or TWRP recoveries
-Tablet Information
-Lockscreen modding tool
-NabiLab patching system to install updates to this program
-Fix TWRP touchscreen issues
-While not a built in function using the tools to fix broken Wifi
Download
Read the installation section below to determine which version you want.
File names:
NabiLabFull.zip 1.1GB
Download
NabiLabLite.zip 97MB
Download
Download Mirror
NabiLabv2Update.zip 10.1MB(upgrade patch for v1 users)
Download
Download Mirror
Installation
There are 2 versions of Nabi Lab: Full and Lite. The full edition is 1.1GB and includes a stock 1.9.37 backup of the system, data, and boot partition. It's usefulness is really only of interest to those that need to restore to a stock backup. It should be a rather limited group of people as you should have a backup of your system already that you could use in lieu of this. However in the event you have lost your backup, or have mangled the system to the point you aren't sure what to do, the option to restore to stock 1.9.37 is in the full edition. The likely download of choice is the Lite edition at a more manageable download size of 97MB. It has all the tools of NabiLab just without the ability to restore a stock backup(which of course you have one of your own). The upgrade patch zip is for v1 users.
NEW INSTALLS
1) Download Nabi Lab
NabiLabFull.zip 1.1GB
NabiLabLite.zip 97MB
2) Extract the zip files to a location of your choosing. Run the NabiLab.bat file.
PATCH INSTALLS(For version 1 users)
1) Download NabiLabv2Update.zip 10.1MB
2) Extract the zip IN to the directory NabiLab is in not FROM the directory. What ever your unzip program it should be extracting to X:\somefolder\somefolder\yourNabiFolder\ If you do it right there will be a file RunOncePatch.bat in the same folder as NabiLab.bat, and a NabiPatch.zip in a new folder called patch in your NabiLab folder.
3) Run RunOncePatch.bat
note: This is only necessary this time, any future patches will be applied by downloading a NabiPatch.zip, and installing inside the NabiLab program.
Prerequisites
1) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
2) Unsure you are on version 1.9.37. Enter Mommy/Daddy mode. Open settings->About Tablet->Product Version. If it's at something less then 1.9.37 go up to the "Update" selector and check update and install. You may have to do this more then once.
Notes: At this point it is believed that the Madagascar Nabi 2, and UK version have product versions of 1.9.34, and 1.9.35/6 respectively. You can attempt to use NabiLab at those versions but I cannot guarantee results. Most things should work however.
Usage
Obviously using this product on your Nabi 2 voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Installing drivers
The provided drivers are for Windows XP,Vista, 7 and 8 32bit and 64bit. They are modded version of the drivers by 1wayjonny found in this thread. The mod to those drivers are adding the Nabi, and the HP Touchpad Tenderloin(only because I have one). The are digitally self signed by "NabiLab".
Menu Option 1 - Auto Install
Check in the top left corner under Detected OS to see if it matches your configuration. The most important part is if it says "x86"(32bit) or "AMD64"(64bit) this is what the auto installer is going to install. If you don't know right click "my computer" and look under system type. If everything looks right proceed. An installer will launch and guide you through install.
Menu Option 2 - Manual Install
If you want to manually install, an explorer window will launch allowing you to pick the NabiDriver32.exe or NabiDriver64.exe. In case it needs stating the NabiDriver32 is for 32bit OS, and NabiDriver64 is for 64bit.
Notes: The driver can be uninstalled by going into control panel and add/remove programs, select Nabi Driver and click uninstall. The digital certificate for Nabi lab is installed in Trusted Root Certification Authorities. Probably the easiest way to view is internet explorer. Go to tools->internet options->content->certificates. It can be removed from here should you feel it's a security risk. I don't think it installs properly on XP, so if you want to add it go to your program files folder->NabiLab->driver and find the NabiLab.cer, right click and select install. When you come to option of where to install manually select Trusted Root Certification Authorities.
MENU 2 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android and upgrading to 1.9.37. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have 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.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps, and/or getting rid of the Android is Upgrading message. It is the immensely popular t499user Gapps with the 2 stray .odex removed. No sense in reinventing the wheel. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
Note: The layout of this is based on the original work by jmztaylor, modified for what we currently know about the Nabi and tweaked accordingly.
MENU 3 - Return Nabi to Stock Condition
The menu options will only be available if you have downloaded Nabi Lab full. If you have a stock unrooted backup you should try that first.
Menu Option 1 - Return Nabi to Stock 1.9.37. Android can boot.
This is useful if you just want to return your Nabi to stock for regular use, sale, or warranty(morals aside). This is the mode to use if you can boot Android. This operation will take some time to run, so let it. Upon completion TWRP is still installed, to entirely restore to stock you will need to install the stock recovery(see Menu 4). You have the option to put on external or internal storage. Although I don't think I compiled TWRP to use "in place" install, which would mean it still copies to internal. I'm not sure on this one, so internal is probably the best bet, but I have performed it on external and it works fine. You will need space on internal storage to do it.
Menu Option 2 - Return Nabi to Stock 1.9.37. Android not booting.
This is useful if you are in a situation that has left Android unbootable and you have no backup. Otherwise it's the same as Option 1. You will boot to TWRP and then perform the restore. Again TWRP will still be installed afterward, no be completely at stock you will have to remove it by Main Menu 4. I have it this way in the event you plan to immediately reroot it.
Notes: If you want to view this menu in the lite version, you need to open the file havefiles.txt, it is located in the stockimage folder. Change the line backup=false, to backup=true. You can then view the menu. You can then copy files you wanted to the stockimage folder and restore. Since the restore portion is manual I'm not sure why you would ever use it this way but if you want to play around that's how to enable it.
MENU 4 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.9.37
Installs TWRP 2.3.3.0. This is the version that everyone should be trying to use first before trying other versions. This is the version that has symlinked paritions since it is thought currently their might be different partition structures for various Nabi's. Newer Nabi kernel and fixes touchscreen issues for some people that were using 2.2.2.1.
Menu Option 2 - Install TWRP 2.3.3.0 for Nabi Versions prior to 1.9.37
Use this option if Option 1 didn't work for you. Older Nabi kernel, otherwise same as Option 1.
Menu Option 3 - Install TWRP 2.2.2.1
This is the original TWRP from the first Nabi rooting thread. Use this if the other 2 don't suit you, or you just trust my compile skills, which may be prudent... :silly:
Menu Option 4 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Menu Option 5 - About Recovery Installer
A leftover from my initial recovery installer, I was too lazy to remove it.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 5 - Tablet Information
Nabi Information, serial, version, build date, device mode, internal/external size, detected backups.
Note: This only detects if a backup folder is present, not if there are backups actually inside the folder. The only way this would be the case is if you manually deleted them or just made a empty folder in there, so be aware. Also if you have made a ramdisk modifying init.rc, used creative symlinking to swap internal and external SD, or used a prebuilt app to swap this screen may be incorrect.
MENU 6 - Lockscreen Mod Tool
Don't use this if you have updated to v2.0.5, I haven't tested but the framework-res.apk was updated in the 2.0.5 update and if you are using the old one you could throw yourself in to a bootloop
Menu Option 1 - Install custom lockscreen
Use this to install a custom lockscreen. You will need a picture that is in .png format and is 1440 x 903. A explorer window will open up showing you the location to put the picture. The file MUST be name lockscreen.png, there is one there that is black, you can overwrite it be there MUST ALWAYS be a lockscreen.png file in that folder if you use the tool. Bad things could possibly happen if it doesn't. You have the option to manually install the lockscreen, or automatically install it after the zip is built. In either case it copies whatever you named the zip(you are prompted for a name) to the internal SD, along with a file called lockorig.zip. The lockorig.zip is there if you mess up and Android won't boot you can manually install the lockorig.zip in TWRP to put it back to stock.
Menu Option 2 - Install stock lockscreen
Use this to return to stock. Remember if you used Option 1 there will already be the stock lockorig.zip on your internal storage.
Notes: If you make a custom lockscreen, while it copies the installable zip to your device it also copies it to your picture folder so you can share with others. Make sure you visit in share your creation over in this thread.
MENU 7 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to Nabi Lab this is where you can automatically load them. Basically you will download NabiPatch.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Note: Since this option wasn't in NabiLab v1, we have to do some trickery when coming from version 1 to install, so the procedure is different, all subsequent patches will be the above method however. Coming from version 1 you will need to download NabiLabv2update.zip and extract it into the NabiLab directory such that RunOncePatch.bat is in same directory as NabiLab.bat, and the other file NabiPatch.zip is in the folder "patch", then run the RunOncePatch.bat If you extract into your NabiLab directory it won't be a problem, the hint you didn't do it right will be if the RunOncePatch.bat isn't right there with NabiLab.bat
Credits
jzmtaylor - Original Nabi root. Nabi device code from which to build newer TWRP
t499user - Gapps fix
Dees_Troy - TWRP build tutorial
Eric Karz - Lockscreen Modding, NabiLab scripting
1wayjonny - Universal Driver base code
TeamWin - They are the guys that make TWRP possible
In all honesty everyone that has participated in the main Gapps thread has indirectly made the program what it is from testing, to information, to troubleshooting and everything else Nabi.
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Sent from my EVO using xda app-developers app
DarkAngel said:
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Click to expand...
Click to collapse
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
strive53 said:
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Click to expand...
Click to collapse
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
aicjofs said:
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and not while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
Click to expand...
Click to collapse
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
DarkAngel said:
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
Click to expand...
Click to collapse
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
aicjofs said:
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
Click to expand...
Click to collapse
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
strive53 said:
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
Click to expand...
Click to collapse
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
Click to expand...
Click to collapse
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
aicjofs said:
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
Click to expand...
Click to collapse
This is the first time installing it actually since I Rooted and installed GApps through Ubuntu. I just wanted to try it so I can try and change the lockscreen image and update TWRP while I was there also. I downloaded v2 with the backup. I was going to try v1 to see if that made a difference or try the PDAnet driver.
Sent from my NABI2-NV7A using Tapatalk HD
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
kieronw3 said:
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I could add a line that says, go check the mail, run to 7-11, trim the dogs toe nails. Hehe. Glad it worked eventually. 58 or so downloads and not many complaints, I can live with that, better then a brickfest. :laugh:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Eric Karz said:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Click to expand...
Click to collapse
I need something for a version 3, so why not?
delio77 said:
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Click to expand...
Click to collapse
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
bradleyw801 said:
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
Click to expand...
Click to collapse
Have you verified that your fastboot drivers are working? If you navigate to the folder where adb.exe and fastboot.exe are you can just iddues the command fastboot devices to see if the device is connected while in fastboot.
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
aicjofs said:
I need something for a version 3, so why not?
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
Click to expand...
Click to collapse
I am using NabiLab and it said not detected. I eventually got it to work with PDAnet
Ken Esq said:
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
Click to expand...
Click to collapse
So is the device still on .23? Probably 3 ways to go about it if that's the case,
1) backup apps with something like Titanium backup, restore the original backup "stockunrooted" of Nabi, reinstall stock recovery, update to 1.9.37, reapply root and gapps, restore app backups, or
2) backup apps, restore a stock 1.9.37 from NabiLab, reapply root, gapps, restore app backup. or
3) you can try updating the safe OTA's people have posted, I came late to the game so I didn't study those, I know there is the wifi issue between kernel and modules if you don't do it right. If you already are on .37 but just rooted back on .23 the only thing to do is gapps to fix android upgrading. The optimizing android is fixed by flashing the fixed gapps.(Gapps only, option 2 then option 3 in NabiLab)
How would you like to see cloning? It just loops through the procedure and you just keep plugging Nabi? Or a restoring image to all of them. Help me visualize what you think would be best.
I'm not sure how you are doing it. How I would do it currenlty for Nabilab if I had 20 brand new Nabi's is like this. Once all Nabi's are at version you want (1.9.37)
Take one Nabi and do a recovery, root, gapps, backup(Option 2, Option 1)
Grab the backup it made and move it to computer.
Take remaining Nabi's
Install TWRP 2.3.3.0(Option 4, Option 1)
Install Root Only(Option 2, Option 4)
Install Gapps Only.(Option 2, Option 3)
What you accomplish here is making the backup only once. So first Nabi takes 15 min, the remaining maybe 3 min.
No thank you for popping in with some feedback.
I WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.
after looking at numerous threads and advice, it seems quite complicated to install a simple fn app, which by definition, is supposed to be easy,
why firefox doesn't have it, considering that most stuff is only available on itunes or google store these days, is beyound me.
Even more so that i thought that the dual core would a) let me run ffos or android ie via easy restart mode,
and b) android would have the google store app.
so. how do i get this on. some ppl seem to be able, and there explanation is: its complicated.
fair enough. i hope you will help me and others to work through this. An explanation for dummies.
this is the best post i'v seen so far.
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
along with these links:
http://developer.android.com/tools/help/adb.html
https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173/page3
so i can change my os from ffos to android and back. no problem:
https://www.youtube.com/watch?v=axOYIfo7y2s
http://down.comebuy.com/Open_c_root_Android4.4.rar
but i get stuck with "adb reboot bootloader"
that won't work, so advice for dummies, from that point forward would be much appreciated. Thanks
ok, so tried installing two other adb programs, http://www.rockchipfirmware.com/sites/tntfiles/PDAnet-64bit.zip
and while neither where completely successful, they did manage to allow adb to access phone,
and for the commands to have determined affects, so have moved on to Upgrade tool, which does not recognize device, thoughts? help?
Hi darth lotus,
To install google play store, you need to be able to write to the system file system, to do this you would either need to root and push google apps (gapps) via adb, or replace the stock recovery with a custom recovery which will allow you flash .zips that are not signed by ZTE.
Installing clockworkmod recovery, for example would allow you to do this,
There are examples of clockwork recovery here http://forum.xda-developers.com/firefox-os/general/zte-c-roms-cw-recovery-50-t2806173 and here http://www.modaco.com/topic/373213-recovery-clockworkmod-6050-for-zte-open-c-kis-3/
And TWRP recovery here http://www.modaco.com/topic/373288-recovery-twrp-2710-for-zte-open-c-kis-3/
The second clockwork and the twrp recovery are by a developer named Konstat who has uploaded all his sources to github https://github.com/KonstaT/android_device_zte_kis3
Konstat has also started work on getting a stable version of Cyanogenmod 11 on the ZTE Open C, please see here http://www.modaco.com/topic/373214-devrom149-cyanogenmod-11-android-444-for-zte-open-c-kis-3/
I apologise for linking to a different website but until we can ask xda to create a zte open c forum, I do not really have an option :crying:
Hello,
I'm having an odd issue with Remix OS for PC, and wanted to see if anyone else experienced this and hopefully found a resolution. Please see the bottom of the thread for info on my PC setup. My laptop is definitely more than powerful enough to handle remix, and it used to run fine, but now I seem to have the following issues after not booting into Remix for a while:
***Wifi does not automatically connect, it only connects if I click the wifi icon in the tray (then it connects to my network automatically)
***Nearly all apps will not open, including the Settings app. I'll click on an icon on the desktop, and the icon lights up, registering my click, but the app never opens and the icon stays lit as if something froze. However, I can still "swipe" from the left desktop to the right one, and vice versa.
***When attempting to install an app (Eventually, without any rhyme or reason that I've noticed, I can open the Play Store and maybe the settings app), the app hangs on Installing after it downloads. I've tried waiting a good 20 minutes, but I know the apps install much quicker on this laptop, and I've tried this with small apps.
***Similarly to the above, clicking the Remix OS menu button does nothing as well.
With those symptoms in mind, it seems like there's something holding the system back, but the actual GUI performance is fine. For example, there's no lag or hesitation when an app finally eventually opens or when I click around through the Settings app (when it finally opens). It doesn't seem to only be with graphic intensive apps either, as I tried a simple text/memo app and when that one eventually opens, the desktop background is black and the app window is black with only a menu near the top.
My attempts to fix it
So far, I've tried running an e2fsck -f data.img command to repair the data.img file. It didn't appear to report any issues and the problem did not go away. I've rebooted the thing about a billion times, no luck! Getting into the Settings app is hit or miss and I haven't really had any idea of what setting might help, and installing third party apps appears to not be an option either.
The only other option I could think of would be to backup my data.img and reinstall the OS, and then restore the data.img file, but this seems like it will restore the problem with it. Also, I haven't experienced any problems in Windows, so I don't think there is any issue with the drive. Sorry for such a long thread, just wanted to be detailed!
Any ideas are much appreciated!
My PC: Lenovo Ideapad y510p
Windows OS: Windows 10 64-Bit
Remix OS for PC: 3.0.207 dual booted with the above Windows 10 installation
Hard Drive: 500GB SSD drive
RAM: 16GB
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
ViolentNeurosis said:
I don't have any of those issues. My issues are a bit different...
I can't seem to find a copy of RemixOS 3.xx that actually has "true" root access. I know there is a method you can use to remount the volume as r/w, but since I am running it from a flash drive, I apparently cannot access any of the system files in Windows with hidden files and folders visible. And, after first boot the USB drive running the OS will somehow end up with a corrupted "REMIXOSDATA" partition.
Good luck on your quest.
Click to expand...
Click to collapse
Thank you for the response! In reading the issue you're having, I'm wondering Remix OS for PC, in its current state, is more susceptible to corruption issues in under some circumstances rather than others. When I first installed it, I installed the 64-bit version and I kept having issues where I'd boot it up and it suddenly would not start. I found somewhere on a forum where someone recommended to just use the 32-bit version and the issue went away for a long time, until I had the issue described in my original post. I'm wondering if it just isn't stable enough yet to be run from a flash drive, as it seems to me like it has issues with being easily corrupted.
This brings me to my next comment, I was able to fix my issue! I tried a couple things that didn't work, reinstalling Remix and then choosing YES to erase the entire virtual drive, then copying a backup of my original data.img back into the directory so I don't have to reinstall everything. This didn't fix the issue, so instead I downloaded the 64-bit version and installed it, but this time I chose NO on the prompt to erase my data.
Upon booting into Remix, it gave the standard Android message about optimizing apps and is now running good. I wish I did this workflow with the 32-bit version, as I'm wondering if it would have worked. I suspect I'll experience the same issues I originally experienced with the 64-bit version.
Anyway, I hope this may shed any light on how you can try to resolve your issue. Good luck!