Related
!!This is ONLY for Elocity A7 PLUS! (model with 1024x600 resolution)
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on my homepage at Dexter's mods
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
You can download from here MD5SUM: 7d69789e85e946c7f456c8f8f455a352
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your ownproblem if it does FC alot, if you do not wipe
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
ISSUES
- Screen brightness cannot change (Settings crash when selected)
- Volume in status bar not included (using old A7 mod here, ill figure a solution out, maybe app from Market?)
KERNEL USED IS STOCK ROM EDITION, SINCE SOURCE IS NOT RELEASED
CHANGELOG
v1.00
- Initial release
- includes a fixed RECOVERY , which allow you to do a proper WIPE (Factory reset)
- DSP audio manager
- rotation fix for some games
- all google apps functionality with calendar and email and sync
- flash player 10.3 included (full embedded media support) , if you want to upgrade, please uninstall the old one first.
- still no "move 2 sdcard" (needs different release 2.3.6 to support it and new kernel)
- no longer uses /storage as sdcard location.
/mnt/sdcard is now internal storage,
AND
/mnt/sdcard/sdcard-disk is external sdcard location.- root enabled (Superuser is used here)
- wma/wmv media support
THANKS to all who donated previously and up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
PS: you can ALWAYS use the elocity Recovery from A7 install instructions here
If you like it press "THANKS"
reserved for future.
Bro plzz check ur pm box
Need ur help Dexter...
hey dexter need ur help...... ive tried porting sense 3.5 to defy......when i went in the port section in kitchen.........i setup the port and i got 2 folders MY KERNEL,MY DEVICE FOLDER....i am porting it on defy...i changed the folder MY DEVICE FOLDER to "WORKING_sense" and then set up a working folder and then built up the rom but it didnt work out...i got an error
E:error status 6...wat shud i do..plzz help
hey bud my usb does not work on this mod also is there a honeycomb for the plus version
gemini002 said:
hey bud my usb does not work on this mod also is there a honeycomb for the plus version
Click to expand...
Click to collapse
usb stick works fine here? and shows in "storage" when mounted.b
Dexter_nlb said:
usb stick works fine here? and shows in "storage" when mounted.b
Click to expand...
Click to collapse
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again
gemini002 said:
weird soulution then?i tried to flash again but same thinh..maybe i will put orginal sofware then update again
Click to expand...
Click to collapse
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.
when i plug it in its not detected does not light up..i flashed orginal software and port works
---------- Post added at 09:04 PM ---------- Previous post was at 08:45 PM ----------
when i install ur rom @ first boot i get boot loop so i have to turn off then it boots but no working usb port so frustrated
---------- Post added at 09:42 PM ---------- Previous post was at 09:04 PM ----------
Dexter_nlb said:
did you note, mount location changed from original rom?`its no longer in /mnt/storage but /mnt/sdcard like other tablets.
Click to expand...
Click to collapse
yes usb is not bein mounted at all
The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Sent from my HTC EVO 3D X515m using XDA App
gemini002 said:
The latest fw was on my tablet also on orginal fw in recovery when I choose factory reset it just shuts of ..
Click to expand...
Click to collapse
you need to install my version, and then go back into recovery and you see recovery name is changed, and now factory reset would work fine.
yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd
gemini002 said:
yes works fine now ..sometimes sceen turns off and wont turn back on reboot needed also when will update to this come out wnt to move apps 2 sd
Click to expand...
Click to collapse
the SOD issue was a well known problem of Tegra2 in its early days. problem with this tablet is that it needs a new kernel update and i do not see that one coming to solve SOD problems (from the past).
strangely the first A7 did not have it,while my Folio100 suffered badly from SOD with the early kernels.
so its known, but not being fixed i guess.
actually Nvidia wrote on their webpage that this hardware had the problem on some tablet could be awakened again by pushing out the sdcard? maybe an idea?
u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?
gemini002 said:
u have made this tablet a rel steal for me now only paid 120 cdn for it...now how can we get tablet to install to sd card?
Click to expand...
Click to collapse
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.
Dexter_nlb said:
we need a kernel, the function required for installing to sdcard (loopback device) is not compiled into the kernel. so its not working for any rom.
i made CM7 + HC3.0(from A7Comb) working, but without the function from the kernel, those are not worth using. so im holding back those for a release until a solution is found.
Click to expand...
Click to collapse
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory
gemini002 said:
Does it have more internal memory free??would love to try it ..also how dani increase my internal memory
Click to expand...
Click to collapse
you can find the CyanogenModPlus edition now using link in post to download.
its beta but until a kernel is ready, we have to live with minors. as its work quite well.
remember to have embedded video working, install the CF3D plugin from Market (ChainFire 3d) and reboot, and you can see embedded video quite fine on cyanogenmod too.
Hey Dexter_nlb,
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Thanks in advance.
JF
JF-GINO said:
This seems to be the best rom available for this tablet - its more stable then the stock roms and offers some improvements and speed overall making it the best so far.
Click to expand...
Click to collapse
i would dare say its the only one for A7+ now
activity has changed alot since all the new android tabs got out.
JF-GINO said:
I just have one problem with it that you might be able to help out with:
I have just noticed that your ROM is missing the ability to change the WIFI Sleep Policy. Its set for ON by default - but cannot be turned off. This is a big problem as WIFI disconnects every time the screen turns off. It then takes over 30sec to re-connect (depending on wifi network) and any programs open that require a connection stop responding or start to force close.
I use my Tablet as a controller for my home theater and because of this I cant use this great rom. I cant use the stock rom either as The stock rom does not work with my home theater apps.
I was wondering if you could fix this easily or could show me how - EG: Build.prop string??? or other mod? - port settings.apk or wifi related libs from std rom?
I just need the WIFI to stay on.
Click to expand...
Click to collapse
you might be able to download an app from Market that solves it?
Advanced WIFI LOCK (Free edition)
it might help.
otherwise only way around is going into Development settings, and chose "stay awake"?
anyways, the wifi issue is more common being a kernel issue, which in the early nvidia for these tablets had a deep sleep issue, which also killed wifi signal. its only solved by a full kernel upgrade to android 3.x (2.6.36.x or higher) which i have no good chance of doing completely.
to get better support, the CyanogenModPlus rom is getting better now, since kernel is changing with OC support and better market install support as well.
but thats probably the best this can offer for now.
I just got a refurbished A100 earlier this month, I had wanted something that was able to be used
has a GPS when traveling, and a Android PC when at home when attached to a HDMI monitor,
the Android PC setup works well with a bluetooth keyboard and mouse, however the Microsoft
bluetooth mouse that I have stops working after it sets still for a bit, and I have to manually reconnect, I
hope to find a mouse that auto reconnects or does not time out, the only other problem I have
with the Android PC setup is that one of the HDMI TVs I have, an old Sharp 720p TV, the TV I needed
to use for this, the top and bottom of the screen are cut off, and this TV has no adjustments for that,
but the A100 works good on a newer Vizio 1080p TV that I tried.
Here are the steps I took to unlock, root, install recovery and CM, copied from my notes.
I installed the drivers and rooted the A100 using:
Full root for A10x and A5xx ICS. Simple method.
I noticed that at this step my superuser will not update from within the superuser app.
I then unlocked the boot loader using this:
[How to] Install unlock bootloader for A100/A101
It happened so fast that I missed it and had to run the commands
"fastboot oem unlock"
and
"fastboot reboot"
after getting back into the bootloader using the Quick Boot app.
I then installed TWRP from:
[RECOVERY] [OFFICIAL] TWRP 2.2.2.1 for Acer Iconia Tab A100
then used TWRP to wipe and install CM10 from:
[DEV/WIP] CyanogenMod 10 Preview
and the Jelly Bean optimized Kernel for A100 from:
[DEV] [KERNEL] UNOFFICIAL - Jelly Bean optimized Kernel for A100
and the Gapps file gapps-jb-713.zip from:
http://d-h.st/I1K
After logging into my Google account and downloading a filemanager,
and letting it do a few updates, I used TWRP to make a backup from
my real SD Card.
I then ran/installed "jb-mount-swap.sh", Crossix's mount swap modded for CM10 by pio_masaki,
got that from:
http://forum.xda-developers.com/showpost.php?p=29592981&postcount=101
I put the "jb-mount-swap.sh" in "/etc" then changed permissions on the "jb-mount-swap.sh"
to give it everything, I then updated BusyBox and Superuser, and used Script Manager to
load "jb-mount-swap.sh" on every boot.
UPDATE
"jb-mount-swap.sh" Should be placed into "/system/etc"
The next problem was the touch screen sensitivity was crazy and the tablet was hard to use,
It was not like that in ICS.
I found this:
[Q] Screen too sensitive
And tried this first:
http://forum.xda-developers.com/showpost.php?p=22777698&postcount=65
I used "Acer Liquid Settings", found the app over at:
[APP] Liquid-settings v 1.3 final
and it sometimes worked but I still had problems, so I tried "TouchRecalibrate"
from:
http://forum.xda-developers.com/showpost.php?p=20189952&postcount=52
and seems to work a little better.
Tips and Fixes:
I had the CM10 launcher Trebuchet endlessley crash after changing some CM10 settings,
so I wiped the Trebuchet settings by going to "Settinga/Apps/All/Trebuchet/Clear data"
I then downloaded and installed a different launcher, I used Nova.
If you change the lcd density the Play store might start showing "Your Device Is Not Compatible With This Item"
you may be able to fix by going to "Settinga/Apps/All/Google Play Store/Clear data", and doing a reboot, you
may also have to change the lcd density back to the way it was, on my a100 its set to "160"
You can load a TEXT file from the Android browser by typing: "file:////mnt/external_sd/YOUR-TEXT-FILE.TXT"
or "file:////mnt/sdcard/YOUR-TEXT-FILE.TXT"
I had some wallpaper problems until I placed the wallpapers into "sdcard/media/wallpaper"
and used the APP "image 2 wallpaper"
My Problems:
My GPS doe not work, I have tried all the fixes that I can find, but my GPS just will not work, I have tried
[DEC.05.2011] Instantaneous GPS Fixation v1.2! *FOR ALL ANDROIDS PHONES!*
[GPS][Fix] Automate long term orbit data download
AGPS Patch Iconia 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
I have been using GPS Essentials and GPS Test to try and get a GPS lock, I never get anything, I tried with and
with out a case, I tried leaving it set out side for about an hour, it never got any satellites.
GPS UPDATE
My GPS now works, all I had to do was re-flash the ROM, Kernel, and Gapps, I made a backup
before I re-flashed my rom using TWRP, and restored "Data" only from that backup right
after I re-flashed, that restored my APPS, and passwords.
HDMI and Bluetooth Mouse UPDATE
I found a HDMI to VGA converter that works well, it also outputs audio, here is the link
SANOXY HDMI to VGA and Audio Converter (Support 1080P, Input HDMI, Video Output: VGA, Audio Output: 3.5 mm-outs)
It only converts HDMI to VGA, it does not scale anything, but the video and audio are both good,
however video is a tad soft looking, might be the cables I am using, you do have to adjust the monitors
settings, but I was able to fill the screen, I tested a a few monitors with the converter box, the Viewsonic
vs11354 I have worked fine, an old NEC LCD1560NX did not, and the Sharp 720p TV that I had problems
with HDMI, worked well threw its VGA with some screen adjustment.
I also got a Motorola Bluetooth Mouse SJYN0817A, it works well and does not die on me, it also pairs
without a pin like the Wii Remote controler, it was cheap, I think they are getting rid of them.
Lol could have saved yourself a lot of typing
search feature
http://forum.xda-developers.com/showthread.php?t=1711125
http://forum.xda-developers.com/showthread.php?t=1931085
Btw, why wouldnt you just browse to your text file with a file explorer and open it. Lol your making it WAY too hard for yourself.
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
justjackyl said:
Lol could have saved yourself a lot of typing
search feature
http://forum.xda-developers.com/showthread.php?t=1711125
http://forum.xda-developers.com/showthread.php?t=1931085
Btw, why wouldnt you just browse to your text file with a file explorer and open it. Lol your making it WAY too hard for yourself.
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
Click to expand...
Click to collapse
I knew about both guides, but this was from my own notes, that I wrote for my self,
I take notes on stuff I do like this for two reasons, one is if I screw up, the other
reason is if I forget.
I often use the Web browser to open a text file containing my huge WiFi passwords
and such, so that I don't have to retype them, this is done before I have a
file manager, and often downloading and installing a file manager is the next
thing I do.
will1384 said:
I knew about both guides, but this was from my own notes, that I wrote for my self,
I take notes on stuff I do like this for two reasons, one is if I screw up, the other
reason is if I forget.
I often use the Web browser to open a text file containing my huge WiFi passwords
and such, so that I don't have to retype them, this is done before I have a
file manager, and often downloading and installing a file manager is the next
thing I do.
Click to expand...
Click to collapse
I appreciate your addition to the A100 forums. Several of your links are broken on my end. As for the GPS, I would suggest a full wipe and reflash as a starting point.
Edit : I'm assuming GPS was working fine on stock?
Romman0 said:
I appreciate your addition to the A100 forums. Several of your links are broken on my end. As for the GPS, I would suggest a full wipe and reflash as a starting point.
Edit : I'm assuming GPS was working fine on stock?
Click to expand...
Click to collapse
I got the tablet refurbished and then let it do the OTA updates, the very next thing I did was
root, install recovery and CM, I only used it about a day or so with ICS and only installed what
I needed to, I never thought to test GPS, I guess I can try to backup, then wipe and reflash.
Thanks for pointing out the bad links.
will1384 said:
I got the tablet refurbished and then let it do the OTA updates, the very next thing I did was
root, install recovery and CM, I only used it about a day or so with ICS and only installed what
I needed to, I never thought to test GPS, I guess I can try to backup, then wipe and reflash.
Thanks for pointing out the bad links.
Click to expand...
Click to collapse
I swear that TouchRecalibrate does nothing! lol
I had to do some google searching and there are a lot of reports saying that you must follow the instructions carefully, and than it says recalibrating and does nothing, no matter how long you let it set.
I may be wrong.
Now Liquid Settings, I set the sensitivity to 0 and it did help.
Thanks for those! Pretty cool.
will1384 said:
I got the tablet refurbished and then let it do the OTA updates, the very next thing I did was
root, install recovery and CM, I only used it about a day or so with ICS and only installed what
I needed to, I never thought to test GPS, I guess I can try to backup, then wipe and reflash.
Thanks for pointing out the bad links.
Click to expand...
Click to collapse
I backed up, then wiped, then reinstalled CM10, Kernel and Gapps, and then restored "data"
only, from the backup I made earlier, let it reboot, and now GPS works, I got 9 satellites
a few seconds after walking out the door WOW.
justjackyl said:
I swear that TouchRecalibrate does nothing! lol
I had to do some google searching and there are a lot of reports saying that you must follow the instructions carefully, and than it says recalibrating and does nothing, no matter how long you let it set.
I may be wrong.
Now Liquid Settings, I set the sensitivity to 0 and it did help.
Thanks for those! Pretty cool.
Click to expand...
Click to collapse
I get two problems with sensitivity, touch is too sensitive, and I get rapid touches from a single touch,
TouchRecalibrate does seem to help, but not completely, as it seems to help the most with the rapid
touch problem, and not very much for the sensitivity.
I also would not doubt the pseudo effect, but from what I understand the TouchRecalibrate APP is made
for the ViewSonic gTablet that seems to share the same resolution and CPU, its just that the screen sizes
and PPI are different, so there is a possibility of it working.
will1384 said:
I backed up, then wiped, then reinstalled CM10, Kernel and Gapps, and then restored "data"
only, from the backup I made earlier, let it reboot, and now GPS works, I got 9 satellites
a few seconds after walking out the door WOW.
Click to expand...
Click to collapse
Cool man glad it fixed it for you. Enjoy
I just had something odd happen, I started having trouble changing the wallpaper,
then the "jb-mount-swap.sh" stopped working, some games and apps also stopped
working, and it froze and then spontaneously rebooted on me a few times, I tried
rebooting and changing the directory of the "jb-mount-swap.sh" file thinking I had it in the
wrong place, I tried placing the file in both the internal and external storage and rebooting,
I even made sure the permissions were correct, then out of the blue the A100 only booted
to a blank screen, and would not boot into android, so I booted into recovery, factory
wiped, installed CM10, the Jelly Bean optimized Kernel for A100, and Gapps, then
restored my "Data" from my backup, and it seems to be working, I wonder what happened ?
If the mount swap is removed or stopped from running it can cause allot of issues with apps. The mounts go back to normal so apps lose their data and info and go insane.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
If the mount swap is removed or stopped from running it can cause allot of issues with apps. The mounts go back to normal so apps lose their data and info and go insane.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
I had the storage card problem again, shortly after the last restore, this is what I did to fix it.
I put "jb-mount-swap.sh" into "/storage/sdcard1/" and made sure the permissions were correct, I then
checked Script Manager's "List" it showed a few phantom "jb-mount-swap.sh" from when I tried using
other directories, so I deleted all of them, then with Script Manager I selected "SU" and Boot" icons for
"jb-mount-swap.sh" and pushed the "save" tab, I then updated Superuser and BusyBox, and its working,
hope it stays that way. :fingers-crossed:
You do know that's supposed to run from /system/etc? I'm surprised its working at all considering you're remounting the partition its sitting on.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
You do know that's supposed to run from /system/etc? I'm surprised its working at all considering you're remounting the partition its sitting on.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I had put "jb-mount-swap.sh" into "/etc/" not "/system/etc" I wonder if thats why I had problems,
it does seem to be working good in "/storage/sdcard1/" I have not had any problems, but I will
move "jb-mount-swap.sh" over to "/system/etc" to help keep any future problems to a minimum.
/etc and /system/etc are linked, so that's fine.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
/etc and /system/etc are linked, so that's fine.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
"jb-mount-swap.sh" stoped working after I moved it into "/system/etc" but the superuser APP shows
that it gave root to SManager just after boot, and when I use SManager to run "jb-mount-swap.sh" I get
"mount: Device or resource busy", I then reboot, and the "jb-mount-swap.sh" is working, so I reboot again,
and "jb-mount-swap.sh" stops working, its does this:
(1) "jb-mount-swap.sh" not working
(2) Reboot
(3) "jb-mount-swap.sh" is working
(4) Reboot
(5) "jb-mount-swap.sh" not working
Did you update smanager to run it in the new location?
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Did you update smanager to run it in the new location?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just for a test, I copied the "jb-mount-swap.sh" to another directory, then deleted
"jb-mount-swap.sh" in "/system/etc" I then made sure that "jb-mount-swap.sh" was
not listed under SManager's "List" or "Favorites" then I copied the "jb-mount-swap.sh"
back to "/system/etc" and set it to run with SManager again, I still have the problem,
so the next thing I tried was using SManager to change the "jb-mount-swap.sh" file
permissions, so I used SManager to remove all the permissions for "jb-mount-swap.sh"
and then add them back, rebooted a few times and it still has the problem.
I tried reinstalling SManager, did not help, I tried using ROM Toolbox to run the script at boot,
but still have the same problem.
After much debate I have decided to make my work public as a lot of people seem to want these features!
THIS IS AN ALPHA SOFTWARE! EXPECT BUGS!
THEREFORE IF YOU INSTALL, ITS YOUR CHOICE. I TAKE NO RESPONSIBILITY IF THINGS GO DOWN THE PAN!
To get this working well, I need you guys! The testers - the community!
TFU ROM UPGRADE PACK ALPHA 3
What is it?
This software pack will supply your STOCK UK nook with software 1.2.0 with the following features:
ROOT
BUSYBOX
ADB
A clean nook friendly interface
A custom kernel (Thanks guevor http://forum.xda-developers.com/showthread.php?t=1906507)
Multitouch
Browser, Email, PDF, News Feed, Lots of tools
A custom built video mod to improve multitouch speed, refresh rates, delay and general display performance
MORE (but I cant remember)
Follow this guide to backup your nook and find out everything you need to know about the process. Please do this BEFORE any other tinkering! Make sure you know what you are doing!
http://forum.xda-developers.com/showthread.php?t=1961835
How to Install
Make a CWM SD card:
http://forum.xda-developers.com/showthread.php?t=1360994
Flash my zip:
http://dl.dropbox.com/u/13673492/TFU_ALPHA3.zip
Reboot:
You now have everything you need to get started!
BUGS:
Cant install apps unless you use ADB or drop them into /data/app and install.
If some of the preinstalled apps don't work follow this procedure:
-Open nook color tools and disable/enable allow non-market apps.
-Use file explorer to browse to /data/app and click on and install the broken app.
If you need help with ADB or want a different way to root check out my other post here!
http://forum.xda-developers.com/showthread.php?t=1961835
If you find a bug let me know please!
RESERVED
Hi Loney,
Installed just now and all seems well so far - well done!
John
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.
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
stelph said:
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
Click to expand...
Click to collapse
You are spot on. I didn't want to cause problems for people. Is your firmware 1.2.0? its firmware differences which are most likely to cause a problem. If you have a good backup, give it a go. If it works great. If not, you could try sending me your framework.jar file and I can try and find out what the differences are. Good luck!
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 for posting this. Very useful for people who aren't familiar with the nook. I will mention your name and this post when I update my guide with this information.
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
roustabout said:
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
Click to expand...
Click to collapse
This is great news. Everyone will benefit from some constancy across all devices.
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
stelph said:
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
Click to expand...
Click to collapse
In my next update you will be able to customise the launcher as you like. The fact that you cant is a bug that can be fixed by clearing the launcher data using the included titanium backup program.
Since i'm back from the hell of the "bricked nook", now i can come back to test your mod with more understanding.
It seems that if we change the language to all but english, the installation of the mod is doomed to a blank launcher. (that was the case for registering the nook i have to do it in english).
I reflash my nook after setting it in english and that correctly installs everything (not Opera but that's easy to recover it).
may be a note for foreigners who try to install this mod is to be aware of keeping the nook in shakespeare's mother tongue.
would you mind integrating in your future version the manga reader "perfect viewer"? fastmode.apk is also a request but now i understand that is not so easy.
thanks for your contribution. :highfive:
I'll report my experience using this technique. A few days ago, I purchased a US Nook Simple Touch (non-glow) which came with software v.1.0. I made a backup using the method referenced in the OP. I then upgraded to software v.1.2 via the manual (USB mode) method shown at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/ . I made another backup. I verified both backups using the SD card method as suggested by roustabout. Everything looked good.
I followed the OP instructions and was successful in installing TFU_ALPHA3.zip with CWM.
Upon reboot of the NST, I saw a dialog chooser asking me to select either the standard Nook software or Launcher7. I first tried Launcher7 and was greeted with a large gray "n" background. Nothing else. The only button that had functionality was the "n" button which brought up the "home" menu at the bottom of the screen. This got me back to the standard Nook software. So at least the reader still worked.
I rebooted and tried Launcher7 again, just to be sure. Still nothing but the large gray "n" background. No apps.
I restored my v.1.2 backup without any problems, and am now back to a "stock" NST. All good.
So while the TFU_ALPHA3.zip installation proceeded without incident, I didn't see any apps that I could run from Launcher7. I guess I'll have to try a different technique.
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
i had the launcher7 without anything loaded. I had to set the language in english then reinstall the TFUAlpha3 to make it work correctly.
hope it helps.
jjinkou2 said:
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
Click to expand...
Click to collapse
I have the US version of the NST. I couldn't find any way to change the language in the settings.
fastmode is working but we have to set it manually. i read this here http://forum.xda-developers.com/showthread.php?t=1241419, and i tested it.
Code:
adb shell
# cd /sys/class/graphics/fb0/
# echo -n 1 > fmode
# echo -n 0 > pgflip_refresh
since no-refresh and fastmode are autoexclusive i set pgflip_refresh to 0.
values are lost when the nook reboots.
New version coming soon. Lets start a list of requests guys. And if anyone has tested custom graphics settings, what works for you?
Loney,
Things that aren't working for me:
* Launcher 7 settings can't be altered (changes don't "save")
* apk installs are hitty-missy. Sometimes moving an apk into /data/apps and rebooting will work, other times I need to install it again by clicking on it in a file explorer.
* Fast mode app does nothing (but we knew that...)
Other than that, all is cool. I have also installed the patched .jars from the "mod manager" thread and they work alongside your changes.
Well done for your efforts on our behalf. Shout if you want anything specific testing - I'm confident that I can recover from "bricking"!
John
loney01843 said:
New version coming soon. Lets start a list of requests guys.
Click to expand...
Click to collapse
I haven't tried this yet, but when I do I would imagine access to google markets would be needed.
A follow-up on my experience which may (or may not) help getting this to work with the US NST (non-glow). Yesterday, I decided to give GlowNooter (http://forum.xda-developers.com/showthread.php?t=1675706) a try. Suspecting that it wouldn't work out-of-the-box, I deleted /system/framework/framework.jar from the glownooter.zip file. Installation of the .zip succeeded, and I was able to run ADW Launcher. I added my account to YouTube, attempted to sync in GMail, rebooted, and installed the PART-2-END.zip. Then I tried to open up Market, but kept getting connection errors. I also tried the Browser app, but was unable to enter text into Google's search page. So I guess there is stuff in glownooter's framework.jar file that is needed for everything to work. I didn't try too much more.
Anyway, I reverted to the stock NST 1.2 software for now. But I am happy to help with testing new firmware since I'm pretty confident about restoring to stock software.
great feature does anybody goy it working on windows 7 and android 4.1.2 ? :silly:
video http://www.youtube.com/watch?v=HVvczhM5KxI :good:
Yeah the dude in the video have done it
posted by the Q Master, woepidooo
coolnessQ said:
Yeah the dude in the video have done it
posted by the Q Master, woepidooo
Click to expand...
Click to collapse
But does someone has the download files ?
Sent from gs3
gasb00st said:
But does someone has the download files ?
Sent from gs3
Click to expand...
Click to collapse
Might be find able via google
posted by the Q Master, woepidooo
coolnessQ said:
Might be find able via google
posted by the Q Master, woepidooo
Click to expand...
Click to collapse
only found it for windows 8 and i run windows 7
Try porting the app but that might give some errors
posted by the Q Master, woepidooo
Hi Guys... Please follow the link of the thread that I did for whom need to have how to get the side sync phone screen app installed on non-Samsung PC… hope you enjoy it!
http://forum.xda-developers.com/showthread.php?p=41243207#post41243207
yeah did found that thread but when installed can't find programm can't get it working on win 7
I found a semi-working app for non Samsung PCs, thanks to https://twitter.com/KashaMalaga
He posted the SideSync app, and a hacked SideSync.exe that runs on any PC, and they work on mu Compaq PC, but upon trying the connection with the SideSync app on my S3, it crashes (Force Close). I don't know if this is for all (bad hack of the exe), or it is my ROM (which is a stripped down version of Samsung EMD2, many bloatware removed, and many frozen useless apps)
While the Phone Screen Sharing works just fine, quite fast. no issues
mcbyte_it said:
I found a semi-working app for non Samsung PCs, thanks to https://twitter.com/KashaMalaga
He posted the SideSync app, and a hacked SideSync.exe that runs on any PC, and they work on mu Compaq PC, but upon trying the connection with the SideSync app on my S3, it crashes (Force Close). I don't know if this is for all (bad hack of the exe), or it is my ROM (which is a stripped down version of Samsung EMD2, many bloatware removed, and many frozen useless apps)
While the Phone Screen Sharing works just fine, quite fast. no issues
Click to expand...
Click to collapse
thanks man it works great on windows 7
sjg83 said:
Hi Guys... Please follow the link of the thread that I did for whom need to have how to get the side sync phone screen app installed on non-Samsung PC… hope you enjoy it!
http://forum.xda-developers.com/showthread.php?p=41243207#post41243207
Click to expand...
Click to collapse
i have installed it again and it seems to work fine now thanks !
Quick write-up:
First a YouTube video with the functions: http://youtu.be/HVvczhM5KxI
Links as posted by KashaMalaga on his twitter -> https://twitter.com/KashaMalaga
First link, full package: http://goo.gl/WcbGP
Second link, cracked sidesync: http://goo.gl/1RfeS
Extract both archives.
1. Open this folder from the first link: Side Sync 1.0.2.12 and execute the inst.exe file as admin. (Wait till its done)
2. Open this folder from the first link: Phone Screen Sharing 1.0.0.1 and execute the Chain_Install.exe file as admin. (Wait till its done)
3. Copy the file SideSync.exe from the second link and paste it in this folder C:\Program Files (x86)\Samsung\Side Sync
4. Of course overwrite
5. Grab your phone
6. Open Samsung Apps on your phone (Pre-installed on s3 en note 2 as far as I know).
7. Download Side Sync and Phone Screen Sharing (Both made by Samsung)
8. Go to settings -> Developer options -> Slide top right slider to on position -> Check Usb-Debugging
9. Hook up your phone to your pc (Wait a minute for windows to install drivers and such)
10. Open Phone Screen Sharing app on your phone
11. Open Phone Screen Sharing on pc
12. Let Phone Screen Sharing on pc look for updates and such and follow instructions.
13. Everything should work now.
Tips:
Notice that you have two hidden arrows on the side of the phone preview on your pc. Top and bottom.
Top arrow hides functions like taking a screenshot and taking a movie. It also hides drawing and file manager.
The bottom arrow seems to have the equivalent function of holding the home button (Sort of a task manager)
You can re-size the preview phone, just grab it at the top left corner.
You can drag files from your pc to your phone preview. It will always ask if its okay to overwrite even though its a completely new file.
To be honest we are only using the Phone Screen Sharing app.
I couldn't get the Side Sync to work, which in my opinion is only handy if you have a dock for your phone.
I think the functions of Side Sync and the Phone Screen Sharing app are identical (Its just missing the backup function).
NOTES:
I opened both files as admin, I don't know if its necessary.
Also, I just wrote down what I did. Its up to you how you deal with those files and if you trust them.
Working on S3, Paranoid 3.15, Win7, but just the Screen Sharing one.
alternative app.
there's an alternative app with does the same job (well, almost the same job).
for those having issues getting sidesync to work, you might wanna give ShareKM a try. (google it, i can't post links just yet)
If anyone has an old UK device at the bottom of a drawer somewhere which they recollect has a non-English language dictionary from B&N on it, please contact me before trying this.
Spoiler: How I did it
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
The most important discovery was that the "UK ROM" was still there in the US FW 1.2.2 update. That is to say, if you copied over the splash screens from the UK 1.2.1 update and the Oxford dictionary, you had nearly everything that was different between the two. Except it didn't work. It looked different on boot, but was still the US version (you can tell by looking at Settings which are different in the two versions).
Eventually I took at look at the update script in the B&N zip and saw that it was checking build.prop before doing anything else. I compared that file on the UK 1.2.1 and US 1.2.2 zips and found the major difference was in localization. In two entries "GB" was used instead of "US". Was it that simple?
Yes!
Ah...but it refused to register. In fact, it refused to authenticate, so it never got to asking about your account. The final discovery was the result of a completely idle-brained attempt (because I was out of ideas). I had rooted an instance after skipping OOBE. In the launcher app drawer I saw the familiar junk, including DeviceRegistrator (anyone who has rooted an NST knows this app with the smiley-face icon). I've always thought it was just cyber-detritus, an early version or mock-up left by B&N developers. They were not very tidy, after all. But maybe intents of the app are used in the current registration process. Who knows? Anyway, I tapped on the icon and proceeded to successfully authenticate the device. That got my attention! Then I tried to register with my existing B&N account and password. BINGO! I could see my device on the B&N website under my account and I was able to "buy" a free book using the Shop app (you need a credit card on file with B&N to get even a free book).
So it works for me, in the US.
Because of the changes I made to the original US 1.2.2 update zip, the internal signature is broken, so it cannot be used as an auto-update zip. Hence the need for CWM.
To avoid the necessity to root (for those who would rather not), I removed the broken Lancher.apk in /system/app and replaced it with a simple launcher in the Gingerbread style that is able to run as a system app. So when the device gets to displaying "home", it asks how you want to do that. Initially, the Launcher app is selected so that you have access to an app drawer and the DeviceRegistrator app. After registration, a reboot will present the "home" option choice again. This time the "always" box can be ticked and the B&N "Home" app selected. The Launcher.apk will never be heard from again. Those who go on to root can remove it from /system/app if they wish.
Outstanding issue to be explored: dictionaries. There seems to be a capability for adding different language dictionaries. The User Guide refers to this also. I have not been successful in doing this and don't know whether there ever were any other dictionaries. Since this was not a US option, I'm guessing that the only hard-coded URLs for the dictionary downloads are to non-existent UK servers. I still haven't tracked down where those URLs are. The Nook app for Android is reputed to have the same capability, but when I installed it on one of my rooted tablets, it only had an English dictionary. The format of this db file seemed to be exactly the same as the Oxford dictionary on the UK ROM. I got a Spanish book from B&N and tried to look up a word from there. This gives an option to download a dictionary (as the user guide says) but the result just sends you to the Settings where the only dictionary visible is the default English. So maybe you have to be in another country? Anyway, I could not get the NST to recognize the English dictionary offloaded from the Nook app, despite the apparent structure similarity with the Oxford already onboard. Perhaps there is a database somewhere that would keep track of the dictionaries on the device if the download function were still working. I have not found it. Or, perhaps additional "downloaded" dictionaries have a special place to be (Edit: YES! They go into /data/media/B&N Downloads/Dictionary). Someone with a long memory who has experience with the UK ROM but is not primarily an English speaker might hold the key.
Spoiler: Q&A
--Is this the same thing as the Region Changer?
No. The region changer procedure gives you a device running US firmware (although it looks like B&N still knows it's a UK device based on the serial number and their own records--or they might be identifying its point of origin by the internet connection). This update zip will give you a true UK ROM: the different splash screens, the different settings options (including language) and the ability to enter letters with diacritical marks from the keyboard. It also features the Oxford dictionary. However, it will contact US B&N servers, not the non-existent UK ones.
--Do I need to have an existing B&N account?
I think so. The back door we are using to authenticate and register the device does not have an option for creating a new account.
--Should I deregister my device before doing this?
If you did a region change and are currently running registered US FW 1.2.2, I would recommend deregistering the device before converting to the UK ROM, just to avoid potential conflicts. You can use the same account to register the new ROM. If you have B&N content, it might even show up since it's the same account (mine did).
--Can I purchase books from B&N using the Shop app?
Maybe. I was able to "buy" a free book from B&N and have it appear on my device (note: to purchase even a free book you need to have a credit card on file for your B&N account). But, I am in the US. The B&N Terms of Service says that you have to use (or have on file) a credit card with a US address. There appear to be workarounds like purchasing a US-based cash card, etc. Seems like a lot of extra effort, but apparently some people have done it.
--I live in the US but this sounds interesting. Can I try it too?
Well, I did! The ROM is interesting in a number of ways. It really is a Western European variant, not just UK. German, English, French, Italian and Spanish are the available languages. If your primary language is not English but instead one of these, this might be an attraction. However, there is at least one unexpected consequence. Some external servers will be absolutely convinced you are outside the US. I found this out by trial-and-error when I could not get my Today's Comics app to work. When I changed the region to English (US), it began to work, so I guess the content was region-blocked. I jiggered the Settings app of the UK ROM slightly so it would display the English(US) option.
--I see "Chinese" among the languages! Can my NST display Chinese?
Well, no. Unfortunately the only way to get English(US) to display is to display all of the "development" languages. I tried to suppress "Chinese" but had no luck. There are Chinese characters in DroidSansFallback but the strings for the B&N system were never fully translated (maybe not at all). There is a lot that is translated (appears to be Taiwanese Chinese), probably left from the original phone ROM they used to make the NST OS. However, if you select Chinese any apps you may have installed that are correctly localized for Chinese will display appropriately.
How to do it
Note: I did this on a deregistered device. It does not matter whether your device is currently US FW 1.2.2 or a UK FW 1.2.1.
1. Prepare a CWM card (if you don't already have one, use one of the two sdcard versions). If you've never done this sort of thing before it's probably easiest to download the zip for the Nook Region Changer and follow the instructions there for making the sdcard (steps 1-3). You don't need the two update zips that are on the card, but it's still CWM. If you already have a Region Changer card, you can use it as-is.
2. Download a copy of my 1.2.2 UK update zip. Copy the update zip to the CWM card (the card should be in the card-reader slot of your PC, not in the Nook)
3. Power down your Nook.
4. Insert the CWM card into your Nook and power up. You'll see the logo and maybe the opening menu.
CWM is a little wobbly on the NST. Sometimes it seems to get stuck on a white screen after the logo. If that happens to you, press the lower right hardware button. That generally wakes it up.
Navigating in CWM involves using the upper left hardware button (go back to the previous menu), the two right hardware buttons (go up and down a menu) and the "n" button (do what is highlighted).
5. Move down to "backup and restore". Press "n".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. The menu should show "backup" at the top. Press "n". This will backup your current configuration onto the sdcard.
7. At the conclusion of the backup you should be returned to the top of the menu.
8. Move down (or one step "up") to "advanced". Press "n".
9. Move down one step to "wipe dalvik cache". Press "n".
Then move way down (or a little up) to "yes". Press "n".
Here you may run into another CWM issue. At least for me, CWM has a tendency to freeze after any kind of wipe. If that happens to you, don't panic. If the buttons don't seem to be responsive, press and hold the power button. If the device does not reboot back into CWM, release the power button and press and hold again. Eventually the device will reboot, taking you to the top of the menu again.
10. From the top of the menu move down to "wipe data/factory reset". This option is just like the previous one, including the potential freeze. Do it.
11. From the top of the menu, move down to "install zip from sdcard". Press "n".
12. The top of the next menu says "choose zip from sdcard". Press "n".
13. Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
14. After the update is complete you need to return to the top of the menu where it says "reboot now" (if you are not already there). At that point, remove the CWM card from the device and press "n" to reboot.
15. Your Nook will boot into the UK ROM setup. You'll see the familiar multi-lingual splash screen, the marching dots, and finally come to a Language choice screen.
Select whichever language you prefer. You can change this later from Settings.
16. The next screen is the "Welcome" screen.
You are now going to execute a "skip OOBE". Since registration fails in the usual setup wizard, we will have to go in the back door, so to speak. At the "Welcome" screen, press and hold the upper right hardware button and swipe your finger across the top of the screen from left to right. You should see a "Factory" button appear in the upper left corner of the screen. Tap it.
17. Now you are on the Factory screen.
Again, press and hold the upper right hardware button and tap the screen in the lower right corner. You should see a "Skip OOBE" button appear on the screen. Tap it.
18. OK, so now you are faced with a choice which I have added to the ROM in order to finesse the registration issue without needing to root the device. There should be two options listed on the screen: Home (the B&N home screen) and Launcher (I added this). For now tap on "Home". The B&N home screen loads up with the infinite spinner in the lower half (no registration, no wi-fi, no data).
19. Press the "n" button and select "Settings". Set up a wi-fi connection and set the time zone and time display format. Leave wi-fi on. Use the power button to shut the device off.
20. Power up your Nook. When it has passed the marching dots it will ask you again whether you want "Home" or "Launcher". This time, choose "Launcher".
A simple Android launcher screen is displayed. All you care about is the app drawer, that little square of tiny squares in the center of the bottom of the screen. Tap it.
21. There is a bunch of stuff (mostly junk) in the app drawer. Resist the impulse to fool around there. Keep your eyes on the prize! Locate the DeviceRegistrator app (stupid smiley-face icon). Tap it. Check to be sure your wi-fi is on.
22. You need to do two things here.
First, register (authenticate) the device itself. That's the first button on the left in the first row. Tap that. If all is going well (and your wi-fi is on) you should get a confirmation alert. After that, type in your username (email) and password for your B&N account. There is no option here to create an account, so you need to have one already established for this to work. After you've typed in the information, tap on "Register User". You should get a confirmation alert. You can now turn off wi-fi. Press the "n" button and select "Settings". Check Device Info>About your NOOK. If everything went according to plan you should see that it is registered.
23. Shut down the Nook. Power up one more time. After the marching dots you are again faced with the choice of "Home" or "Launcher". Before you make your selection, tap on the little (empty) checkbox. This will make your next move permanent. Now tap on "Home".
You'll never hear from "Launcher" again. It will just languish in /system/app with all the other unused apps and your Nook is now registered and good to go!
If you want to root and further customize your Nook, select one of the updated NookManager packages. I strongly recommend using NookManager to make a backup of your device before rooting. The CWM backup you made at the beginning of this process is not a complete nandroid backup and you'd be better off with one before you make any more changes. If you are not interested in rooting, you may want to make another backup with the CWM card at this point and then put it away somewhere safe. Just in case.
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
ashh87 said:
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
Click to expand...
Click to collapse
Thanks a lot for the feedback. Now we know it was not just a one-time fluke for me. I'm glad it worked for you as well.
Also worked for me. After registering I used NookManager to root it, then installed the latuk kernel from this post with CWM and it's now UK 1.2.2 and external keyboard supporting. That's all I was looking for. Another thumbs up for the repeatability of your method. Thanks for the detailed instructions.
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
markeq said:
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
Click to expand...
Click to collapse
Let's say--hypothetically, of course--that you did that. There are two ways around it.
1. If you rooted with the "traditional" or "stealth" versions of NookManager, you have ES File Explorer. You can use it to access the App Manager and remove the defaults from the "Launcher" (or "Home", or whatever). After doing this, a reboot will present you with the choices again. Screenshots for a likely sequence below.
2. A more general quick-and-dirty method that will work in any situation: install yet another launcher app. When you reboot, the activity picker will see a new option and give you your choices again. When you've got it right, just uninstall the additional launcher (which you never have to run for this method to work). Here's a link to another simple and relatively useless launcher that will fit the bill.
nmyshkin said:
Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
Click to expand...
Click to collapse
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
any ideas on what i could try different to get working ? otherwise im stuck on a de-registered 1.2.1uk so my only option might be to nuke all b&n and go custom ereader route (which is probably fine tbh)
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Renate said:
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Click to expand...
Click to collapse
yeah it looks normal on my computer (im running popos although i cant see how that would change anything)
Well, you can always do it semi-manually, at least you'll get feedback.
Extract META-INF\com\google\android\update-binary
Go to TWRP and use ADB to push both the (original) zip and the (extracted) update-binary somewhere useful.
Use ADB (you do have a rooted prompt?)
Code:
# chmod 755 update-binary
# ./update-binary 2 1 whatever.zip
You'll get text out of this and maybe figure out what the problem is.
cyberboy666 said:
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
Click to expand...
Click to collapse
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, just in case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
nmyshkin said:
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, jus tin case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
Click to expand...
Click to collapse
omg thanks ! yes i think issue was with CWM card - i flashed a new one from the link you gave and now it is working
and also thanks for the advice @Renate - i want to get set up/learn to send ADB anyway so this is helpful
Hmm, well, I didn't know that.
OTOH, you would have seen that you couldn't find an update-binary in that zip.
nmyshkin said:
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
Click to expand...
Click to collapse
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
jewelie said:
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
Click to expand...
Click to collapse
I'm glad it worked for you. That's my reward
Unless your glowlight is not turning off completely, I can't think of any other factor on a stock system that would drain the battery fast, barring some unknown hardware issue.
Hopefully this sorts it out.
On top of the running an unregistered device, I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing. Other possibilities that have been suggested to me are corrupt books, and maybe having the WiFi off.
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Device is now on sleep with wifi off and no books after the fresh start. I also hacked the cover I was using to make sure it wasn't touching the screens or buttons. It's at 79% now, let's see what the percentage goes to over the next few days...
EDIT: BTW The reason I know it's not the battery itself is because I disassembled it and tested the battery through a few 0.5A charge & discharge cycles and gave it a week to see if there was any significant self discharge - madly, it still has almost the full 1500mAh capacity - impressive for a device that's been going for 10yrs now!
jewelie said:
I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing.
Click to expand...
Click to collapse
I think this has been debunked in the distant past although I can't put my finger on the particular post.
jewelie said:
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Click to expand...
Click to collapse
That part is interesting and the initial result is not surprising. Unfortunately CWM cannot do a thorough wipe unlike, say, TWRP. A factory re-image is the most thorough cleaning I'm aware of, followed by the deregister/erase, then with CWM bringing up the rear. The reason I didn't include a factory re-image at the beginning of the process is that I wanted to keep it simple and not scare away those averse to anything approaching root. The 8-failed-boot-attempts method for a factory re-image is tremendously tedious and involves close timing and dexterity. OTOH, a NookManager card can initiate the process with the push of one hardware button. But that means making yet another card and flirting with the whole root thing (not necessary to root just to do the factory re-image).
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
@nmyshkin Thank you so much for the detailed guide.
I followed all the steps without any issue. I even got the freezing bug after clearing the Dalvik cache. But followed your steps, pressed on the power button twice and it restarted.
I used a 2Gb memory card and used the sd_2gb_clockwork-rc2.zip and I've written the image with WinImage 8.50.
nmyshkin said:
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
Click to expand...
Click to collapse
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
jewelie said:
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
Click to expand...
Click to collapse
I'd say so, especially if you've been doing any reading at all.
nmyshkin said:
I'd say so, especially if you've been doing any reading at all.
Click to expand...
Click to collapse
Update: It's over a month later, battery is still on 26%. Touch wood, it's fixed. THANK YOU!