Related
(UPDATE: 8/24/11 New flashable update.zip for install via recovery, includes Gscript (credit goes to PinkVenture for developing the app!) and my simple on/off scripts already installed. You can link shortcuts directly to the desktop for each ON or OFF through add shortcut on homescreen, see attachments at the end of this post)
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
echo 1 > /dev/qct_diag_enable (to enable diag mode)
..and your phone should go into USB diag mode. when you are done just:
echo 0 > /dev/qct_diag_enable (to disable diag mode)
Click to expand...
Click to collapse
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip signed-diagscripts.zip flashable update.zip file for recovery
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
cool, thanks, man!!!
Sure thing, let me know if anyone experiences issues by pm or reply. I was thinking about compiling an installable zip so this can be installed after rom in recovery too.
Sent from my ADR6300
Just wondering... Any idea if this will work on Evo as well?
Work on the EVO too?
Yeah, I would really like to know if this would work on the evo!!
hydrosity said:
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip gscript_diagscripts.zip
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
Click to expand...
Click to collapse
so wait let me get this straight. this mod is so we can update our prl??? or is this for people that would like to still run the altel hybrid prl?
because a simple *22899 will let you update it. i know this because i have been on cm7 nightly from day one and there was 1 update of the prl and it worked.
EVO + CM 7 + this solution = GO (GREEN LIGHT) WORKS.
Is there any way of running the ##3282# (if it's a file you run or an APK you install?)
Hows about this
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
tronoftroy said:
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
Click to expand...
Click to collapse
Remember, Im on CM7 GingerBread, not SENSE....
Ok so it should work on the EVO since the architecture is pretty much the same as the DINC. Now as far as it being for updating the PRL, yes it can be for that. But it is for people who need to use a program such as QPST or CDMA Workshop to change carrier based settings on their phones(IE the "flashing" [no not as in rom flashing, but carrier]). Where *228 and such is not a feasible replacement for doing so and would prevent their phone from functioning correctly, such as with mine which is flashed to cricket.
Any sort of *228 business breaks my cricket flash, and I used to have to make a backup and go back to restore a sense rom to go into the EPST app with ##778 or to be able to dial ##3424 to put the phone into DIAG mode where I could revise the settings again to make it function properly, THEN flash back since CM7 does not have the EPST.apk which supports both of these features.
With this you can avoid the whole hassle of all this if you have the QPST application for your PC by simply putting your phones DIAG mode ON or OFF. Where you can manually put in what ever PRL you want and manually set any carrier-specific settings. Not as convenient as EPST and its ##778 feature, but much more so than the previously described process.
ALSO I've now included all of this in a simple .zip file flashable from recovery to streamline this crude process a little more. Get it HERE. The file in the original post has been updated too.
m4f1050 said:
Remember, Im on CM7 GingerBread, not SENSE....
Click to expand...
Click to collapse
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Can you check if you have the file /sys/devices/virtual/usb_composite/diag/enable? If you do.. Create a GScript that echoes 0 or 1 (0 for disable and 1 for enable) to the file /sys/devices/virtual/usb_composite/diag/enable it works like a charm!
tronoftroy said:
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Click to expand...
Click to collapse
Hmmm... Can you write to NVItem 0,1 or 2 this way?
m4f1050 said:
Hmmm... Can you write to NVItem 0,1 or 2 this way?
Click to expand...
Click to collapse
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
tronoftroy said:
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
Click to expand...
Click to collapse
in EFS you can access NV items locked (on some HTC devices, tested with EVO 3D and EVO 4G) by creating folder "open sesame door" rebooting phone then going back to EFS the folder NVM should not have the lock, allowing you to see / write these NV items. So if you lack an easy to use NV Item browser you can use this approach.
Can you please update the link for the update.zip file to flash in recovery? Or if someone has it can you point me in the right direction?
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Curious! said:
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Click to expand...
Click to collapse
yeah, just open up your QPST Configuration. and set the Comport then your phone will show in QPST.
Hmmmm, modem? You're on 64 bit Windows 7? I recommend 32 bit..
Does this work on the evo??
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
this is awesome!
cb22 said:
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
Click to expand...
Click to collapse
I can't thank you enough for this, it's been fantastic so far! I only have a few questions, as I am extremely new to arch linux...as in this is the first time I've used anything aside from debian in the linux world.
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Despite all of that, this has breathed new life into my tablet, you're doing fantastic work and I hope you only continue to make it more amazing!
fankuan19 said:
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Click to expand...
Click to collapse
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
whoops
timothyb89 said:
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
Click to expand...
Click to collapse
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
fankuan19 said:
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Click to expand...
Click to collapse
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Razorbacktrack5535 said:
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
Click to expand...
Click to collapse
Without using a PC... Hmm, that could be tricky. If you're in Android, and you add this line to the top of /data/linux/home/user/.xinitrc
Code:
maliit-server &
(before the exec line)
It should give you the virtual keyboard when you restart into Linux.
cb22 said:
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Click to expand...
Click to collapse
I was actually able to just use the terminal emulator in android to navigate back to the .xinitrc file, turns out i wasn't supposed to leave the "--with-yadda-yadda" bit, so i got lxde working...and as it turns out, i don't like it nearly as much as the DE you included, so i'll be switching back to that!
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
koiulpoi said:
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
Click to expand...
Click to collapse
I don't think sleep/suspend/hibernate is implemented at all quite yet. The backlight seems to turn off completely when the screen times out though so you can fake having a low power mode, though obviously true sleep would be nice.
As for volume control, use pavucontrol. You may need to install it with `pacman -S pavucontrol`.
For brightness ... there's no good way to do this as far as I can tell. XFCE has a brightness control applet you can add to the bottom panel but it doesn't seem to work, and most of the usual packages (e.g. xbacklight, etc) don't detect the backlight device. Oddly enough I gave e17 a try and its builtin brightness applet worked fine, I wonder what they do differently ...
At any rate you can control it manually: the file /sys/class/backlight/pwm-backlight/brightness has a 0-255 value which controls the screen brightness. Note that you need to run the echo command as root
Code:
# echo "1" > /sys/class/backlight/pwm-backlight/brightness # minimum brightness
# echo "255" > /sys/class/backlight/pwm-backlight/brightness # maximum brightness
# echo "0" > /sys/class/backlight/pwm-backlight/brightness # completely turns off backlight. use with care
Setting it to zero makes it next to impossible to see the screen. I ended up having to ssh into the device (or reboot) to get it back.
I modified the file through a PC and It works ! Thanks, no problems with wifi
Sleep / Suspend isn't implemented yet.
But, I did a bit of testing, and the TF should last for about ~40 hours with the screen off, and the processor in the Low Power mode (which it does automatically. Obviously, it's still wasteful compared to proper suspend, but it's not too bad.
Really liking this so far, other than managing to break wifi once, which I fixed by doing a quick re(install I guess is the proper term). Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Thanks for all your work cb22, and thanks for taking my advice and switching file hosts
This may be a dumb question
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Shingaling said:
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
Disregard, didn't see the edit until after you posted essentially the same thing I did.
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
koiulpoi said:
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
Click to expand...
Click to collapse
I don't think it works at all, I've tried every permutation sudo pacman -S flash-plugin that I could think of and I've gotten notwhere.
They is no flash for ARM for pure Linux.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
Itege said:
Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Click to expand...
Click to collapse
In theory you should be able to install a proper display manager without too many issues:
Code:
# pacman -S lightdm lightdm-gtk-greeter
# systemctl enable lightdm
...though when I tried this the DM would never actually be run. I was able to run it manually over SSH without issues (both lightdm and slim worked, more or less). I'm in the process of investigating why it isn't run at startup like it should be, whatever the issue is doesn't seem to be related to the display manager itself.
I have an issue with wifi.
1: The WLAN do not find any Network with Channel 12 or 13.. I think I must change the region in germany, but where?
2. The WLAN do not connect, they search for an network adress and after 30seconds they ask for wlan key again.. the key is correct and my router shows the connection.. but archlinux means the key is wrong.. testet with router und smartphone wlan hotspot..
3. 3G not connecting, i have create a profile for BASE Germany, but they do not connect.
UPDATE:
for 2: Sometimes they connect and I can surf. But the ping are more then 600ms.. After few seconds the connection lost, sometimes they connect again, sometimes say ask for wlan key again.
Maybe you can help me. Sorry for my bad english.
Yours Sincelery
Robert
Could any of you guys find out if you have a process running in "interruptible" state named "kinteractive_lo"?
You can check that using "top" in CLI or installing gnome-system-monitor. I guess the standard xfce task manager works as well.
It's driving me nuts and I believe is one of the reasons why I have to hard-reboot my tablet, since invoking reboot with --force works perfectly.
Thanks in advance!
I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.
staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!
Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:
Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.
Hi all,
Thanks to the huge discount on Nook Simple Touch earlier this month in UK, hopefully the device will regain some popularity and draw more attention from the XDA community. Unfortunately all the new devices come with firmware v1.2.0 while most posts in the forum were for the outdated v1.1.x, including the brilliant multitouch mod from wheilitjohnny. I know there is a way to downgrade to v1.1.x but I still prefer v1.2.1 after I tried v1.1.0. So I decided to port wheilitjohnny's mod to v1.2.1. After one week's hard work as I'm a newbie to the Linux world, I finally built the kernel and saw no more boot loop. All the multitouch test tools from Market correctly reported up to 2 fingers.
Before put the kernel to your device, make sure it's already running 1.2.1 firmware and rooted. You can find the link to the official upgrade file in the forum and you can use Nook Manager to root your device which is also available in the forum.
Then please found the kernel attached as zip file. You need to unzip the file and follow arkusuma's post on how to install it.
http://forum.xda-developers.com/showthread.php?p=24168019#post24168019
All credits go to wheilitjohnny. It's all his work.
One lesson I learned for all the developers who may be interested in more mod development is, to make a bootable kernel you MUST use toolchain from "http://www.codesourcery.com/sgpp/lite/arm/portal/release1293". Select the IA32 GNU/Linux TAR one (MD5: c6930d14801b4fab6705d72df013e58b). Any other toolchains including Google's own or even another version from codesourcery won't work. The generated kernel built with any other toolchains will only cause boot loop.
[UPDATE] Oh forgot to say, you need to add one more line to your /etc/permissions/required_hardware.xml on your device. You should be able to find the first line already in the file, just add the second line.
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
More info please check http://forum.xda-developers.com/showthread.php?t=1563645
Does this kernel work with NoRefresh (I assume debug2 version for FW 1.2.x)?
koltshin said:
Does this kernel work with NoRefresh (I assume debug2 version for FW 1.2.x)?
Click to expand...
Click to collapse
Yes. I have NoRefresh_Debug2 and Fast Mode mod running together with this kernel. No problem so far.
Thx. Does this kernel works for both Nook Simple Touch and the Glow light model?
Sent from my GT-N7100 using xda app-developers app
waynesi said:
Hi all,
One lesson I learned for all the developers who may be interested in more mod development is, to make a bootable kernel you MUST use toolchain from "http://www.codesourcery.com/sgpp/lite/arm/portal/release1293". Select the IA32 GNU/Linux TAR one (MD5: c6930d14801b4fab6705d72df013e58b). Any other toolchains including Google's own or even another version from codesourcery won't work. The generated kernel built with any other toolchains will only cause boot loop.
I've had good success with the toolchain on Ubuntu; just install the gcc-arm-linux-gnueabi packages, and add the Makefile and head.S changes that were in the fastmode2 patch; I've not tried building this touch mod, but it has let me build my own kernels with usb host and with TLS support.
Click to expand...
Click to collapse
I can confirm that this kernel works on a NST with Glowlight on FW. 1.2.1 Thanks for the hard work.
Can I use this kernel for 2 fingers zoom in? I tried it with aldiko, but do not work with pdf.
You need to unzip the file and follow arkusuma's post on how to install it.
http://forum.xda-developers.com/showthread.php?p=24168019#post24168019
Click to expand...
Click to collapse
Could somebody please help me installing this without adb over wifi? Because i have internet only over ethernet. I was thinking of CWM.
Thanks
Sagittarius0 said:
... without adb over wifi?
Click to expand...
Click to collapse
Well, how about ADB over USB?
Renate NST said:
Well, how about ADB over USB?
Click to expand...
Click to collapse
Can you please help me exactly how to do it? I have tried it once for some other reason and it didn't work... :crying: And after that I searched for it here and found a post which said that adb works only over wi-fi.
And I am quite new with android so please explain the process well.
waynesi said:
Yes. I have NoRefresh_Debug2 and Fast Mode mod running together with this kernel. No problem so far.
Click to expand...
Click to collapse
Fast Mode don't works on my NST fw 1.2.1. What app exactly are you using to activated the fastmode?
update: this kernel don't have / sys/devices/platform/omap3epfb.0/graphics/fb0/fmode so fastmode is not possible
tebra said:
Fast Mode don't works on my NST fw 1.2.1. What app exactly are you using to activated the fastmode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=39529578&postcount=140
Step one, use noogie and do a full backup of your Nook.
It should be almost 2GB file size.
Using noogie, copy uRamdisk.
Use bootutil.exe (in signature):
Code:
bootutil /x /v uRamdisk init.rc
[i]edit init.rc[/i]
bootuil /r /v uRamdisk init.rc
The line you edit out (with a number sign) is
Code:
[color=red]#[/color] setprop service.adb.tcp.port 5555
(uncomment this line to go back to using WiFi ADB)
Copy uRamdisk back to the Nook.
Reboot your Nook.
Read up about getting the ADB drivers working on your desktop here:
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
This thread is old, I know, but hopefully someone will spot this. So I took the plunge and installed Multi-Touch (running FW 1.21 and rooted). I followed the instructions for the ADB wireless method and also changed the required_hardware.xml file, resetting the permissions of the edited file to match those of the original.
Nothing is different? My original hope was that the pinch-zoom function in Dolphin 10.2.6 might work with this mod. It doesn't seem to work on either Android or Desktop settings in that browser. I can't see that it works anywhere. Maybe I need to reinstall Opera Mobile and test it there?
...
O.K., I just reinstalled Opera Mobile. No effect at all that I can discern.
Hmm....I am underclocking with No-frills CPU Control to 300 MHz. Is that the problem? Nope....changed back to 800 MHz and no effect.
So...what am I missing? Is there something I can check to be sure I did the ADB thing correctly (after I'm done using the "shell" do I just close it down or is there some closing command I should have used?). Does this mod have to be used in conjunction with something else?
I usually jump out of an ADB shell with ^C
There's an interim release of UsbMode-1.7a.apk in the signature.
If you touch the left 3/4 of the screen it will report touch coordinates.
It will indicate multiple touches.
That's the easiest way to see how many simultaneous touches your device supports.
My Nook: 2, my Kyocera: 4, my ZTE: 5
I installed a multi-touch test app from the Market and it showed that two fingers were recognized (no more), although the recognition was somewhat spotty.
I've been fussing around with it and sure enough it has begun to work with Opera Mobile, both at 800 MHz and 300 MHz (no discernible difference there). It also works very well with Perfect Viewer. It does not work with Google News and Weather (which really needs it), at least not the version that came with NookManager rooting.
Alas, it does not work with Dolphin, which was my main impetus for trying this. I've got Dolphin to the point where it is much more reliable than Opera Mobile but the only way to zoom is via a gesture which requires going to a blank screen, drawing the gesture and then returning to the current page. It makes one want to draw gestures that are not found in children's books. Although Dolphin claims pinch-to-zoom, it doesn't seem to work with the NST, at least not this version of Dolphin. Maybe I need to delve back into the past versions (which will probably be less stable in other respects...).
Well, anyway it works. I'll have to see if it affects the battery life in any significant way (I read on my Nook, too!). If not, I may as well keep it although its utility to me is limited.
Now to look at "no-refresh"......
nmyshkin, what about Google Maps?
Yes, I forgot to mention Google Maps (I was using "Places" but it amounts to the same thing). That works with multi-touch as well. I also noticed that to some extent multi-touch zooming in Opera Mobile is web-site dependent. For example, it does not seem to work at all on Wikipedia but worked OK on some other sites I tried. I just wish it would work in Dolphin
I just tried it with Orion Viewer (which I like for PDFs) and it also works there. It seemed to want to work with Kingsoft Office on the same PDF file but then the app crashed. There are other ways to magnify in both, of course.
I finally tried NoRefresh, and while it worked, I was left wondering what it is for other than as a "we can do this" feature. Lots of flickering while it made up its mind as a white-listed app was launched and then the image degradation thing. After I exited the app my screen was such a mess I had to reboot. I guess I'm used to the way the e-ink display sort of tears when scrolling (or even zooming now, for that matter). The NoRefresh just doesn't seem to give me anything I want. I have not tried FastMode. As I currently underclock to 300 MHz I am reluctant to overclock the Nook just so it will (sort of) work like something it is not and run down the battery really fast.
** DoPa5 v1.0 (AOSP v5.0.2_r1 - Lollipop) is now available for US/UK/AU users **
If you would like to upgrade from the stock ROM, see this post for downloads and installation details
Click to expand...
Click to collapse
DoPa v2.0 is an enhanced version of the stock ROM that features a custom-built kernel. It is based on Hisense's August, 2013 update (build P756.6.02.20) and is intended for US (8gb) versions of this tablet. It does not support the 32gb models sold in the UK and Australia. See Post 2 below for packages to root this tablet and install CWM Touch recovery.
This ROM de-bloats the original, roots it using SuperSU, and adds several useful apps, among them: Apex Launcher and ES File Explorer. It also includes several Xposed Installer modules to tweak your system, including GravityBox and my Phab7 UI switcher. For the hackers amongst us, ADB always runs as root.
The kernel is built from Hisense's source and offers enhancements and bug fixes. Most notably, it provides USB-OTG support so you can connect USB storage devices (e.g. thumb-drives) to your tablet using an OTG cable. It comes in two flavors, a non-overclocked version included in the main package, and a separate overclocked version that can be installed (and uninstalled) independently.
Installation
Having CWM installed is a prerequisite; if you haven't installed it yet, see Post 2. This ROM is intended to function as an update, preserving your apps and data. Unless you want to start from scratch, do NOT wipe or clear anything - the install script will do what's needed.
copy the file(s) to your internal or external SD card
reboot into CWM, then select "install zip"
I recommend you select "toggle signature verification"; enabling this will confirm the file hasn't gotten corrupted (if you get a verification error, stop, then copy the file to a different SD card)
choose the menu entry corresponding to where you put the file(s), then select "sero7pro-bld60220-dopa-v2.0.zip" from the list
after confirming your selection, the update will display what it's doing; you should NOT see any error messages
if you'd like to install the overclocked kernel, you can do so once the main package is in place, or at some later time
reboot
Notes
when you attach a drive using the USB-OTG feature, it is automatically mounted at '/usbdisk'. Be aware there is no easy way to unmount it - you may have to use adb or a terminal app to ensure a clean unmount. This should only be an issue if you write to the disk; if you're only reading, it may be safe to just pull the plug.
the overclocked version of the kernel runs the processor at 1.5ghz rather than the standard 1.3ghz. Using it may result in a significant loss of stability on some systems. You may want to install one of the many apps that let you control the maximum speed to regain stability and reduce power consumption.
much of the app-bloat this ROM tries to eliminate (such as Sams Club or Playstore Magazines) may still be present if you've ever gotten updates for any of these apps. To get rid of them permanently, uninstall them using Settings->Apps->Downloaded. For "system" apps like the Google stuff, select "Uninstall updates", then "OK" when it asks if you want to revert to the factory-installed version (which doesn't exist anymore). The apps will be gone for good.
to enable the many tweaks offered by GravityBox and Phab7, open the Xposed Installer app and enable it via the "Framework" option but don't reboot yet. Back out and choose "Modules", then tap directly on the checkbox to the left of each module's icon (not on the icon or text). Now, reboot to activate their features.
Note: GravityBox's Quick Settings tiles and statusbar mods only work with the Phone or Phablet UIs (i.e. not Tablet UI). To get the full effect from Tablet UI, open Apex Launcher's settings and select "Homescreen settings->Use tablet UI mode"
Geek Alert: with the addition of DriveDroid (not included), this kernel lets your tablet emulate a USB CD drive that can be used to boot your PC. See the app's description for details.
Credits
xboxexpert - for getting things going
randomblame - for many of the patches used in this kernel
Files
new and improved:
sero7pro-bld60220-dopa-v2.0.zip - the DoPa v2.0 ROM with the standard kernel
sero7pro-boot-dopa0oc-v2.0.zip - the overclocked kernel
sero7pro-boot-dopa0-v2.0.zip - the standard kernel (in case you want to reinstall it)
old and tired: (do not use with v2.0)
sero7pro-bld60220-dopa-v1.1.zip - the DoPa v1.1 ROM
sero7pro-usbotg-dopa-v1.1.zip - USB-OTG add-on
sero7pro-macfix-dopa-v1.1.zip - random MAC address fix
sero7pro-sysui-dopa-v1.1.zip - removes screenshot button
miscellaneous:
sero7pro-bld60220-removed.zip - files that were removed from the DoPa ROMS (note: unlike the other files here, this is not a flashable zip. Unzip it, copy the apps you want to your SD card, then install them from there)
stock-v60220-full-update.zip - the complete 6.02.20 update from Hisense - this is the closest you'll get to the original stock ROM
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
XDA:DevDB Information
Sero 7 Pro (US) - DoPa v2.0 Modified Stock ROM, ROM for the Android General
Contributors
dolorespark
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
Based On: Stock ROM
Version Information
Status: No Longer Updated
Current Stable Version: 2.0
Stable Release Date: 2014-01-22
Created 2015-01-26
Last Updated 2015-01-27
Root/CWM packages
These packages will root and install CWM Touch recovery on the US (8gb) model of the Sero 7 Pro. There are separate versions for Windows and Linux. They have been tested under Win XP, Win 8, and Ubuntu, and should avoid problems encountered with other root/recovery packages.
The packages are modular so that you can run some or all of the functions as-needed. They consist of 4 scripts:
step0-DoItAll - displays some setup info then runs all 3 of the following
step1-adb - enables ADB ("Android Debug Bridge") to locate the tablet
step2-root - roots the tablet and installs the SuperSU app
step3-cwm - installs CWM Touch Recovery v6.0.3.2
Versions of ADB for each OS are included, so no other packages or downloads are needed. Usage should be fairly simple: unzip the package into a convenient directory, doubleclick on step0-DoItAll, then follow the (minimal) instructions. Alternately (and better), open a command prompt/bash shell, change to the directory where you unzipped everything, then run the script(s) from there.
Avoiding Frustration
If you haven't rooted an Android device before, please read the following because there are a few "gotcha"s. If you have but things aren't going as expected, review the following in case you missed/forgot something.
Developer options must be visible in the Settings app. If they aren't, select "About tablet", then tap on "Build number" 7 times. A small popup will tell you that you're now a developer. Back out to the list of settings categories - you should now see "Developer options".
USB debugging must be enabled under "Developer options". Please be sure it is. If it isn't, select it then tap OK when a warning popup appears.
Both Windows and Linux require extra files to be in place before ADB can communicate with your tablet. Click on the button for your OS to see the ugly details.
Windows
Windows requires USB drivers to be installed. Drivers that will work with the Sero7Pro (and possibly any Android device) are included in the package.
After enabling "USB debugging" and connecting your tablet, a wizard may pop up to guide you through the steps. If not, force it to appear by opening Device Manager. Look under "Other devices" where you should see something like "Android phone". Doubleclick on it, then select the "Install driver" button on the window that appears.
When the wizard pops up, tell it you'll select the drivers, then choose the option that tells it where to look. Click the "Browse" button and navigate to the directory where you unzipped the package. Select the usb_driver folder, press "OK", then "Next" - the drivers should install without any problems.
Notes: On Windows XP, the first wizard to pop up may want to install drivers for "MTP" which XP doesn't support. If so, cancel out of that, then wait for the "Andoid Phone" wizard to appear. On later versions of Windows, you may get a popup warning that the drivers aren't signed properly; if so, select "Install driver anyway". On Win 8-64bit, driver installation will fail unless you started the current session with "Driver signature enforcement" disabled.
Linux
Linux (or at least Ubuntu) doesn't allow user programs to access USB devices directly without the appropriate permissions in place. This package includes a file named 99-android.rules which provides those permissions
If you've never provided access to other USB devices, just copy the file to /etc/udev/rules.d. Otherwise, you can either copy it or merge its contents with the .rules file containing your other USB entries.
Note: both the rules.d directory and its contents are owned by root. You will probably have to use the sudo command to gain access. For example, from a bash shell whose current directory is the one where you unzipped the package, you'd enter "sudo cp 99-android.rules /etc/udev/rules.d". Also, be sure the file's permissions match the others in that directory. If not, run "chmod 644 /etc/udev/rules.d/99-android.rules".
Notes
When you're done, open the SuperSU app to enable it. It will ask to update the su binary. After selecting OK, the app will be enabled and will popup warnings whenever an app requests root access for the first time.
The Linux script is actually designed for both Linux and Mac OS X. However, I haven't fully tested it yet so I don't want to make any incorrect claims of support. You may have to correct some file permissions and will almost certainly have to run it from the Terminal app.
Files
sero7pro-root-win-dopa.zip - Windows
sero7pro-root-unix-dopa.zip - Linux
[Obsolete] Remove Screenshot Button / Add Instant UI Switcher
The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.
If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.
If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.
Good work. Hope to see more devs and more Roms
Really good. I'm using it right now. Keep going with the good work
Good Job! Looking forward to more posts!
Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.
Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!
Thank you. Your ROM runs smooth and fast.
Great work man, downloading it now! Thanks!
Antutu result for this ROM
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Installed and working. Thanks.
taba4real said:
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Click to expand...
Click to collapse
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
larryf said:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why am I getting 10500 on this ROM then?
Does this root and cwm change kernel like xbox's?
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Cooter007 said:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Click to expand...
Click to collapse
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
lordroy said:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
Click to expand...
Click to collapse
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Cooter007 said:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My desktop ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Click to expand...
Click to collapse
Of course as soon as I mention something, my Sero decides to play nice.
Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good: