Sorry, I'm new and don't know where else to post this. Searched and searched these forums ad nauseam, even threw wider net and Googled the internet to no avail.
I've made a mistake and screwed up my Kindle Fire by following the instructions to install BurritoBoot3 and the FireFireFire bootloader. It seems to have successfully rooted my KF; but, as warned, it can no longer do Amazon things like watch Amazon videoes! Says "Your device is no longer correctly configured to play Amazon videos. ..." Of course, it's because I rooted it.
Now I want to go back to the way it was so I can watch videos again. Also, I installed the FireFireFire bootloader; but, I don't know what it's supposed to do and I don't think it works. Now when I turn on the KF it starts with this yellow triangle thing that doesn't do anything (I tried all the press until button goes orange and all that). I want to get rid of this, it's annoying.
It's my mistake. I should have done more homework first. I should never have installed or done anything to my Kindle without assuring myself there is procedure available and clearly explained on how to "undo" whatever I did.
For a "root" mechanism, I failed to check if it could also toggle back to "unrooted". If BurritoBoot3 is supposed to have that capability, I never found it documented and I don't know how to BurritoBoot3 is supposed to unroot the device.
Background:
This is a Kindle Fire updated to 6_2_2.
I installed ADW Launcher (side-loaded) so I could put my grandson's picture as wallpaper. Discovered that changing the wallpaper (regardless which launcher) won't "stick": every time the device starts up or comes unlocked the wallpaper switches back to one of the rotating Amazon Kindle wallpapers. This is a known problem and the fix requires temporarily rooting the device so the wallpaper file can be changed to readonly preventing the unlock code from changing it.
So I followed the instructions to install BurritoBoot3 and also let it install something called FireFireFire bootloader (it sounded like I was supposed to do that).
So how do I undo what I've done? I don't have any way to know what all the installation of BurritoBoot3 does, but it has to be more than rooting the Kindle. I managed to unroot it by installing SuperOneClick 2.3.3 from ShortFuse.
But unrooted, my Kindle still can't play Amazon Videos! There has to be more than just unrooting it.
I've rooted my Droid X without any problem at all. Had to use a couple different apps, one when it was new and a different one after Android 2.3.3 update. Each time the apps provided a simple means of toggling root on/off. I just assumed this would, too.
The last thing I want to do is restore the device back to factory condition. I've spent many weeks installing apps (many side-loaded), music, pictures, books, changing settings, etc.
Can anyone help? I will be most grateful if someone could point me at a thread or forum or web site where I could get more ideas on how to fix this mess.
johnk300 said:
Sorry, I'm new and don't know where else to post this. Searched and searched these forums ad nauseam, even threw wider net and Googled the internet to no avail.
I've made a mistake and screwed up my Kindle Fire by following the instructions to install BurritoBoot3 and the FireFireFire bootloader. It seems to have successfully rooted my KF; but, as warned, it can no longer do Amazon things like watch Amazon videoes! Says "Your device is no longer correctly configured to play Amazon videos. ..." Of course, it's because I rooted it.
Now I want to go back to the way it was so I can watch videos again. Also, I installed the FireFireFire bootloader; but, I don't know what it's supposed to do and I don't think it works. Now when I turn on the KF it starts with this yellow triangle thing that doesn't do anything (I tried all the press until button goes orange and all that). I want to get rid of this, it's annoying.
It's my mistake. I should have done more homework first. I should never have installed or done anything to my Kindle without assuring myself there is procedure available and clearly explained on how to "undo" whatever I did.
For a "root" mechanism, I failed to check if it could also toggle back to "unrooted". If BurritoBoot3 is supposed to have that capability, I never found it documented and I don't know how to BurritoBoot3 is supposed to unroot the device.
Background:
This is a Kindle Fire updated to 6_2_2.
I installed ADW Launcher (side-loaded) so I could put my grandson's picture as wallpaper. Discovered that changing the wallpaper (regardless which launcher) won't "stick": every time the device starts up or comes unlocked the wallpaper switches back to one of the rotating Amazon Kindle wallpapers. This is a known problem and the fix requires temporarily rooting the device so the wallpaper file can be changed to readonly preventing the unlock code from changing it.
So I followed the instructions to install BurritoBoot3 and also let it install something called FireFireFire bootloader (it sounded like I was supposed to do that).
So how do I undo what I've done? I don't have any way to know what all the installation of BurritoBoot3 does, but it has to be more than rooting the Kindle. I managed to unroot it by installing SuperOneClick 2.3.3 from ShortFuse.
But unrooted, my Kindle still can't play Amazon Videos! There has to be more than just unrooting it.
I've rooted my Droid X without any problem at all. Had to use a couple different apps, one when it was new and a different one after Android 2.3.3 update. Each time the apps provided a simple means of toggling root on/off. I just assumed this would, too.
The last thing I want to do is restore the device back to factory condition. I've spent many weeks installing apps (many side-loaded), music, pictures, books, changing settings, etc.
Can anyone help? I will be most grateful if someone could point me at a thread or forum or web site where I could get more ideas on how to fix this mess.
Click to expand...
Click to collapse
If you want to watch videos....download otarootkeeper from the android market and temp unroot it ..reboot after and you can watch video again
Also clear the cache/data of the amazon video app
Sent from my Transformer Prime TF201 using XDA Premium HD app
Looking for a fix, not a workaround
Just to clarify my post ...
The problem is not that I can't watch videos, it's that installing BurrittoBoot3 and FireFireFire has damaged my KindleFire and I want to fix whatever it did. I'm looking for instructions on how to undo whatever installing them did. I want to get rid of the annoying yellow triangle when I turn it on. I've broken the way it is designed to play videos and who knows what else doesn't work now and I want to fix it, not workaround it by finding another way do what's broken.
Clearing Amazon Video app cache/data fixes video playing
NORCALkID said:
"Also clear the cache/data of the amazon video app"
Click to expand...
Click to collapse
Thanks, NORCALkID, again! Clearing cache/data fixes the video play problem.
For those readers (like me) who need help with that, here's how:
From HOME screen, tap little "Settings" wheel icon in upper right corner.
Tap Plus icon for "More ..."
Tap Applications, pull down filter by and select "All Applications"
Scroll down to and tap "Amazon Video"
Tap "Clear Data", tap OK to the Delete warning message.
If Clear Cache Button is still live (not grayed out), tap it and OK to warning, too.
Then, Back, Back, Back, etc. to Home screen and tap Video at the top and try playing a video. Worked for me.
I just have quick question, i just got my nook yesterday at got it updated to new firmware, i see the several rooting options for nook and im sure i can install any of them without probs what i was curious bout is stability of the different rooting problems with new 1.1.2 are they all pretty compatible to new firmware or is there select few, thanks for any help.
they are compatible. 1.1.2 has improvements on wifi issues, not much changes on the other things.
ok i got it rooted i cant seem to do anything on it the market says "a server error has occurred", opera mini wont even boot at all the scree just flashes for second and the other browser loads and shows internet but when you touch anywere to type it crashes back to main menu. Im tryin to figure what went wrong i followed the directions on TouchNooter 2.1.31.
also youtube wont reboot up screen just flashes. When i first did install it was working ok i got to my gmail account got it set up etc. is touchnooter just outdated and use a different method to root now instead?
ok i got it unrooted and back to original 1.1.2 format. Do i follow the instructions on that still or is there new way to root the nook? Im not best in rooting files but i can follow information posted. Can someone please direct me to most reliable working rooting method for nook 1.1.2? Also i was curious i never used android before all the pdf options you can get from market, is it even worth rooting nook if thats prime reason, most pdfs i have has alot of image heavy files or am i just better off leaving it unroot use adobe to rebuild them instead?
opera mini wont work, i couldnt make it work tho. try opera mobile. to solve market issue, you have to wait 1+ day.
search wont work even after then.
try to check gmails after root, if it works then its ok. dont wory about youtube, since you wont watch any video there.
you can use multitouch + norefresh hack + ezpdf reader after root, that is perfect for pdfs that contains images and such.
check it out: watch?v=6pBPsyno5PY
ok i used minimaltouch this time got it rooted and working having some bugs not sure how to fix it, i know reg msrket you cant search in it so i use the search market app when i try to click on a app to download in search app it flashes attempts to go to next page were download is but fails and goes back to list of search. also the my apps button does same thing it goes back to previous screen in act of will. I also like to access the regular home to get to my reg nook books in my library but when i do it goes on its own accord back to android home, could osmeone help me with those minor bugs?
heres more detailed list on whats going on hopefully somoene will have idea whats wrong so i can fix it than reroot for third time. when you hit the N button and select home it goes to nook home for split second then instantly goes back to android home, when you hit library it goes to library but constantly refreshes non stop you cant select any menus or no ebooks show up in list so you have to rego back to android home. i installed search market for while i was able to download off android market, but now after i do search in searchmarket and select "file1" it does same as home button it goes to next page with download link for split second then it instantly goes back to list of search results. and in regular market when you hit "my apps" it does same thing again it goes to your list of downloaded files for split second and then goes right back to market main menu i cant go anywere no matter how many times i click it it keeps going back to previous menu non stop. gmail still works and syncs and i can access my pdf program i installed but i cant read any of my nook books cant do single thing on market cant go home or to library i also installed nook mobile it works just fine but everything else listed wont work, what could cause this glitch / bug, i followed directions to minimaltouch to letter and i didnt have single hitch during install all way through but now its like this. Is there anyway i can fix this or just keep rerooting 100 times till it finally works?
nevermind
I'm not sure of the reason, but the touch screen of my Yotaphone 2's e-ink stopped working. The e-ink screen itself visualises what it is supposed to, but it doesn't react to touches. The LED screen is OK. I thought this may be a software problem, so I did a factory reset that would probably eliminate it. It didn't, and the problem that I have now is that I can't even use the LED screen, because at startup it runs the tutorial, and the tutorial requires you to interact with the e-ink screen, which, in my case, is impossible, because it is not responsive to touches. So I never get to the "desktop" and the app launcher - the tutorial has to be completed. If I slide from the top rim I can get into Settings. I've tried stopping the process from the list of active apps, but it doesn't work. Anyone has an idea what to do?
I have the same issue yesterday and couldn't find a way to bypass the tutorial. As you I tried to kill the process via adb and didn't work. I also thought that there might be a place in the phone where the app checks to see if it has been run as it only runs the first time.
Two things to try:
1. Do you have the folder /data/data/com.yotadevices.yotaphone2.tutorial ? I see this in my phone so maybe it is created as a check. The folder is empty, you can try to create it as root to see if this bypasses?
2. Send the events via adb sendevent to the /dev/input/event4 or via input tap. You will need to calculate the coordinates somehow.
Good luck!
jaboto said:
I have the same issue yesterday and couldn't find a way to bypass the tutorial. As you I tried to kill the process via adb and didn't work. I also thought that there might be a place in the phone where the app checks to see if it has been run as it only runs the first time.
Two things to try:
1. Do you have the folder /data/data/com.yotadevices.yotaphone2.tutorial ? I see this in my phone so maybe it is created as a check. The folder is empty, you can try to create it as root to see if this bypasses?
2. Send the events via adb sendevent to the /dev/input/event4 or via input tap. You will need to calculate the coordinates somehow.
Good luck!
Click to expand...
Click to collapse
There was nothing I could do about it, but I found a workaround which would at least let me use the phone somehow. From the bottom side you can launch Google search and search for a popular android app, which will take you to the Play store. From then I installed Sidebar Lite by Mohammad Adib (probably other sidebar launchers would also work) and then the sidebar launcher works on top of the Tutorial and you can dock several apps in there.
A strange problem of my (rooted) NST: open a book, close it, insteading of going to the first place in the Library ( sorted from most recent ), it disappears completely. The book is still there, as the total number of books remains the same, it is still searchable.
Adding a new book doesn't making it appear in the library either, though searchable too. So it seems the adding book module is wrong.
Possible cause: unplugged the battery while NST is on ( it was off, but during middle of opening the back, somehow the power button was touched, too lazy to turn it off again )
Tried to restore from backup using NM, doesn't solve the issue?
Any suggestions of how to fix it? Thx in advance for any help.
smjohn1 said:
A strange problem of my (rooted) NST: open a book, close it, insteading of going to the first place in the Library ( sorted from most recent ), it disappears completely. The book is still there, as the total number of books remains the same, it is still searchable.
Adding a new book doesn't making it appear in the library either, though searchable too. So it seems the adding book module is wrong.
Possible cause: unplugged the battery while NST is on ( it was off, but during middle of opening the back, somehow the power button was touched, too lazy to turn it off again )
Tried to restore from backup using NM, doesn't solve the issue?
Any suggestions of how to fix it? Thx in advance for any help.
Click to expand...
Click to collapse
Seems a few reboots fixed the problem. Must be temp file system issue. The OS is still robust.
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!