Attached, Just run the blockupdates.bat file then sit back and relax. Obviously you need the Nook plugged in and ADB access enabled.
Code:
echo off
cls
echo *****************************************
echo * We will create the directory .Android *
echo * We will also create the adb_usb.ini *
echo *****************************************
md "%USERPROFILE%\.Android"
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini"
echo Success
adb kill-server
adb devices
echo ************************
echo * Blocking OTA Updates *
echo ************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
sqlite3 devicemanager.db "update registry set value='manual' where name='com.bn.device.fota.mode';"
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
del devicemanager.db
ping -n 2 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting! *
echo * Disconnect the USB cable! *
echo * Done :) *
echo * *
echo * www.thexboxexpert.com *
echo *****************************
pause
exit
To allow access to updated run the following script the same way above was ran.
Code:
echo off
cls
echo *****************************************
echo * We will create the directory .Android *
echo * We will also create the adb_usb.ini *
echo *****************************************
md "%USERPROFILE%\.Android"
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini"
echo Success
adb kill-server
adb devices
echo ************************
echo * Allowing OTA Updates *
echo ************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
sqlite3 devicemanager.db "update registry set value='auto' where name='com.bn.device.fota.mode';"
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
del devicemanager.db
ping -n 2 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting! *
echo * Disconnect the USB cable! *
echo * Done :) *
echo * *
echo * www.thexboxexpert.com *
echo *****************************
pause
exit
Thanks xbox, your a scripting genius, I'm not worthy.......
Do we need "shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system" in the script? I'm a noob and I don't know what this does...
Because the other thread (http://forum.xda-developers.com/showthread.php?t=933291) doesn't mention this.
redking79 said:
Do we need "shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system" in the script? I'm a noob and I don't know what this does...
Because the other thread (http://forum.xda-developers.com/showthread.php?t=933291) doesn't mention this.
Click to expand...
Click to collapse
Just run the script and stop asking questions - j/k
That sets rw to the system folder until reboot. Eliminating any errors that might occur. To successfully answer your question, no you do not need it in the script but it doesn't effect anything negatively either.
xboxexpert said:
Just run the script and stop asking questions
That sets rw to the system folder until reboot. Eliminating any errors that might occur. To successfully answer your question, no you do not need it in the script but why are you editing my scrip in the first place :/
Click to expand...
Click to collapse
I am not editing your script nor doubting your abilities, but I'm asking because I want to learn.
redking79 said:
I am not editing your script nor doubting your abilities, but I'm asking because I want to learn.
Click to expand...
Click to collapse
Edited my response due to the fact that I've been working for 13 hours and am edgy I know you wanted to learn sorry for that read my edited post up top
redking79 said:
Do we need "shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system" in the script? I'm a noob and I don't know what this does...
Because the other thread (http://forum.xda-developers.com/showthread.php?t=933291) doesn't mention this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=933291 is where this came from, of course.... So probably better to ask there.
xbox just likes reposting things.. I guess he's making it slightly more user friendly so he can sell it on ebay.
I try running this script and keep getting "sqlite3 is not an internal or external file " and will not complete. I just installed the combo adb driver pack and everything installed fine. Can anyone help?
xboxexpert said:
Attached, Just run the blockupdates.bat file then sit back and relax. Obviously you need the Nook plugged in and ADB access enabled.
Code:
echo off
cls
echo *****************************************
echo * We will create the directory .Android *
echo * We will also create the adb_usb.ini *
echo *****************************************
md "%USERPROFILE%\.Android"
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini"
echo Success
adb kill-server
adb devices
echo ************************
echo * Blocking OTA Updates *
echo ************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
sqlite3 devicemanager.db "update registry set value='manual' where name='com.bn.device.fota.mode';"
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
del devicemanager.db
ping -n 2 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting! *
echo * Disconnect the USB cable! *
echo * Done :) *
echo * *
echo * www.thexboxexpert.com *
echo *****************************
pause
exit
Click to expand...
Click to collapse
khaytsus said:
http://forum.xda-developers.com/showthread.php?t=933291 is where this came from, of course.... So probably better to ask there.
xbox just likes reposting things.. I guess he's making it slightly more user friendly so he can sell it on ebay.
Click to expand...
Click to collapse
ebay got suspended months ago
Are there any sqlite apps in market to edit DBs on nook itself?
Jf-ws6. You likely need to install the android sdk on your PC.
bonzer2u said:
Jf-ws6. You likely need to install the android sdk on your PC.
Click to expand...
Click to collapse
I do have android sdk on my PC. i used this link and downloaded the combo sdk and driver.
http://forum.xda-developers.com/showthread.php?t=910008
JF-WS6 said:
I do have android sdk on my PC. i used this link and downloaded the combo sdk and driver.
http://forum.xda-developers.com/showthread.php?t=910008
Click to expand...
Click to collapse
Ahhh, did u edit/add to your path in windows?????????
# This step is optional but makes using ADB a lot easier
1. Start > Right-Click Computer > Properties > Advanced > Environment Variables
2. Under 'System Variables', scroll down to 'Path' and double click it
3. In 'Variable Value', scroll to the end and add ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools" (without the quotes)
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz1CpsmBNGE
Under Creative Commons License: Attribution Non-Commercial Share Alike
bonzer2u said:
Ahhh, did u edit/add to your path in windows?????????
# This step is optional but makes using ADB a lot easier
1. Start > Right-Click Computer > Properties > Advanced > Environment Variables
2. Under 'System Variables', scroll down to 'Path' and double click it
3. In 'Variable Value', scroll to the end and add ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools" (without the quotes)
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz1CpsmBNGE
Under Creative Commons License: Attribution Non-Commercial Share Alike
Click to expand...
Click to collapse
I'll try this tonight. Hope it works
confirmation of being run?
Since this was a Windows .bat file I ended up running the commands manually at a Linux shell prompt. The NC definitely rebooted, but is there an easy way to tell if the OTA updates were actually turned off?
Thanks!
Robert
Robertjm said:
Since this was a Windows .bat file I ended up running the commands manually at a Linux shell prompt. The NC definitely rebooted, but is there an easy way to tell if the OTA updates were actually turned off?
Thanks!
Robert
Click to expand...
Click to collapse
Unfortunately no. That's why I prefered to do it manually. Nothing wrong with the script but I just felt more confident doing each step myself and typing it in and making sure everything was what I expected. I did the block two days ago on my AutoNootered 1.01 NC and have used it extensively and haven't received any updates.
redking79 said:
Unfortunately no. That's why I prefered to do it manually. Nothing wrong with the script but I just felt more confident doing each step myself and typing it in and making sure everything was what I expected. I did the block two days ago on my AutoNootered 1.01 NC and have used it extensively and haven't received any updates.
Click to expand...
Click to collapse
You should never get updated as long as you maintain the 'manual' setting as described. I also do it manually but thats a personal preference, I asked xbox to script it as a courtesy to others that have asked since he is a scripin kinda guy....
bonzer2u said:
Ahhh, did u edit/add to your path in windows?????????
# This step is optional but makes using ADB a lot easier
1. Start > Right-Click Computer > Properties > Advanced > Environment Variables
2. Under 'System Variables', scroll down to 'Path' and double click it
3. In 'Variable Value', scroll to the end and add ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools" (without the quotes)
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz1CpsmBNGE
Under Creative Commons License: Attribution Non-Commercial Share Alike
Click to expand...
Click to collapse
Ok, did the path edit and still no luck. still says "sqlite3 is not recognized as an internal or external command, operable program or batch file"
I'm starting to get very frustrated!!!!! anymore ideas? i really dont want the update and each day goes by my chances go up. my wife's got updated yesterday. hers is stock though. please help....
ADB Wireless
I edited the bat file and added an "adb connect IPORT" for wireless ADB (app in market). This is a much simpler method than trying to install the USB driver.
Thanks worked
For me!
Sent from my LogicPD Zoom2 using XDA App
Related
DISCLAIMER: You know the risks, bricking, breaking etc. I'm not, nor is anyone else responsible if something goes wrong with your device, especially should it turn into a cave troll and bludgeon someone to death.
You will have to be rooted for this to work.
Update 1/5/11
Changed the install and loader scripts re-compressed and uploaded, new download link. Stream lined the installation process (removed 5 steps)
Update 1/4/11
reflect changes to ubuntu.sh and bootubuntu scripts and streamlining the process. Added screenshots
_________________________
I was over at nexusonehacks.net and looking at the ubuntu on nexus one hack and was thinking that this could be ported to the nook color. The idea is to run ubuntu from an img on the sd card.
The following is a modified version of the "how to" orginally posted here
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
Credits
The guys at NexusOneHacks
xda user munday who has modified the scripts to work for the nook color
Devs at XDA Developer for the Ubuntu ARM image for HTC HD2
Saurik (Jay Freeman) for the Debian G1 script, which was hacked for Ubuntu on Nexus One! and then re-hacked for the Nook Color by munday
Here we go:
1) Go download the ubuntu file here: http://www.megaupload.com/?d=67BU4Y3T
2) Extract the contents using 7zip http://www.7-zip.org/download.html
3) Copy the extracted folder "ubuntu" to the root of your SD card
4) Unmount the nook from your pc, go into the app NookColor Tools (if you don't have it download it here courtesy of Ben 74 and click All Settings->Development then uncheck Auto Mount. This will prevent the SD card from being mounted automatically when plugged into the PC
5) Plug the Nook back into your pc and open a command line then navigate to your android sdk folder ie C:\android-sdk or wherever you have it and type
Code:
adb devices
Hit enter and make sure that the nook color comes up (should be the SN of your Nook)
Note: This can also be done from terminal emulator instead of adb...but it is kind of a pain
6) Now we want to go into the command line on the nook so type
Code:
adb shell
Hit enter and this should bring up a "#" sign.
7) Type
Code:
su
hit enter (I do this just as a force of habit)
8) Now we navigate to the ubuntu folder we just copied to our sd card by entering
Code:
cd /sdcard/ubuntu
hit enter. To confirm you are where you want to be you can type
Code:
ls
and it should list the contents of the ubuntu folder.
9) Run the setup script ubuntu.sh by entering the following:
Code:
sh ./ubuntu.sh
hit enter
10) Now type
Code:
bootubuntu
and hit enter
11) So now we have ubuntu command line up and running which should look like:
Code:
[email protected]:/#
We will need to get some packages to run a gui and then connect to it via VNC client. So we need to update a few things first. Type:
Code:
apt-get update
then
Code:
apt-get install tightvncserver
now we need the gui elements so enter this:
Code:
apt-get install lxde
12) Type the following:
Code:
export USER=root
vncserver -geometry 1024×600
this sets the resolution...you can change it to play around, but the native resolution for the nook is 1024x600. This is also where you will set the password for your vnc server...make sure to remember it
13) Next, we are going to add the following to /root/.vnc/xstartup file using cat command: (hit enter after each line and ignore the fact that it looks like it does it twice)
Code:
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
After hitting enter after the last line press "Ctrl+D" twice then press enter
14) We need the vnc server to start every time we start ubuntu, type this:
Code:
cat > front
export USER=root
cd /
rm -r -f tmp
mkdir tmp
cd /
vncserver -geometry 1024×600
Same as before, hit enter after each line then after hitting enter for the last line press "Ctrl+D" twice then press enter.
15) Enter this
Code:
cat front /root/.bashrc > temp
Then
Code:
cp temp /root/.bashrc
16) Now on the nook open up your vnc viewer app (android vnc viewer or PocketCloud...or whatever you use)
Use the following settings:
Host Address: 127.0.0.1 (some don't require this)
Password: the password you set up in step 16
Port: 5901
Save and then click connect and you should be up and running on ubuntu! To leave ubuntu type exit from adb. This should kill ubuntu. Exit adb and then you can disconnect the nook from your pc.
To start ubuntu from the nook open up a terminal emulater and type:
Code:
bootubuntu
Hit enter, this should bring up the [email protected], hhen press "Home" key and open up your vnc app. Now you are ready to rock your Linux tablet!
You could also use gscript lite to automate the process of starting ubuntu so you don't have to type it in the terminal everytime. You can get gscript lite from the market or download the file I have attached.
It does seem a little laggy..just a little...for now anyway
To exit ubuntu: Disconnect the vnc client then hold the "Home" key (I use button savior which brings up a nice little task manager) and click the Terminal emulator when it pops up under running tasks. Once you are back in the terminal you can type:
Code:
exit
to shut down ubuntu.
Enjoy and make sure you thank munday and the guys at nexusonehacks and all the devs who helped make it possible.
-devastator
EDIT:
I noticed that after rebooting the nook would hang at the "Future of reading" screen....if this happens turn the device off remove the sd card the turn the nook back on. It should boot fine. After it's finished you can return the sd card and mount it. This is strange and I'm looking into it. I'm not sure if this is limited to me or if it is universal to all nooks. It also still fails at shutting ubuntu down for some reason. I'm still looking into this.g into this.
I got it going, just needed a few "busybox"-es here and there . It needs some work, right now to get X you have to use VNC.
It's sluggish but a bit more work might just yield something a bit more usable. I'll play more tomorrow night.
Here's my scripts:
ubuntu.sh
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
busybox modprobe ext2
rm -f /data/local/bin/fsrw
rm -f /data/local/bin/bootubuntu
rm -f /data/local/bin/unionfs
rm -f /data/local/bin/installer.sh
rm -f /data/local/bin/mountonly
mkdir /data/local/mnt
#busybox clear
rm /system/bin/fsrw
rm /system/bin/bootubuntu
rm /system/bin/unionfs
rm -/system/bin/mountonly
busybox cp -f fsrw /system/bin
busybox cp -f bootubuntu /system/bin
busybox cp -f unionfs /system/bin
busybox cp -f mountonly /system/bin
cd /sdcard/ubuntu
busybox chmod 4777 *
cd /system/bin/
busybox chmod 4777 *
cd /
#busybox clear
echo " "
echo "Ubuntu Chroot Bootloader v0.1"
echo "Ubuntu Bootloader is now installed!"
echo "This process does NOT damage Android OS!"
echo " "
echo "Original Installer by Charan Singh"
echo "Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net"
echo " "
echo "To enter the Debian Linux console just type 'bootubuntu'"
bootubuntu
Code:
mount -o remount,rw /dev/block/mmcblk0p5 /system
export kit=/sdcard/ubuntu
export bin=/system/bin
export mnt=/data/local/mnt
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
busybox mknod /dev/loop2 b 7 0
mount -o loop,noatime -t ext2 $kit/ubuntu.img $mnt
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4"
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "Setting localhost on /etc/hosts "
echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo "READY TO ROCK AND ROLL BABY! "
echo "Brought to you by NexusOneHacks.net and the open source community! "
echo " "
busybox chroot $mnt /bin/bash
#After exit command is executed clear it all up
echo " "
echo "Shutting down Ubuntu"
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
Then just followed the instructions at nexusonehacks.
note: to run bootubuntu i had to use sh and the use the full path:
Code:
# sh /system/bin/bootubuntu
other note: I was using adb not a term app on the nook.
Obligatory video
I can't post links yet so check: youtube.com/watch?v=TnXfZ6aagn8 for a really boring video
EDIT: switched the names, DOH!
I also had to use sh and the full path also. Thanks for the update on the script...gonna try it in the morning (it's 2am here) will also see if I can help to get it running smoother. What class SD card are you using? I imagine a class 4 or higher would yeild better results as far as responsiveness goes.
The sd is a class 2 that came in one of my dev phones. I'll pick up a faster one tomorrow after work and test it out.
It's just about 3am here now, we must be in the same time zone.
I'm going to bed now, but first here's a modded version of the script you had originally posted that also works now.
bootubuntu
Code:
#!/bin/sh
mount -o remount,rw /dev/block/mmcblk0p5 /system
export kit=/sdcard/ubuntu
export bin=/system/bin
busybox [ ! -d /data/local/ubuntu ] && mkdir /data/local/ubuntu
export mnt=/data/local/ubuntu
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
busybox mknod /dev/loop1 b 7 0
busybox losetup /dev/block/loop1 /sdcard/ubuntu/ubuntu.img
mount -t ext2 /dev/block/loop1 /data/local/ubuntu
#mount -o loop,noatime -t ext2 $kit/ubuntu.img $mnt
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4"
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "Setting localhost on /etc/hosts "
echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo "READY TO ROCK AND ROLL BABY! "
echo "Brought to you by NexusOneHacks.net and the open source community! "
echo " "
busybox chroot $mnt /bin/bash
#After exit command is executed clear it all up
echo " "
echo "Shutting down Ubuntu"
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
busybox losetup -d /dev/loop1
#unregistering the loopback device just seems to die. need to fix or remove.
I'll look at the N1 formus tomorrow too and see if they have made progress in getting X to run fast or without need for VNC.
Nice work, I am addicted in seeing the crazy crap people are doing everyday.
Couldn't sleep so I'm messing around with it now...I'm using a class 4 and have it up and running. It does seem to be a little laggy, but I don't have a class 2 to compare it to. Let me know what you find out, I'll keep playing with it also to see if I can get it to be more responsive...but we are definately on our way to having a great little linux tablet in addition to android. You should also be able to use this for other builds of linux also by just changing out the .img file to a flavor of your choosing. I'm excited
I have also updated the OP with the how to and credits. Really appreciate your help munday.
I noticed that after rebooting the nook would hang at the "Future of reading" screen....if this happens turn the device off remove the sd card the turn the nook back on. It should boot fine. After it's finished you can return the sd card and mount it. This is strange and I'm looking into it. I'm not sure if this is limited to me or if it is universal to all nooks.
Edit:
Running into some strange occurrences...it appears that when you type exit from the terminal to kill ubuntu, I believe ubuntu stays running...anyway, I'm going to bed and will work on it more tomorrow.
devastatorx said:
You should also be able to use this for other builds of linux also by just changing out the .img file to a flavor of your choosing. I'm excited
Click to expand...
Click to collapse
Are there any increased risks with changing the version you use?
Well, you will want to make sure that the build supports ARM based devices.
munday said:
Then just followed the instructions at nexusonehacks.
note: to run bootubuntu i had to use sh and the use the full path:
Code:
# sh /system/bin/bootubuntu
Click to expand...
Click to collapse
I fixed this, the scripts were backwards, I have updated the OP to reflect the changes and bootubuntu now works
devastatorx said:
I fixed this, the scripts were backwards, I have updated the OP to reflect the changes and bootubuntu now works
Click to expand...
Click to collapse
sweet, i can't wait to get home to play more!!!
I've tried running ubuntu.sh from the terminal emulator (With su) and from ADB, and have not had success with either.
The readout is:
Code:
': File existste '/system/bin
': File existste '/system/bin
': File existste '/system/bin
: not found
: not found
cd: can't cd to /sdcard/ubuntu
: not found
: No such file or directory
: not found
cd: can't cd to /system/bin
: not found
: No such file or directory
: not found
cd: can't cd to /
: not found
: not found
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
etc., etc.
Is there a problem with how I copied the script? I assume the first part about the file existing is due to this being the third or fourth time I've tried running the script (Unsuccessfully), but I've no idea how to interpret the rest.
Thanks
munday said:
sweet, i can't wait to get home to play more!!!
Click to expand...
Click to collapse
I sent you a message
Link3737 said:
I've tried running ubuntu.sh from the terminal emulator (With su) and from ADB, and have not had success with either.
The readout is:
Code:
': File existste '/system/bin
': File existste '/system/bin
': File existste '/system/bin
: not found
: not found
cd: can't cd to /sdcard/ubuntu
: not found
: No such file or directory
: not found
cd: can't cd to /system/bin
: not found
: No such file or directory
: not found
cd: can't cd to /
: not found
: not found
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
etc., etc.
Is there a problem with how I copied the script? I assume the first part about the file existing is due to this being the third or fourth time I've tried running the script (Unsuccessfully), but I've no idea how to interpret the rest.
Thanks
Click to expand...
Click to collapse
Try using these, just unrar and then copy them in your ubuntu folder, if it asks to overwrite just click yes...also you have autmounting of the sd card turnned off in nook color tools settings right?
Yeah, it must have been an error on my end. Using the updated scripts you posted worked like a charm.
Thanks!
Link3737 said:
Yeah, it must have been an error on my end. Using the updated scripts you posted worked like a charm.
Thanks!
Click to expand...
Click to collapse
Good to hear!
I'm currently working on making this a port to the SD card so that with the sd card in it boots into ubuntu from power off, and with the sd card out it boots to android then you replace the sd and use it for storage like normal. It will also run a lot snappier....well that's the idea anyway.
devastatorx said:
Good to hear!
I'm currently working on making this a port to the SD card so that with the sd card in it boots into android from power off, and with the sd card out it boots to android then you replace the sd and use it for storage like normal. It will also run a lot snappier....well that's the idea anyway.
Click to expand...
Click to collapse
Booting from SD in the same fashion as Nookie Froyo? That sounds like it would give a huge performance boost over the current method, I can't wait to see what you come up with.
This should be acheivable using the method mentioned in this topic:
http://forum.xda-developers.com/showthread.php?t=873243 thanks to clockworx.
Currently looking into this
devastatorx said:
This should be acheivable using the method mentioned in this topic:
http://forum.xda-developers.com/showthread.php?t=873243 thanks to clockworx.
Currently looking into this
Click to expand...
Click to collapse
I was thinking the exact same thing, the nook seems to like booting from sd, so we should be able to set up the partitions like the foryo sd and edit the init.rc and env.txt to boot ubuntu instead of android. Just a theory though. It's my plan for tonight anyway.
munday said:
I was thinking the exact same thing, the nook seems to like booting from sd, so we should be able to set up the partitions like the foryo sd and edit the init.rc and env.txt to boot ubuntu instead of android. Just a theory though. It's my plan for tonight anyway.
Click to expand...
Click to collapse
I also stumbled across this: http://androix.org/ Which talks about a native android xserver which does a way with the vnc aspect altogether. I downloaded and attempted to install but I get the error "There is a problem parsing the package" and I haven't had any luck plus there isn't much documentation.
Let me know how it goes munday, I'll be working on the same thing later (have to take the fiance out for dinner)
question
I was just curious, after installing ubuntu can we install flash as we would had we booted linux from netbook?
Sorry for opening a new thread on this, but as new users can't post - for a good reason, I am sure - in the dev's section, I, being a new user, can't as well...
I have the same problem as described by haggardh and arko.amit, which is the nt not showing up when running the NookandZergy.bat after following all the steps mentioned, hopefully, properly. Running the NookandZergy.bat as admin gives an error message stating the command "adb" is unknown.
Just hoping to emphasise that this issue might be statistically significant (and worth looking into)...other than that this is just another me-too-post. Sorry once more.
Give this a go:
http://forum.xda-developers.com/showthread.php?t=1363652
i had to download the program in that thread and delete all usb references to Nook from my computer.
My Solution to Root
Wurstwarenfachverkäuferin said:
Sorry for opening a new thread on this, but as new users can't post - for a good reason, I am sure - in the dev's section, I, being a new user, can't as well...
I have the same problem as described by haggardh and arko.amit, which is the nt not showing up when running the NookandZergy.bat after following all the steps mentioned, hopefully, properly. Running the NookandZergy.bat as admin gives an error message stating the command "adb" is unknown.
Just hoping to emphasise that this issue might be statistically significant (and worth looking into)...other than that this is just another me-too-post. Sorry once more.
Click to expand...
Click to collapse
I experienced some of the same problems you and haggard wrote about and even some other users that were experiencing no serial number showing up when running the Nookandzergy.bat. After reading and a little experimentation of my own I got mine rooted last night. My test machine was Windows XP SP3 I am skipping the tgps.apk part on the Nook because I ran into no problems with it. It did goes as the instructions said. With that said make sure you put all the checks in the right place in the debug menu.
First of all if you can't run adb then you have the adb.exe in the wrong folder or you are trying to execute with the wrong path. Should be in the C:\ntroot directory. Open a command line up (Start > RUN >CMD)
You will need to change to directory c:\ntroot
Once your cmd prompt reads C:\ntroot you should be able to run adb. You really shouldn't have to unless you are running into a problem with the serial number not showing up after running zerg. If that is the case you can always run "adb devices" that will start the adb daemon and then run the command and tell you rather or not your computer is seeing the nook. If you get no devices connected then you are back to the driver issue.
My solution for the driver issue I got the same USB Mass Storage Device and then would try and change the driver to the Android one, but kept getting the above problem when trying to run zerg.
So I uninstalled the driver (Android and USB Mass Storage) and unplugged the Nook.
Then in Windows Explorer went to the usbdrivers folder and right-clicked on the file android_winusb.inf and clicked "install"
I then plugged the nook back in and the driver showed correctly in Device Manager as an Android device.
I then ran zergy again and it all worked an the ID showed up correctly.
I hope this helps.
k
Thanks for the suggestions. The OS is Win 7 64 if that matters.
I have de- and reinstalled the usb-driver several times in the device-manager (installing by "install..." from explorer's context menu doesn't work for this file and this OS) - the device just doesn't show up in command line, regardless whether I use the adb devices command or run the nookandzergy.bat.
Sounds definitely to be the driver. I read the link posted by AugustusBot helpful, but not sure it would work for sure. I had to uninstall and reinstall until finally I ran the INF like you mentioned that didn't work for you.
Does the device show up with an exclamation or as a USB mass storage device?
With no specific driver installed (intentionally, that is), the device is shown as both usb mass storage device and "nook tablet" with the yellow exclamation mark within the device manager.
I also used that usb deview tool mentioned in the other thread to wipe all usb devices. This doesn't do a permanent uninstall - as deleting the driver would. Unplugging a device and plugging it in again and it would just show up as it did before... Either way, the tool doesn't help here.
Have you right clicked on Nook tablet within device manager clicked properties > driver > update driver software > update driver > browse my computer for driver software > Let me pick from a list of device drivers > Have Disk > Browse > C:\ntroot\usbdrivers\android_winusb.inf
I just tried that process on a Windows 7 64bit and got an error saying the device driver is not compatible with a 64 bit OS. If you get the same error you may have to find the 64 bit version of that device driver or if you are familiar with working with XP classic within Windows 7 you may have better luck using it through that.
Try right clicking on the mass storage device and select to install manually then install from a specific location, have disk, then select the inf file for the driver... might work.
Sent from my BNTV250 using xda premium
I did install the driver both ways using the bat-file and manually through device manager, pointing to the folder that contains the inf-file. Actually, you can't point to a file but only to folders (saying "you", I mean "me", of course; is that different on your machine?)
(Why do I get a prevent-spam-wait-5-mins-message editing my own post? Weird.)
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
armysean77 said:
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
Click to expand...
Click to collapse
Download the settings file listed in the post via your tablet, install using the package installer, enable debugging (checking both debugging options) run the script to root.
Sent from my HTC Glacier using xda premium
I had no end of difficulties with the root process.
Running Windows 7 32 bit.
Procedure to root instructions neglect to emphasise the NEED to DROP the Nook Tablet into debug mode first before connecting it to the PC. I didn't do this, and so Window drivers were installed automatically on first connect, and this started a long trip trying to replace the drivers to no avail. Eventually managed to removed the drivers from all USB using the tools from another thread.
After that, I managed to install the USB drivers and have the Nook show up as an Android phone.
Unticked/ticked all debug mode a second time to ensure they are locked in place.
Run the Zergy.bat and get the numbers for ID of the tablet, and the thing starts to proceeds and then stops with an error stating that it is not a Tablet device... 8(
Gave up and re run the entire procedure on a Windows XP laptop (fresh install) and everything went through without a hitch. I now have a rooted Nook Tablet.
I suspect something in Windows 7 is interferring with the second script.
Key point:
Put Tablet in debug mode first.
Untick and retick the USB connection on Tablet before each attempt to run Zergy script.
Another thing I did, but was unsure if it fixed anything was manually changed the runmefirst.bat script to look like this:
@echo off
echo Please unplug your nook device before continuing!
pause
if exist "c:\ntroot\.android\adb_usb.ini" echo You do not need to have it added!
IF NOT EXIST "c:\ntroot\.android\" md "c:\ntroot\.android"
echo 0x2080 > "c:\ntroot\.android\adb_usb.ini"
echo success!
echo now plug it back in
echo now install the drivers - instructions in the thread
echo **************************************************************
echo * Install "Nook" with the drivers I provided in this pack. *
echo * You can find the fixed drivers in the "usbdrivers" folder. *
echo * After your done you should have adb access through DOS! *
echo **************************************************************
devmgmt.msc
pause
echo "now you can run the Nook&Zergy"
ping 1.1.1.1 -n 1 -w 2000 > NUL
and the nookandzergy.bat script to look like this:
@echo off
color 0c
adb kill-server
cls
:vendorfixed
find "0x2080" "c:\ntroot\.android\adb_usb.ini"
if errorlevel==0 goto start
if errorlevel==1 goto novendor
:start
cls
adb kill-server
adb devices
echo did your nook Tablet show up?
echo type Y for yes and N for no
SET /P menunr=Please make your decision:
IF %menunr%==Y (goto check)
IF %menunr%==N (goto sorry)
:check
echo first need to make sure you didnt lie about it showing up and check for root.
adb wait-for-device
echo verifying that your device is indeed a Barnes and Noble Nook tablet
del build.prop
adb pull system/build.prop
find "ro.product.device=blaze" build.prop
if ERRORLEVEL==0 SET device=Nook Tablet
if ERRORLEVEL==1 goto oops
echo now checking for root!
del su.txt
adb pull /system/bin/su su.txt
cls
if exist su.txt echo already rooted! && goto prerooted
if not exist su.txt goto ok
k
cls
echo your device is a %device% meaning we can continue!
ping 1.1.1.1 -n 1 -w 2000 > NUL
echo now just making sure you WANT to root it!
:choice1
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok1
goto choice1
k1
set C1=%C%1
goto %C1%
:Y1
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device
adb install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell "cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /"
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb install busyboxinstall.apk
cls
:N1
echo would you like to install gApps?
:choice2
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok2
goto choice2
k2
set C2=%C%2
goto %C2%
:Y2
set gapps=yes
adb remount
adb push system\app\CarHomeGoogle.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system\app\FOTAKill.apk /system/app/
adb shell chmod 644 /system/app/FOTAKill.apk
adb push system\app\GenieWidget.apk /system/app/
adb shell chmod 644 /system/app/GenieWidget.apk
adb push system\app\GoogleBackupTransport.apk /system/app/
adb shell chmod 644 /system/app/GoogleBackupTransport.apk
adb push system\app\GoogleCalendarSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleCalendarSyncAdapter.apk
adb push system\app\GoogleContactsSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
adb push system\app\GoogleFeedback.apk /system/app/
adb shell chmod 644 /system/app/GoogleFeedback.apk
adb push system\app\GooglePartnerSetup.apk /system/app/
adb shell chmod 644 /system/app/GooglePartnerSetup.apk
adb push system\app\GoogleQuickSearchBox.apk /system/app/
adb shell chmod 644 /system/app/GoogleQuickSearchBox.apk
adb push system\app\GoogleServicesFramework.apk /system/app/
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb push system\app\LatinImeTutorial.apk /system/app/
adb shell chmod 644 /system/app/LatinImeTutorial.apk
adb push system\app\MarketUpdater.apk /system/app/
adb shell chmod 644 /system/app/MarketUpdater.apk
adb push system\app\MediaUploader.apk /system/app/
adb shell chmod 644 /system/app/MediaUploader.apk
adb push system\app\NetworkLocation.apk /system/app/
adb shell chmod 644 /system/app/NetworkLocation.apk
adb push system\app\OneTimeInitializer.apk /system/app/
adb shell chmod 644 /system/app/OneTimeInitializer.apk
adb push system\app\Talk.apk /system/app/
adb shell chmod 644 /system/app/Talk.apk
adb push system\app\Vending.apk /system/app/
adb shell chmod 644 /system/app/Vending.apk
adb push system\etc\permissions\com.google.android.maps.xml /system/etc/permissions/
adb push system\etc\permissions\features.xml /system/etc/permissions/
adb push system\framework\com.google.android.maps.jar /system/framework/
adb push system\lib\libvoicesearch.so /system/lib/
echo Thank you for choosing to install gapps courtesy of anlog
ping 1.1.1.1 -n 1 -w 2000 > NUL
cls
:N2
echo Would you like to replace certain system applications to make you have a more tablet like experience?
echo this replaces Keyboard, Email, Gallery, and adds live wallpapers! Please select Y or N.
echo you need another launcher to be able to use live wallpapers.
:choice3
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok3
goto choice3
k3
set C3=%C%3
goto %C3%
:Y3
adb push Email.apk /system/app/Email.apk
adb push Gallery3D.apk /system/app/Gallery.apk
adb push LatinIME.apk /system/app/LatinIME.apk
adb push LiveWallpapers.apk /system/app/LiveWallpapers.apk
adb push LiveWallpapersPicker.apk /system/app/LiveWallpapersPicker.apk
adb shell chmod 644 /system/app/Email.apk
adb shell chmod 644 /system/app/Gallery.apk
adb shell chmod 644 /system/app/LatinIME.apk
adb shell chmod 644 /system/app/LiveWallpapers.apk
adb shell chmod 644 /system/app/LiveWallpapersPicker.apk
:N3
@echo off
echo Please select 1 for Go launcher
echo Please select 2 for ADW Launcher
echo please select 3 for HoneyComb Launcher
echo Please select 4 for none of them and to continue to the debloater
SET /P launch=Please make your decision:
IF %launch%==1 (set launcherinstall="yes "& set launcher=GO)
IF %launch%==2 (set launcherinstall="yes "& set launcher=adw)
IF %launch%==3 (set launcherinstall="yes "& set launcher=Honeycomb_Launcher)
IF %launch%==4 (goto debloater)
echo %launcher%
adb install launcher\%launcher%.apk
IF %launcherinstall%=="yes " adb install launcher\Homecatcher.apk
pause
goto debloater
:sorry
echo Your device is not found, I'm sure USB debugging HAS to be enabled.
ping 1.1.1.1 -n 1 -w 2000 > NUL
exit
ops
echo your device is NOT a nook tablet! Please try again with either usb debugging properly enabled, or with the correct device hooked up. You might also need to install drivers!
echo just incase you missed doing it, running runmefirst.bat
if exist runmefirst.bat call runmefirst.bat
if not exist runmefirst.bat echo No batch file found!
:complete
echo OK!
:N4
echo Thank you for using Indirect's batch script to root the nook tablet combined with Anlog's script to install gApps.
adb shell chmod 644 /system/app/*.apk
adb shell chmod 644 /data/app/*.apk
set install=ok
if install==ok echo GOOOD JOB! Now rebooting!
adb reboot
ping 1.1.1.1 -n 1 -w 2000 > NUL
exit
:novendor
cls
echo Oops! You do not have the USB Vendor ID entered into the correct file! Running runmefirst to correct this.
ping 1.1.1.1 -n 1 -w 2000 > NUL
call runmefirst.bat
goto vendorfixed
rerooted
cls
echo Your device was found to be rooted. Which is upsetting because now the root won't work again (you already have root) so you also can't use this script to install gApps or system mods.
echo _
echo because ADB doesn't allow us to remount unless adb is running as root (can't run without a kernel mod)
echo _
echo You can however download the one click unroot app in the Android Development section to unroot after you install it on your device.
echo _
echo However, before you do that, I suggest backing everything up as it COMPLETELY wipes the device (including the system partition) so you lose root and all mods.
echo _
echo Have a nice day!
ping 1.1.1.1 -n 1 -w 10000 > NUL
exit
:debloater
cls
echo Do you want to de-bloat the device?
echo This does NOT remove anything that would remove access to the nook function of E-reading and whatnot. Just removes
echo Hulu, default launcher (if you installed a new one), default search app (if you used gApps), Chess, Sudoku and thats it.
echo Search being removed will actually stop you from using the search function in the nook bar.
:choice4
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok4
goto choice4
k4
set C4=%C%4
goto %C4%
:Y4
ebloatmenu
cls
echo Please select 1 for Full Debloat (Launcher, games, Hulu and pandora, so basically 2,3, and 4.)
echo Please select 2 for Launcher only removal (Will only run if you have installed a new launcher) It's a safety feature.
echo Please select 3 for Game applications removal
echo Please select 4 for Media application removal (Hulu and Pandora) (NOT NETFLIX)
echo Please select 5 to run the EXTREME debloater (Does all of the above and
echo removes ALL barnes and noble apps from your device
echo so you lose ALL functionality towards B and N but
echo you have a normal android tablet
echo DO NOT ASK FOR SUPPORT WITH THIS OPTION, you will be ignored.)
echo Select 6 to finish this section of the script.
SET /P debloat=Please make your decision:
IF %debloat%==1 goto Full
IF %debloat%==2 goto Launcher
IF %debloat%==3 goto Game
IF %debloat%==4 goto Media
IF %debloat%==5 goto Extreme
IF %debloat%==6 goto complete
:Full
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
set gapps=no
goto debloatmenu
:Launcher
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
set gapps=no
goto debloatmenu
:Games
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
set gapps=no
goto debloatmenu
:Media
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
goto debloatmenu
:Extreme
Echo ARE YOU POSITIVE YOU WANT TO RUN THIS?
echo We will not be mad if you say no,
echo these apps that are removed do nothing to the tablet
echo but remove the ability to read from the library and in general use the entire nook as an e-reader / anything from barnes and noble
echo and it turns it into a normal android tablet.
echo I removed these apps and the tablet itself functions fine
echo I just can't use anything from B&N.
echo If you run this, I WILL NOT HELP YOU!
echo Use the one click unroot app to get back all of these apps.
:choice5
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok5
goto choice5
k5
set C5=%C%5
goto %C5%
:Y5
adb shell rm -r /system/app/Accessories.apk
adb shell rm -r /system/app/AppLauncher.apk
adb shell rm -r /system/app/B3AndroidReader.apk
adb shell rm -r /system/app/BnAppInstaller.apk
adb shell rm -r /system/app/BnAuthenticationService.apk
adb shell rm -r /system/app/BnCloudRequestSvc.apk
adb shell rm -r /system/app/BnConnectivityService.apk
adb shell rm -r /system/app/BnPolicyManagerSvc.apk
adb shell rm -r /system/app/CloudService.apk
adb shell rm -r /system/app/CryptoServer.apk
adb shell rm -r /system/app/DemoMode.apk
adb shell rm -r /system/app/DRPReader.apk
adb shell rm -r /system/app/GSearch.apk
adb shell rm -r /system/app/Home.apk
adb shell rm -r /system/app/LatinImeTutorial.apk
adb shell rm -r /system/app/Library.apk
adb shell rm -r /system/app/NookCommunity.apk
adb shell rm -r /system/app/Quickoffice_Viewer_3.3.5.apk
adb shell rm -r /system/app/RDGEReaderAcclaim.apk
adb shell rm -r /system/app/Reader.apk
adb shell rm -r /system/app/Shop.apk
adb shell rm -r /system/app/Social.apk
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
goto debloatmenu
:N5
echo you decided to not run the Extreme Debloater
echo now returning you to the debloater menu.
ping 1.1.1.1 -n 1 -w 1000 > NUL
goto debloatmenu
My reasoning was prior to me changing the path from %USERPROFILE to C:\ntroot I was receiving an error in profile path due to Windows XP having the profile set to C:\documents and settings\kerry63\... and I was getting some error about not being able to parse the space in "documents and settings".
I would not imagine this needing to be changed on Windows 7 due to the fact that the %USERPROFILE should be C:\users\kerry63 hence no spaces. All the runmefirst.bat script does is place the .android folder with a .ini file that gives the vendor ID to the nookandzergy.bat script.
This is nothing new just trying to make sure all the bases are covered since people do run different Windows OS. I take no credit for the script just trying to give advice and procedures that helped me get mine working. I did have all the problems that everyone else spoke about.
I had to triple check the three changes made in the debug mode by tgps.apk on the NOOK.
Changed the script and then ran it.
Installed drivers and uninstalled them until I got the NOOK! and installed the .inf prior to the plugging in of the NOOK.
The above scripts are verbatim of what I used you can use them by just pasting them separately into notepad and naming them accordingly.
Hope this helps.
armysean77 said:
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
Click to expand...
Click to collapse
Make sure the Tablets is in debug mode and automount is unticked. Even if it is set correctly, untick and retick the settings BEFORE each attempt to run the Zergy script.
In my case, I manage to get it ot recognise the tablet, but the scripot aborted with an error stating that it is not a tablet device... 8(
Running the same procedure again on another laptop running xp worked.
kerry63 said:
Another thing I did, but was unsure if it fixed anything was manually changed the runmefirst.bat script to look like this:
[...]
My reasoning was prior to me changing the path from %USERPROFILE to C:\ntroot I was receiving an error in profile path due to Windows XP having the profile set to C:\documents and settings\kerry63\... and I was getting some error about not being able to parse the space in "documents and settings".
I would not imagine this needing to be changed on Windows 7 due to the fact that the %USERPROFILE should be C:\users\kerry63 hence no spaces. All the runmefirst.bat script does is place the .android folder with a .ini file that gives the vendor ID to the nookandzergy.bat script.
This is nothing new just trying to make sure all the bases are covered since people do run different Windows OS. I take no credit for the script just trying to give advice and procedures that helped me get mine working. I did have all the problems that everyone else spoke about.
I had to triple check the three changes made in the debug mode by tgps.apk on the NOOK.
Changed the script and then ran it.
Installed drivers and uninstalled them until I got the NOOK! and installed the .inf prior to the plugging in of the NOOK.
The above scripts are verbatim of what I used you can use them by just pasting them separately into notepad and naming them accordingly.
Hope this helps.
Click to expand...
Click to collapse
If I got that right, you changed the paths replacing %userprofile% with c:\ntroot. Sorry for asking, as I should be able to find out myself, but... are there more changes made? (The runmefirst.bat you used is not the same (anymore) as in the root-thread by indirect.)
However, I replaced %userprofile% with c:\ntroot in both scripts. The outcome was an empty .android folder being created in c:\ntroot by the runmefirst.bat - this didn't happen before. Other than that still no device listed by adb.
I gave it one more try and used the runmefirst.bat from the usbdrivers.zip - after that the nook was listed and more or less rootable (more: it kind of worked; less: the root script's command line just closed at some point within the debloating leaving the device in Idontknowwhat state... but it still seems to work)
However, as there are two files named runmefirst in the whole package, people should be told which runmefirst.bat to actually run first (or at all).
Thanks for all the advice! It did help.
Solved
I tried several computers and could not get the nook to install with the unknown devise question mark. I finally figured it out. I had an SD card already installed in the Nook. It kept getting registered as a mass storage device. I removed the SD card and started with a fresh install of XP. Everything worked perfect.
this orked for me that way... hope this help you guys.
dodgepot said:
Try right clicking on the mass storage device and select to install manually then install from a specific location, have disk, then select the inf file for the driver... might work.
Sent from my BNTV250 using xda premium
Click to expand...
Click to collapse
thanks. for all the great minds and great Devs here.
Files
Do you guys still have access to these files all links I've found point to a drop box folder that is out of order.
I found this Windows application on this thread http://forum.xda-developers.com/showthread.php?p=23291051 I think its a valuable software to install all our apk in one time to save time after each ROM flash.
Windows? Owwww. I have linux mint. imo I don't like windows
sent from my x8 running sde ROM
Click THANKS if I helped
wilbso said:
Windows? Owwww. I have linux mint. imo I don't like windows
Click to expand...
Click to collapse
Let me help you with a very basic script then...
Code:
#!/bin/sh
for apk in `ls $1 | grep .apk`
do
adb install $apk
done
Copy/Paste into gedit, save in, for example, ~/bin, as apkbatch, make the script executable.
For example, run it as...
apkbatch ~/Android/APKs
Of course this is just a skeleton ... you could refine the script with:
- a check to see if adb even exists in the search path
- a check if adb is already running or not - and if not starting it up
- checking back with the user about to either WiFi connect or USB connect
Hint: Modify and extend the skeleton script from above to learn a bit about shell scripting and surprise us with a fully-fledged APK batch installer script for Linux.
APK batch installer
Based on B.Jay's answer, I believe the best thing for linux is to do this.
install android-tools-adb, nautilus-actions
Save the following code to $HOME/bin/apk_batch_install and make it executable.
Code:
#!/bin/sh
which adb || { notify-send 'Please install android-tools-adb before using this script.' ; exit 1; }
echo "APK install log:" > /tmp/apk_batch_install_log
echo "" >> /tmp/apk_batch_install_log
count=1
(
adb start-server
echo "#Waiting for device ..."
adb wait-for-device
for file in "[email protected]"
do
echo "#Installing $count/$#: $(basename "$file")"
adb install "$file" 1>> /tmp/apk_batch_install_log
echo "" >> /tmp/apk_batch_install_log
count=$(( count+1 ))
echo "$(echo "scale=0; $count*100/$#" | bc)"
done
) | zenity --progress \
--title="APK installation" \
--text="Starting adb server ..." --percentage=0 --auto-close --no-cancel
notify-send "APK installation completed"
zenity --info --text="$(cat /tmp/apk_batch_install_log)"
rm /tmp/apk_batch_install_log
and use "Nautilus Actions" to put it to context menu.
After that just select the files you want to install -> right click -> APK install !!
To configure "Nautilus Actions"
1) Add new Action
2) Name it "APK install"
Command Tab
3) Command Path: /home/.../bin/apk_batch_install
4) Command Parameters: %F
Mimetype Tab
5) Add a mimetype filter with mimetype: application/vnd.android.package-archive
6) Remove the filter with * in mimetype
Save
Well done for reviving a year old thread
Sent from my X8 using xda app-developers app
Can anyone write an .sh script so i can use it on android device to install apk from storage
Thanks in advance
Kellwa said:
Can anyone write an .sh script so i can use it on android device to install apk from storage
Thanks in advance
Click to expand...
Click to collapse
Why would you need one? Simply use the relevant xposed module to suppress install notifications and click through them once.
Dropped my phone this morning (~80cm) & screen cracked; now I've got no response from touchscreen at all.
LG Optimus G
CWM 6.0.4.7
Cyanogenmod 11
all data backed up
I can access ADB shell when it's in recovery mode but once booted up it just connects as MTP device and ADB doesn't see it (nor does fastboot). I've tried an OTG cable with mouse, no luck there. I have a bluetooth mouse but no way to pair it!
Do I just have the wrong driver in windows? Device manager says "LGE Android MTP Device" because I had (at some point earlier) installed the LG usb drivers and recovery tool.
You don't have debugging on is my best guess, but if you're just trying to pull some files you can do this through recovery. Or is there another reason you want adb on while in os?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You don't have debugging on is my best guess, but if you're just trying to pull some files you can do this through recovery. Or is there another reason you want adb on while in os?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct, I don't believe it was enabled in android os. I was hoping to use Screencast or ADB or something to control my phone until I get a chance to order a new screen
you can try this
boot to recovery
use adb to pull build.prop
Code:
adb pull /system/build.prop /location/on/pc
add these lines (or change accordingly if present)
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
now push it back
Code:
adb push location/on/pc/build.prop /system/build.prop
and fix permissions in recovery or
Code:
adb shell
su
chmod 644 build.prop
or try just editing it in a shell like
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
then reboot
either method i would suggest doing a backup in recovery first, just in case, but should be fine
best of luck!
Thank you! I will try when I get home
demkantor said:
you can try this
boot to recovery
use adb to pull build.prop
Code:
adb pull /system/build.prop /location/on/pc
add these lines (or change accordingly if present)
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
now push it back
Code:
adb push location/on/pc/build.prop /system/build.prop
and fix permissions in recovery or
Code:
adb shell
su
chmod 644 build.prop
or try just editing it in a shell like
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
then reboot
either method i would suggest doing a backup in recovery first, just in case, but should be fine
best of luck!
Click to expand...
Click to collapse
Here's what I got:
Code:
G:\android sdk\sdk\platform-tools>adb devices
List of devices attached
01a9a0f610c750f6 recovery
G:\android sdk\sdk\platform-tools>adb root
adbd is already running as root
G:\android sdk\sdk\platform-tools>adb pull /system/build.prop C:\testing\
remote object '/system/build.prop' does not exist
G:\android sdk\sdk\platform-tools>
so then I tried:
Code:
G:\android sdk\sdk\platform-tools>adb shell
~ # ls
ls
boot external_sd property_contexts storage
cache file_contexts recovery sys
charger fstab.geehrc res system
data init root tmp
datadata init.rc sbin ueventd.geehrc.rc
default.prop initlogo.rle888 sd-ext ueventd.rc
dev internal_sd sdcard
emmc mnt seapp_contexts
etc proc sepolicy
~ # cd system
/system # /system # ls -R -l
ls -R -l
.:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
./bin:
Then I found default.prop in ./ (http://pastebin.com/RFyhMJe9) and added the first two lines you suggested (it already had usb.config=mtp,adb) but rebooted and no USB debugging. Booted back into recovery and the lines I added were gone.
You may need to mount /system r/w first as its protected its possible that it won't allow you to pull it otherwise... Can't recall
Default.prop I believe will often do this upon reboot as its part of the ramdisk. To fully edit this try looking at this
http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
But really you just need to look for the build.prop
Just follow the part where I said edit in shell from above, this should work
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You may need to mount /system r/w first as its protected its possible that it won't allow you to pull it otherwise... Can't recall
Default.prop I believe will often do this upon reboot as its part of the ramdisk. To fully edit this try looking at this
http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
But really you just need to look for the build.prop
Just follow the part where I said edit in shell from above, this should work
Click to expand...
Click to collapse
I'll try that. Is there a find command I could use to find build.prop? I'm out of ways to look for build.prop, as I couldn't find it in /system or /sys.
It should be in /system , never seen it elsewhere. Maybe grab the build.prop from the ROM you are running (like direct from a download of the ROM, just unzip) edit this and push it in place, then fix permissions
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You may need to mount /system
Click to expand...
Click to collapse
Bingo! looked in CWM recovery settings and found "Mount /system"
Once I did this, I could see all the files in /system, including build.prop. I updated build.prop and checked file persmissions (they were already correct, wierd). Rebooted, now ADB can see it:
Code:
>adb devices
List of devices attached
01a9a0f610c750f6 unauthorized
and when I try to run screencast (https://code.google.com/p/androidscreencast/) I get a bunch of java errors, including this:
Code:
java.io.IOException: device (01a9a0f610c750f6) request rejected: device unauthorized. Please check the confirmation dialog on your device.
If I try to send a keyevent, I get a similar message:
>adb shell input keyevent 3
Code:
error: device unauthorized. Please check the confirmation dialog on your device.
Realized this meant my PC wasn't authorized, so I followed these instructions: http://stackoverflow.com/questions/...ithout-previous-usb-pairing/15747430#15747430
and now I'm authorized!
Glad it worked out for you! Check out droid explorer and android commander, both should work well for you and have some more advanced options besides just screen cast
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks again, demkantor! I'll give those a try, since screencast only displays on my PC, none of the controls seem to work, and running commands like below are pretty slow:
Code:
adb shell input swipe 390 1100 650 1100 [I] (unlock swipe)[/I]
adb shell input keyevent 3 [I](home button)[/I]
[CODE]
EDIT:
Tried those but they both seem depricated and old. I got AirDroid which isn't exactly remote control but allows reading/writing of texts among other things, and works whenever you get on wifi.
I am trying to do the same thing but I do not know how to append the line I got from my PC. As well on my LG e970 which has not been ever authorized I keep getting the error that there is no directory for /data/misc/adb/adb_keys and I have CWM too in which I have also mounted the data partition. Please help!
Hello, I decided to publish some guide + scripts I already use for a while, which allows you to use all CPU cores and boost GPU performance.
Battery consumption using this configuration surprisingly does not change much or even did not change at all, with default as well with new config my watch stays alive for ~32h with daily usage.
Some theory:
Sparrow is sold with Qualcomm Snapdragon 400 1.2GHz, which is 4 core CPU. ASUS AW2.0 official kernel though supports only 600MHz and 787MHz, as Asus probably thinks this is good balance between battery life and performance.
GPU is Adreno 302/305, which is capable running up to 450MHz, which is also supported by ASUS AW2.0 kernel.
Where is the catch?
During boot there are all four CPU cores enabled, however there is post-init script, disabling two of those and setting frequency as fixed 738MHz with performance governor (no frequency scaling). GPU is set to fix 200MHz:
/system/bin/init.asus.post_boot.sh
Code:
#!/system/bin/sh
PATH=/system/bin
cd /sys
echo 4 > module/lpm_levels/enable_low_power/l2
echo 1 > module/msm_pm/modes/cpu0/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu0/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/idle_enabled
#Put all other cores offline
echo 0 > devices/system/cpu/cpu2/online
echo 0 > devices/system/cpu/cpu3/online
governor="performance"
scaling_min_freq="787200"
if [[ `grep "oem_perf_change" /proc/cmdline` ]];then
if [[ `grep "oem_perf_on" /proc/cmdline` ]];then
oem_perf_stats="1"
else
oem_perf_stats="0"
fi
echo -n $oem_perf_stats > /factory/oem_perf_stats
fi
echo $governor > devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu1/cpufreq/scaling_governor
#below ondemand parameters can be tuned
echo 50000 > devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 2 > devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential
echo 70 > devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential_multi_core
echo 787200 > devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 300000 > devices/system/cpu/cpufreq/ondemand/sync_freq
echo 80 > devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo $scaling_min_freq > devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 787200 > devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu1/cpufreq/scaling_max_freq
#Below entries are to set the GPU frequency and DCVS governor
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/max_freq
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/min_freq
echo performance > class/kgsl/kgsl-3d0/devfreq/governor
chown -h system devices/system/cpu/cpu[0-1]/cpufreq/scaling_max_freq
chown -h system devices/system/cpu/cpu[0-1]/cpufreq/scaling_min_freq
chown -h root.system devices/system/cpu/cpu[1-3]/online
chmod 664 devices/system/cpu/cpu[1-3]/online
It is indeed required just to alter this script and you can enable all 4 cores with "ondemand" governor, scaling 600-738MHz and GPU scaling 200-450MHz using "msm-adreno-tz" governor:
(and this requires root of course)
Code:
#!/system/bin/sh
PATH=/system/bin
cd /sys
echo 4 > module/lpm_levels/enable_low_power/l2
echo 1 > module/msm_pm/modes/cpu0/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu0/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/idle_enabled
governor="ondemand"
scaling_min_freq="600000"
if [[ `grep "oem_perf_change" /proc/cmdline` ]];then
if [[ `grep "oem_perf_on" /proc/cmdline` ]];then
oem_perf_stats="1"
else
oem_perf_stats="0"
fi
echo -n $oem_perf_stats > /factory/oem_perf_stats
fi
echo $governor > devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu1/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu2/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu3/cpufreq/scaling_governor
#below ondemand parameters can be tuned
echo 50000 > devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 2 > devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential
echo 70 > devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential_multi_core
echo 787200 > devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 300000 > devices/system/cpu/cpufreq/ondemand/sync_freq
echo 80 > devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo $scaling_min_freq > devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo 787200 > devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu3/cpufreq/scaling_max_freq
#Below entries are to set the GPU frequency and DCVS governor
echo 450000000 > class/kgsl/kgsl-3d0/devfreq/max_freq
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/min_freq
echo msm-adreno-tz > class/kgsl/kgsl-3d0/devfreq/governor
chown -h system devices/system/cpu/cpu[0-3]/cpufreq/scaling_max_freq
chown -h system devices/system/cpu/cpu[0-3]/cpufreq/scaling_min_freq
chown -h root.system devices/system/cpu/cpu[0-3]/online
chmod 664 devices/system/cpu/cpu[0-3]/online
(both files also attached to this post)
To exchange files in your watch, you can easily use following bash script in linux:
First push desired file into sdcard and go to ADB shell:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
In ADB shell remount system to RW, replace the file and fix privileges, than remount system back to RO:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Update 2018/09/05:
In case you want to experiment, I'm also sending "full_power" script, setting all cores to max frequency and performance governor. There should be no issues, except probably less battery life. Just test yourself, how battery life is affected if it is affected at all. Just unpack the zip file, rename the sh script from init.asus.post_boot_full_power.sh to init.asus.post_boot.sh. Rest of the procedure is still the same.
Without kernel sources, this is probably the maximum performance you can get from the watch. Obtaining kernel sources we might get up still twice of current maximum, as the HW is there, but locked on kernel level.
I just swapped the files and I'll give this a try over the next few days. It would be awesome to destroy lag without needing a kernel tweak app to make it happen. You are the man!
Update: I followed your directions, then I wiped cache and dalvik in TWRP. I have only used the watch for a few minutes with this tweak and it is noticeably faster/smoother already. Text messages display lightning fast after being received on the phone. I'm currently on WiFi in my office. The times I notice most lag on my watch is when I'm on 4G, have music playing, and get a call. The phone may ring for 5-10 seconds before the watch displays. I'm excited to see how helpful this tweak is under those conditions. I'll know later today and keep you posted.
I have not experienced any Bluetooth lag since enabling this. This is a must have mod. Thanks for this!
Glad to hear that @CVertigo1. This is just simple SW enablement of things already present in kernel, so even no cache cleans are required. You can play with it on the go even without watch restart.
Amazing will be getting some kernel with much more CPU freq. steps, like 300-768 or even to 1.2GHz (yes, our chip is capable doing so, it is just not enabled in kernel). With proper governor battery will be still ok, resting CPU most of the time in low clocks. It is pity we have great HW, but it is taken out from us with stock kernel.
It would be nice if Asus would upload the kernel source for AW2.0.
CVertigo1 said:
It would be nice if Asus would upload the kernel source for AW2.0.
Click to expand...
Click to collapse
Well we do have latest kernel source
https://www.asus.com/us/ZenWatch/ASUS_ZenWatch_2_WI501Q/HelpDesk_Download/
Or directly here:
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_WI501Q/ASUS_WI501Q-5.2003.1603.10-kernel-src.zip
We just need some handy guy able to compile it and add more governors and frequencies. That is something what overlapping my skills.
That is the latest kernel source for 1.5. They have not released their source for 2.0, nor any firmware for 2.0. I have contacted Asus about it multiple times and none of their reps have any idea what I'm talking about.
CVertigo1 said:
That is the latest kernel source for 1.5. They have not released their source for 2.0, nor any firmware for 2.0. I have contacted Asus about it multiple times and none of their reps have any idea what I'm talking about.
Click to expand...
Click to collapse
Ah, I see I thought 2017/05/12 stated as a release day was after AW20 concluding this had to be the new one. Pity.
Maybe they'll release it eventually...at an Asus speed, like next year.
please help me(rom Sparrow_7.1.1_Debloat ROM ):
adb shell
sparrow:/ $ su
Permission denied
htduy11 said:
please help me(rom Sparrow_7.1.1_Debloat ROM ):
adb shell
sparrow:/ $ su
Permission denied
Click to expand...
Click to collapse
Hi there, you are missing super user in your ROM. Did you installed SuperSU and Busybox thru TWRP after flashing the ROM?
Do this in TWRP, not Android.
'the command can be used in adb in windows or are different? watch must be in recovery or bootloader? wrote a step by step for noob guide please
You must boot in the TWRP recovery. You need the ADB drivers installed on your computer and is easier to use your computer for this.
mastermoon said:
'the command can be used in adb in windows or are different? watch must be in recovery or bootloader? wrote a step by step for noob guide please
Click to expand...
Click to collapse
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
LeeonLee said:
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Click to expand...
Click to collapse
yeah worked perfectly... after 9 month the zenwatch is back on my wrist....
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
LeeonLee said:
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Click to expand...
Click to collapse
worked perfectly.... after 9 months zenwatch is back on my wrist
Hey guys,
do i need to do it every time i booted up ?
And can i messure this Overclocking anywhere ?
Greetings
Namelocked said:
Hey guys,
do i need to do it every time i booted up ?
And can i messure this Overclocking anywhere ?
Greetings
Click to expand...
Click to collapse
Hi, this is permanent solution. To revert you need to replace the file with original one.
I am also not aware of any reliable Wear benchmark, but you can see HW info using e.g. AIDA64 for Wear.
LeeonLee said:
Hi, this is permanent solution. To revert you need to replace the file with original one.
I am also not aware of any reliable Wear benchmark, but you can see HW info using e.g. AIDA64 for Wear.
Click to expand...
Click to collapse
I dont even find the AIDA64 for my smartwatch :/ ?
how can i check core, cpu speed etc... aida64 isn't compatible .. tnx..