Well, I posted about this in another thread but figured I would post here to get more exposure.
So, here is the issue. I rooted my NT and renamed the LatinIME.apk to LatinIME.apk1 so I can move my swiftkey apk (which I was going to rename LatinIME.apk). Of course, I had a blonde moment and renamed the built in APK before renaming the swiftkey apk and I lost the keyboard. No big deal right? Just reset device. So, I reset by going into settings and doing the reset/deregister device. Got back into the set up....still no keyboard. So I tried a hard key reset (n and power) and still no keyboard.
It appears that, when doing a reset, the device wipes all data but does not actually RESET the OS through any recovery type process.
Question........any ideas? I can't get adb obviously because I have lost debugging.
Curious if there might be anyway to boot the device differently to access shell or something. Hopefully someone has an idea, I have to wait tell monday to replace it if it comes to that
what about installing nook color tools then you can get back to the development menu. enable usb debugging and take care of the rest with adb.
Drewmungus said:
what about installing nook color tools then you can get back to the development menu. enable usb debugging and take care of the rest with adb.
Click to expand...
Click to collapse
As I understand it. Nook color tools is an apk...which I cannot install due to not being able to get past the B&N account login screen. Can't get past that without a keyboard
I'm in a similar boat. Was trying to get the market working following the thread on the other page, and I copied the entire apps folder over my existing one (why I didn't backup the old one!) Now I have no keyboard either, and I'm getting constant force closes!
Maybe someone could post an un-modified system folder?
Try a failed 8 boots, turn on, after black N screen hold power until screen turns off and repeat 8 times.
^. After a certain amount of failed boots the nook will default into a total factory reset. Witnessed it earlier today when after installing Chainfire the NT went into a a boot-loop. Then automatically reset itself.
Worth a shot.
Well, I tried 8 failed boots, and it didn't re-image. I then peeked in the rom/devconf/ folder and there's no "bootcnt" file?
*edit* Got it to work. Took 10 times.
Ok, so I kept trying to boot which resulted in it eventually giving me a screen saying "please reboot your device. If the error continues contact customer support or goto nook.com/tablet/support". The website was no help. Took it to a store, they called customer support and got confused. Customer support told them to replace it. So they did...I didn't even have to give back my charger...so now I have an extra!
Returns
I really hope B&N Customer Support figures out it would be a heck of a lot cheaper to let us run our own image off an SD card, and not have to deal with all the customer support calls and returns.
Unfortunately - they are much more likely to yell Warranty Violation and refuse to do anything...
Would it have been possible to mount the device and access it from Ubuntu and then just renaime the file?
Got mine to re-image. Re-rooted and market installed. I'm happy again!
Sent from my BNTV250 using Tapatalk
Details please. How did you do it?
You power down, then power back on. As soon as the white screen comes up (with the "n" on it) hold down the power button until it powers down again. Do this ten times in a row and it will automatically start the re-image. If at any time the boot animation starts up you have to start over.
Sent from my BNTV250 using Tapatalk
tonyp22 said:
Would it have been possible to mount the device and access it from Ubuntu and then just renaime the file?
Click to expand...
Click to collapse
For the particular issue I was having...no. Since I reset the device I was not able to get past the B&N login screen and therefor had no access to the /system/app folder. Although, it seems that some people are having success with the re-image process. I think mine was trying to re-image but something was corrupt and caused my to have worse issues that resulted in nothing but replacement.
Related
Hey guys. as many of you know i am no stranger to the Android system, although i have been pretty much totally absent from the forums since i got a job with limited privelages on my comp.
Before I explain what happened to me, i should say that i have not made ANY changes to my system for at least 4 months, with the exception of build.prop updates, which i my phone has been running fine on for weeks. i found a setup i liked and ive been running it, along with the same root applications, for quite some time.
With that said, heres my timeline of events:
Normal day, doing what i always do on my phone everyday: phone was plugged in to a wall outlet at my desk. streaming music, browsing web, youtube, etc. nothing out of the ordinary
i first noticed something wierd was up when i went to install an old .apk i had saved on my sd card. i opened it through file manager which, naturally, brought up the stock package installer. i clicked ok to install, and it said "installing"..however it nevver finished. it was stuck on "installing" for several minutes. i tried a couple more times, same thing kept happening. i had no idea what was going on.
i went into settings>applications>manage applications. i scrolled down to package installer and clicked on it, with the intention of clearing cache/data, however the values never loaded, it just kept saying "computing". it was doing that for all other apps i checked as well.
then i opened titanium backup and wiped data for package installer through that. operation was performed successfully.
i went to reboot my phone, and thats the last thing it remembers. now whenever i try to turn my phone on, it gets past the kernel splash screen and its all black from there (i have the "no boot anamiation" command in my build.prop). the only response i get at that point is the led buttons will light up if i tap them. i have to pull the battery to turn the phone off/reboot.
i tried pushing packageinstaller.apk to /system/app using adb but that didnt solved anything. i also tried wiping cache/dalvik and fixing permissions through clockwork. nothing has worked.
i am running Froyo Trigger w/ Bali kernel.
sorry for the long post, but i figured id be as detailed as possible to minimize questions.
any suggestions would be great. i ask that no one please suggest factory reset/reflash/odin. i realize that those options are there, but i consider them last resorts. id rather brainstorm a solution than bail immediately.
thanks ahead.
also i forgot to mention, there was nothing wrong with the .apk i was originally trying to install. i have installed it/uninstalled it many times. i tested other .apk files i had, but package installer still behaved the same way
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Br1cK'd said:
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Click to expand...
Click to collapse
not sure if i should be embarrassed to admit this, but ive never used logcat...ill look into that
Your first step there is to get the android sdk setup on your pc, then once adb is part of your command line the simple command is "adb logcat" without it quotes. That will start the log displaying in the command line window.
There are other options with the logcat command, that output the log to a text document and its more in depth, but I dont remember it off the top of my head. Maybe someone can post it for you.
The only caveat is how far your phone is booting before it hangs, I think logcat will show something, but won't know for sure until you try it.
Sent from my ZenDroid, meditating on the XDA App
http://forum.xda-developers.com/showthread.php?t=1319802
Eugenes Froyo that doesn't brick, followed by an Odin to jfd.
Sent from my SGH-T959V using XDA App
So I was all rooted. I had Go Launcher, Market, and Swiftkey all working awesomely. My NT life was good. Then Swiftkey started throwing up errors. So I went to Any Cut to find a shortcut to Swiftkey's settings. There was like 8 settings under activities but not a specific Swiftkey settings. So I created shortcuts to the 8 settings and thought I would try them all and maybe one was for swiftkey.
When I clicked on the second settings shortcut the NT through up an error that stated there was an authorization error and the tablet would reset. When the tablet restarted it forced a wipe to factory settings. I thought...that sucks...but whatever I'll start over.
When the tablet had finished and restarted It started to go through the setup screens as one might expect. However, Swiftkey is apparently still selected as the keyboard and the NT keeps giving the Swiftkey force close errors. I can't enter in my registration info because I haven't an effin' keyboard. I didn't have usb debugging turned on so I don't think I can use adb to remove swiftkey. Although, I've never really used ADB unless I'm rooting and following very specific instructions from one of these forums.
Is there a way to bypass the initial registration and sign in crud so I can install root explorer and remove Swiftkey?
Sorry for the long story. Hopefully someone will have a suggestion on how to fix this.
Thanks in advance.
tldr- NT hard reset and now stuck without keyboard because Swiftkey was still selected and Swift key won't work during initial registration....argh!
Tip the screen corners starting top left in clockwise motion.
http://nookdevs.com/NookColor_Factory_Mode/Skip_Out_of_Box_Experience
This has worked for people to skip registering their device good luck god bless.
I did test this method when i got t the last prompt to skip Oobe(out of the box experience) I did get a force close error. However I just reopened the menu by hitting the volume up and the lower right portion of the screen. The Oobe button came back up and i clicked it with success, bypassing the registration.
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
demonhater said:
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
Click to expand...
Click to collapse
I think what you did is really smart( never mind the semi brick part) and important. This could help out a lot of people that lose keyboard access or other issues that occur. Using the nook reader with google search was a great way around your problem.
SwiftKey force closes on me randomly and will not stop until I re-run the apk inside /System/App again but after that it works fine for awhile. I wonder if it's just SwiftKey because I haven't tried any other keyboards yet
I've noticed several keyboards don't stick after a reboot. Thickbuttons and Hackers seems to be the only 2 I've tried that do stick.
yaggermr said:
I think what you did is really smart( never mind the semi brick part) and important.
Click to expand...
Click to collapse
The scary part was that the NT forced a random wipe on it's own after a quick error about "authorization."
Sorry didn't know about the authentification error and I was joking about the semi brick part. I just thought your recovery method could help somebody out of semi brick hell.
No need to say sorry. I knew you were joking. And hopefully, it will help someone else.
I rooted my device before going through the setup process on the nook tablet. After completing the root, every time the tablet boots, it brings me right back to the setup process. Is this expected behavior? Every time I go through the process, it gives me an error when logging in with my B&N account. I'm officially perplexed.
I've had my NT for a little while now, but iirc, you are supposed to register first, and then root. I'm assuming you found some way to skip the "OOBE" (Out Of Box Experience) initially then? Because without circumventing that, I believe you are required to fill it out before proceeding with anything. I did circumvent it once, just to see what would happen; I think the only thing it affected was my ability to access the B&N book store (probably B&N Market as well, but who uses that? lol). Since I thought I might still use the book store, I did a factory reset, registered, then rooted and went along about my business. Once you skip the OOBE, I think you may have to reset if you want to fill it out again, but then again I seem to recall maybe seeing a way to access OOBE from some hidden menu (although I can't remember where now, and a quick look in Nook Color Tools didn't seem to turn up anything).
So anyway, getting around to the part of your question about it bringing up the OOBE at every boot, NO, I don't recall that behavior at all from the time I had circumvented it, but then again, now that I think about it, it could just be because I didn't reboot during that time? And I don't think I stayed that way very long before just deciding to reset.
So if it's annoying you that much, I would say to do a factory reset, register, then re-root, etc. Of course if you have a lot of time into setting up your NT to your liking, this may not be acceptable. Another alternative would be to wait until CM7 comes out (should be only a few weeks now, but don't quote me on that, lol) and then wipe and install CM7 at that time.
Edit: right after posting, I found some info here that may be helpful: [Q] Reregistration? BN - not skip
Thanks TRS-80 for the insight, seems like I've hit a wall as a factory reset still leads me to the same error when hit with the set up process. I'll have to bring it in to BN and get a replacement today.
Here are my thoughts on the Nook Tablet and my rooting process. I try to write to be as friendly as possible for the newbies to rooting devices. This is really just a reflection of my experience with the device and my rooting effort thus far .
If money is no issue, by all means go with the 16GB. But if you really want the best bang for the buck, go with the new 8GB version over the 16. The main difference is the RAM but since we are not talking about a true multitasking device, the extra RAM does little. Even if you root and hack and upgrade and tweak the hell out of it, you'll never really do more than one thing at a time on the device itself so 512MB is usually plenty. I have found that the Nook is the perfect companion device (for references and reading) to go with my netbook (which is the pefect portable productivity device) and my rooted android cell (universal connectivity device with tether hack). Those three things working in tandum mean that I can get online anytime, anywhere, and work comfortably. Now, if I can just find an Android phone that has a battery that lasts for more than 4 hours with the wi-fi/tethering/mobile hostpot turned on.
I have successfully used jichauan89's Root for Nook Tablet 8GB (w/ Android Market) root method number 1 (the SD image). Thank you jichauan89! It was easy and worked great the first time. His procedure...
http://forum.xda-developers.com/showthread.php?t=1529553
Here was my specific procedure and thoughts.
Prior to the attempt. Make sure that the device has plenty of battery power or is plugged in the wall adapter. This is a good practice for all rooting/hacking attempts on these types of devices, including cell phones and media players. I backed up the data on my SD card by simply copying all the files to a folder on my netbook's desktop.
Used Sandisk 8GB microSDHC card I had in my old Samsung Captivate. I used the SC card adapter it came with orginally to insert it into the built in SD Card reader in my Windows XP netbook.
Downloaded the SD card image from exactly where jichauan89 described.
Used Win32DiskImage.exe to format and write the image to the SD card. Worked without error. I used the safely remove hardware option in Windows to disconnect the hardware before removing the card from the reader.
Powered off the Nook Tablet 8GB.
Inserted the freshly formatted and imaged SD card into the Nook.
Held the power in until it powered on.
Saw a cardboard box. It reminded me of Amazon's frustration-free packaging.
Waited.
Saw the "Read Forever" Nook logo.
Waited exactly 3 minutes.
Held the power button in until the powered off.
Removed the SD card and set it aside. It's mission is complete.
Held the power button in until it powered on.
Routine booting began.
Upon boot completion, I clicked the n button and selected "search". I searched for "market". It found the Android Market. Don't look for "play". The hack itself uses an old version of the market that will upgrade itself to Google Play after you run it (as long as you are connected to WiFi).
At this point, your device is rooted successfully. Anything else you do is really just gravy. I suggest doing the NT Hidden Settings to allow sideloading and I also suggesting doing the hack to stop updates so that you get to keep all your hard (not really) rooting working in tact if and when B&N rolls out 1.4.3 of the Nook's firmware. Here are the additional steps that I took, again, this is all thanks to jichauan89's simple instructions and the feedback given in his thread. Also note, when I did have issues, I kept reading the thread rather than jumping the gun and posting my own questions. All the answers were already there...
I installed NT Hidden Settings from the market.
I immediately used the hack to allow 3rd party apps. There was some confusion and error here. I ran it a few times and it didn't appear to do anything, but then I pressed the n button once and a super user screen appeared asking me to give NT Hidden Settings rights, which I allowed. I tried the 3rd party hack a few more times to no avail. I rebooted the device and tried and tried and it wasn't working and the check mark on the previous screen for allowing Uknown Sources simply seemed to uncheck itself. I was watching the new episode of South Park on TV and at one point I reran the hack for about the 300th time it felt, a message came up that the app had been given SU rights, and I moved my attention to South Park for several minutes. When my eyes came back to the Nook, I checked the Unknown sources setting again, and it was checked, all by itslef. Lesson, I believe that the 3rd party app hack takes a few minutes to actually do anything after it is granted SU rights but doesn't give any notification that it is successful (or I missed it while grandma was trying to make Butters eat a urinal cake). I believe the app checks the Unknown Sources box itself as a part of its script and all the other times I had run the hack, I was just being impatient. After several reboots, the check now stays.
I then ran the NT Hidden Settings hack to keep updates from being installed. I was notified almost immediately that the installation was successful.
I then installed Go Launcher and HomeCatcher. I got Homecatcher from an XDA forum post and not from the Android Market. After running HomeCatcher, I clicked the n button and selected home and I was prompted to choose between a little andorid guy and the stock nook launcher. I made sure that put a check in the box to make this decision default (which i kind of wish i didn't, but it should be easily undone) and then selected the Andorid icon. Now whenever I select home, it goes to the Go Launcher app, awesome.
I also immediately installed File Expert and Titanium Backup and everything seems to work perfectly.
I then installed the Amazon App Market from Amazon.com in the Nook's stock browser. Every app from their seems to fail and says "SD card required" or some such thing. I am assuming that if I put the SD card back in everthing would work fine, but I'm not sure why this is an issue. Shouldn't it be able to use the Nook Tablet's internal memory? I'll keep testing.
The only thing I'm thinking about now is that I want to find the fastest way to switch back and forth between the stock B&N launcher and Go Launcher. I like B&N's ecosystem, even though it is limited, but I enjoy the advantages I get from walking in the store and getting to read books and even though the user interface of their digital store is one of the dumbest things I have ever seen, I find myself wanting to us it because I support Barnes & Noble a lot and wish them the best. I do, however, wish they would listen to all of us who are *****ing about their Market's limitations and ridiculous pricing and either treat the device more like a tablet like the name implies. But I'm preaching to the choir, right?
Try installing adw launcher, it should break the default status of go launcher, I'm not positive if there is a way to disable it other than that.
Sent from my Nook Tablet using XDA
You can actually go into the application settings and clear the cache and clear the defaults for HomeCatcher and then do a force stop. Run it again in the app drawer and the next time you click the n button it will ask wich launcher to run again. I made sure I didn't select the default action checkbox this time. Now everytime i hit n, it asks which launcher I want to use. I like it! Quick access to my wonderful root stuff and just as quick access to to an (essentially) stock Nook environment.
I have read it and did not find anything about pre-requisites. So am I totally safe doing this from a stock 8gb 1.4.2 nook tablet with no prior mods installed?
I understand the risks involved of course.
Piercing Heavens said:
I have read it and did not find anything about pre-requisites. So am I totally safe doing this from a stock 8gb 1.4.2 nook tablet with no prior mods installed?
I understand the risks involved of course.
Click to expand...
Click to collapse
If you're just looking to root, then yes, use the method linked in this thread.
The "N" button
I rooted mine and everything worked fine.
I installed Button Savior and use that when I wanna be in Android tablet mode for going to the home screen and I just leave the Barnes & Noble 'n' as it is so when I press it I can go straight to the B&N look. It's pretty easy.
But this thread has been a great help to me.
Thanks
I followed a very similar procedure and everything worked great the first time, thanks to this board!
Thanks
I wanted to throw a thanks out to you as well.
I read your post as well as jichuan's post before I even tried anything.
The only issue I have had is the "unknown sources" not staying checked.
Like you, I tried and tried to get it to stick, finally looked away for a bit, and poof! Magically it's checked. Maybe patience is indeed a virtue! However, I can not for the life of me get HomeCatcher to install. I am rooted obviously as I was able to download NT Hidden Settings from the Play store. Any ideas, or did I overlook something?
I had a lot of problems with unknown sources but it just happened all by itself
1.4.3
Doesn't seem to be working with 1.4.3. I installed NT Hidden settings and some apps from the play store but they are nowhere to be seen.
THANK YOU!!!!!
Thank you!!! I did this to my NOOK Table and it's working fine!! Thanks!! :laugh:
issue
I'm hoping someone can help me.
I rooted my NT last week (using these tips and tricks) and installed a bunch of stuff on it. And just today I installed the BEATS AUDIO on it and it asked me to reset the device... upon resetting it, it started up like a stock NT and I had to re-register it. Does that mean my device is no longer rooted?
I have an SD card on there and I did a backup using Titanium, but I'm not able to access the apps or get to NT Hidden Settings to download anything. When I navigate the web to the play store I'm able to see that it recognizes some of the apps as installed, but I cannot even download an apk or get anything to download through the play store even though it says a download will begin soon. Also, in the SEARCH option I do not get an option to choose where to search, it's just a general nook search.
I hope this is enough information. I want to try to re-root it but am afraid I might brick it.
PLEASE HELP!
Was your NT running 1.4.2? If so check to see if it's now on 1.4.3 in which case you had an OTA update which un-rooted your tablet.
digixmax said:
Was your NT running 1.4.2? If so check to see if it's now on 1.4.3 in which case you had an OTA update which un-rooted your tablet.
Click to expand...
Click to collapse
still on 1.4.2.
I guess somehow it reset itself and I lost the root. I had to reroot it and use titanium to get most of my files back. So glad I had set up a backup right before I downloaded the app. I ended up deleting the beats installer and just installed Volume+.
I'm still not sure what went wrong.
Hey folks,
OK, I'm just a little bit out of my depth here, so here it goes!
This probably sounds dodgy, but it is what it is: my daughter's phone (rooted HTC Desire 816) appears to have been "hacked" by someone at her school - whether its a prank gone wrong or she's a victim of bullying, we don't know and now we're dealing with the fallout.
By hacked what I mean is that the person or persons have somehow managed to find out my daughter's PIN and have then used it to gain access to her phone. Once in, they have turned off the custom lock screen installed (Hi Locker) and turned on the default lock screen and set a PIN which we don't know. Obviously, we're trying to get back into it without wiping it and don't know how to except for trying all 10,000 combinations!
So yeah, does anyone know how I might be able to go about getting back into the phone quicker than trying all 10,000 combos of PINs!?
Like I said, it is a rooted device; I was the one who initially set the phone up for my daughter. So its running TWRP and through TWRP I've been able to do an 'ADB Pull' request and dump the contents of external_sd and sdcard to my laptop so that at least that much data is preserved. I've also backed up the mmssms.db so that hopefully I can restore these databases if needs be. My daughter would like to not have to wipe the phone as she can't remember what other data (if any) might be lost if we do and I said I would try all other avenues before it gets to that.
Anyhow, I thought I would reach out to the community to find out if there is some way that I might be able to disable the lock screen or at least initiate some sort of backup process from the lock screen that would enable us to reset the lock screen. If not: such is life. But, if there is something that could be done, well, that would just be absolutely fantastic.
Thanks in advance folks for your responses and time.
Kind regard,
Dodgy Bob.
Hi folks,
After a bunch of further digging through random blogs and YouTube videos and whatever else, I happened across this site which pointed out a couple of different tricks that hadn't popped up on other sites I had come across. These were:
Safe Mode Option; and
adb shell rm /data/system/gesture.key
Safe Mode Option didn't work for me, because it wasn't the 3rd party lock screen app that was the issue.
However, the gesture.key option did work for me, albeit with a couple of tweaks! Gesture.key wasn't present because the phone is running a newer version of Android, v6.0 (I had forgotten this!), so I had 2 gatekeeper files and 3 db files -and- rather than deleting them, I added .orig to the file names. Once I had done this, I rebooted back into System from Recovery and ta-da, I was back into the phone!
Big thanks to @Helloworld294 for this post here which I found after searching more due to reading this page.
It's all worked out in the end.
Kind regards,
Dodgy Bob