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.
Mysterious Magic (G Watch)
The First Custom G Watch ROM Based on the Android 5.1.1 (LDZ22D) OTA
Prerequisites:
Unlocked Bootloader (fastboot oem unlock)
ADB Debugging Enabled (Settings > About > Tap on build number 7 times > Swipe back > Developer Options > Enable ADB Debugging)
Drivers Installed (Windows)
Features:
Rooted out-of-the-gate (su, busybox)
Init.d support built in (/system/etc/init.d)
Improved transitions
Improved speed (slight overclock)
Improved battery life
Increased vibration
Forced GPU rendering
Easy to use installer (Windows, Linux, OSX)
Hotplugging of all 4 cores, as needed
Special Thanks:
invisiblek - For his wonderful custom kernel work!
okibi, arter97, Tomsgt, nagasgura, PlayfulGod, WindyCityRockr, and all other community developers - For their time, effort, and inspiration, in making this watch run faster, better, and even smoother!
All of the community members, watch owners, and rom flashers - Without my amazing users, and the help of this community, none of this would be possible, or even exist!
Donations:
If you happen to like my ROM and find yourself wishing to donate, you can do so by pressing the "Donate to Me" button below my username on the left side of the screen. I spend my free time developing my contributions to the community, and every penny is greatly appreciated!
Changelog:
Version 1.0 r2 (7/12/2015) :
- Removed vibration intensity from the tweaks and added it to it's own seperate file, for end user configuration.
- Removed governor and frequency settings from tweaks and added it to it's own seperate file, for end user configuration.
- Changed the default governor from ondemand to smartmax, to accomodate the kernel included with this rom.
For the best results, refrain from changing the default governor, unless you plan on pairing this rom with a different kernel other than invisiblek's (included).
- Added the ability to change dpi settings.
- Added the ability to enable a specific number of cores (when not using the included kernel).
- Fixed adb, fastboot issues some users were having.
- Major revisions to the installer!
Version 1.0 (7/5/2015) :
- Initial release.
Downloads:
Version 1.0 r2 (md5: 1c2652a3607a53d889c664eec72a37f2)
Mirror 1
Mirror 2
F.A.Q
How do i use the installer?
Extract the archive.
Enter the "Installer" folder.
Enter the folder of the platform you're using (Windows, Linux, or OSX).
Run the installer and follow the on-screen instructions.
Linux and OSX scripts may need the proper permissions in order to run.
Please note: First boot will take some time, and you'll need to re-pair your watch and phone.
How do I edit and install custom settings?
Enter the "Settings" folder.
Open the settings file with the text editor of your choosing.
Make changes to the settings file.
Save the settings file.
Run the installer, select Install Settings, and follow the on-screen instructions.
Questions? Comments? Concerns?
Leave all questions, comments, and concerns below, and I'll be sure to reply as fast as possible!
installer doesnt work
ker2gsr said:
installer doesnt work
Click to expand...
Click to collapse
Which version? Can you screenshot the specific errors?
Sent from my SM-G925P using XDA Free mobile app
MysteriousSparrow said:
Which version? Can you screenshot the specific errors?
Sent from my SM-G925P using XDA Free mobile app
Click to expand...
Click to collapse
that info might help lol yes i was using the wimdows installer im using windows 8 x64 the installer detected my device but when i went to do a reboot it said command anniciated but device didnt reboot into fastboot it went through all format steps and said succesfully flashed rom but device never rebooted to format on flashboot sorry no screen shot i flashed manually
ker2gsr said:
that info might help lol yes i was using the wimdows installer im using windows 8 x64 the installer detected my device but when i went to do a reboot it said command anniciated but device didnt reboot into fastboot it went through all format steps and said succesfully flashed rom but device never rebooted to format on flashboot sorry no screen shot i flashed manually
Click to expand...
Click to collapse
After looking into it, it seems I added an extra unneeded character to the script. I'm reuploading the correct version now, and I'll replace the download link accordingly! Sorry about that!
The fixed version is now uploaded. Give that a try and let me know!
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
dude1981 said:
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
Click to expand...
Click to collapse
Thanks! Let me know!
MysteriousSparrow said:
Thanks! Let me know!
Click to expand...
Click to collapse
Installer worked fine on Linux Mint. Will test on watch for a couple days and report back. What kernel is it running?
installed on windows 8 no issues...waiting for sync to test this bad boy out
thanks dev
dude1981 said:
Just installed with windows 10 and installer worked with no problems. Will boot into mint and try installer and report back.
Click to expand...
Click to collapse
dude1981 said:
Installer worked fine on Linux Mint. Will test on watch for a couple days and report back. What kernel is it running?
Click to expand...
Click to collapse
invisiblek's dory kernel
Thanks for the feedback, good to hear the installers are in working order now.
Will download when I get home. Can't wait to try this out...
goast said:
installed on windows 8 no issues...waiting for sync to test this bad boy out
thanks dev
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Report back and let me know what you think!
Ralphyralph said:
Will download when I get home. Can't wait to try this out...
Click to expand...
Click to collapse
Can't wait to hear what you think!
rom working great so far i had already installed manually so i didnt test again for you but others seem to have no issue now great work watch feels more snappier and responsive
ker2gsr said:
rom working great so far i had already installed manually so i didnt test again for you but others seem to have no issue now great work watch feels more snappier and responsive
Click to expand...
Click to collapse
Good to hear! Let me know if you have any concerns or questions in the future, regarding the rom.
Sent from my SM-G925P using XDA Free mobile app
upload
View attachment 3392477 Ok what am I doing wrong?
The Struggle:
If you have ever installed a fresh copy of Windows 10 on the Lenovo Yoga Book using a standard Windows 10 ISO you know the struggle! You need several pieces of hardware before you can even begin. After Windows has installed your nightmare is still far from over! Windows will be missing several drivers that have to be sorted out and downloaded, some from Microsoft, and others from Lenovo. All this nonsense takes far too much time and effort and shouldn't be required from the end user. Fed up after my last install, I began putting this together for my own personal use. Upon seeing how well it worked I knew I had to share! Using this guide you will inject 32 new drivers into your Windows 10 installation media. All other files remain untouched. Nothing else added and nothing is ever removed.
This guide will not enable Windows installation on the Android version of the Yoga Book.
Benefits:
1. You no longer need several pieces of hardware to install Windows. An eight gigabyte USB flash drive and an OTG adapter are all that's required.
2. Windows setup starts with touchscreen and pen support from the very beginning.
3. After the “Getting devices ready…” stage of Windows setup you will have full hardware support!
The keyboard, trackpad, touchscreen, audio, and Wi-Fi all function allowing for a quick and painless install.
4. Windows 10 boots the very first time with all of the correct drivers already installed, even if you don't connect to Wi-Fi during setup.
5. You now have a fallback copy of Windows 10 that works right out of the box. This is something Lenovo should have provided.
6. Several users have reported a noticeable gain in performance.
Required downloads:
You will need to install four programs to complete this guide. All are small downloads (less than 15 megabytes combined) that are free or have fully functioning trials. To keep things as simple as possible please save all downloads onto your desktop.
NTLite - used to build the new Windows 10 ISO.
Rufus - used to write your updated Windows 10 ISO on your flash drive.
WinRAR - used to extract both the Windows ISO and the Yoga Book Setup Files.
Yoga Book Setup Files - contains all of the drivers and supporting files needed to complete this guide. Updated 4/30/2018
You will also need a clean stock 64 bit Windows 10 ISO. For this you have two options.
Microsoft’s Media Creation Tool or Windows ISO Downloader (suggested method) can be used to download an ISO from Microsoft's servers. ISOs downloaded using Microsoft’s Media Creation Tool use ESD compression. This highly compressed version, while quicker to download will increase both build and install time considerably. ISOs downloaded with Windows ISO Downloader use WIM compression and are far less compressed, making them much quicker to build and install. This decreases the time it takes to install Windows by roughly 7-10 minutes! Windows ISO Downloader also has the added benefit of allowing you select which update level you would prefer to download.
ISO files downloaded from other sources (torrents or warez sites) may not be clean or compatible. As such their use is highly discouraged.
Build process:
It is very important to follow this guide carefully. Skipping any of the steps or even changing the order of certain steps can cause issues. I have installed Windows well over 100 times and spent over 150 hours working on this. Once completed you will end up with a Windows 10 installation that runs BETTER than the first time you enjoyed your Yoga Book!
Step 1. Highlight both the Windows 10 ISO and “Yoga Book Setup Files.rar” files. Right click one of them and select “Extract each archive to separate folder”
Step 2. Launch NTLite. On the first launch you should disable auto loading presets. To do so click File then Settings and uncheck "Load auto-preset 'Auto-saved session'".
Step 3. Drag and drop the extracted Windows 10 setup folder into NTLite.
Step 4. Double click "Boot/Setup | boot.wim".
Step 5. Double click on "Microsoft Windows Setup (x64)" and wait for it to finish loading.
Step 6. Click “Drivers" then drag and drop the "Boot.wim Drivers" folder into NTLite.
Step 7. Click "Apply" then select "Don't backup log and preset". Leave all other options as is and click "Process".
NTLite will ask if you want to disable Windows Defender to increase performance. This is completely optional but recommended.
Step 8. Click "Source".
Step 9. Double click your version of Windows, "Windows 10 Home x64 Core" or "Windows 10 Pro x64 Professional" and wait for it to load.
Step 10. Once loaded right click your version Windows and select "Explore mount directory".
Step 11. Copy and paste the included files from inside the "Mount Directory Files" folder into the base of the Explorer window that opened. After confirming the file copy prompts you can now close this window.
Step 12. Click on “Drivers” then drag and drop the "Install.wim Drivers" folder into NTLite.
Step 13. Click on "Registry" then drag and drop "RegistryEntries.reg” into NTLite.
Step 14. Click "Post-Setup"
Step 15. Now open the "Post-Setup Files" folder and drag and drop each of the 4 files into NTLite. Each file is numbered and should be added in order.
Step 16. Click "Apply" and use the following settings.
Under “Saving mode” select "Save the image and trim editions".
Under "Image format" make sure "Standard, editable (WIM)" is selected.
Select "Don't backup log and preset".
Select "Create ISO".
NTLite will ask you to name your ISO file. Save the ISO on your desktop as Win10Yoga.
NTLite will now ask for a disc label. Set this as Windows 10.
Step 17. Click "Process" and wait for your custom Windows 10 installation ISO to be completed!
You can now close NTLite.
Preparing the USB drive:
Now we will use Rufus to write the setup files on to your flash drive. The ISO file can also be burnt to a DVD if so desired.
Step 1. Launch Rufus and insert an 8GB or larger USB flash drive.
Step 2. Make sure the correct drive is selected under “Device”.
Step 3. Set "Partition scheme and target system type" to "GPT partition scheme for UEFI".
Step 4. Set "File system" to "Large FAT32 (Default)".
Step 5. Set "Cluster size" to "32 kilobytes (Default)".
Step 6. "New volume label" should set itself to "Win10Yoga" after step 8.
Step 7. Check "Create a bootable disk using ISO Image"
Step 8. Click the small button to the right of the "ISO Image" dropdown and browse to the Win10Yoga.iso located on your desktop.
Step 9. After verifying your settings below click "Start".
{
"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"
}
Congratulations, your custom Windows 10 installation media is complete!
Starting Windows installation:
Make sure that your Yoga Book has completely shutdown. To begin press and hold the volume up key followed by the power button. Continue holding both until the pen light begins flashing. You can now let go of the power button. When the screen lights up you can release the volume button. If everything was done correctly your drive should now show under the "Boot Menu". Select the drive you've created to begin installing Windows 10.
Prebuilt ISO
I have included a pre-compiled ISO based on Windows 10 1803 for those unable to do so. Windows 10 Home and Professional are included in this ISO file. Download, flash, install, and enjoy. The stripped builds are no longer included. This ISO will be removed at Microsoft's or XDA's request!
Download Now (3.13GB) Updated 4/30/2018
Tips & Tricks:
To enable touchscreen support in the BIOS it must be updated to the latest version.
Windows 10 will activate automatically as long as you have installed the correct edition.
Due to a limitation on which drivers can be injected into the boot.wim file Windows setup will display in portrait mode until the "Getting devices ready..." stage. Setup will automatically switch to landscape mode when possible.
During Windows setup, right before the first reboot you will see a 10 second countdown. Wait until the last three seconds or so and unplug your flash drive, Windows setup no longer requires it.
After testing your USB drive feel free to uninstall WinRAR and NTLite. All other downloads and extracted files can also be deleted. Keeping an archival copy of the completed ISO is strongly recommended.
Thank you so much for sharing. I have one question. After followed your guide I found out there is no Dolby. Do you know how to install Dolby on yoga book?
nooweat said:
Thank you so much for sharing. I have one question. After followed your guide I found out there is no Dolby. Do you know how to install Dolby on yoga book?
Click to expand...
Click to collapse
It should have installed. Have you clicked the up arrow down in the system tray to check for it? I am currently installing a test version for myself. I will check into it shortly and get back with you. Did you have any other issues?
figure out
I just figure out.
i download audio driver from Lenovo website directly. after reinstall drive and reboot, dolby folder is created.
nooweat said:
I just figure out.
i download audio driver from Lenovo website directly. after reinstall drive and reboot, dolby folder is created.
Click to expand...
Click to collapse
You we're absolutely correct. You did have sound right, just not Dolby? I am sorry about that. Other than the one hick up did everything else work properly? I am working on fixing this now!
Sandman45654 said:
You we're absolutely correct. You did have sound right, just not Dolby? I am sorry about that. Other than the one hick up did everything else work properly? I am working on fixing this now!
Click to expand...
Click to collapse
other thing works properly. thank you again
I am glad you found it helpful. You are very welcome Thanks for the feed back.
The new version with Dolby included has been uploaded! The written tutorial has been updated as well. Setup now includes all of the updates posted on Lenovo's driver page as well. Every thing except for Lenovo Paper. It has been left out because of the UAC prompt on start up.
Sandman45654 said:
The new version with Dolby included has been uploaded! The written tutorial has been updated as well. Setup now includes all of the updates posted on Lenovo's driver page as well. Every thing except for Lenovo Paper. It has been left out because of the UAC prompt on start up.
Click to expand...
Click to collapse
Hi sandman, I'm writing using my yoga book, I full restored using the recovery option in the boot menu. But I don't have the drivers yet, I tried using Lenovo system update but it simply doesn't work. then, I tried downloading the drivers one by one, but they don't have any installer or something, only the driver for halo keyboard has it.
How can I install the drivers that I just download from Lenovo's site? or, is there a way a can use the yoga files you have in the tutorial?
Ill be waiting for your response, happy holidays.
P.S: excuse my English.
Download the Yoga Setup Files from the link in my first post. Extract it using Winrar. The Install.wim folder has the majority of the drivers. The MSI has the rest. I would probably install those first. If you need more help let me know.
Happy Holidays to you too
Sandman45654 said:
Download the Yoga Setup Files from the link in my first post. Extract it using Winrar. The Install.wim folder has the majority of the drivers. The MSI has the rest. I would probably install those first. If you need more help let me know.
Happy Holidays to you too
Click to expand...
Click to collapse
Thanks for your response , I already have those files you mentioned, but i don't know how to install them, all I have in the folders are .dll .sys and .pnf files. I tried by looking for drivers in the device manager but it shows me that that the drivers are up-to-date.
I'll appreciate your help.
Regards.
No problem at all. First start off by installing all the drivers in the MSI folder. Once that is done right click the start button and select device manager. Anything that does not have a driver installed should have a little yellow triangle next to it. Take you pick as there will likely be several and right click one. Select "Update driver" on the menu that pops up. A window with two options should open. Click the bottom one that says "Browse my computer for driver software". Click the "Browse" button and navigate to the install.wim folder. Once you've set the folder make sure "Include subfolders" is checked and click the "Next" button. Windows should automatically find and install the correct driver. You will need to do this for each missing driver.
This is the nightmare my setup files prevents
Hi again, I did what you said about the msi drivers, but when I go to the device manager, none of the devices have the yellow triangle, and when I
---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
Sandman45654 said:
No problem at all. First start off by installing all the drivers in the MSI folder. Once that is done right click the start button and select device manager. Anything that does not have a driver installed should have a little yellow triangle next to it. Take you pick as there will likely be several and right click one. Select "Update driver" on the menu that pops up. A window with two options should open. Click the bottom one that says "Browse my computer for driver software". Click the "Browse" button and navigate to the install.wim folder. Once you've set the folder make sure "Include subfolders" is checked and click the "Next" button. Windows should automatically find and install the correct driver. You will need to do this for each missing driver.
This is the nightmare my setup files prevents
Click to expand...
Click to collapse
Hi again, I did what you said about the msi drivers, but when I go to the device manager, none of the devices have the yellow triangle, and when I tried to update the driver, windows show me that the best driver is already installed.
I do not know what else is missing, but the haptic feedback is not working for me.
Eljosemata said:
Hi again, I did what you said about the msi drivers, but when I go to the device manager, none of the devices have the yellow triangle, and when I
---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
Hi again, I did what you said about the msi drivers, but when I go to the device manager, none of the devices have the yellow triangle, and when I tried to update the driver, windows show me that the best driver is already installed.
I do not know what else is missing, but the haptic feedback is not working for me.
Click to expand...
Click to collapse
Awesome your battle is almost complete! Inside the setup files folder you should see a file named "RegistryEntries". Click that file and it will ask if you want to merge the data, click Yes. You should also see a folder named System32. Copy it, folder and all in to your C:\Windows folder approving any prompts that open. Reboot and you should be golden.
Eljosemata said:
Thanks for your response , I already have those files you mentioned, but i don't know how to install them, all I have in the folders are .dll .sys and .pnf files. I tried by looking for drivers in the device manager but it shows me that that the drivers are up-to-date.
Click to expand...
Click to collapse
And you have an *.inf file in each drivers folder... right click it and choose install...
jamespmi said:
And you have an *.inf file in each drivers folder... right click it and choose install...
Click to expand...
Click to collapse
While you can do this unless you know what specific driver you are installing you may end up wasting a lot of time installing drivers that may already be installed. Most drivers are installed during Windows setup. There are only a small handful of trouble makers. Some drivers have 2 or more INF files in their directory. Getting haptic feedback working this way won't work without additional files. If you want to install drivers by hand the device manager is a safer bet IMHO. I'm sticking with my custom setup disk either way Don't have to deal with any of this stuff that way!
If you follow this guide you will never have to struggle to get haptic feedback working. Touchpad gestures work without finding the right drivers and installing them in the right order. You won't have issues with your Yoga Book suspending when you lower the screen. You don't have to download and install several patches off of Lenovo's website. You simply install Windows, then your programs, then your done. No fiddling, no fussing, and no cussing It solves many of the common issues you see about this laptop. It's as close to a restore image you will get for the Yoga Book. The only thing missing is the Lenovo Paper app. If you have the MSI file for Lenovo Paper it too can be added in the post setup part of the process (bottom of the list). The one time setup of this guide saves a lot of time and hassle down the road.
Sandman45654 said:
I'm sticking with my custom setup disk either way .
Click to expand...
Click to collapse
Totally and the community should be more than thankful for your effort...
But a year back when I reinstalled Windows (I do that with all devices I get, hate the bloat all manufacturers preinstall) there was no guide or collection like yours, furthermore hardly drivers. Not even on Lenovo's site...
Merry Christmas
jamespmi said:
Totally and the community should be more than thankful for your effort...
But a year back when I reinstalled Windows (I do that with all devices I get, hate the bloat all manufacturers preinstall) there was no guide or collection like yours, furthermore hardly drivers. Not even on Lenovo's site...
Merry Christmas
Click to expand...
Click to collapse
I really appreciate the compliment I am the same way, I always wipe new machines when I get them. When I wiped my book Lenovo did have the first round of drivers up but they really dropped the ball with this awesome lil machine! I downloaded everything that was posted and fought with it for a quite a bit to get everything just right. Then the last time I installed I seen things were still far from perfect and I was tired of having to hook up a hub and other hardware. One struggle right after another. I started toying with the idea of doing what I've done here and the rest as they say is history. The hardware, for its size is on point but the supporting software just isn't nearly as refined as the machine that runs it. A system this unique should have came with a factory restore download or even included it on a cheap 8 gig micro sd card! That extra $3 would have went a long way into making happy customers!
Merry Christmas to you and all of our XDA family as well!
Sandman45654 said:
Awesome your battle is almost complete! Inside the setup files folder you should see a file named "RegistryEntries". Click that file and it will ask if you want to merge the data, click Yes. You should also see a folder named System32. Copy it, folder and all in to your C:\Windows folder approving any prompts that open. Reboot and you should be golden.
Click to expand...
Click to collapse
Hey, thank you so much for your help. I am done with my yoga book, i did what you said about the system 32 folder, but it didn't work. then, I install one by one every single .inf and it work perfect to me.
Again, thank you for putting all the drivers together and for being very accesible to respond my "new/nervous user".
By the way, i do a lot of mistakes while writing, is there an option to use some predictive keyboard as in the cellphone?
MERRY CHRISTMAS
Eljosemata said:
By the way, i do a lot of mistakes while writing, is there an option to use some predictive keyboard as in the cellphone?
Click to expand...
Click to collapse
You use it as a cellphone? lol just kidding...
Unfortunately not in all apps. Google for example did not implement it in Chrome even embedding it would be very easy for them. There are a lot of developers slowly embedding it in their apps. It's not just a YB issue, same on Surface and alternatives... try to type something in Notepad and you will see it's even showing up there...
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
- Backlight Control (added 25/5/2018)
I'm getting very near to have the touch and the keyboard working though
P.s. In attach you find the outputs from 3DMark - IceStorm Extreme (default settings), would be much appreciated if someone with the real Win version shared its score
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Broomfundel said:
Any chance of posting you work to date. Got an X90F just crying out for Windows.
Click to expand...
Click to collapse
I have added the link to the guide! If yo have any issues let me know but keep in mind that currently no input devices (touchscreen or keyboard) work!
Thanks for posting this. I am really so impressed. Will be trashing my X90F tomorrow. Just got to dig out a powered USB hub. Ill report back, and lets see what happens.
(Hopefully not a brick)
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Broomfundel said:
OK,
So far so good. I get to the amending of the of aml. But keep getting.
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20180508
Copyright (c) 2000 - 2018 Intel Corporation
iASL: Segmentation Fault
iASL: Terminating
To clarify the process. Decompile the DSTDroid.aml, then insert the OperationRegion (GNVS, SystemMemory, 0x7B3CF000, 0x0369)
Field (GNVS, AnyAcc, Lock, Preserve)
{ etc.. } section from the DSTDroid.dsl and use it to replace the equivalent section in the DSTWin.dsl in your files.
Then compile the DSTWin.dsl with the
iasli -ta DSDTWin.dsl
command.
This is how I am reading it, but have not managed to get it to work yet.
It decompiles with the two errors you mention, but wont recompile no matter how I try it.
I am using Notepadd++ so its not hidden characters.
Any thoughts, and thanks again for your efforts on this.
Click to expand...
Click to collapse
Hello Broomfundel,
I never got that error, but it seems to be a problem of the ASL Compiler build not of your file.
I am using Mac so I have another build, if you want to post the file I can compile it for you .
Otherwise you can try an older release or to build the tool from source maybe?
Poz1 said:
Hello guys!
I'm starting this thread as I managed to install win10 on my X90L (Android) YogaBook
It was not easy to find a way to fix the ACPI error but it is possible!
Will update this post in a few hours with a guide on how to do it yourself.
UPDATE: link to the guide -> poz1.com/windows-on-android-lenovo-yogabook/
PLEASE NOTE THAT IF YOU CONTINUE YOU WILL END UP WITH A YOGABOOK WITHOUT INPUT DEVICES!!!
(EXTERNAL KEYBOARD WILL BE NEEDED) AND NO ANDROID INSTALL!!!
So far i got almost everything working except:
- Touchscreen
- Keyboard
- Webcam in the keyboard panel (the other one works fine)
- NFC
I'm getting very near to have the touch and the keyboard working though
Click to expand...
Click to collapse
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
THE MAXIMUM POWER said:
Hi, i have the Lenovo Yoga Book Windows version, im crying to install Stock Android on it, can you PLZ write a guide about doing it, or at least if there is a way to install the kernelflinger.efi or the fastboot mode on YB windows it will be great.
to fix the whole bugs you faced, try to reinstall windows 10 using this methode https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Thanks
Click to expand...
Click to collapse
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Broomfundel said:
OK, Older release worked, but I get a .hex file, your instructions talk about a new aml file. Do I use the .hex file or is there another option other than the -ta one that would create the aml.
BTW. I am enjoying this. So thanks again.
Click to expand...
Click to collapse
With the -ta option I get both the .hex and the .aml file but you can try -tc if it doesn't work. Maybe due to the different build
P.s. (for other people that may incur in this) If you don't get the output files check that you have as last line of the terminal
"Compilation complete. 0 Errors"
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Poz1 said:
Hi,
KernelFlinger is opensource and come with an installer, it should be pretty simple to install it.
Right now I don't have my YogaBook as I am travelling but I can try in the next few days
Click to expand...
Click to collapse
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Poz1 said:
Hello guys!
Click to expand...
Click to collapse
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
As Poz1 is obviously busy at the moment. Can anyone else get the DSTDWin.aml file for me to try and decode?
Thanks
Sorry guys I've been busy with university
Broomfundel said:
OK, I am getting 7 errors. My current theory is that the DSTDWin.dsl will only compile with the same version number of the compiler it was decompiled with. I have attached my DSDTDroid.dsl so you can have a go. At least it will prove I got things right up to that point. Might be worth posting the original DSTDWin.aml for me to try this end.
If we are lucky it might turn out that the patched DSTDWin.aml files are consistent across the same model devices.
Click to expand...
Click to collapse
There you go I'm also updating the files DSTDWin of my blog with one with some fixes Well they depend on the settings you use in your Bios (that's why Windows may not boot after install, it changes some parameters (the wait time of the bios and the default boot partition)). When you use the builtin one is the bios that "updates" it for you but for now we need to do it by hand If we are going to end with everything working we can release a patched "Win" bios and everything will be simpler
Riskypedia said:
So... It seems both pen mode and keyboard mode of holo keyboard won't work... Am I right?
It's sad that if they won't work even we install the drivers from the lenovo website
Click to expand...
Click to collapse
I know There something in the DSDT (the file that tells the os which and where your pc components are) that has to be fixed to make Windows see these parts correctly
THE MAXIMUM POWER said:
can after installing Windows booting to kernelflinger? if you can make a thread about how can you install/reinstall kernelflinger will be amazing?
Thank you
Click to expand...
Click to collapse
Didn't try Will do as soon as I have some free time :fingers-crossed:
Kinyapiplele said:
Have you tried with the ISO from this forum with the Windows injected drivers? Here https://forum.xda-developers.com/yoga-book/how-to/windows-guide-creating-windows-10-t3718823
Click to expand...
Click to collapse
Yep, but the problem is in the DSDT Thanks fot the input anyway
Poz1 said:
Sorry guys I've been busy with university
Click to expand...
Click to collapse
Don't worry, we all have real lives as well. I'm in the UK and we have a bank holiday on Monday. So this weekend, Ill get stuck in again.
Thanks for all your doing on this. You have already got further than anyone else who tried.
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Poz1 said:
let me know if you have more problems
I have added a 3DMark test in the first post for those that are interested in how it performs
Click to expand...
Click to collapse
Just another Question, you as a Advance user, do you believe that we (yoga book Windows owners) can boot Android yb STOCK ROM ( i mean not the Android x86 based distros)?
Yes, but I think you would have to do the "reverse" DSDT injection (from win to android) as the official ROM has drivers for that components.
This means that, if you're lucky you would end up with our same problems (keyboard, pen and touch). If we don't fix that before
The problem with Android is that it is meant to be flashed on rom instead of being installed and this makes things more difficult.
It should be possible to flash the rom on an USB key, add grub and use it for DSDT injection like we do and see what happens.
Another problem is that the provided kernelflinger seems to have most of the security options enabled so 99% it will refuse to boot anyway.
Since it is opensource it should be possible to fix this anyway.
So yes, but it a loooong journey
Hi All !
Some of us do know the application a long time but others don't. Therefore this small GUIDE.
Removing system apps without root/unlocked can be done in a few ways like :
manually : with an ADB list and described HERE huge thnx @SirTAVARES
automatic : if you don't like to do it manually, you can use the ADB/Fastboot Tool which will do the job for you.
The XiaomiADBFastbootTools isn't explained in depth afaik and can do a lot more but I'll focus on the removal of those system apps.
HOW TO :
NOTE : do try some apps (not all at once) and see if the phone boots again - if you would have a problem you can always restore the onces you removed or perform a factory reset to restore all apps (as they are not really gone )
0. enable developer options to enable USB debugging ( go to settings/about phone/tap MIUI version 7 times to enable dev. options -> then go to settings/additional settings/ dev. options/enable USB debugging )
1. download the latest version HERE
2. run the .jar application
3. you'll get this screen
As you can see, the tool will start by default in ADB. You'll see a bunch of apps you could de-install under the Uninstaller tab.
If you're sure which apps you want to de-install just check the ones you want and tab UNINSTALL
google where is the nearest gas station
TIP : try one first like Google Chrome f.e. and see if it works
EXAMPLE : Removal of Google Chrome :
Once removed you can check if the app is gone of your home screen apps or under settings/installed apps/tap the 3-dot sign to show all apps/ search for ''chrome'' and the app should be removed.
4. if you want the removed app(s) back, just tap the Reinstaller and check the ones you want to re-install. Easy right !
Once re-installed your Chrome app will appear again on your home screen/app list
5. TIP : before removing, check the app name under settings/installed apps/show all apps/tap on an app and tap the Ⓘ to get the app info
Other functions :
1. As you probably noticed besides running in ADB, this tool can easily boot into Fastboot, Recovery, System or EDL.
When booting into Fastboot you can see some other functions you can apply. Be aware of the risks applying things under fastboot !
2. Very useful option is the possibility to push, pull ,... apps/folders with FILE EXPLORER. Just tap OPEN and you can easily perform some actions afterwards.
(ignore the KB sizes - once pulled you'll get the right folder/apks )
E N J O Y
Nice tuto....will debloat for sure...
SirTAVARES said:
use this list: https://drive.google.com/open?id=1TbofebVTy5U1FDMQEAfv6O1CsxTblpO7
includes some adaway hosts to block Xiaomi Stuff
Click to expand...
Click to collapse
Dear SirTAVARES, Can you tell me, is adaway worked with Global stable NON Root ? How to push it inside system files ??
N.ice tool, but I have a doubt... How I remove the Security Center?
PS. I have a Mi 9, with locked bootloader and now I'm beta 9.6.27
Thank you very much for sharing, i will test for changing system font
Sorry for that stupid question, but I don't get the tool running
Prinz069 said:
Sorry for that stupid question, but I don't get the tool running
Click to expand...
Click to collapse
You must have the JRE environment installed and pointing to the correct path.
omgomg said:
You must have the JRE environment installed and pointing to the correct path.
Click to expand...
Click to collapse
What is "JRE Environment" please? Why same not included in the OP instructions?
All help appreciated!
belerephont said:
What is "JRE Environment" please? Why same not included in the OP instructions?
All help appreciated!
Click to expand...
Click to collapse
This is what you have to install to be able to run .jar files. OP just assumed everyone has java installed (I would too to be honest) and didn't mention it.
I have installed the updated java and am trying to open the windows 10 boot tool and it refuses to open. Yes I did upzip it but the program will not open. Any help please?
gardenwarlord said:
I have installed the updated java and am trying to open the windows 10 boot tool and it refuses to open. Yes I did upzip it but the program will not open. Any help please?
Click to expand...
Click to collapse
What version you installed? I recommend that you install 6.5.1:
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/6.5.1
That is what I downloaded...Win version. I unzipped and then tried to open but it does not work.
gardenwarlord said:
That is what I downloaded...Win version. I unzipped and then tried to open but it does not work.
Click to expand...
Click to collapse
You don't need unzipped. Download the version .JAR an run it. I made this way
Evidently I have absolutely no idea what I am doing. Nothing opens
gardenwarlord said:
Evidently I have absolutely no idea what I am doing. Nothing opens
Click to expand...
Click to collapse
Lets go from begining:
- First thing that I did, I uninstalled all versions of Java;
- Second, (I made this way, you can jump this step) - reboot my laptop;
- Third, I installed the latest version (in this moment is version 8, update 221) - I installed both 32 bits (x86) and 64 bits (x64);
- Fourth, run the tool (just download .JAR version) and clicked with right botton for open with Java.
When I right click nothing asks to open it in java
If you have java installed, then just a double click on the XiaomiADBFastbootTools-6.5.1.jar is enough.
Opens in 7z
gardenwarlord said:
Opens in 7z
Click to expand...
Click to collapse
Probably you made 7zip as default app. Right botton, "open with...", choose Java
Hello! Tried different versions ... NOT FOUND Redmi 4X MIUI 10 Global 9.6.27 Android 7.1.2 N2G47H