Related
I was trying to root a clean NST (firmware 1.1.0) with just released TouchNooter 2.1.26, but ran into the same problem as reported on the dev thread. Since I am a new member and can't reply there, I am sharing my experience here.
In a nutshell, the new release does not seem to be able to start ADW.Launcher. I found a workaround by overlaying it on top of version 1.11.20 (all Nooter versions are available from the project download page here), but still had to wait about 10 hours to get Market working.
Here are my steps:
1. Restore to factory firmware (make sure it is 1.1.0) with n2T-Recovery tool
2. Clean user data with "Settings->Device Info->Erase & Deregister Device"
3. After reboot, register the device again (It doesn't seem to require the email address to the same as Google account -- I used a different email address)
4. Start initial rooting with touchnooter-1-11-20.img
5. Step through the Android welcome screen and choose "Skip" on sign-in page
6. Enable location service when prompted
7. Verify you can bring up App Drawer, then STOP (don't go to YouTube yet)
8. Now insert the SDCard with the new touchnooter-2-1-26.img and reboot
9. You should be prompted with option to bring up ADW.Launcher
10. Now continue with YouTube sign-in, GMail sync, and Market activation, etc. steps in as per the original TouchNooter 2.1.26 instructions (I used a Google account email (not gmail) and it worked for me)
11. Wait up to 24 hours to get Market to work
I hope this helps, and would appreciate someone posting this information to the original TouchNooter 2.1.26 thread.
Rooted Forever.
I had issues with touchnooter and now I'm getting boot loops. For some reason those recovery img's are dead. Do you know of any other links to them?
Edit: Never mind I think I know what I did wrong, didn't up date to 1.1 before root. Also I just did the 8 boot loops to get it back to stock. Fixed and thanks.
yo i had problems with my gmail not syncing after signing into youtube. So i rebooted. youtube crashes to home whenever i tried to open it. So i was trying to sync my gmail with the account i entered into youtube, but of no avail. So instead, i created a new account and then my nook said it synced the account i just created, after that i tried to click on the original account, and bingo it synced too...i am just waiting for the market to load up
After boot touchnooter 2.1.26, how much time one have to "wait for the screen flash black"?
z117 said:
After boot touchnooter 2.1.26, how much time one have to "wait for the screen flash black"?
Click to expand...
Click to collapse
After 15-20 seconds, the screen turns black.
I have waited for 15 minutes, and nothing happens, and restarted the device.
I am one of the TouchNooter 2.1.26 victims too
I have gone thru the steps twice, but not with success.
So I restored my device, and now waiting for an update.
Or should I try another root method, I don't know
me neither. i waited for 10~15 mins.Screen didnt flash. So i removed card and rebooted. my Nook just showed the stock apps (stock home screen)along with the button saviour app(which didnt work) and it never showed me the rooted home screen. ended up rooting with Tomirunooter.Flawless victory
posted in the thread, confirmed this as working for me. thanks for finding a fix!!
I tried to root twice using TouchNooter 2.1.26, first time it booted but without being rooted, used n2T-Recovery, downloaded TN 2.1.26 again e tried again, now my NST is on boot loop. Where i can find touchnooter-1-11-20.img?
http://nookdevs.com/Nook_Simple_Touch/Rooting
if you scroll down you can find the TouchNooter 1.11.20 file
Nooter images download page
brunobbarcelos said:
I tried to root twice using TouchNooter 2.1.26, first time it booted but without being rooted, used n2T-Recovery, downloaded TN 2.1.26 again e tried again, now my NST is on boot loop. Where i can find touchnooter-1-11-20.img?
Click to expand...
Click to collapse
You can find all TouchRooter versions in the Nooter project's download page, see the highlighted link in my original post above.
Nevermind, found the issue, will be updating with a new version soon that fixes it.
Updated with new version that fixes Launcher not properly installing can be found here: http://forum.xda-developers.com/showthread.php?t=1343143
Duplicated apps
Hello, since I can't post on the Dev channel, I'll use this thread. Sorry, OP
Why Gabrial / Torimu (the two nooters I've tried with success) chose to rename the included apps -names+version numbers-, instead of using the unique, official name -installed app-? I think that can cause problems of duplication.
Both latest versions bring apps that some of us have from a previous root. For example, they use "NookTouchTools_v1.0-beta2.apk" instead of "io.xor.nooktouchtools.apk". Or "Opera_Mini_v6.5.2.apk" instead of "com.opera.mini.android.apk".
The result is they write some applications already present at data/app (and perhaps with different versions). I do not know exactly if this will create problems with the Android system, but can be solved very easily on nooter's part...
TIA,
jugaor
PS: btw, sorry for my bad English…
jugaor said:
Hello, since I can't post on the Dev channel, I'll use this thread. Sorry, OP
Why Gabrial / Torimu (the two nooters I've tried with success) chose to rename the included apps -names+version numbers-, instead of using the unique, official name -installed app-? I think that can cause problems of duplication.
Both latest versions bring apps that some of us have from a previous root. For example, they use "NookTouchTools_v1.0-beta2.apk" instead of "io.xor.nooktouchtools.apk". Or "Opera_Mini_v6.5.2.apk" instead of "com.opera.mini.android.apk".
The result is they write some applications already present at data/app (and perhaps with different versions). I do not know exactly if this will create problems with the Android system, but can be solved very easily on nooter's part...
TIA,
jugaor
PS: btw, sorry for my bad English…
Click to expand...
Click to collapse
I renamed the ones in TouchNooter so that users could easily identify what I was providing with TouchNooter to users, I don't think it'll cause problems as I've noticed a few times before where I'll look into my data and see com.appname.something-1.apk along with com.appname.something.apk which seems to be caused by something other than TouchNooter because I've noticed it with apps that I installed just through market. The only thing you "may" have to worry about is that the extra apps may consume more space from /data
The fix however is simple an app that's in /nooter/data/app that you know you already have for whatever reason you could simply remove (If you've previously rooted that's quite a few of them) or you could uninstall them and let Nooter install them.
Hiya, I'm another one who can't post on the dev thread.. and since this thread was already here and I had the same problem..
I rooted my new 1.1 NST last night using the current touchnooter. The device went through the steps, screen turned black, I pulled SD card and rebooted.
I did wait just in case..but all the nook did was refresh the screen with the dots on it for twenty minutes. I could not break the boot loop.
I ended up using the NST restore zip on a CWM disk (that I tucked in the slot and sort of held the power button down and prayed at). It worked and I was left with a half-rooted nook. (I had the launcher, Amazon app market and a few other random things... they really didn't work, told me a I needed a rooted device.) I was able to install and use opera funny enough.
I deregestered, reregestered.. and rechecked the specs (just in case!)...and tried again. Same result.
So I deregestered, reregestered... and now I will try the MinimalTouch 1.1beta5. I'm not sure why touchnooter did not work. It should have.
Hi All,
I'm in a bit of a unique pickle. I have a Lenovo ThinkPad Tablet 1838-CTO, it is a US 32GB wifi-only tablet with all stock hardware (with disconnected keyboard folio).
I am running build number ThinkPadTablet_A310_02_0037_0075_US
It is not liking to play more than 5 minutes of a video before saying video cannot be played, video it played fine before. Tried all the standard steps, recopying, rebooting, etc etc. The device also sporadically reboots 20-30 minutes into use, sometimes. I have root, rootprotector, and I have CWR. I have not used my tablet since about a week after the first update from my current version above: my device went loopy, THEN the update failed, and I stuck it in a closet, $%^@%$*&@ed off at it for not working.
I want to either (depending on difficulty, and recommendations here) update my device to the latest Lenovo ICS *OR* Run a custom JB ROM (perhaps http://forum.xda-developers.com/showthread.php?t=1778375 though it is for ROW not US, unsure if that matters). Priority on maintaining root access, could care less about what recovery is used, etc.
OTA updates are failing since I had to get CWR , and I am not sure how to use CWR to manually patch/update.
As for the glitching and all that, I am fairly certain it has something to do with when I rooted it, I was a very early adopter of the first permaroot (I place no blame except myself for any and all issues, and muchly appreciate the efforts of others in allowing me to root my device, whether it bricks it or makes it 10x better). I just want to update my device to ICS and start using it again. I have done some searching but am finding that almost everyone is using 0089 or later with the same issue I have, trying to get back to stock bootloader. Honestly I would like to get it on Lenovo ICS, maintain root, and go from there.
I appreciate any and all advice, it's a personal device so I am fairly lenient on what I am willing to try.
Update: I would most appreciate a stock Lenovo ICS dump flashable from CWR if someone knows where to get one, again though any help at all is appreciated.
Update 2: CWM 5.5.0.4 unable to mount the SD card (/sdcard - not even sure if it is trying to mount internal or external, I have ALWAYS had nothing but issues with the external ALWAYS being write-protected no matter the position of the physical slider switch, though it always reads fine - Sandisk 32GB micro-SDHC with Sandisk MicroSD to SD adaptor), so flashing anything from CWM is a no-go. I want to take this thing and send it on a flying ride out the window, the only thing stopping me is it would probably survive just fine to spite and mock me. Sorry about being long winded, rather give you guys as much as possible info.
Is rooting the tablet all you've done? Did you remove any stock apps? I had the same problem with my TPT when I tried upgrading to ICS(from build 0089_US on wifi only 16GB)but only because I had a corrupt busybox file or something. Try going back to complete stock(NO recovery no root) and try to do an automatic OTA 2, then OTA 3. It should work.
How do I go back to stock recovery/bootloader? I rooted back when you had to swap in ClockworkMod Recovery, so my updates fail consistently when I have to reboot to apply, my guess is that the updater tries to pass calls to the lenovo bootloader that do not exist with CWR.
If there is a way to restore my bootloader then I should be all set, otherwise I think I need to find a good cooked rom
Get Some ICS
Sublime865 said:
...otherwise I think I need to find a good cooked rom
Click to expand...
Click to collapse
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!
pwstein said:
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!
Click to expand...
Click to collapse
Going to try it tonight/tomorrow. Updating my Vivid to a non-corrupt CWR then flashing HolICS 1.3 from 0.9b tonight. Oh the adventures I get myself into... XD
Thanks for the upload, I'll let you know if(when) it works, either way I appreciate the effort!
I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2
Hi,
First of all, sorry about my english. It's not my primary language.
I recently bought a used Nook Simple Touch on eBay. The previous owner had tried to root it, but failed somewhere along the way. I got it dirt cheap and figured I could fix it..
I've read "all" the unbricking guides here on the forum, but I'm yet to make it start. I can boot CWM, but for some reason noogie is not starting at all.
At first, the device said "Rooted forever" all the time, but after some messing around in CWM it's instead displaying "Your NOOK is starting up..." in five different languages, and stops there.
The thing is, I'm not even interested in the reading features (B&N apps, e-books, etc.), I just want to use the device to display a status webpage that I've made (weather updates, bus/subway/tram departures, etc. etc.), so as long as it can run Chrome or similar I would be perfectly happy! Is there a vanilla android ROM available so I don't need to care about the "device specific" data that I've been reading about (the one you're supposed to take a backup of)? Or can I just flash it with any NST firmware if I'm not interested in the reading functionality?
Thanks!
Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.
nmyshkin said:
Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.
Click to expand...
Click to collapse
I agree. I just received my nook from ebay a couple of days ago. I've tried a number of different root methods and google apps installers. Nook Manager + NTGApps was by far the simplest for me.
Also, have you tried the stock factory reset?? I'm new to this, so I'm not sure if it will work -- but I thought I bricked mine 3-4 times and the factory reset saved me every time.
0) Take out any SD cards (just making sure you don't have anything bootable on the card)
1) Press and hold the power button until it resets
2) As soon as it begins to reboot press and hold the bottom left and bottom right physical buttons until you see a prompt.
3) Wait for the prompt and press the "n" button once to confirm the factory reset
4) Press the "n" button again to begin the factory reset again.
After you factory reset, upgrade to 1.2.1 and then root using Nook Manager. Then, you'll have the browser available to you.
* Use Nook Manager to make a backup *
Thanks for the suggestions you guys! I finally got it to work!
Noogie finally booted up. I just left the nook, with the noogie sd card in, connected to my computer when I went to work. When I got home, it had started. Since then it started every reboot. No idea why it didn't work in the beginning?
Alright, this is how I did. This information is scattered around the forum already, but hopefully it can help someone in my position.
1) I realized that the partitions table was probably messed up, so after "aligning" it using fdisk and the table found here:
http://forum.xda-developers.com/showpost.php?p=29585690&postcount=6
I could restore my /rom partition. After I've made a backup of the /rom files...
2) ... I flashed this file using noogie:
http://forum.xda-developers.com/showpost.php?p=49389880&postcount=2
3) I mounted partition2 on my computer (still using noogie) and copied my /rom files back to it.
4) It started! So I applied the official 1.2.1 update from B&N. After update I realized that I actually have a glowlight! It was listed as a regular Simple Touch, so that was a pleasant surprise.
5) Rooted using NookManager. Worked flawlessy. Installed Opera Mobile 12.1 (which have websocket support that I needed). I now have an awesome status "frame".
Thank you for all you help, including the guys & girls posting in the threads linked in this post.
Hey all,
I rooted my NST waaaay back and haven't touched it again until now. I want to use it for another project now but want to update it first.
I'd like a rom with adb, button savior, usb host mode, su, busybox, and that's it (unless i'm missing something that i should really have).
I'll sideload anything else I need, and I don't want gapps or amazon appstore or anything.
Though I wouldn't mind an 'e-ink friendly' theme or whatever.
Is the best process to erase and deregister, or can I just use CWM and whatever rom I want on an SDCard and update it directly?
Thanks
There only seems to be three ROMs still being developed. Two of them are somewhat full of bloats. But the CM11 port being worked on right now is operable off a micro SD card and it is barebone. Doubt that it have the requested features (button savior?) but out of the three, that one seems to be the best match. And it will only gets better once the porting stabilize some more.
Deafcyclist said:
There only seems to be three ROMs still being developed. Two of them are somewhat full of bloats. But the CM11 port being worked on right now is operable off a micro SD card and it is barebone. Doubt that it have the requested features (button savior?) but out of the three, that one seems to be the best match. And it will only gets better once the porting stabilize some more.
Click to expand...
Click to collapse
That is partly true, but the current CM11 build is nowhere near stable enough to run as a daily driver.
Our friend here should probably go the NookManager route to start off; what do you think?
I'm far from using it as a daily driver, and I might even be able to drop the host mode requirement. It just needs to run an android app I'll develop, but wifi will need to work too. I'll check out CM11.
If I can start with a rooted version of the latest firmware, that'd be fine, but NookManager says: "For best results, however, you should be on 1.2.1 before using this tool." So, what's the best path to update to 1.2.1 or the latest firmware, given that I'm already on a rooted (and registered ) 1.1.0?
Modulus said:
I'm far from using it as a daily driver, and I might even be able to drop the host mode requirement. It just needs to run an android app I'll develop, but wifi will need to work too. I'll check out CM11.
If I can start with a rooted version of the latest firmware, that'd be fine, but NookManager says: "For best results, however, you should be on 1.2.1 before using this tool." So, what's the best path to update to 1.2.1 or the latest firmware, given that I'm already on a rooted (and registered ) 1.1.0?
Click to expand...
Click to collapse
A factory wipe will be the first thing to do. Restore your Nook to the state in which it came out of the box.
Then, either register or bypass Oobe to get into your "new" Nook. Once that's done, you can follow the instructions here to update to 1.2.1.
After that, you can use NookManager.
I found some instructions that you had previously given to someone in another thread here
It took me forever to get the 8-interrupt restore to work, and afterwards, it still had ADW launcher and some other stuff that I had installed.
I did not do the 'Erase and deregister this device' at any point.
After the 8-interrupt restore, I transferred the 1.2.1 update to the root of the Nook, rebooted and let that install.
Then after it booted, it pleasantly informed me it was at 1.2.1 but it still had the ADW launcher, so I rebooted onto NookManager and rooted it.
Now it's rooted, but still has ADW launcher and also has ReLaunch obviously.
Should I have done the 'Erase and deregister' to fully wipe it back to how it was when it came out of the box?
If I use the NookManager option to factory restore it, will that get me a clean slate?
Thanks for the help man, I know this thing is ancient
Modulus said:
I found some instructions that you had previously given to someone in another thread here
It took me forever to get the 8-interrupt restore to work, and afterwards, it still had ADW launcher and some other stuff that I had installed.
I did not do the 'Erase and deregister this device' at any point.
After the 8-interrupt restore, I transferred the 1.2.1 update to the root of the Nook, rebooted and let that install.
Then after it booted, it pleasantly informed me it was at 1.2.1 but it still had the ADW launcher, so I rebooted onto NookManager and rooted it.
Now it's rooted, but still has ADW launcher and also has ReLaunch obviously.
Should I have done the 'Erase and deregister' to fully wipe it back to how it was when it came out of the box?
If I use the NookManager option to factory restore it, will that get me a clean slate?
Thanks for the help man, I know this thing is ancient
Click to expand...
Click to collapse
To avoid potential issues in the future, you definitely should use the Restore factory.zip function of NookManager. That will assuredly get you back to the factory state.
Then, update to 1.2.1, root with NookManager, and you're on your way.
And you'd be surprised at how much development is still underway for the Nook Touch - it may be old, but it sure isn't obsolete. In fact, the Nook Touch is my personal specialty, as you might have guessed from my username.
Anyways, if you ever need help with your Nook in any way, shape or form, don't hesitate to PM me or post on the forums. Either way, I'll see it and reply.
ИΘΘK¡€ said:
To avoid potential issues in the future, you definitely should use the Restore factory.zip function of NookManager. That will assuredly get you back to the factory state.
Then, update to 1.2.1, root with NookManager, and you're on your way.
And you'd be surprised at how much development is still underway for the Nook Touch - it may be old, but it sure isn't obsolete. In fact, the Nook Touch is my personal specialty, as you might have guessed from my username.
Anyways, if you ever need help with your Nook in any way, shaoe or form, don't hesitate to PM me or post on the forums. Either way, I'll see it and reply.
Click to expand...
Click to collapse
Just posting to say that this is sound advice. I was in a similar situation, wanted to give my Nook ST the latest and greatest developments,. What worked for me was to use NookManager to restore factory.zip, this actually upgraded the Nook to 1.2.0, so I assume that comes with NookManager somehow. Then I used the Nook 'Settings' to go to unregister/reset the device, then finally, bypass the OOBE setup using crazy_jake's method ...
http://forum.xda-developers.com/showthread.php?t=1162693
... and now I'm off to re-root it and add all the apps again!
Big thanks all!
Grab what you need from here: https://drive.google.com/folderview...EwRndzUklrN1dRVTRuZVJXRlp1N0hWRTQ&usp=sharing
All zips install via CWM.
But for What you want grab & Flash these in this order:
nook_1_2_update.zip - This is just an optimized version of the default UK ROM with init.d+Busybox.
ReLaunch-ONLY.zip - This will replace the Home with ReLaunch.
USB-Audio+FastMode+Host.zip - Also enables ROOT/SU - Install this after logging into your B&N account. If you install it before you won't be able to register with B&N.