Related
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 recently ordered an Onda obook10 dual booting tablet (Android 5.1 +Win10) from GearBest, and received it a week (and a half) ago. It is the V5 version (9th and 10th digits of S/N). Booted into Android at first, swiped around a little, and then left it alone for when I was free. Day before, I booted into Windows, and seeing that an account was already set up, hit the factory reset option (Options: remove all personal files, normal wipe (not thorough)). It rebooted, said it was resetting, then got stuck at 5% for a half hour. I then did a hard reboot, and it starting resetting again. I repeated this a few times, with different waiting periods, but it always got stuck at 5%. I wanted to see what was going on, so I opened the OS selector menu and tried to boot into Android, but that put the device into a bootloop, and it's stayed that way since. I downloaded the recovery WinPE from their website, and tried running it; all went well until the last step (installing the install.wim file), which succeeded, but when the batch file tried to set the boot options/flags, it threw an error about not being able to access D:, and failed. Tried making the recovery USB and installing multiple times, but it failed every time. I then tried Gandalf's WinPE image, which booted, and tried using imagex to install the .wim file to C: manually, as detailed here. This failed too.
I'm at my wits' end, honestly. I have no idea what else to try. There's another WinPE file available for download, but it's dated only a couple of weeks after the one I already have, so I'm hesitant to download it if there's any other option (I have very low bandwidth, it would take me at least two days). Also, it's hosted on Baidu, and the download times out after about an hour, and cannot resume. If anyone could give me any ideas, or point me towards a guide I haven't found yet (I've read all the relevant ones I could find on the Onda forums, but please post them anyway if you think they would be helpful), that would be great.
What would be perfect is if someone could upload, or point me toward a system dump/partition clone of at least the Windows partition and boot partition; I have the tools needed to flash those.
Thanks in advance.
EDIT: I managed to fix this a while ago, and have put the procedure somewhere in this thread, but since people keep popping up every now and then asking for it, I'm going to put this here so it's easier to find. Copied from later in the thread, here, and modified to be more general:
This uses slightly modified commands from the Onda firmware install script, and will result in a COMPLETE WIPE and reinstall of Windows - all the files on the Windows partition will be lost. This SHOULD work for anyone whose Android is working but Windows isn't, but I can't guarantee that. I can't even guarantee that this will work (though I am pretty sure it will) - I have not tested it completely. If you can, you should make a backup of anything files on the internal storage, just in case. As always, read the whole procedure before starting.
NOTE: If your Android isn't working, you need to install that first - get the Android file from the Onda Baidu page (look for the one for OBOOK 10 (not SE), with the appropriate V1, V2, V3, V5, or V7 code - you can find your code by checking the serial no. on the back of your device, the 9th and 10th characters), and follow the instructions in the document included in the zip - they are pretty straightforward, but you'll have to use Google Translate, as they're in Chinese. This MUST be done before the Windows procedure, because the Android installer wipes the entire disk.
If you want, you can make the procedure easier for yourself and save all the commands below to a text file, put it in the root folder of the USB before booting, and open it in Notepad by using:
Code:
notepad D:\textfile.txt
Or whatever name you give it. That way, you can copy paste them all easily.
Boot into the Windows installer, and when the command window appears, press Ctrl-C. After a few seconds, it will ask you if you want to terminate batch job, type 'y' and press enter. You now have a command prompt to work with.
You have to delete your Windows partitions first. The below partition numbers should be correct, but you should make sure first by running "list partition" and checking if it corresponds with the last 3 partitions, which should be your Windows partitions - their sizes are usually 128 MB, 35 GB, and around 800-1024 MB, and their types are Reserved, Primary, and Recovery (DO NOT delete the Primary partition at the beginning of the disk). DO NOT delete the Unknown partitions - those are Android's.
Code:
diskpart
sel disk 0
sel partition 14
delete partition
sel partition 13
delete partition
sel partition 12
delete partition
Your Windows partitions are now completely gone, so you'll have to recreate them first.
Change directory to the images folder.
Code:
cd D:\images
Get filesizes of .wim files to create partitions accordingly:
Code:
for %I in (Install.wim) do set INSTALL_SIZE=%~zI
set /a INSTALL_SIZE_MB=%INSTALL_SIZE:~0,-6%
for %I in (Winre.wim) do set RE_SIZE=%~zI
set /a RE_SIZE_MB=%RE_SIZE:~0,-6%
if %RE_SIZE_MB% LSS 430 (set /a RE_SIZE_MB=480
) else (
if %RE_SIZE_MB% GEQ 430 (
if %RE_SIZE_MB% LSS 680 (
set /a RE_SIZE_MB=%RE_SIZE_MB%+320
) else (
set /a RE_SIZE_MB=%RE_SIZE_MB%+1024
)
) )
Make sure to preserve all the spaces and brackets in the above code.
Enter diskpart, run the following:
Code:
sel disk 0
create partition msr size=128
create partition primary
shrink minimum=%RE_SIZE_MB%
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
You should now have 14 partitions when you do "list partition".
Exit diskpart.
Now for the actual installation:
Code:
md w:\recycler
md R:\recovery\windowsre
DISM /Apply-Image /ImageFile:"D:\images\Install.wim" /ApplyDir:w: /Index:1 /Compact /ScratchDir:w:\recycler
xcopy D:\images\Winre.wim r:\recovery\windowsre /y
Create boot entry:
Code:
bcdboot w:\WINDOWS
If that doesn't work, then:
w:\WINDOWS\SYSTEM32\BCDBOOT w:\WINDOWS
Set recovery environment:
Code:
w:\windows\system32\reagentc.exe /SetREImage /Path R:\recovery\windowsre /target w:\windows
And that's it! You should have both OSes operational now.
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
EDIT: I've put the guide in the first post.
Flashing Help
SirVer said:
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
Click to expand...
Click to collapse
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
[email protected] said:
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
Click to expand...
Click to collapse
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Widows swith icon
SirVer said:
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
[email protected] said:
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
Click to expand...
Click to collapse
Is the partition still there, or is that just free space you're seeing? For me, the partition was gone, with unallocated space in its place. If the partition is still there, then your job is relatively simple.
1. Make a WinPE recovery drive from another Windows machine, or just use a custom one (like Gandalf's WinPE, Google it).
2. Boot into it from the BIOS menu.
3. Load a command prompt.
4. Type "diskpart" (no quotes). Wait until you get a prompt like: DISKPART>
5. Enter the following commands:
a. select disk 0
b. list partition
c. select partition xx (where xx is the number of the Windows partition. If it's not labelled, it'll be the one about 36 gigs in size.
d. assign letter=c
e. exit
6. Now just run "bcdboot C:\Windows"
7. Reboot, and you should see Windows in your BIOS menu once more, and the button should pop up on Android as well.
If the Windows partition is not there, and it's just free space, things become more complicated. You'll need to get your hands on the Windows installer image. There is an older version on the Onda website (December 2015) that should do the job - or rather, there's a link to their Baidu account. You can find the more recent version in their account as well. The issue is that Baidu doesn't allow you to download files that large without installing their crapware. I got around it by registering an account and some URL-fu, but it's a PITA, especially if you have a slow connection. There's a Yandex mirror somewhere, but I'm not at home, so I don't have the link right now. I'll post it when I get back. EDIT: Here it is.
After you get the files, DON'T install it; it might wipe your Android install (did for me). There's an issue in their install script that made the command that hides the Android partitions from getting deleted not work. What I did was terminate the automatic install, and selectively apply the relevant portions of the script manually. You could probably do the same, but it could take you a while; took me two days and a bunch of background reading. If you're used to messing with Windows installs though, it'd probably be a cakewalk for you. I'd prepare some instructions for you, or even try and write a script myself using that one as a base, but I have exams right now, and I wouldn't have time for at least a week. If you haven't figured it out by then, just ask, and I'll do it.
Sent from my LG-D855 using Tapatalk
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Frezza said:
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Click to expand...
Click to collapse
You can enter the BIOS menu by connecting a keyboard and holding down ESC while booting up.
Sent from my LG-D855 using Tapatalk
Help
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
[email protected] said:
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
Click to expand...
Click to collapse
I don't remember exactly what it's called, but I think it was the second menu entry - Boot <Something>. In that menu, you should see your USB drive USB EFI device or something like that listed - it might also show the manufacturer name (it showed my USB as a Sandisk). If you don't see it, you may have made a mistake when making the bootable USB - try it again while reading the instructions on Gandalf's site carefully. If you used Rufus to make the bootable, maybe try Unetbootin this time - it worked fine for me.
P.S. In case you meant boot into the file - you can't. You have to write it to a USB drive first. Instructions are on the same site you downloaded it from.
Sent from my LG-D855 using Tapatalk
Can I install Windows 7 by Gandalf on this Tablet?
Frezza said:
Can I install Windows 7 by Gandalf on this Tablet?
Click to expand...
Click to collapse
Install? Maybe, but you wouldn't have any of the necessary drivers, so touch and WiFi and stuff wouldn't work. However, you can download the drivers and try installing them, which might work, though it probably won't since they're made for Windows 10.
Sent from my LG-D855 using Tapatalk
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Frezza said:
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Click to expand...
Click to collapse
Depending on certain things, you may be able to just run the installer without doing anything extra. Are you able to boot into Android? Open a CMD window, and run the following commands:
1. diskpart
2. sel disk 0
3. list partition
Post the output of these here. A screenshot will also be OK.
Sent from my LG-D855 using Tapatalk
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
betsesv said:
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
Click to expand...
Click to collapse
When you extract that, you'll get a bunch of files and a DOC in Chinese explaining the procedure to make the recovery disk. Once you've made that, a WARNING before you boot into it: it will automatically open a CMD and start a delay counter, after which it will start the install automatically. Since this might break the Android side, you'll have to cancel it with Control-C in that delay period, which will give you a normal CMD to work with. You can use this to run the commands from my last post. If you want to be extra safe, also download a different WinPE recovery file (like Gandalf - actually you should download this anyway, it has some useful tools you might need later on), and boot into that instead. Depending on the output of those commands, you may be able to just run the automatic installer without worries.
Sent from my LG-D855 using Tapatalk
obook20 crashed
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
alexander137 said:
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
Click to expand...
Click to collapse
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
SirVer said:
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
alexander137 said:
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
Click to expand...
Click to collapse
Just press it down for a long time, at least 10 seconds, that'll do it. For some reason it takes a really long time to force shutdown. If that doesn't work, then there might be an issue with your hardware. Also try typing the "exit" command - it should put you into the BIOS menu directly.
Sent from my LG-D855 using Tapatalk
Hi XDA community, since I don't have enough power to land this on other forums I choose here.
First, this is my disclaimer:
Please try this at home at your own risk, the steps performed on this guide worked for me and may work for you.
Click to expand...
Click to collapse
But come on, this is XDA, you will figure it out without problems.:fingers-crossed:
Second, the good thing about this is you only need 3 ingredients:
Old tablet, The HP Stream 7 tablet SPECS
Precious Disk Space :victory:
Sweet Internet
W00t? no USB or Keyboard required? Yes, that's why it took me a while to glue the pieces together. Now, here we go:
I suggest to download PhoenixOS (November Release v1.1.2-226), because it worked for me immediately, I have an issue with RemixOS that I didn't try to fix it yet, I got stuck on the "Select Language" screen, but the steps may work for you.
Now, free disk space on your tablet, I did the upgrade to Windows 10 a while back and I had almost 1GB left on C, that's ridiculous because the drive has 20GB-ish, so, I google (yes, you need to do your homework too because I did the steps on the fly) how to recover space from the greedy Windows 10 OS, I removed a lot of useless info/cache/downloads/apps/etc and even compressed the Windows binaries (yes, you can do that). Concerned about Windows performance? be not, it works faster than ever. After the next steps this may seem useless but free space is free space, you'll need it later on life.
After all that dark magic, I was able to reclaim 10GB-ish, yeah!, but then realized I had 8GB more on the tablet "lost", this is the recovery partition for Windows 10, now, this is something that you may think of because you can get rid of all that info and reclaim what is yours, that partition is for you, but maybe you wont so this is one of these life choices. I did, I don't care about recovery stuff, most of my gadgets have custom ROMs or OSes. Used Minitool Partition Wizard Free and managed to reclaim the precious Disk Space.
Important thing here, some users Shrink the drive C to create a new partition, I didn't, used the 8GB partition instead.
We have Disk Space available, now, we prepare the operations table:
Disable Bitlocker on the drive you want to install the new OS.
Disable Secure Boot, power off the device and press Power+VolDown for a few seconds until you're on the BIOS.
Boot on Windows and install the Android OS flavor you want, I'll split the installation in two because for RemixOS is harder.
NOTE: Remember that grub doesn't support touch and both Android OSes grub have Windows as first OS to boot and kids, there is the key.
PhoenixOS
Download the OS
Extract it and run the installer
Select install to Hard Drive and install it on the Drive desired (I did that on E: which is the 8GB partition).
Restart and let the system do the job, you'll land on Windows again.
In Windows, as you read on the NOTE, we need to change grub.
Open Windows Powershell ISE in Admin mode (yeah yeah, yo can use whatever you want)
Then execute the command
Code:
mountvol B: /s
With this you'll be able to see the contents from the UEFI partition
Now, remember to select view all files, with WPISE open the grub.cfg file located on
Code:
B:\EFI\PhoenixOS\
Put the Windows entry below the PhoenixOS entry, change the grub timeout to 3 or whatever timeout you want, this change is for faster boot, save the file and you're ready to go.
Restart the system, press Power+VolDown -> F9, Select the PhoenixOS, let grub do the magic and you win
Notes about PhoenixOS
Phoenix OS installation, straight-forward on the 8GB partition
Needed to change Grub but friendlier than RemixOS
Keyboard behaves weird, you need to be accurate when using your fingers
When using browser and playing videos the tablet heats up hard
Rotation is wrong, I selected not to use rotation so I can use the UI without problems
Is fast, Wireless work
Something I saw one time is it got stuck when showing my user recently booted, restarted the device and then it worked again.
Video after the break.
Veredict: It works for me and can play with Android in a tablet without the need to buy another.
RemixOS
It supposed to have more support for things but looks like PhoenixOS has more . Not going to start a war here, I always try to find what suits best for me .
RemixOS is a pain on this tablet with the newest November 2016 version, I need to play more and harder.
You do almost the same as PhoenixOS, the installer is easy as well but it shows you an installation issue the first time, you need to restart the device and try the installation again. After that it was a game of try and fail but I sorted out the pieces.
Restart and you'll be on Windows again, well, let the system land on Windows and modify grub, kind of same as PhoenixOS:
Open Windows Powershell ISE in Admin mode
Then execute the command
Code:
mountvol B: /s
With this you'll be able to see the contents from the UEFI partition
Now, with WPISE open the grub.cfg file located on
Code:
B:\boot\grub\
Remember to select view all files
Put the Windows entry below the RemixOS entries, save the file, change the timeout and you're ready to go.
For RemixOS you also need to change the timeout for the theme.cfg file on
Code:
B:\EFI\RemixOS\
Restart the system, press Power+VolDown -> F9, Select the OS Bootloader, let grub do the magic (after some errors, just let it be) and you win (see, no hands mom!), well, sort of because it freezes :silly:.
I'll try to do more tests with RemixOS and see what happens.
Is this guide enough for you, not? blame the Internet or leave your comments.
Enjoy.
Thanks for the info.
I'm not getting any sound with PhoenixOS. WiFi is OK but sound & Bluetooth is not functional. Any suggestions ?
I've experimented with RemixOS as well...... sound works but it's very laggy and touch-screen / rotation is unresponsive. PhoenixOS is very stable and far far better but no sound :crying:
android x86 nougat on hp stream 7
Try this ISO of Android Nougat on the Stream 7, Wifi Bluetooth & Audio work. touchscreen is a little sensitive
Search youtube for HP Stream 7 for a link to the ISO.
I'm not aloud to post links on hear
mlckchip said:
Try this ISO of Android Nougat on the Stream 7, Wifi Bluetooth & Audio work. touchscreen is a little sensitive
Search youtube for HP Stream 7 for a link to the ISO.
I'm not aloud to post links on hear
Click to expand...
Click to collapse
Could you please explain the installation instructions?
Any news? I tried newest phoenix, but it´s way too heavy for it. Runs very slow. The older lollipop works better. The touchscreen is more a problem, it´s like a tablet from hell, very bad sensitivity.
The "Trekstor Surftab Xintron i 7.0" should be the same hardware and has android, so there could be a way to install this or at least use the touchscreen drive in phoenix. But I´m afraid of bricking it.
Step by step guide for Oppo R9s Plus international version
This is for the Oppo R9s international version cph1611
1. First download the files from this folder (alternative links at the end of the post):
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0 )
2. Than first install the Oppo driver.
For Windows 7 just install the QcomMtk_Driver_Setup.exe and test later.
2. For Windows 10 you'll have to shutdown/power off your phone, than connect it to your usb, while pressing Vol+ and Vol- at the same time, until you plugged it in. Then go to your device manager and search for new hardware.
It will find a new device without proper driver. Install the driver from the Win10_Qualcomm.rar manually.
It will say the driver is not verify able, just install anyway.
After that check your device should now be listed as something like: qualcomm hs-usb qdloader
3. Register the oppo.reg
4. Than extract the file CPH1611EX_11_A.01_161210.tar.bz2 (don't know which programme do that under windows. i used ubuntu to extract, I saw 7zip should do it)
5. Extract the recovery.img into the same folder as the files from CPH1611EX_11_A.01_161210.tar.bz2, or MsmDownloadTool.exe will not start.
6. Power off your phone completely, by pressing the Power Button long and slide to shut down.
7. Connect your phone to usb, while pressing Vol+ and Vol- at the same time.
8. Check your device manager, it should show something like Qualcomm HS-USB QDloader ............
9. Inside the extracted folder from CPH1611EX_11_A.01_161210.tar.bz2 folder, you will find the tool: MsmDownloadTool.exe
Open it and set language as you need. After opening press F5. A pop up menu will appear. There deselect all, but recovery.img and boot.img (if you wanna keep your private data).
For the recovery.img you need to choose your file by clicking into the right side of the pop up menu and search for the location.
10. Flash your phone
11. After successful flashing, power the phone on by pressing: Vol+ and Vol- and Power at the same time.
After power comes on (short vibrate, display shows Oppo) switch directly to pressing Vol- and Power button to boot into the new twrp recovery.
12. From there you can install supersu (.zip file have to be copied into your phones memory, than install in twrp)
13. Reboot (don't need to wipe cache/data)
Install xposed and than whatever you want
Install hookup for ColorOs3.0 to get rid of root warning (It is in chinese, but don't panic, just switch on all options and your done)
Let me know, in case the link above goes down.
I will add pictures for better understanding, when I have time.
Have fun with your rooted phone
{
"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"
}
ALTERNATIVE DOWNLOAD LINKS:
First download this:
https://yun.baidu.com/share/link?uk=797461041&shareid=616882441
and this
http://rapidgator.net/file/5a9de514b0a8431a373cbe9aa92811f8/recovery.zip.html?
and than the drivers from here (check what you need win10: Win10Qualcomm.rar / win7: QcomMtk_driver_setup.exe also grab the oppo.reg file)
https://pan.baidu.com/s/1qXVAbDy#li...9s/线刷万能root&twrp教程&parentPath=/android/第三方ROM
i cant choose recovery.img explorer popup wont come out... do you knoe how to figure out it ?
Sent from my MI MAX using XDA-Developers Legacy app
for god sake, what's so hard about using mega or ****ing dropbox, why would you post an international root on a site in chinese
---------- Post added at 01:46 AM ---------- Previous post was at 01:43 AM ----------
D1G1LANT3 said:
for god sake, what's so hard about using mega or ****ing dropbox, why would you post an international root on a site in chinese
Click to expand...
Click to collapse
please post the files somewhere more convenient that doesn't ask us to sign up
D1G1LANT3 said:
for god sake, what's so hard about using mega or ****ing dropbox, why would you post an international root on a site in chinese
---------- Post added at 01:46 AM ---------- Previous post was at 01:43 AM ----------
please post the files somewhere more convenient that doesn't ask us to sign up
Click to expand...
Click to collapse
i just collected the links.
like i said all credit goes to xu wailin (reason for the chinese sites)
but for you all, i'm re-uploading the complete package with hookup to dropbox. just give me a few days, while my upload here is terrible slow (thailand standard). will post as soon as all is up.
Hey guys,
here the new upload:
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0
I also repacked the files in the tar.bz2 to a normal .zip added hookup to remove root warning etc.
for hookup:
after installation go to exposed and activate hookup. IT IS IN CHINESE! but don't worry. just activate all options (all slide buttons) and you are done.
no root warning etc.
have fun and tell me if the new archive is ok. haven't tested it yet.
D1G1LANT3 said:
for god sake, what's so hard about using mega or ****ing dropbox, why would you post an international root on a site in chinese
---------- Post added at 01:46 AM ---------- Previous post was at 01:43 AM ----------
please post the files somewhere more convenient that doesn't ask us to sign up
Click to expand...
Click to collapse
actually no sign up needed. just download through ubuntu (you can also you use a live cd)
i tried first under windows too and couldn't register my thailand number on baidu. i than switched to my zorin installation and voila, no problem for downloading.
here my new drobbox link. maybe this is more convenient for you?
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0
Ok, just tested and can't extract the recovery.img from .zip.
let me know if you have the same probelm? i will reupload tonight
sebj84 said:
Ok, just tested and can't extract the recovery.img from .zip.
let me know if you have the same probelm? i will reupload tonight
Click to expand...
Click to collapse
Msm download tool doesn't start even when run as administrator (Windows 10). All the dropbox files work tho so thankyou!
D1G1LANT3 said:
Msm download tool doesn't start even when run as administrator (Windows 10). All the dropbox files work tho so thankyou!
Click to expand...
Click to collapse
did you install the oppo drivers before? and register the .reg? i could open it after download.
anyhow. i will upload the tar.bz2 file again and the recovery.img. think while zipping there got something broke.
OK, I reuploaded the recovery.zip already. can open now. already on the upload for the tar.bz2 file will finish in the next 10 min. (internet at work is nice and fast i see). you can still use the old folder link. unpacking the tar.bz2 -> 7zip should do it, but i never tried it under windows
sebj84 said:
OK, I reuploaded the recovery.zip already. can open now. already on the upload for the tar.bz2 file will finish in the next 10 min. (internet at work is nice and fast i see). you can still use the old folder link. unpacking the tar.bz2 -> 7zip should do it, but i never tried it under windows
Click to expand...
Click to collapse
OK all up again.
have fun with you rooted phone!
D1G1LANT3 said:
Msm download tool doesn't start even when run as administrator (Windows 10). All the dropbox files work tho so thankyou!
Click to expand...
Click to collapse
ok re-up already. try the tar.bz2 and the recovery.zip. should work now.
use 7zip for tar.bz2 or anything else that can unzip under windows. add the recovery.img to the same folder as the firmware and the msmdownload tool (it has to be all in one folder) if not msmdownloadtool won't start
sebj84 said:
did you install the oppo drivers before? and register the .reg? i could open it after download.
anyhow. i will upload the tar.bz2 file again and the recovery.img. think while zipping there got something broke.
Click to expand...
Click to collapse
Yeah I had an issue installing the drivers, when i chose the driver files it said they were already up to date.. I followed everything else though. If you updated the .zip I'll try again but it could be a problem with my PC, I'll try again.
Step by step guide for Oppo R9s Plus international version
Step by step guide for Oppo R9s Plus international version
This is for the Oppo R9s international version cph1611
1. First download the files from this folder (alternative links at the end of the post):
https://www.dropbox.com/sh/qbobokagdgme2oa/AABQBtKTmbwChne9z1DaayHca?dl=0
2. Than first install the Oppo driver.
For Windows 7 just install the QcomMtk_Driver_Setup.exe and test later.
2. For Windows 10 you'll have to shutdown/power off your phone, than connect it to your usb, while pressing Vol+ and Vol- at the same time, until you plugged it in. Then go to your device manager and search for new hardware.
It will find a new device without proper driver. Install the driver from the Win10_Qualcomm.rar manually.
It will say the driver is not verify able, just install it anyway.
After that check your device should now be listed as something like: Qualcomm HS-USB QDloader
3. Register the oppo.reg file
4. Than extract the file CPH1611EX_11_A.01_161210.tar.bz2 (don't know which programme do that under windows. i used ubuntu to extract / I saw 7zip should do it)
5. Extract the recovery.img into the same folder as the files from CPH1611EX_11_A.01_161210.tar.bz2, or MsmDownloadTool.exe will not start.
6. Power off your phone completely, by pressing the Power Button long and slide to shut down.
7. Connect your phone to usb, while pressing Vol+ and Vol- at the same time.
8. Check your device manager, it should show something like Qualcomm HS-USB QDloader ............
9. Inside the extracted folder from CPH1611EX_11_A.01_161210.tar.bz2 folder, you will find the tool: MsmDownloadTool.exe
Open it and set language as you need. After opening press F5. A pop up menu will appear. There deselect all, but recovery.img and boot.img (if you wanna keep your private data).
For the recovery.img you need to choose your file by clicking into the right side of the pop up menu and search for the location.
10. Flash your phone
11. After successful flashing, power the phone on by pressing: Vol+ and Vol- and Power at the same time.
After power comes on (short vibrate, display shows Oppo) switch directly to pressing: Vol- and Power button to boot into the new twrp recovery.
12. From there you can install supersu (.zip file have to be copied into your phones memory, than install in twrp, NOT extract before, twrp can only handle .zip files)
13. Reboot (don't need to wipe cache/data)
Install xposed and than whatever you want
Install hookup for ColorOs3.0 to get rid of root warning (It is in chinese, but don't panic, just switch on all options and your done)
Let me know, in case the link above goes down.
I will add pictures for better understanding, when I have time.
Have fun with your rooted phone
)
ALTERNATIVE DOWNLOAD LINKS:
First download this:
https://yun.baidu.com/share/link?uk=797461041&shareid=616882441
and this:
http://rapidgator.net/file/5a9de514b0a8431a373cbe9aa92811f8/recovery.zip.html?
and than the drivers from here (check what you need win10: Win10Qualcomm.rar / win7: QcomMtk_driver_setup.exe also grab the oppo.reg file)
https://pan.baidu.com/s/1qXVAbDy#li...9s/线刷万能root&twrp教程&parentPath=/android/第三方ROM
D1G1LANT3 said:
Yeah I had an issue installing the drivers, when i chose the driver files it said they were already up to date.. I followed everything else though. If you updated the .zip I'll try again but it could be a problem with my PC, I'll try again.
Click to expand...
Click to collapse
I think you forgot to power off? Power off your phone. than connect it to your pc while pressing VOL+ and VOL- until plugged into usb. than you should be able to install the drivers.
if not try to uninstall your old drivers, reboot and than repeat the steps above.
you use win7 or win10?
sebj84 said:
I think you forgot to power off? Power off your phone. than connect it to your pc while pressing VOL+ and VOL- until plugged into usb. than you should be able to install the drivers.
if not try to uninstall your old drivers, reboot and than repeat the steps above.
you use win7 or win10?
Click to expand...
Click to collapse
I'm certain I've followed the instructions correctly. The msmdownload tool just wont open and i made sure the recovery.img is there as well im running windows 10
D1G1LANT3 said:
I'm certain I've followed the instructions correctly. The msmdownload tool just wont open and i made sure the recovery.img is there as well im running windows 10
Click to expand...
Click to collapse
hm. i saw that the old. zip had a problem for me as well.
try the .tar.bz2 and recovery.zip, i've uploaded today.
the files out of those two archives are working (for me)
i've deleted the .zip from the dropbox folder already
wow all these files look really familiar
---------- Post added at 11:03 PM ---------- Previous post was at 10:41 PM ----------
D1G1LANT3 said:
I'm certain I've followed the instructions correctly. The msmdownload tool just wont open and i made sure the recovery.img is there as well im running windows 10
Click to expand...
Click to collapse
Referring to the Chinese user guide, it did say drivers definitely work on Windows 7, the drivers for windows 10 didn;t work for some users. So Master Wu highly recommend users to root in Windows 7 platform.
If msndownloadtool appears as "unauthorized", please open msndownloadtool0.exe hack version and exit, then open msndownloadtool.exe version.
In your case, I suspect your drivers are not properly nstalled on your Windows 10. Don't ask me why but this does happen to some users.
carlochiefsg said:
wow all these files look really familiar
---------- Post added at 11:03 PM ---------- Previous post was at 10:41 PM ----------
Referring to the Chinese user guide, it did say drivers definitely work on Windows 7, the drivers for windows 10 didn;t work for some users. So Master Wu highly recommend users to root in Windows 7 platform.
If msndownloadtool appears as "unauthorized", please open msndownloadtool0.exe hack version and exit, then open msndownloadtool.exe version.
In your case, I suspect your drivers are not properly nstalled on your Windows 10. Don't ask me why but this does happen to some users.
Click to expand...
Click to collapse
I don't have a windows 7 pc, would a virtual machine running windows 7 do the trick?
D1G1LANT3 said:
I don't have a windows 7 pc, would a virtual machine running windows 7 do the trick?
Click to expand...
Click to collapse
Might work. I generally used virtual machine for jail breaking
---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------
D1G1LANT3 said:
I don't have a windows 7 pc, would a virtual machine running windows 7 do the trick?
Click to expand...
Click to collapse
Did you disable drivers signature in windows 10 before you install Oppo drivers?
{
"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"
}
Live Linux System:
It can be run on any Computer as:
Burn into a CD, or USB Flash Drive, boot into any Computer
Run it as a Virtual Machine using any Virtualization Software
355 MB iso file
Click HERE to Download HP_Touchpad Novacom Repair Android
Novacom Drivers to load:
TPToolBox by jcsullin -- Reflash battery A6 Firmware ( Only)
Create Boot -- Repair boot
TWRP Recovery 3.2.1 by Flintman -- Flash any Android ROM
Wipe All Create Android with Swap Partition -- Make Tablet 100% Android with Swap
Make changes to Android
Android Debug Bridge ( ADB ) -- Control and make changes to Tablet using TWRP Recovery or Android
Media Transfer Protocol ( MTP ) -- Transfer files using TWRP or Android
Ramdisk -- Customized all settings for the Tablet
VNC Server -- Allows to control a connected HP Touchpad from anywhere.
VNC Viewer -- Connect to VNC Server to make changes to any connected HP Touchpad
Web Browser -- Download any ROM or flash file need it to update the HP Touchpad.
How to Videos:
User Interface
Load the ToolBox
Ramdisk from zip flash files
Ramdisk from /boot uImage
Screenshots:
How to Burn the ISO file onto a CD; USB Flash Drive or use it as a Virtual Machine
The Palm Novacom Driver is the essential to communicate with the HP Touchpad to repair it, if is not booting into the moboot menu.
The drivers are not been updated and must be install on old Operating System to work properly. As new PC Operating System are updated the Palm Novacom Driver may become unstable or not work at all.
The provided ISO file is a Puppy Linux 32 bit compatible with Ubuntu Bionic (Latest version)
Click HERE for the Original Version of BionicPup32
Click HERE for the Puppy Linux Main Web Page
Basic instructions:[/U][/B][/SIZE][/COLOR]
To burn the ISO file to a CD, use the Operating System software or the free ImgBurn.exe for Windows
Click HERE for ImgBurn for Windows
Use it in a Virtual Machine
Click HERE for Virtual Box
Click HERE for VM WARE Player
To create a boot-able Live USB drive using UNetbootin:
Click HERE to Download UNetbootin for Windows, Linux and MacOS
Good news HP_TOUCHPAD,
It seems like I am the first 'layman' to install HP_TOUCHPAD's Novacom repair tool.
I feel like the first man on the moon! Because it was quite an adventure.
First I had to mount an E: drive using Virtual Clone Drive software so I could place the HP_Touchpad_Novacom_Repair_Android.iso file on that drive. This step did not need to be done, but I am glad I did it because I was able to see all the indivual files that made up the .iso file. As you see in the below pic on drive E:
Then I installed and ran the VM player and loaded the .iso file, but it was complaining that the setting vt-X had to be enabled. So I actually had to go into my PC's BIOS to enable that setting. But as you see in the below pic everything is working now, I just plugged in my Touchpad to my PC, and ran the Toolbox option, and would you believe it, the toolbox came up on my Touchpad, and then I reset the batteries A6 firmware with it. I also tested the WipeAll icon and it also worked with success.
So this tool that HP_TOUCHPAD has created would make J.C. Sullins proud.
DoubleStuff said:
Good news HP_TOUCHPAD,
It seems like I am the first 'layman' to install HP_TOUCHPAD's Novacom repair tool.
I feel like the first man on the moon! Because it was quite an adventure.
So this tool that HP_TOUCHPAD has created would make J.C. Sullins proud.
Click to expand...
Click to collapse
You did it the hard way and congratulations!
There is no need to mount the ISO file.
In the Virtual Machine Software, on your case VM Ware Player, just select the ISO file as the operating system to install, remember there is no installation is a Live CD. On the Virtual Machine settings it only needs 1GB of RAM to run or less. Just Run the Virtual Machine and as it shows, once you connect the Tablet to the host then it will ask if you want to connected to the guest machine. Using a Virtual Machine allows not to reboot your Main PC ( host ).
There is no worries about upgrading windows or any OS in fear that the Palm Novacom driver will stop working.
This should work in a Virtual Machine environment for EVER until we die, because the Tablet will keep working.
Burning a CD or a USB flash drive will allow to boot into any PC, anywhere you go. If anyone finds an HP Touchpad in a dumpster somewhere, using this ISO will provide everything need it to have all done from a complete data reset, to the ToolBox and installing any ROM !
HP could have done the same and use the WebOS Dr, on a Linux CD, providing the Palm Novacom drivers and all the details, it would have avoid a lot of confusion with the boot symbols, but to save half a penny it was not included in the box with the Tablet and now the Palm web site is down with no option for a regular user to get the Tablet working. The ToolBox is an Arm Linux architecture of 67MB that loads into memory.
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue. I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work. BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it. I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them. That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
smithylovestouchpad said:
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue. I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work. BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it. I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them. That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
Click to expand...
Click to collapse
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready. That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD, but I guess he did not reply to HP_TOUCHPAD's request to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
smithylovestouchpad said:
I'll leave all this hocus pocus to your guys. I have two Windows 10 laptops with Novacom drivers installed and they work fine. I did have the one PC where the driver became corrupted, but a simple uninstall/ reinstall fixed it without issue.
It took you very long time to figure that out to a point of just given up, go to this post:
https://forum.xda-developers.com/showpost.php?p=80016636&postcount=406
And there was more than that,
I personally don't subscribe to one must use a PC with an old operating system installed to get Novacom to work.
Eventually it will come to that, in the software business nothing has lifetime support, the codes are changing with every update. That is why Virtualization has become so important, any software or Operating system can be use on new hardware if need it, or have a Live Linux CD to repair a broken Operating System. Is not hocus pocus, it is how is done at the present time.
BTW, what do you call an old operating system, XP? After 9 years of playing of with TouchPads, I have never had a problem installing or using Novacom. Any driver can become corrupted on any PC and a simple reinstall will fix it.
You did not know the driver was corrupted, had to use another PC to resolve the issue and any OS update can render the driver useless and the user will not even know it and then again blame the Tablet for been ""brick".
Old is when the Software Company will not update the OS anymore, on January 2020 Windows 7 becomes OLD.
I have never not been able to fix a driver issue on any PC that reinstalling the driver did not fix the issue. I am not saying that your method does not have a place in someone's software toolbox. But Novacom is so easy to install. Just right click on the Novacom Installer and click "Install" and in few seconds, it is installed. Put the TPTBv42, TWRP or WipeAll batch files in the Palm, Inc. folder and run them.
It is not as easy as you are stating, you are the perfect example. You did not know how to load an uImage into the Tablet. The user must be aware and know how to use the novacom command
novacom boot mem://
That just seems so much easier than burning ISO's to CD' s or thumb drives or in VM's and watching all these tutorials to learn how to use your Novacom Repair method. I'm not a software junkie like you guys. I like straight forward and simple. And one click to install Novacom is SIMPLE!
Having the Novacom installed on any PC will not fix any Tablet when connected. Plug in a tablet with the triangle or USB symbol to any of your PC with the novacom driver and it will not even show anywhere.
What does the user do then?
Connect the Tablet to an up to date OS and it will not recognized it, not even automatically download the drivers for it from the OS update servers, which in theory by Plug and Play any device connected to the new OS should be recognized and automatically search and install the driver.
Hats off to you HPTP for creating an interesting method. Just not my cup of tea.
Smithy
Click to expand...
Click to collapse
On the next Operating System upgrade, the support for old drivers could be block or it could actually crash the system. Does that mean the PC can not be updated or maintain just to use the Novacom drivers to get something done on the Tablet.
Every user can use any method that is easier for them, but the more options and solutions the better as you never know when it maybe need it.
DoubleStuff said:
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready. That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD, but I guess he did not reply to HP_TOUCHPAD's request to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
Click to expand...
Click to collapse
I was always under the impression that all this is open source. That as long as credit was given, one could modify and adapt any thing related to Android, Linux and the like. Why would Sullins care if HPTP updated and improved TPTB? If he has the knowledge and skills, all five or ten of us who still use a TouchPad would benefit. When you run TPTB, no where do you see anything about it being copyrighted or that modifying or improving it is prohibited. Where people get in trouble, they take a program or app, rename it, put their name on it and put it out as their own.
So what is going on concerning ttinstall in another thread? Link?
Smithy
---------- Post added at 03:34 AM ---------- Previous post was at 03:21 AM ----------
HP_TOUCHPAD said:
On the next Operating System upgrade, the support for old drivers could be block or it could actually crash the system. Does that mean the PC can not be updated or maintain just to use the Novacom drivers to get something done on the Tablet.
Every user can use any method that is easier for them, but the more options and solutions the better as you never know when it maybe need it.
Click to expand...
Click to collapse
You missed commenting on a couple of statements I made, 1. I am not saying that your method does not have a place in someone's software toolbox. 2. Hats off to you HPTP for creating an interesting method. It's just not my cup of tea. Those were complements.
Lastly, you are WRONG, I did and do know how to load a uImage, it was the corrupted Novacom driver that was throwing me a curve. Once I used a second PC to prove it could be done, I went back to the first PC, and reinstalled the Novacom drivers. That's called trouble-shooting pal. And your link to post 406 proves my point.
Smithy
DoubleStuff said:
All valid points Smithy, I too have Novacom installed on my Windows 10 64bit laptop, but last time I checked more and more Novacom links to install the software were broken and they were getting harder to find, and I was hearing of others having issues trying to install it on newer PC's.
The universal Novacom installer stopped working long ago, it was an interesting and effective concept back then.
So the idea of having a Novacom permanently ready to go appealed to me, in case, when we go to Windows 11 or 12 and Novacom does not install, I have learned this new method and will be ready.
It is 100% reliable every single time, and if use on a Virtual Machine the user can fix the Tablet no matter what type of OS or how new the PC, as long as it has USB ports.
That being said, I dont really use my Touchpads too much, I just like playing around with new install methods and reading these threads on XDA, and maybe helping a newbie or two. Like you said it would be fun if JC Sullins came back for a day or two and made some final comments on the state of the HP TOUCHPAD,
The HP Touchpad is a Palm device that uses WebOS. The experts for this type of operating system can be found at
https://www.webosnation.com/
but I guess he did not reply to HP_TOUCHPAD's request
I did not contacted JC Sullins as the account on XDA has not been active.
to have permission to change the TP Toolbox code for some important modifications that have been needed since 2015 and the advent of incompatible zips. Boy that term is also a blast from the past as was "ttinstall" which is going on in another thread as we speak.
Click to expand...
Click to collapse
The thread about modifying the ToolBox can be found on my guide, read it !
https://forum.xda-developers.com/hp-touchpad/general/Click HERE for how to modify the ToolBox
Also to mentioned, the HP Touchpad is the perfect Device to learn Android OS. If you have an Android Smartphone, is risky to modified the OS or make changes, it can be bricked and no way to make a phone call !
The Tablet can be use as the experiment device and see how the internal of the OS works.
One of the most important is the Ramdisk, which required a Linux OS. The user have total control by using this ISO to make any permanent modification and learn. It is not only an OS with Novacom Driver, read the guide again for everything that it can do.
smithylovestouchpad said:
I was always under the impression that all this is open source.
I know Andriod is open source and most of the developers like Flintman et all post their source on github which is open to the public. But as per JC Sullins TPTB this is posted on some of his code.
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
That as long as credit was given, one could modify and adapt any thing related to Android, Linux and the like. Why would Sullins care if HPTP updated and improved TPTB? If he has the knowledge and skills, all five or ten of us who still use a TouchPad would benefit.
LOL, 5 or 10 users, that is funny and you maybe right that their is 5 or 10 "regulars" who post on these threads, but I have posted the number of downloads of the alternate method
and its in the thousands. And even the most recent zip I posted in July already has over 300 downloads.
When you run TPTB, no where do you see anything about it being copyrighted or that modifying or improving it is prohibited. Where people get in trouble, they take a program or app, rename it, put their name on it and put it out as their own.
So what is going on concerning ttinstall in another thread? Link?
look at the last couple of pages of this link you will see the ttinstall mentioned
https://forum.xda-developers.com/hp-touchpad/general/android-9-pie-dirty-unicorns-v13-0-t3911621
Smithy
Click to expand...
Click to collapse
See my comments in blue above.
---------- Post added at 09:50 PM ---------- Previous post was at 09:35 PM ----------
HP_TOUCHPAD said:
snip....
I did not contacted JC Sullins as the account on XDA has not been active.
snip...
Click to expand...
Click to collapse
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179[/QUOTE]
Again read this specific post:
https://forum.xda-developers.com/showpost.php?p=78649680&postcount=3
Probably a request was never sent, it was a discussion on how to removed the restriction of installing only specifics ROMs. Keep in mind I am not a developer and not connected to that side of the spectrum, I looked for an alternative and found out that I could use TWRP to re-partition and use TWRP to flash any ROM and that is where the Wipe_All came to be.
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
https://www.sheldonsblog.com/cant-download-novacom-drivers-for-windows-to-connect-hp-touchpad/
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
---------- Post added at 04:35 AM ---------- Previous post was at 04:29 AM ----------
HP_TOUCHPAD said:
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
Click to expand...
Click to collapse
Again read this specific post:
https://forum.xda-developers.com/showpost.php?p=78649680&postcount=3
Probably a request was never sent, it was a discussion on how to removed the restriction of installing only specifics ROMs. Keep in mind I am not a developer and not connected to that side of the spectrum, I looked for an alternative and found out that I could use TWRP to re-partition and use TWRP to flash any ROM and that is where the Wipe_All came to be. [/QUOTE]
You know there is an easy work-around. Just use one of the compatible recoveries and gapps files available and immediately after installing, flash the updated version of TWRP. Worked like a charm for me when I reverted my TP back to Sullin's CM11 sans swap. Fresh start, complete data reset and all that.
Smithy
P.S. I agree with DS, sure looks like some kind of contact with Sullins was attempted.
smithylovestouchpad said:
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
Click to expand...
Click to collapse
Thanks Smithy I clicked the link and dowloaded the NovacomInstallers and put them on a
thumb drive along with HPTP's .iso file, because you never know how long these "rogue" links
will be up, and when I am going to need it.
As per contacting JCSullins controversy, I can't find the link, but I believe Flintman tried to contact him about the TPTB code back in the Evervolv 5 days, and maybe even some others have tried, and of course Sullins XDA has been inactive for quite a while, but I am sure ( he is no dummy ) he has probably created a new account and comes on here and poses as a newbie once in a while.
I am hearing rumors now that Android Q, will not be named after a tasty treat, because these treats names, Petit Four, Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, IceCream Sandwich, JellyBean, KitKat, Lollipop, Marshmallow, Nougat, Oreo and Pie even though popular treats in the USA, does not mean these treats have worldwide appeal, nor were they fully understood in other languages. So I am hearing Android Q will just be named Android 10, so I guess
we have reached an "end of an era".
Quote:
LOL, 5 or 10 users, that is funny and you maybe right that their is 5 or 10 "regulars" who post on these threads, but I have posted the number of downloads of the alternate method and its in the thousands. And even the most recent zip I posted in July already has over 300 downloads.
Good to know there are a few lurkers out there who choose to take but not participate. It's nice to get feedback on your work as well as an occasional thanks.
Quote:
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
Would have been nice if he has posted that in the OP of his thread instead of burying it in his code. I'm not a lawyer, but just because you put that claim of being copyrighted out there does not mean it is. I doubt if he actually ever filed the paperwork to copyright TPTB. Although as arrogant as he always came across, he just might have done so. God forbid that someone else could help improve on HIS work.
Smithy
DoubleStuff said:
See my comments in blue above.
---------- Post added at 09:50 PM ---------- Previous post was at 09:35 PM ----------
DoubleStuff says,
Ok well somebody did, because I am quoting your comment from this post below...
HP_TOUCHPAD says,
It could be the only file to load, but I am not going to change it, a request was sent to jcsulling for permission, but no replied. Anywhere jcsullins is " Many Thanks"
see this post for context:
Post #179
Click to expand...
Click to collapse
Just curious, so you create this Linux Live CD or run this operating system in a virtual machine and regardless of the PC you run it on, it is going to work? So Linux contains all the drivers needed to work on all the hardware out there, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba, desktop, laptop, regardless?
Smithy
smithylovestouchpad said:
snip.....
Would have been nice if he has posted that in the OP of his thread instead of burying it in his code. I'm not a lawyer, but just because you put that claim of being copyrighted out there does not mean it is. I doubt if he actually ever filed the paperwork to copyright TPTB. Although as arrogant as he always came across, he just might have done so. God forbid that someone else could help improve on HIS work.
snip.....
Smithy
Click to expand...
Click to collapse
I agree with you on the copyright Smithy, because recently a music artist named Katy Perry was sued by Flame, because Flame said Katy Perry copied from his song, when she created the song "Dark Horse", if only Katy would have given Flame some kudos/credit for the song, I think Flame would have been OK with it. Plus HPTP wants people to "save a click" and not even press the thanks button, I am sure he does not want any money for his work. So if he gets sued, what is 50% of $0.00, you guessed it a big zero. LOL. I have learned so much over the past 2 years because of everybodies work in trying to improve the touchpad install method, that its worth it for me. But I wish JCSullins could come back for a day or two and tell us his final summary of the past 4 years.
And maybe JC could mend the fences with some people he was at odds with, it would be like the big reunion of Jerry Lewis and Dean Martin, after they had that bitter split for for 20 years, finally reunited during the 1976 Jerry Lewis Telethon.
smithylovestouchpad said:
Just curious, so you create this Linux Live CD or run this operating system in a virtual machine and regardless of the PC you run it on, it is going to work? So Linux contains all the drivers needed to work on all the hardware out there, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba, desktop, laptop, regardless?
Smithy
Click to expand...
Click to collapse
@smithylovestouchpad
All your comments, suggestion and critics are well welcome. The most valuable asset of the thread are the comments, questions, answers and debate, that's what we learned from. Nobody has to agree or use any specific method, but the most important is to post valuable and helpful information for any user to have the best experience using the HP TP.
On the Linux Operating System the drivers are incorporated into the Kernel, there are many versions of Linux with different Kernels. Most Linux OS can boot on any Computer and provide support for a lot of hardware and devices, Dell, HP, Lenovo, Sony, Asus, Acer, Toshiba and Apple. All those Personal Computer brands use the same Processor, Intel or AMD with same technology standards. Linux is very powerful it does not need to be install to run on a computer, is call a Live CD or (USB Flash drive).
An example:
The computer hard drive is failing and not booting into the OS, or the boot sector is damage. A Linux (CD) (USB) can be connected to the computer and it loads the Linux OS into memory ( RAMDISK ). Data can be copy from the failing hard drive or the boot sector can be restore, it can resolve many issues.
The Linux version used for the HP Touchpad Novacom Repair is based on Puppy Linux compatible with Ubuntu Bionic. If you read the info the OS is less than 300 MB with more software support that of a full modern OS. It will boot on any Computer, from 20 years ago to the most current. The computer does not need a hard drive and no more than 1GB of RAM. The smallest Linux Distro is Tiny Core :
https://distro.ibiblio.org/tinycorelinux/downloads.html
Is a 16 MB Operating System that support most computers with Graphics, Sound, Networking, Mouse, Keyboard, CD, Hard drive.
The most current FireFox browser can be install to a total OS of about 200 MB and is all loaded into Memory and due to that even a computer that is about 15 years old will browse the web faster that any new one !
Booting from a Virtual Machine will work 100 % on anything even on an ARM processor. It can even be run on any modern Android Smartphone, meaning your phone can connect to the Tablet to repair it.
Virtualization adds a layer of software codes that mimic the hardware that the OS needs to run from.
Puppy Linux is the distro that I found small enough that supports the Novavcom Driver and allows for the Ramdisk to be modified. At only 355 MB total it can be copy onto a 1GB flash drive and still have 700 MB for extra files. It can be boot on any old computer, with no hard drive, monitor, keyboard or mouse. The only thing extra is a network card and USB port. Once it boots VNC Server is active and using VNC Viewer it can be control remotely. There are many ways on using it but no matter how, it will always work as intended.
DoubleStuff said:
Plus HPTP wants people to "save a click" and not even press the thanks button, I am sure he does not want any money for his work. So if he gets sued, what is 50% of $0.00, you guessed it a big zero. LOL.
Click to expand...
Click to collapse
Is posted on my Guide, I am a user not a developer and all the modifications I am doing is what any user can do, but I am trying to make it easier for others to apply on to the Tablet. I am not creating any proprietary code or special software. But there are other "humans been" that the only thing they care is personal gain and will use others people ideas and work, modified it and call it their own. It happens all over, look into this web site XDA and you will find it. There is a reason for a patent registration that is stronger than just a copyright and even patents takes years to get approved and still others use it.
Jc Sullins spent a lot of time creating the ToolBox and just posted it for everyone to use. Anyone can easily modified it, repack it and distributed with another name and charge, that is the reality. But the ToolBox is not a proprietary software or code, is a version of Angstrom v2015.01, Built from branch: master, Revision: 038d832 (open source )
http://www.angstrom-distribution.org/
Running scripts to perform the task with busybox and LVM. There is no custom codes, but the script and that is just a way of writing a command to be executed.
Attached are the list of scripts from the Toolbox, when a user enter an option the script it call and executed by busybox or LVM.
It is very well done and perfectly executed. If the WiFi drivers can be ported to Anstrom Arm OS, a system can be built that will do it all, with web browser built in to automatically download the latest Recovery, Android Version, Resize all Partitions and automatically fix any issues. But the drivers for the HP TP are proprietary and not available or easily portable to other OS.
Read very careful this links, it could have provided the information to create the HP Touchpad Debrick, the Pre phone runs on WebOS, same as the Tablet.
One situation which cannot be recovered so easily is the extremely unlikely event of corruption of the installed bootloader (bootie) stored on the Pre's flash disk.
And this is the Most important, that clearly state that a WebOS device can not be brick even if the bootie is damage.
If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.
https://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery
https://forum.xda-developers.com/showthread.php?t=1564938
smithylovestouchpad said:
I saw your post elsewhere about the java installer for Novacom not working any more. There is a Windows installer version you can download here:
https://www.sheldonsblog.com/cant-download-novacom-drivers-for-windows-to-connect-hp-touchpad/
Just right click on NovacomInstaller_x64.msi and click install. There is a 32 bit version too. Easy peazy. No java installer needed.
Smithy
Click to expand...
Click to collapse
Thank you for sharing the information, it is good to know that you recently found the Novacom drivers for Windows. I do have all the drivers for all the OS.
On this post August 5 when your Windows Novacom Driver malfunctioned, you asked for the drivers:
By any chance do you have the novacomd installation files. I could try reinstalling that. I have even tried a different USB cable.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
The java installer was the Universal to get it working on any OS, but it need it java to be install and that was another challenge plus about 200 MB extra just to use a driver.
The Windows driver installed on my Windows x64 with no issues, attached are the screenshots.
It is very easy to install, just a click. But having the Novacom Installed on Windows or any other OS does not mean that the Tablet will get fix. Is only a driver that was created in 2009 to communicate with Palm phones that came with software that used the driver.
Your issued is the perfect example and this is how it all started:
I am looking at triangle with an exclamation point in it and www.palm/ROM below that. I'm not bricked so to speak, but I no longer have a boot loader, so the tablet is useless. I now have a nice paperweight.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80014852&postcount=391
With the HP Touchpad Novacom Repair Android, is not only the driver but the user knows what to do when they see a symbol on the tablet screen and the only thing to do is connected and click. It will always work as long as the PC has a USB port and the Tablet connection works.
If the user is using any other OS, Windows as an example, it must know how to open a command prompt in the Palm, Inc directory.
That is not an easy task for a regular user, you could not do it as in your post:
OK, using Windows File Explorer, I navigate to the Palm, Inc folder and right click the mouse. The options menu that opens does not give me a selection to open a command window
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
As you can recall, it was a challenge for a user like you that claims using Novacom drivers is as easy as a click and all done, well think what it can be to others using different operating system.
HP_TOUCHPAD said:
Thank you for sharing the information, it is good to know that you recently found the Novacom drivers for Windows. I do have all the drivers for all the OS.
On this post August 5 when your Windows Novacom Driver malfunctioned, you asked for the drivers:
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
The java installer was the Universal to get it working on any OS, but it need it java to be install and that was another challenge plus about 200 MB extra just to use a driver.
The Windows driver installed on my Windows x64 with no issues, attached are the screenshots.
It is very easy to install, just a click. But having the Novacom Installed on Windows or any other OS does not mean that the Tablet will get fix. Is only a driver that was created in 2009 to communicate with Palm phones that came with software that used the driver.
Your issued is the perfect example and this is how it all started:
https://forum.xda-developers.com/showpost.php?p=80014852&postcount=391
With the HP Touchpad Novacom Repair Android, is not only the driver but the user knows what to do when they see a symbol on the tablet screen and the only thing to do is connected and click. It will always work as long as the PC has a USB port and the Tablet connection works.
If the user is using any other OS, Windows as an example, it must know how to open a command prompt in the Palm, Inc directory.
That is not an easy task for a regular user, you could not do it as in your post:
https://forum.xda-developers.com/showpost.php?p=80016787&postcount=418
As you can recall, it was a challenge for a user like you that claims using Novacom drivers is as easy as a click and all done, well think what it can be to others using different operating system.
Click to expand...
Click to collapse
So what's your point. Only thing I see is you saying I'm stupid and you are so smart. That your way is the best and only way because you created it. Do you get a thrill putting people down? I have posted a link to an installer that does not require java, you put me down for that. I pay you complements, you don't even have the courtesy to say thank you. The only issue I had was a corrupted driver that caused the problem. You try to make it out that I don't know what the hell I am doing. I was the one who figured out it was a corrupt driver and I shared that. And why is it that someone asks for a link to a possibly needed file and no help from you. You say you have the Novacom driver for all OS's. How come you could not have provided a link? And BTW, after the fact I realize your suggestions were misleading. To run TWRP, TPTB or your Wipe routine on the TouchPad, all one has to do is run the associated script. No command window needed. I acknowledged early on that hardware was my area of expertise, not software, writing scripts or code. So why are you holding that against me? Oh wait, that makes you the big man cause you know it all and I admitted I did not understand what you were saying. You must live in a really big building to accommodate your huge ego. But that's OK, my TouchPads run just fine without your Wipes, Swaps, Optimizations or Reducers.
And since I am about to say "adios" to this little circus, you should really find someone to edit your threads, posts and guides. I asked you before if English was your first language and you said it wasn't, and it's very obvious it is not. At times it is really difficult to understand what you are trying to say because of it. You never say anything in your videos. Now we know why, no one could understand you.
Well, I've had my fun at your expense. So I only have one thing left to say, BYTE ME!