Database Users

Throwing in the Towel on the A7

After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.

Just my 2 cents... There is not eLocity (Stream TV Network) problem
Google denied Market at some tablets. G considered that their OS version 2.X is not compatible with tablets.
These tablets do not have Market "out-of-box":
Viewsonic G Tablet
Malata ZPad
Advent Vega
Archos (all versions)
etc...
Idk why Galaxy Tab has market "out-of-box". May be Samsung proved Google that it's big phone)))

StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up
Click to expand...
Click to collapse
Try nameing the file Update. Do not add the.dot zip, holding down the power button until the third line of text is seen then release will get you into program mode.. selling a tegra tablet to get anything other than another tegra is like going backwards...

StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
Where are you located? I'm. Sure if there is a member here local to you, they'd be willing to help you out.

I'm enjoying my A7 but, I do have to give a certain amount of blame to Stream for the lack of user friendliness the device presents. There are all sorts of documentation out there for companies to reference when designing an Android device, giving them an outline of what will work. The choice to implement a code structure or hardware features that do not work or require a work-around is directly the fault of Stream, as testing should have revealed the issues.
Take a look at how long Dexter has been working on the mod many of us are using, the feedback people give after putting it through the "real world" challenge and then the subsequent updates from Dexter...if Stream did the testing and verifications on this product from concept to creation to now...someone needs to be fired or doesn't care. Without detracting from Dexter's efforts or anyone else contributing on this board but, if the customer base can put so many fixes in place:Why can't the OEM? Why are they so slow in comparison on responses? Why don't their updates fix the most common issues? How did they allow themselves to release a tablet without a proper OS and fail to do better funtionality testing?
I'm glad their are folks like Dexter out here and forums like XDA otherwise decent hardware like this would allow companies to seperate us from our dollars on inflated claims of fuctionality and force us to jump through hoops to get a remedy.

problem with A7
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
\
email me at [email protected] and I will do what I can to help.

A7 Towel
Here are some quick things to know/try that work for me -
1. SD card must be formatted as FAT format, FAT32 is fine
2. Mod file is named update.zip in sd card, do not put it in any folder in the SD card
3. When you are powered down, if you hold the power button in for about 15 seconds and then release and then hold in again for a few seconds you will see, hold in for another 5 seconds to go to boot menu, immediately hold in for another 5 seconds and then release, you should see a android character, tap on home icon on right and it should go into a boot menu
4. Use the buttons on the tablet (home, etc on the right) to page down and up the list of selections. Top 2 buttons on the right are up and down. Second to bottom icon is select.
5. Scroll to "apply sdcard:update.zip"
6. Select that option (second to bottom icon on right of screen)
it should now apply the update.zip on your sd card. It could take a while.
If there are any errors then the update.zip file may be corrupted. All updates are over 90MB in size except for the patch that Dexter sent recently which is around 3MB.
Let us know if this works.

Thanks for the responses
I have done several times the instructions some of you have responded back with and watched several posts on YouTube also. Yes my card is formatted to Fat32 and yes I used a capital U on Update.zip. I have followed the instructions to a "t" for installing DexMod and Elocity's own instructions on their website in regards to the 2/24/11 update. My A7 simply would not recognize and open the SD card file and would then abort the program. I'm simply at a point where how much more of my time do I want to spend spinning my wheels on the A7 tablet in order to have access to the Android Marketplace. Thanks again everyone.

Please see my response at bottom.

A7 issue
sorry to hear that. I suspect your update.zip file is probably not being recognized as a zip file. mine is named update.zip, no uppercase anything. Sometimes there can be a hidden extension of another .zip so the system sees it as update.zip.zip
I downloaded the mod and renamed mine on my pc and then copied it directly to the microsd card. Sorry to hear about the time its taken you so far. As I said earlier I would be happy to work with you if you wish.

just to clarify, you can't really install the latest feb 24 update from elocity AND dexters elocitymod rom. Unless, that is, you take the mods that dexter has done and apply them to the latest elocity update and regression test it, debug it, etc... elocity did a fair job of putting out a cheap android tablet. they made some sacrifices on the hardware side - no multitouch and no hi res screen, but for the price, it's hard to beat. and dexter's mod makes the a7 infinitely more useful. have you tried other microsd cards? you can get cheap 2gb and 4gb ones at target or bestbuy. if those don't work, you can just return them. lots of people have been using dexter's elocitymod successfully. without it, i probably would have returned the a7 also. if you're looking for something a bit more polished, get ready to spend a bit more. samsung galaxy tab goes for about $600-$800 motorola xoom about the same price as well.

Did you check your sd card for bad sectors or tried a different sd card? Just curious.

Same problem adding Dexter Mod
I've just got the A7 and I'm following the threads about the Dexter Mod. I'm a little confused about 1- what to name the file...some say with a capital U and some not...2- with or without .zip...again same thing 3- can you use the 1.2 Mod after Elocity's latest firware update...the reason I ask this is because the link for 1.3 is down and I do have 1.2 on my pc for some reason.
On my sdcard it doesn't have a directory "ROOT" do i just copy it to the open card. So may questions...sorry about that, been at it for 3 hours and no success. Have to laugh tho....
BTW I have a file named LOST.DIR on the sdcard

file name
The file when you download it is already in zip form. All you need to do is rename it to ( update ).

Dexter Mod 1.3
Thank you. Just installed on 1 of my A7's but the 1.3 Mod...Was able to download it this morning, the site is back up again.
Now to do the bluetooth fix...life is all go...lol

Ok, lets clear this up once and for all...
For everyone that is getting confused about update.zip, Update.zip, Update.zip.zip, and whatever other additional permutations of combinations that people have been able to come up with.
The answer: although some people have reported success with a lower case "u", the best way is to simply follow the directions layed out for you and name it "Update.zip"
Here's the simple truth of the matter, the file you download is <Dexter's_webspace>/ElocityModv13.zip ... or if you are going after eLocity's updates it would be
<elocity's_webspace>/update.zip
Notice that both files have ".zip" at the end. No question about it, no chance that this is not true, no chance that as I actually saw someone post on here "elocity never named it .zip".
Now, here's where people have the opportunity to get confused and do something wrong...
PC Users:
A default out of the box Windows installation is set to HIDE file extensions of known file types (zip files included). So, when you look at your download it will appear to be just "ElocityModv13" or just "Update" even though the file extension (.zip) is actually there. So when you try to rename it to "Update.zip" you are changing only the information BEFORE the file extension, thereby making it "Update.zip.zip"... This is no one else's fault. Please don't blame eLocity, please don't blame Dexter, please don't blame the Android OS itself.
The Solution!:
Open Windows Explorer, go to the "Tools" drop down menu, go to "Folder Options", click on the "View" tab on the window that just popped up, uncheck the "Hide extensions for known file types" checkbox, click "OK", profit.
MAC Users:
I am guessing that this applies to most of the "What do I do with all these folders from the zip file" type of posts. The most probable issue here is that Mac's have a rather annoying habit of unzipping zip files as soon as it finishes downloading them, leaving you with just a folder (in this case either named "ElocityModv13" or "update" with no file extension (its a folder).
Mac Solution:
To keep Safari from automatically unzipping your files, the fix is easy.
Open Safari, open Safari's preferences, Click on the "General" tab, uncheck the "open safe files" box, close preferences. Now download either the mod or the stock update again, and you'll have the actual zip file instead of just a folder with the contents of the original file.
Hopefully this helps a lot of people figure this out.
Now...
My Disclaimer:
I already am prepared for the inevitable "stop being rude", "somebody call me a wahmublance", "I'm new to this" type of response that I seem to get more often then not on here. So, before any of that happens let me explain my standpoint.
Anyone trying to go down this route and put a custom rom on their device is attempting to modify it. This SHOULD require at very least a working knowledge of the device or software you are trying to modify. I am not saying everyone here should be on Dexter's level, but at least a little computer know how would be very beneficial. Next, before just diving in to changing things on this little chunk of technology that you just spent a few hundred on, read. Simple as that, educate yourself on the toy you just bough. Creating many many duplicates of threads asking the same extremely basic questions does not help anyone. It clutters up the forums, makes the people that actually have the answers so sick of saying the same thing over and over that they just don't answer any more, makes it harder to navigate the actual different topics, and makes it harder for everyone else to find the answers they are looking for. There should be no "which one of the 15 bluetooth not working threads was that post in?"
I apologize for my complete lack of patience with people that can not search for information and need to be spoon fed. But 99% of the time the question has already been asked and answered. And lets be serious here, the A7 forum only has FOUR SECTIONS, really not a lot of reading. And in the other cases where it is a user error like not knowing how to rename a file or yesterday's hilarious "My SD card doesn't have a folder called ROOT", you really need to ask yourself if this is really something you are up to. If you lack the basic knowledge to perform the easy steps of the process, is it really worth it to risk creating a $300 paperweight to say "look at the cool thing I did" to your friends?
If something I said here seems like it was taken from your post/story, don't take it personal, it was only listed as an example.

I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!

StarBriteK said:
I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!
Click to expand...
Click to collapse
You didn't open a can of worms, it was just a coincidence that the misinforming post that sent the fingers of fury flying happened to be on your thread. and trust me, I have plenty of better things to do, this is just filler.
Seems like you got a hell of a good deal on the G Tab, Congrats.
And yes, the point of a forum is to help other people, which I do. By correcting bad advice, and trying to get people to ask for and give help in a more collaborative way instead of the same questions being asked over and over again. I'm sorry if you find my presence on the internet grating, just be glad that you haven't had to endure my vocabulary in person (apparently it is pretty similar to that of a drunken sailor with tourette's syndrome with the same measure of sarcasm that I treat the net to)
Back at you on the good luck. Expecting a review on the g tab, pro's and con's vs the A7 hopefully

LOL
LOL, you guys are just hilarious

[Q] Newbie needing advice please

Wow, talk about confusing, the A7 is a whole new world to me.
I've had computers for years, currently I have two running XP & 7, plus I have two laptops running XP & 7. I understand a lot when it comes to computers, but the A7 is so different.
I've downloaded & printed the User Manual and I have read it several times. I've read numerous posts on this forum and now I'm confused. I feel so dumb. Too many words that I don't understand. I want to learn everything I can about running every aspect of this tablet, but it's like just as I learn one thing, the next time it doesn't work that way.
I need more reading material. Whether it be links to posts, books to read, anything to help me understand what I am doing. I make notes of things I have read so that I will remember what to do next time. Post something to help me, PM me or even email me.
I will be so greatfull for any help given.
Thank you

The user manual you can download on elocity's site is useless because there is a lot of things that were never edited out to match the actual release version of the tablet.
As far as computer knowledge and relating it to the a7 or android in general, windows knowledge will not get you very far. A good working knowledge of Unix/Linux will give you a much better idea of what's going on behind the scenes since android is based on Linux (loosely, in my opinion) but still functions very similarly.
If you have any programming or web design experience, I would recommend downloading the android sdk and do some playing around with simple programs. Also with the sdk you can make a virtual android device to monkey around with without fear of messing up your new $300 toy I use eclipse as my development environment in Linux, not sure what a good windows alternative would be, but the structure of an android app is pretty easy to follow. There are example programs and source available on the android developer site developer.android.com if I remember correctly (same place to get the sdk). And the language itself tends to be pretty similar to writing a Java app.
I've probably missed the mark completely on the information you were trying to find, but if you are anything like me, you'll find hours (years if it gets you going down the Linux/Unix path lol) of obsession with just this info.
Hopefully it gets you on the opensource band wagon (the reason I love Linux/Android)

Wow...where to start? Well, you got that you turn it on and slide the lock to the dot to unlock. Then you are in a "home page". There are 5 of them. there are dots at the top of the screen showing which home page ur on. Usually the center one. Touch the screen and slide one way or the other to move the home pages.
If you touch the square whitish pad at the right of the screen with a bunch of darker squares in it, it takes you to your apps - the programs that do what you want.
If you touch an app it runs. Touch the return arrow just to the right of the screen to close the app and go back. It always takes u back.
You have to "root" the machine to get the good apps. Usually with Dexters mod. This is easy. You download the file, rename it to upgrade.zip, place it on a micro SD card, and go to settings/About Device/System Updates/ then touch update device.
The home button at the right side of the screen always takes you to the center home page. - It DOES NOT close the app you have open at the moment.
you should get an app closer to close all of the un-closed apps for you.
Oh yea, android market place is the app you want to add all of the apps you want.
You get it with Dexters Mod (4.1 right now)
and there is tons more...............

Based on Linux ... now I understand why this is confusing to me. I've never worked with it before, but I understand from fellow users, they like it better than Windows OS.
I've never done any programming or web design, but maybe it's not too late to learn something new.
I thank both of you for your info and appreciate everything you have said.
mrpete2u I really appreciated the details of your instructions. I know I'm a dummy at this, and I'm sure there are more of you guys out there to help.
Thanks

mrpete2u said:
You have to "root" the machine to get the good apps. Usually with Dexters mod. This is easy. You download the file, rename it to upgrade.zip, place it on a micro SD card, and go to settings/About Device/System Updates/ then touch update device.
you should get an app closer to close all of the un-closed apps for you.
Oh yea, android market place is the app you want to add all of the apps you want.
You get it with Dexters Mod (4.1 right now)
and there is tons more...............
Click to expand...
Click to collapse
Another newbie jumping in....and trying to figure this out. To "root" the machine do I need to update the firmware from the elocity site or can I jump to Dexters right away. If so, where do I find that?
Thanks for your advice.

your a7 is rooted already with dexters mod or elocity firmware.

My Kernel version is 2.6.32.9-svn2514
[email protected]#1
And Build # PBJ8000.2.0124
And ECv is 0.14
Would you mind explaining what these numbers mean, please?
Thank you

koalaw said:
My Kernel version is 2.6.32.9-svn2514
[email protected]#1
And Build # PBJ8000.2.0124
And ECv is 0.14
Would you mind explaining what these numbers mean, please?
Thank you
Click to expand...
Click to collapse
You are one version in the rear, version now is 2.0133, most member her are running Dexter Mod 1.41 include myself an entirely different beast, stock Roman won't let me load Asphalt5 game so Dexter it is...A7 come from factor rooted Don't think any other tablet come out already root...

Your saying I need to upgrade one version
and that my A7 is already rooted??
Thank you for the answers.

koalaw said:
Your saying I need to upgrade one version
and that my A7 is already rooted??
Thank you for the answers.
Click to expand...
Click to collapse
look here for Dexter mod forget about the stock rom ....
http://forum.xda-developers.com/showthread.php?t=890042

I have now updated to 2.0.0133
Now I need to figure out how to get the market icon so I can start looking for more apps & games. Tried downloading earlier and it keeps telling me that I have downloaded to my phone? I don't have a fancy phone to download to.
Here I am again confused, but what's new about that!!

There is a thread in the device section on adding market to stock rom.
Or you could just run elocitymod by Dexter.

I did run the elocity mod 1.41 and my firmware was updated to 2.0.0133
When I am on market.android's site, they want my phone number so they can download the app to my phone.
I'm trying to download the app to my tablet.
Am I confused or what
Thanks for answering me.

koalaw said:
I did run the elocity mod 1.41 and my firmware was updated to 2.0.0133
When I am on market.android's site, they want my phone number so they can download the app to my phone.
I'm trying to download the app to my tablet.
Am I confused or what
Thanks for answering me.
Click to expand...
Click to collapse
Yes, yes you are lol
For all intents and purposes (as far as Google is concerned at least) your tablet is a phone.
Install market enabler on the a7 and fake a cell provider. The a7 should show up on the Google market website after that.
You didn't install dextermod and then apply eLocity update over it did you? Just want to be sure.

Your laughing at me .... that's ok ... right now I'm so new at this, I really don't care, in fact I am laughing at myself for being so dumb.
I went to dexter's site and downloaded a file called elocitymod1.41 and renamed it to update.zip and that is what I installed.
OK I will install market enabler
Thank you again for helping this dummy .... LOL

From the perceived tone of the post prior to my last one, I thought you were already at the laughing stage. I thought I was just laughing along, sorry for the mix up.
Sounds like you are doing everything right. I just wanted to make sure that we were dealing with a clean install of elocitymod, and not something mixed together by trying to ally another update on top of it.

Needless to say ... I am still confused.
Installed the market enabler, but I am not getting anywhere.
Why I try to install an app I get a message telling me there is no phone attached to this account and they want me to log in with another account. When I try creating a new account, there is no place to give a phone number and I get all those stupid messages again.
Just wondering if I am too dumb, because you all make this seem so easy, that maybe I should give up and figure out other ways to get apps and leave the android market site alone???
Sorry if I have frustration in my voice, but I guess I thought this would be easier.

koalaw said:
Needless to say ... I am still confused.
Installed the market enabler, but I am not getting anywhere.
Why I try to install an app I get a message telling me there is no phone attached to this account and they want me to log in with another account. When I try creating a new account, there is no place to give a phone number and I get all those stupid messages again.
Just wondering if I am too dumb, because you all make this seem so easy, that maybe I should give up and figure out other ways to get apps and leave the android market site alone???
Sorry if I have frustration in my voice, but I guess I thought this would be easier.
Click to expand...
Click to collapse
Why not just use market from the tablet? I wouldn't stress so much about trying to get it to work and remotely install from the web site.

Each time I go to the site, I am on my tablet. Mainly because it has a direct install button and not a download, so I want to be on the tablet to install on it.

koalaw said:
Each time I go to the site, I am on my tablet. Mainly because it has a direct install button and not a download, so I want to be on the tablet to install on it.
Click to expand...
Click to collapse
So are you hitting the Market icon (opening the Market app) or are you trying to open http://market.android.com/ in the web browser?

[New Members] COMPUTERS +DEVICE-Learn how to-Flashing

Guys,I am not too new in this social forum dedicated to hacking mobile devices but I am to computers and computer jargon.
We,new comers get excited when reading posts saying I did this,I did that.Worked like a charm,I tweaked this I tweaked that.I am in control of my device,on Gingerbread now my device is on JellyBean.Awesome.
But they were able to have this much of control over their device because they know something which we, are not certain off.
Using their computers and also knowing their device.
One of the fundamental rules in Forum XDA is reading,reading and more reading.And yet there are so many who screw up.It is said that to do any stuff,you must follow the instructions given by the developers to the letter and yet nothing is smooth as it should be.
Lack of absorbing instructions.
Or just can't understand clearly.
Well,it's about the same.You can read,read and read but when it comes down to actually doing it,you would definitely have to use a desktop or a laptop.
That's when the ordeal begins.Did it say this,to press this or do this.Oh bugger,I should not have done that.
F**k,F**K,F**k,shi*,My phones got boot loops,its not opening,Cant get to open my sweet beautiful Xperia Arc/S,Neo/Neo V/Pro/Mini Pro........I'm pricked.
Sorry,bricked my device.Crying!!!!!
[This above anxieties was well documented/experienced by yours truly) So don't nobody say I'm pointing my index finger at you!
Everyday,there are thousands getting hold of a mobile device,new and used,young and old-like me.And those who read magazines or who have friends who read magazines would have heard that one could really take charge of the devices that one owns and be a master of it.But one also must understand and navigate a computer,haha.
So ,I am going to start the ball rolling and everyone is invited to add on this thread.It is not specifically designed to just advice.But a detailed advice would be welcomed.You know this is for newcomers and people who are not well versed in using the computers.So a detailed as and example:
You need to flash this firmware
4.1.B.0.587.
You need:
1)Flashtool-download from here----
2)Firmware-download from here----
Once done downloading,run flashtool in your computer it can be located in 2 places either in downloads or C:\.Now,right click on it and there will be a prompt WinZip and if you are using 7zip it will also be within WinZip asking you where to extract the file to.Extract it to the same page.
Now after the extraction you will see a folder pop up in the page with the same name minus the .exe.Double click on it,you will see a bunch of files.We are only interested in 2.
Drivers-double click on this.There will be a prompt.Press install.Then there will be a couple of more prompts in unison just keep on pressing next,next and press finish when the last prompts pops up.All in all, there will be 4 prompts.I think,I will check.
What this does is linking your device with the computer.Now,this file will open and in it you will find your device name,tick in the box next to your device.Scroll down to the bottom there will be flashtool and flashmode.Tick the boxes beside both.You are done here for now.
Press back on page.You will come back to earlier page.In here there is a file named Firmware.
Click and open it.Inside you will find x10 firmware.This is because the creator of this tool,Bin4ry and Androxyde initially created this tool for the x10 device,I think.Delete this.I had left this there before but after inserting another firmware in another column in the page it will read kernel.sin adsp.sin,kernel and stuff.
Was confused.So I only put one at a time.Should be easier that way.
Leaving it just like this now go and download the 4.1.B.0.587 if you haven't already.
Its always good to prepare everything needed.Just say for argument sake you have already done that.And it is in your download section.
The file will also be a zipped file.Unzip it,like you did with flashtool earlier and now you will have another folder with the same name.
Double click on the folder.There will be another file,click one more time on it, a pagination indicating it is the said file only now it will read as a .FTF file.This is what you need.
Press right click,a window will pop up,as though you didn't know this already,right click on it then copy or cut.
Go back to earlier page,click on firmware folder again and right click and press paste.The firmware is magically transferred here.Sweet.
Now its almost time.Get your USB cable ready.See that your device is at least 70% full.For whatever reason you are connecting your phone to the computer always backup your contacts,call logs,mail.
Whatever that needs to be sync with another remote destination let it sync.This way you can retrieve your stuff if something goes wrong.And you loose everything on your SDcard.But with this very detailed step by step guidance and if you still manage to screw up."Youve got a BIG problem with navigating on a computer.
"Google sync is the best for contacts, call logs and mail.Photos and collection of movies,videos and MP3s you pirated, I would say,your computer.
Also a friendly advice don't put too much hope of retrieving from apps which say that you can backup to.When everything goes,everything goes,even your backup app.Now back to business at hand.
Get your cable,checked
Phone at 70% charged or more,
checked.
Open flashtool,this is where?In your C drive, C:\flashtool and flashtool the folder,double click the folder,bunch of files again.
Double click on Driver prompts,run it,it will open up,again tick on the box beside your device,flashtool and flashmode.Done.
Go back to earlier page,this time click on firmware again,just to check if the firmware that you cut/copy pasted is still there.Present.
Good.
Go back one page,now,towards the bottom of the page there will be flashtoolx86(this is for windows xp if you are using a windowsXP 32bit.You know what you are using,don't you?)And flashtoolx64(this for windows7 and x64bit computers)Click on this,only one.And a reduced size page will appear.This is the main page of flashtool.
Click on the lightning icon another page will appear.This time your firmware that you cut/copy and pasted earlier will appear.
Mind you this detailed tutorial is only for flashing and as an example.
Now,there are 3 coloums at the extreme right of the page.Non of the boxes must he ticked/checked.
Make sure of this,if you don't want to send out PMs to members who might be just about to hit the sack with their partners.
There are some nice members out there as there are others.
Right,coming back,at the bottom
of the page there is a box and beside the box is this line,no final
verification.
Tick only this box and press OK.On the screen you will see an illustration of a USB cable putting in and pulling out and a instruction which says to power off the device.
But wait.You are about to connect your phone to a computer.As such,you must enable USB Debugging in your device.
You can do this by going into your phone Settings>Developer>tick/check the box beside USB Debugging.
Then go into Security>and tick/check the box beside Unknown Sources and finally go back also in Settings>Xperia>Connectivity there will be two Instructions.
One to connect with PC Companion which will have a box beside it.We don't need that but the other without a box.Just press on it a prompt will appear.There will be 2 options.One says MTP,we don't need this too the other we definitely need MSC.Press on MSC.
The tiny l.e.d light will come on.Done.Now your phone is prepped up to connect to the pc.
Switch off your phone.Press the back button,connect one end of the USB cable to your phone still pressing the back button and the other to your computer.
Do not take your fingers off that back button.The l.e.d.light near the volume button will turn green.Now click on the lightning icon again.
The next page with the firmware will appear again.Where's your finger,good,keep on pressing the back button.
Go through the boxes on your extreme right to see none of the boxes are ticked/checked.Go to the bottom now tick/check the box beside No verification.And press OK.
Another page will come on,and some writtings will start appearing on its on.You can now release your fingers from pressing the back button.
And you will see the words at the bottom of the page flashing finished.And then some more.So read and look for the word.Unplug your device.You have done flashing.
Some might think that this is a total waste of time.No one in their correct mind need to do this lenghtly whatever.But to be honest,every hiccup mentioned above occurred to me.
My grasp of understanding computer jargon and navigating on a computer was zilch.And I had a hard time understanding.
Not that I've become and expert,no.
Very very far from it.But I've had this xperia arc since early 2012 and only managed to Root and Unlocked the bootloader recently.
I am always reading and copying how tos and still failed applying a custom Rom.Go figure.
This might help one person or two who knows.So long as it helps.
Whatever I have written above are my experiences.Thank you all at xda for giving me this push to pursue learning computers and also of my device this very late in my life.
Note:Moderators kindly do not close this thread.
Guys,please if this thread stays on,kindly,if you don't mind,just add.I will be adding more in the future.TQ.
Sent from my LT15i using xda app-developers app

Dude my eyes are bleeding, ever heard of a paragraph?
Sent from my GT-I9300 using xda premium

how did you manage to type that all up on your phone?

wow I know you are trying help new people but this so great text is very confusing ...

Sorry,didn't know it was this lenghtly.lol
As for scarrasc,okay done.
Sent from my LT15i using xda app-developers app

As per request.Paragraphed.
Sent from my LT15i using xda app-developers app

Thx bro
Sent from my GT-I9300 using xda premium

Options for registering a UK Nook Simple Touch.

Hello.
I have a second hand nook ST I bought as a spare. Currently registered to the old owner.
I have a UK and a US B&N account but the UK servers are no longer available since they pulled out of the market.
Am I right is thinking I can just flash the UK nook to US firmware and register the device on my US account? (I already have a nook running fine on a US account)
I have a image for the SD card to flash the rom but I cannot erase and deregister the UK nook using the standard menus as it requires server access. Best way to do this? Factory reset?
Any input will be much appreciated.
thanks

I would try a factory reset as that generally forces re-registration. You could then register it to your US account. At least that is my theory.

the_alternate said:
Hello.
I have a second hand nook ST I bought as a spare. Currently registered to the old owner.
I have a UK and a US B&N account but the UK servers are no longer available since they pulled out of the market.
Am I right is thinking I can just flash the UK nook to US firmware and register the device on my US account? (I already have a nook running fine on a US account)
I have a image for the SD card to flash the rom but I cannot erase and deregister the UK nook using the standard menus as it requires server access. Best way to do this? Factory reset?
Any input will be much appreciated.
thanks
Click to expand...
Click to collapse
You may need to use a VPN? Not sure if the U.S. servers will allow registration from outside the U.S.

nmyshkin said:
You may need to use a VPN? Not sure if the U.S. servers will allow registration from outside the U.S.
Click to expand...
Click to collapse
No they don't mind where you are. I have another Nook registered on a US account. I think it needs to be the right firmware though or it will just automatically look for the old UK servers that are not there any more.
David0226 said:
I would try a factory reset as that generally forces re-registration. You could then register it to your US account. At least that is my theory.
Click to expand...
Click to collapse
What is the best way to do a factory reset? I found this on google, any use?
After looking around and trying a few things I was finally able to find a process that works. The first thing is to wipe the data directory by getting it to reset it. To do this on the Nook Simple Touch you have to do 8 uninterrupted starts. So first, hold down the power button (the one on the back) and turn it off. Then hold the power button on the back for a second again to begin to power up the Nook, after waiting a second or two hold both the power and home buttons simultaneously for 5 seconds or so until the screen flashes and it begins to start up again. I found I had to wait a few seconds after the screen turned back on after each flash before holding the buttons again in order for it to reset again. Keep reseting it like that until a restoring screen comes up and it wipes the data drive.
Click to expand...
Click to collapse
thanks

the_alternate said:
What is the best way to do a factory reset? I found this on google, any use?
Click to expand...
Click to collapse
That is the generally accepted (if tedious) method to invoke a reset. I've done it myself in the distant past. I'm wondering what the difference is between a "factory reset", and a return to "factory settings" such as available via NookManager. That path is certainly easier if the net result is the same.
Edit: also, here is a potential alternate method:
-Turn off your Nook Simple Touch completely.
-Turn it on again by holding down power, and then, as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
- Click the home key twice, and you should be on your way.

Thanks, I might give it a go later.
Anyone know, if I end up not being able to register the device, if I can just go ahead and root it? I assume you don't need to be registered to root?
thx

the_alternate said:
Thanks, I might give it a go later.
Anyone know, if I end up not being able to register the device, if I can just go ahead and root it? I assume you don't need to be registered to root?
thx
Click to expand...
Click to collapse
You can skip OOBE (instructions here on XDA somewhere and probably elsewhere) but there are reports that battery life is seriously impacted. No one has substantiated this AFAIK, either with direct measurements or an explanation as to what is going on. However, quite a number of libraries and universities which check out Nooks as readers often suggest this route after doing a factory reset, so it's anyone's guess I suppose.

Ok, update for anyone else stuck with a UK simple touch.
Used this method suggested above (thanks) to factory reset.
-Turn off your Nook Simple Touch completely.
-Turn it on again by holding down power, and then, as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
- Click the home key twice, and you should be on your way.
Click to expand...
Click to collapse
Used this guide to flash US firmware.
https://sites.google.com/site/xcdguides/nook/nookregion
Registered with my US account straight away. I can see the US store and everything (although I am not sure if you can buy directly, I side load everything anyway).
Thx to everyone who helped,

Confirmed.
Used this method after a friend ended up with a migrated online account (Sainsburrys/Kobo) but a reset Nook (incorrect email when registered, don't ask!) After using this I have it coming up with a registration page for the USA site and I'm now looking to ether side load the books or look at possibly rooting the Nook and looking to install the Sainsburrys/Kobo App if such a thing exists.

Great. Having found an old UK NSTG, this has helped onto the first step towards rooting, installing CWM and finally switching to 1337 ROM.
Results so far: US firmware flashed, Nook registered with US B&N account (I completely forgot I had one, but it still works). Off we go...

critialmass said:
Great. Having found an old UK NSTG, this has helped onto the first step towards rooting, installing CWM and finally switching to 1337 ROM.
Results so far: US firmware flashed, Nook registered with US B&N account (I completely forgot I had one, but it still works). Off we go...
Click to expand...
Click to collapse
Critialmass, can you please provide a link to the ROM you will be installing.
I've recently acquired a NSTG and have been searching for GlowNooter but, perhaps due to it's age, any links I have found are broken and/or the file is unavailable.
Any help you can provide would be most appreciated.

StormStealer said:
Critialmass, can you please provide a link to the ROM you will be installing.
I've recently acquired a NSTG and have been searching for GlowNooter but, perhaps due to it's age, any links I have found are broken and/or the file is unavailable.
Any help you can provide would be most appreciated.
Click to expand...
Click to collapse
Hello StormStealer, it's the one from this thread:
https://forum.xda-developers.com/devdb/project/?id=6542#downloads
Install instructions are in the "Discussion" section - look for it in the black bar above the downloads.
I'd almost recommend another one a little stronger - it runs on my other Nook (an NST) and seems a little more stable, the 1337-ROM crashes/reboots sometimes, and mostly unexpectedly. So take a look at this one:
https://forum.xda-developers.com/showthread.php?t=2651053

Thanks
critialmass said:
Hello StormStealer, it's the one from this thread:
https://forum.xda-developers.com/devdb/project/?id=6542#downloads
Install instructions are in the "Discussion" section - look for it in the black bar above the downloads.
I'd almost recommend another one a little stronger - it runs on my other Nook (an NST) and seems a little more stable, the 1337-ROM crashes/reboots sometimes, and mostly unexpectedly. So take a look at this one:
https://forum.xda-developers.com/showthread.php?t=2651053
Click to expand...
Click to collapse
Thank you,
I've been doing a bit of searching elsewhere and you're not the first to say the 1337 ROM is a bit buggy.
A few places have said that most custom ROMs are slower (less responsive) than the stock ROM and that they play havoc with the battery life.
I'll try both ROMs out and see for myself.

I used the method described on this page which worked well for the UK Nook I got on eBay to replace my broken one -> http://heeed.net/resetting-a-nook-simple-touch/
Then I installed NookManager and all is well

It seems you can skip the device registration altogether using this simple method by XDA user mastermind4:
mastermind4 said:
At the "Hi, welcome to your NOOK GlowLight™" screen, hold down the home button and swipe your finger along the top of the screen from left-to-right. A "Factory" box will appear in the upper-left. Press it.
At the factory screen, hold down the home button and tap the lower-right corner of the screen. A "Skip Oobe" box will appear. Press it.
Click to expand...
Click to collapse
The original thread is called "Nook GlowLight (NGL) bypass Oobe"

ivanko021 said:
It seems you can skip the device registration altogether using this simple method by XDA user mastermind4:
The original thread is called "Nook GlowLight (NGL) bypass Oobe"
Click to expand...
Click to collapse
In the distant past, skipping Oobe on the NST was reported to result in high battery drain. I don't know if that was ever confirmed or if it might also apply to the NSTG.

Nook Simple Touch Network Problem - a success story that raises more questions

First of all, thanks to nmyshkin and all the other folks who have put in the time and effort both to develop tools and solutions for the NST and to document the process to share with others. I wanted to document my own recent experience in case it’s of any help to anyone with similar issues.
A little background: I've been using a NST since 2011, which my (US-based) parents bought for me at the time. I've usually kept wifi turned off, except to occasionally connect in order to sync the clock, and I've sideloaded books from my Mac using Adobe Digital Editions and Calibre.
I'd originally written here that I'd never rooted the device; however, years ago I did remove the two default User Guide books from the library. Unless there's a way to do this without root, or unless I just hid the books on a shelf and then forgot about them, then I must have rooted it at the time, at least temporarily.
In 2013, I cracked the device's screen, so I picked up a used on on eBay and swapped the guts from my old one to the chassis of the new one. At least I think that's what I did...it was some time ago, and I didn't document the process.
At any rate, on to the present.
In the evening on 2022-04-26, I took out my NST to read a book, and I was greeted by the “new device” sequence of prompts (as if my device had never been used and needed to be set up for the first time). I believe that the first page I was shown was language selection, but I never saw this page again in this entire process, so I cannot be sure. I stepped through the menus (accepting agreement, choosing time zone, connecting to wifi), but after connecting to wifi, I got a “Network Error” and could not proceed.
Taking to the internet, I found out that this error is usually related to B&N servers no longer being online, and that I should try to bypass the registration entirely. The directions given for this involved factory resetting to get to the Welcome page, holding the top right page turn button and swiping the top of the screen left to right, tapping the Factory button that appears, holding the top right page turn button and tapping the lower right corner of the screen, and finally tapping the "Skip Oobe" button that appears. I found these directions in the following sources, among many others:
https://www.reddit.com/r/nook/comments/ex61b3
I should note that at no point in this entire process was I ever able to get the hidden Factory button to pop up, despite finding these directions all over the internet. I attempted to factory reset several times (reboot and immediately press the two lower page turn buttons as soon as the screen flashes), attempted to factory re-image using NookManager (https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/), and while these resets were successful, I never was able to access the hidden Factory menu at the welcome screen.
I also at this time downloaded and manually installed the Nook 1.2.2 update from B&N, in case I had not done so before (https://help.barnesandnoble.com/app/answers/detail/a_id/4212/~/having-trouble-connecting-to-your-nook?#ManualDL). To make the update happen automatically, I copied the file to the Nook’s internal storage from a computer, put the Nook to sleep, and waited a minute or two until the Nook found the file and started the update. B&N says that this update is necessary to allow connection to their servers, so it seemed like a logical thing to do; however, at this point, this update neither gave me access to the Factory menu nor allowed me to register my device on the B&N servers.
Doing some more reading, I found that UK devices were cut off from their servers a few years ago, and some industrious people came up with a ways to use these devices anyway, the most common being to replace the Nook’s firmware with the US firmware using the “Nook Region Changer” SD card, which is based on clockworkmod (CWM).
https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/
https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion
https://forum.xda-developers.com/t/nst-g-update-fw-1-2-2-uk-unofficial.4360889/
I decided to give this a try, in case my device happened to be a UK or other international device (although I was fairly certain it was US based, because I am located in the US and the device listed time zones from the US…though I suppose it could have been Canada?). The directions I followed were a mix of the second and third links above:
I downloaded the nook_region_changer file (from the first of the three links above) and used Etcher to make a bootable microSD
I followed steps 3-10 in the third link from nmyshkin: power down, boot into CWM, backup, wipe dalvik cache, wipe data/factory reset
I then switched to steps 7-9 in the second link (archive.org): install rom_backup.zip, install nook_1_2_update_US_CWM.zip, reboot twice
Following these steps, I was now getting a slightly different welcome screen when I booted into the Nook firmware, which matches the one in the YouTube video cited earlier in this post, except without the Back button. Unfortunately, I did not take a picture of what my screen looked like before this flash (though I’ve done a little digging into this, which is toward the bottom of this post). Nonetheless, I was still unable to access the hidden Factory menu, and I was also unable to register the device with B&N.
I then decided to apply the B&N 1.2.2 update once again, copying the file to the Nook’s internal storage and putting the Nook to sleep so that it could update. Following this update, the Welcome screen remained the same, and the hidden Factory menu was once again inaccessible. However, this time, my device was able to connect to the B&N servers, and I was able to finish setup.
Things now seem to be in working order.
—————
Some thoughts from afterward:
I’m not sure why my device decided to re-initialize in the first place, as I’ve been using it for the past decade or so, I always keep my Nook’s wifi turned off, and I had sideloaded a book to the device just a few days earlier, opened the book at that time, and everything had been working normally.
I wonder if the Factory menu is only available on international Nook devices. I have no idea why I was never able to access this menu throughout the process, though I did find one other user who had the same problem a couple of years ago (this was the post that pointed me at the nmyshkin custom UK firmware post that became a part of my solution in the end): https://forum.xda-developers.com/t/nook-simple-touch-network-problem.4130461/
This user was also based in the US, so it’s possible that my hypothesis about the Factory menu being inaccessible from US firmware is correct; however, I would have to install some other firmware to check, and as my device is finally working, I don’t want to risk it.
I believe that what clued me in to needing to update to the latest B&N firmware (despite this not solving things once before) was this post by nmyshkin in another thread: https://forum.xda-developers.com/t/...mple-touch-update-1-2-2.3971367/post-80341393
On that note, I don’t know why my device was unable to register after the first time I applied the B&N firmware update.
It’s possible that my device wasn’t a US-firmware device. As I mentioned briefly at the beginning, my original Nook was a gift from my parents in 2011 (and thus was probably a US device), but its screen became damaged and I purchased a second one from eBay. I don’t recall what was wrong with the second one (maybe a bad battery, maybe something else?), but I do remember taking both devices apart and mixing the two of them as I put them back together, presumably to use the good screen from one and…something…from the other. So there’s a chance that the brains of this device are from the second Nook, though it seems unlikely, as my B&N account (through a computer web browser) showed the serial number of this device as having been registered in 2011, which is when I got the first Nook (which was presumably a US device). It also seems likely that I'd have wanted to keep the working internals from the old device and just use the screen from the new one.
A second thought on the unable-to-register-the-first-time-I-updated-my-Nook problem. As I mentioned above, I was getting a slightly different Welcome screen on my device prior to flashing a different firmware with Nook Region Changer. I did not take any pictures at the time, but I believe the old screen looked like this (https://u-mercari-images.mercdn.net/photos/m86876116644_1.jpg?1598739388), and the new one looked like this (https://shopgoodwillimages.azureedge.net/production/48/8-9-2021/35449379212449Nele.JPG). These images are attached to this post, with “Welcome to your all-new NOOK” for the old Welcome screen and “Welcome to your NOOK Simple Touch” for the new. What is also interesting to me is that the other person I found online who was unable to access the hidden Factory menu on the welcome screen (see link above) mentioned the old text, “Welcome to your all-new NOOK,” in their description as well.
Perhaps this is a much older firmware? I wasn’t able to check, because I couldn’t get into a working Nook to look at its version. I remember seeing the announcement a few years back that 1.2.2 would be necessary and that I would need to update if I wanted the device to continue working. I’m not sure whether or not I ever did that, but it seems likely considering I remember the post. One theory is that perhaps if a NST is running a very old firmware, it is unable to directly update to 1.2.2 and requires intermediate updates, which could be why flashing the firmware using Nook Region Changer allowed the later update to 1.2.2 to happen successfully. This would also explain why, after the first time I installed the 1.2.2 update in this most recent series of events (prior to the Nook Region Changer flash), I was still unable to register (and I still had the old Welcome screen).

the.sting said:
I wonder if the Factory menu is only available on international Nook devices.
Click to expand...
Click to collapse
No, it should be available from all devices in general working order. Clearly something else was going on with yours.
the.sting said:
This user was also based in the US, so it’s possible that my hypothesis about the Factory menu being inaccessible from US firmware is correct; however, I would have to install some other firmware to check, and as my device is finally working, I don’t want to risk it.
Click to expand...
Click to collapse
It ain't broke (now). So leave it be. But...I would definitely use NookManager to make a backup. You don't have to root in order to do that (I think).
the.sting said:
It’s possible that my device wasn’t a US-firmware device. As I mentioned briefly at the beginning, my original Nook was a gift from my parents in 2011 (and thus was probably a US device).
Click to expand...
Click to collapse
The differences are subtle, but since you've flashed the UK version now, the point is moot. The opening screen on the US version is the Welcome screen. The opening screen on the UK version is the Language picker, followed by the Welcome screen. Alas, I didn't pay that much attention to any differences in the Welcome screens between the two versions so your attached images don't ring any bells.
In the UK version the dictionary is the Oxford English and the Settings app is a little more expansive, including a dictionary management section (which does not work). Also, the locale or language picker is not fixed on "US English".
the.sting said:
One theory is that perhaps if a NST is running a very old firmware, it is unable to directly update to 1.2.2 and requires intermediate updates, which could be why flashing the firmware using Nook Region Changer allowed the later update to 1.2.2 to happen successfully. This would also explain why, after the first time I installed the 1.2.2 update in this most recent series of events (prior to the Nook Region Changer flash), I was still unable to register (and I still had the old Welcome screen).
Click to expand...
Click to collapse
I have never heard anything like this, but as they say, anything is possible (though I doubt this one).
Wow. You've been on quite a ride! I'm glad if anything I put together was helpful. Again, I strongly suggest a backup. It's possible there is a hardware fault in the device that caused it to run a factory re-image. If that happens again, a backup to restore would be handy.

Thanks, nmyshkin! Your posts were incredibly helpful in navigating my way through this.
It sounds like I must have had a US version previously. I have a fuzzy memory that I may have had the language picker the first time I found my Nook in the initialization sequence, but at that point I was just trying to get through it to use the device again, so I wasn't paying that much attention. But every subsequent time that I factory reset it, it went straight to the welcome screen.
I'm actually currently running the US firmware; I flashed the US image that comes with the Nook Region Changer package rather than the custom UK one that you put together. The custom UK one was the next thing I was going to try, but the device allowed me to register after the flash and subsequent update, so I never got there.
I did run a backup using the clockworkmod tools in Nook Region Changer prior to making that flash, which resulted in several files being generated on the SD card (see attached image -- the times are wrong, but the files with "Today" timestamps are presumably the ones generated by the backup). I'll make sure to perform another backup now that things are working. Would you suggest I use NookManager rather than clockworkmod?
I still have no idea why I was never able to get the Factory button to appear, but it sounds like the "Skip Oobe" workaround has its downsides anyway, so I'll stick with what's working now.
Thanks again!

the.sting said:
I did run a backup using the clockworkmod tools in Nook Region Changer prior to making that flash, which resulted in several files being generated on the SD card (see attached image -- the times are wrong, but the files with "Today" timestamps are presumably the ones generated by the backup). I'll make sure to perform another backup now that things are working. Would you suggest I use NookManager rather than clockworkmod?
Click to expand...
Click to collapse
It has been said, but I cannot verify, that the CWM backups are not "complete". They are certainly better than nothing. The NookManager backup is a single file "image". That's the not-too-impressive extent of my knowledge on that score. I have used CWM backups to restore other devices before, so I might just be all wet on this topic.
the.sting said:
I still have no idea why I was never able to get the Factory button to appear, but it sounds like the "Skip Oobe" workaround has its downsides anyway, so I'll stick with what's working now.
Click to expand...
Click to collapse
I actually had a thought about that after my post. I've never used the hardware buttons for page turns. Never saw the sense. I have them assigned to various other functions but don't use them often. So I could be caught off-guard if, for example, one of them just decided not to work any more.....like the upper right one? Just a thought, but it's probably too easy!

Good to know, I'll look into making a NookManager backup.
nmyshkin said:
I actually had a thought about that after my post. I've never used the hardware buttons for page turns. Never saw the sense. I have them assigned to various other functions but don't use them often. So I could be caught off-guard if, for example, one of them just decided not to work any more.....like the upper right one? Just a thought, but it's probably too easy!
Click to expand...
Click to collapse
I hadn't considered this, as I also barely use the hardware buttons on the sides. But you seem to be spot on...I just checked, and the top right button is the only one of the four that isn't working for page turns either! Sometimes the simplest explanations turn out to be right.
Thanks again!

You can use UsbMode.apk (in the sig) to check the action of physical buttons (or USB or Bluetooth).
I don't use WiFi, I use a little utility to sync the time whenever I sync content over USB.
Such a utility is dependant on the exact syntax of the date command and the ability to directly get a # prompt without using "su".

nmyshkin said:
It has been said, but I cannot verify, that the CWM backups are not "complete". They are certainly better than nothing. The NookManager backup is a single file "image". That's the not-too-impressive extent of my knowledge on that score. I have used CWM backups to restore other devices before, so I might just be all wet on this topic.
Click to expand...
Click to collapse
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.

the.sting said:
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.
Click to expand...
Click to collapse
I should have seen that coming
I've been here before with another member, different button, same general issue. That time it was NookManager-1, nmyshkin-0.
The device has 6 hardware buttons. Whether it will recognize input from the remaining two with the instruction set that is loaded at boot remains to be seen. I've got a busy day, but it's the kind of busy that will allow my mind to wander. I'll see what turns up. Try not to have a device meltdown today.

the.sting said:
In light of the fact that my top right page turn button doesn't work, do you have any thoughts on the NookManager backup process? Unfortunately, "Format remaining space on SD card" (which seems to be a precursor to making a backup) is selected by that top right button.
Click to expand...
Click to collapse
OK, this time around the little grey cells have triumphed!
Do you know about ADB? If not, this will not do you much good, although it's fairly easy to install a minimal ADB package on a Windows machine (if you have one).
Anyway.....
It's possible to synthesize a button press using ADB, and NookManager gives you the option to start up ADB before you do much of anything else. Except there is a catch. The button that starts WiFi so you can connect with ADB is---you guessed it---also your dead button.
Not to worry. The left buttons are unused on that menu screen and I can easily alter that menu for you. All you would need to do is replace the file on the card with the altered one.
Then once WiFi is started, you have the option to start ADB (a left button) and are given the IP address to connect to.
The ADB command for sending a press of your non-working button is:
Code:
adb shell sendevent /dev/input/event0 1 407 1
(those are zeroes--both of them)
This would enable you to access the entire NookManager menu system (if the need ever arose), including the backup and restore functions. You just need to send that code each time you should press that dead button.
But you'd need ADB to do it.
Let me know if you want to pursue it. If this seems like too much for too little, keep your CWM backup safe somewhere. As I said before, I've used them to restore other devices.

Wow, thank you so much for putting the thought into this! I haven't worked with ADB, though it's something I would definitely be interested in investigating (I like to tinker). That said, I'm stretched a little thin to really dive in at the moment...getting married soon and otherwise a bit swamped with work.
I'll definitely save the CWM backup for now. Can I ping you here again if I'm interested in working on this later?
Thanks again!

the.sting said:
I'll definitely save the CWM backup for now. Can I ping you here again if I'm interested in working on this later?
Thanks again!
Click to expand...
Click to collapse
Absolutely. Congratulations on your approaching wedding!