Related
Greetings guys.... i have the 1962934272 bytes eMMC Nook touch. I first backed it up; the back size was 1962934272 with and without the bs=1M parameters and is identical. Tried the TouchNooter 1.6.24 ... didn't work ... stuck at the 'Nook by Barnes and noble' screen.... reverted back from the backup. Tried again per "nookdevs.com/NookTouch_Rooting". Put the rooted uRamdisk in. Installed adb on ubuntu and installed on the rooted nook su, superuser.apk, nook color tools, gapps using adb with some help googling around. Rebooted ... this is when the system got updated to 1.0.1.
Well... now when i reboot i am still at the regular B&N screen. What am i missing? I think i need the 'Go Launcher'. To have the same apps as the TouchNooter, i was thinking of installing busybox and buttonSavior from market afterwards. I need to find how to install go launcher .... search didn't yield good results... can somebody give me a link please...
Will the following files from TouchNooter along with the go launcher make it work and at par with TouchNooter?
/system/build.prop, packages.xml, framework.jar.
thank you,
Prasad
I also have a 1962934272 bytes eMMC Nook touch and there is no problem.
TouchNooter works flawlessly (I just had to install it twice because the first time it got stuck).
By the way, if you want to install GoLauncher, you just have to download the apk here
for instance (or take the apk provided with TouchNooter) and then install it using adb install <name_of_the_apk>.apk
Agree... will try again.
I was thinking along the lines... I will try again. Thanks for replying mdall... wasn't sure if it a retry will work or not... your reply instills confidence in me to retry. Thanks again.
Worked.
Had to reboot after it stuck at the 'Nook by Barnes and noble' screen the first time... worked fine the second time.
thank you.
You're welcome
mdall said:
I also have a 1962934272 bytes eMMC Nook touch and there is no problem.
TouchNooter works flawlessly (I just had to install it twice because the first time it got stuck).
By the way, if you want to install GoLauncher, you just have to download the apk here
for instance (or take the apk provided with TouchNooter) and then install it using adb install <name_of_the_apk>.apk
Click to expand...
Click to collapse
Wait, there are 2 kinds of nook? how do i know if my nook is 1962934272 bytes eMMC Nook touch or the other kind? what's the difference?
the other/prior one had 1958739968 bytes eMMC.
when you do a
dd if=/dev/sdb of=./nookTouchOriginal.img bs=1M
you will get a 1958739968 bytes file in slightly older N2E nook touch
but mine purchased on 20 Aug was 1962934272 bytes.
I have a Touch rooted with Touchnooter. My touch doesn't seem to want to update to 1.1 (I know doing so will kill GAPPS, but I'm okay with that). I've waited for the update to be pushed and I've also put the update file in my Nook directory. Is there something about Touchnooter that prevents the Touch from updating?
I haven't tried to update after using touchnooter, dont really know if it blocks nothing, OTA or prevents from updates, OTA or manullay, but you should restore a copy of your nook if you have it, or use nookrestore and then force a reset to also delete /data.
Or use adb to force restore
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
and then reset normally and if it dosnt let you, force reset, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
That will erase /system (restore) and /data (reset), and you should be able to update.
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
kunchers said:
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
Click to expand...
Click to collapse
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
TJay99 said:
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
There's nothing in TN 1.6.24 that will block updates.
If you want to make sure, here's the cleanest way of doing so:
Block BN OTA Updates the EASY way
Yes, it's a Nook Color thread but it would work for Nook ST aswell.
TJay99 said:
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
Blocking updates is also covered here http://forum.xda-developers.com/showthread.php?t=1346748 but with adb and sqlite.
Search for Blocking OTA updates: on the thread.
Yeah, I hear you. I gotta just do it. Strange though, why my Nook won't update.
ros87 said:
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
Click to expand...
Click to collapse
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
TJay99 said:
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
Click to expand...
Click to collapse
Touchnooter has adb enabled over wifi (If i'm not wrong), so you wouldnt have to enable it again, go directly into the OTA.
TJay99 said:
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
Click to expand...
Click to collapse
You should be good to go if you install jdk + android sdk.
With TouchNooter 1.6.24 you should allready have adb access enabled via wifi.
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Interesting, I need to take a closer look at the update process some day
Yep, same behavior with mine.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
TJay99 said:
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
Click to expand...
Click to collapse
That is my guess. Without knowing for sure you're left with two unpleasant options:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
2) Your nook actually updates and destroys everything!
So you might take the time to "block" OTA updates as other have mentioned. But then there's option...
3) You go through the rigors and just get the 1.1.0 firmware upgrade over and done with, rerooting afterwards.
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Kralik said:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
Click to expand...
Click to collapse
kunchers said:
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Click to expand...
Click to collapse
This is the best time to do that, finally got Gapps to work on 1.1 manully, at last!
If you wish to try it, here is my post:
http://forum.xda-developers.com/showthread.php?t=1346748
Kralik said:
That is my guess
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
Click to expand...
Click to collapse
A good and interesting guess.
There are intervals defined for the update checks, but maybe if it finds an update but are unable to apply it, it end up in a loop..
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Kralik said:
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Click to expand...
Click to collapse
At this moment, fun, learning, and stability (for the moment it allways works, but I need more feedback from people that tried it) eventually, when I delete all the blob that Gapps dosn't need for them to work, and is installed on the default package of Touchnooter (Don't get me wrong I really think its a great method) you will get a cleaner install.
Anyway, If you don't want to go through all the steps you can use the new 1.1 Touchnooter to get root, and then use my GApps method.
diff 1.1 us nst from 2011 vs 1.2 uk nst from 2day
rootfs
pastebin u4M1xRkJ
rom
pastebin uWSAcZ6Y
factory
pastebin XWnXjUeM
data
pastebin PgvewxzB
cache
pastebin P4Wqh1DV
boot
pastebin E3NeJP96
uk cache/recovery/log
pastebin uPLHxivA
Shows uk nst is just old us nst wi software update & new battery (lico vs mcnair)
uk nst manufacture date & mainboard sn is older than us nst from nov 2011
think cache/recovery/log shows b&n updating my uk nst from a 1.1 us nst
= b&n made too many nsts for us market, now they selling them here
= to update us nst to use uk store, think just need to replace factory/factory.zip on an old us nst wi factory/factory.zip from a uk nst & do factory restore
to update us nst to use uk store, think just need to replace factory/factory.zip on an old us nst wi factory/factory.zip from a uk nst & do factory restore
Click to expand...
Click to collapse
I'm happy to test this out if anyone can point me towards a uk factory.zip
can't post links, so http ge.tt forwardslash 4C0LRwQ forwardslash v forwardslash 0
I can confirm that flashing the uk factory.zip onto a us nook works just fine.
Anyone tried "downgrading"?
Hmmm, is the implication from this that it might be possible to "downgrade" to the US version of the software in order to root the device and gain the benefits of full access to android?
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
I might give this a go tonight and see where I get to.
John
johnjtaylor said:
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
Click to expand...
Click to collapse
Ha ha - as an Englishman in New York (well, actually Annapolis) I can relate!
I never know what spelling to teach my kids!
Well that's pretty straightforward the language is called "English" after all!
<grins, ducks and runs>
John
johnjtaylor said:
Hmmm, is the implication from this that it might be possible to "downgrade" to the US version of the software in order to root the device and gain the benefits of full access to android?
I don't know about the other UK owners, but I have no intention of ever buying a book from the Barnes and Noble web-site/store. I like the spelling of my books to be correct after all!
I might give this a go tonight and see where I get to.
John
Click to expand...
Click to collapse
Curses, foiled again! The US nook glowlight has no downloadable firmware..... grrrr
jeff_kz said:
I can confirm that flashing the uk factory.zip onto a us nook works just fine, however, I skipped the OOBE so I can't confirm that the registration process works.
Click to expand...
Click to collapse
I apologise if this is a stupid question, but can you (or anyone else) possibly point me in the direction of how to use this file?
I've done some research (including a search for 'nook simple touch factory.zip'), found out lots of stuff and downloaded lots of files, but I can't find any information on how to use this factory.zip file.
I did find that this is a standard folder/component of the Nook base installation, but how to use it with a stock firmware to effectively turn my US Nook into a 'UK Nook', I have no idea.
I would be really grateful for any help/information
To change the system software, replace the old factory.zip on partiton 3 with the factory.zip from the desired platform and then repeatedly interrupt the boot sequence to force a system restore. You will have to re-root after the system restore.
Code:
adb shell mount -t ext2 /dev/block/mmcblk0p3 /tmp
adb push factory.zip /tmp/factory.zip
adb shell umount /tmp
adb reboot
As soon as the "Read Forever" screen is visible,
Press and hold the power button until the screen briefly blanks white and then redraws the "Read Forever" screen
Briefly release the power button and then go to step 1
Repeat the above two steps six times, finally allowing the system to boot without holding down the power button.
If you've done all the steps correctly, you'll see the system restore screen which will replace your system software with software in factory.zip
jeff_kz said:
To change the system software, replace the old factory.zip on partiton 3 with the factory.zip from the desired platform and then repeatedly interrupt the boot sequence to force a system restore. You will have to re-root after the system restore.
Code:
adb shell mount -t ext2 /dev/block/mmcblk0p3 /tmp
adb push factory.zip /tmp/factory.zip
adb shell umount /tmp
adb reboot
As soon as the "Read Forever" screen is visible,
Press and hold the power button until the screen briefly blanks white and then redraws the "Read Forever" screen
Briefly release the power button and then go to step 1
Repeat the above two steps six times, finally allowing the system to boot without holding down the power button.
If you've done all the steps correctly, you'll see the system restore screen which will replace your system software with software in factory.zip
Click to expand...
Click to collapse
Thanks for the information.
Stupid question alert - the Nook has to be rooted before I do the above? If so, is there a guide? I rooted my old NST (non-glowlight) some time ago but I have since sold it. I now have a nice new shiny NST glowlight (US version) which I want to load the UK firmware onto.
Any pointers would be gratefully received.
Many thanks in advance.
nookingtom said:
Thanks for the information.
Stupid question alert - the Nook has to be rooted before I do the above? If so, is there a guide? I rooted my old NST (non-glowlight) some time ago but I have since sold it. I now have a nice new shiny NST glowlight (US version) which I want to load the UK firmware onto.
.
Click to expand...
Click to collapse
but what is the advantage to running a uk nook over a us? The US store is cheaper, i think, and if you do the conversion you can't register your nook anymore right?
So just to let you know... You can also apply that zip in CWM. It will not break your Nook Touch. It will not update propertly as well, it is somehow strange, so im making a factory reset now...
Disclaimer
Before even consider reading this, know that I cannot be held responsible if following these steps will: brick your device, make your girl friend break up with you, start third world war or do any other kind of damage.
Motivation
This tutorial is intended to help people who did not make a full backup of their device and applied the Alpha-FormatTouch-2.zip to their device and as a result lost the GlowLight feature. It took me a couple of days to figure out how to revert to factory settings, and thus, I hope that I can save others time.
Preliminary
You need
Nook Simple Touch Glowlight, semibricked
SD Card
SD card reader
Downloads
Download the following files:
factory.zip - downloads[dot]nanophysics[dot]dk/nstg/factory[dot]zip (if you have a copy of your own factory.zip -- found on the partition /factory/ -- use that instead)
[ClockworkMod - downloads[dot]nanophysics[dot]dk/nstg/sd_128mb_clockwork-rc2[dot]zip
Install Clockworkmod on SD card
On Mac OS X, plug in the SD card and find the device using
Code:
$ diskutil list
I will assume that your device is /dev/disk1. Unmount the disk
Code:
sudo diskutil unmountDisk /dev/disk1
and write the ClockworkMod to it
Code:
sudo dd if=128mb_clockwork-rc2.img of=/dev/disk1
Copy the factory.zip to the disk and eject it.
On Windows you can use Win32Imager.
Install factory image
Power off your Nook and insert the SD card. Then power it up. After a while the CWM menu will appear (if you get a white screen press right-down). Select "install zip from sdcard" using the right side navigation to go up and down and u to enter. If you enter the wrong menu you can go back on right up. Now select "choose zip from sdcard" and choose factory.zip. Finally, click the option saying "yes - install factory.zip"
After a few minutes the installation is complete and if everything went ok, you should now be back to the original factory software.
Reset user settings (optional)
If you want your Nook to be completely reset, you can optionally do a reset of your settings. Power off you Nook. Power it up again and hold left and right down simultaneously for around 30 s. Answer yes twice. After a while your Nook has been reset.
Backup
Finally, it is time to do what you should have done in the first place (and probably also the reason why you are following this tutorial): Make a full backup of your Nooks internal SD card. See blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch for more information.
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
shank21101985 said:
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
Click to expand...
Click to collapse
If your NSTG is rooted, this may remove rooting - at least I think, I did not try. However, you can always reroot.
Regarding backup, I would make a full image backup before starting. If you have a Windows box, follow the instruction on blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch and make a full backup of your system.
I have only done backup of individual partitions on Linux: Boot the device with noogie.img and plug it in. On Ubuntu,t 6-8 partitions should immediately appear.
jjinkou2 said:
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
Click to expand...
Click to collapse
There was missing a slash in the URL. It has been fixed.
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
roustabout said:
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
Click to expand...
Click to collapse
Remark that I recommend that people use their own factory.zip image. Nevertheless, all these data you mention are stored on the rom partition. To my awareness this partition is only overwritten if one applies rombackup.zip, but not by factory.zip. Thus, your B&N shop should be fully functional afterwards. I did apply someone elses factory.zip first, and I had no problems registering my device. However, if anyone would experience such an issue, please drop a line in this thread.
In any case, you should always do a full system image before following tutorials like this one, or for that matter, before apply someone elses partition images to your own device.
roustabout said:
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
Click to expand...
Click to collapse
Judging from your other post (http://forum.xda-developers.com/showthread.php?t=1836188&page=4), the partition you have made a copy of, is the boot partition? If glow was already working, it will still work after overwriting the boot image.
However, if it was not working already, it is very unlikely that installing a new boot image will resolve the issue described here, since it is a consequence having downgraded the OS.
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
roustabout said:
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
Click to expand...
Click to collapse
Ok. No this thread is not intended for people who have destroyed partition tables etc., but only for people who have downgraded their software by using NST recovering guides on their NSTG device. I found it relevant to explain how this is done, since many people complain that their NSTG works, except that glow light no longer works. If they look into the software version they find something below 1.1.5, like 1.1 which was my case. I could not find a guide which explained me what to do after screwing up the software, hence this guide.
Partition tables and "accidently formatting" is a completely other issue. In the end, here the main problem is that people do not make a backup as they assume that everything is going to be fine. I assumed that myself. However, at some point I will have a look at the rom partition, because I think it is quite limited amount of information you find their. It should be possible to restore your Nooks serial number -- it is written on the package of the Nook -- after applying another Nooks image. I just received my second Nook so I am going to try this at some point.
Thank you so much for sharing the solution.. finally my glowlight works now !!
shank21101985 said:
Thank you so much for sharing the solution.. finally my glowlight works now !!
Click to expand...
Click to collapse
Hic, I cannot download the image file, my backup file was deleted, anyone can upload that image for me?
Thanks so much:crying:
factory.zip
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
So did you actually replace the factory.zip with one for the NST or did you just run a restore from, say, NookManager? I'm not too sure about this, but I think it's kind of difficult to wipe the factory.zip. Anyway, since I'm not familiar with the NTG, and you seem to have done something that others have also done before, have a look at this old thread and see if it gets you anywhere:
http://forum.xda-developers.com/showthread.php?t=1936458
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
nmyshkin said:
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
Click to expand...
Click to collapse
Its dead I need a glowlight factory image
can someone please re-upload the glowlight factory image please.... Thank you in advance
Hello:
Due to a failed factory settings recovery attempt my My N2E is as follows:
On firmware version 1.0.0
IRooted with TouchNooter 2.1.31
My main goal is to root it my N2E using NookManager. For that, I understand that:
First, I have to upgrade the N2E to firmware version 1.2.1
Then, I can root it with NookManager
But (and here's the catch) after upgrading to 1.2.1 (pre requisite for NookManager) the N2E will be still rooted with TouchNooter 2.1.31 which I understand happens to be incompatible with N2E on firmware version 1.2.1
Even if I succesfully get to root the N2E to NookManager inmmediately after upgrading to 1.2.1, shouldn't it be an issue?
Keep in mind: I'd be rooting NookManager on top of an N2E already rooted with TouchNooter 2.1.31
Isn't that a brick scenario or am I missing something here?
Thanks in advance,
Point 1: There is no brick scenario for the Nook.
Whatever you can do can be undone using a system booted off the SD card.
For the white Nook, which has no SD card, there is the boot over USB to resuscitate it.
Boot over USB also works for all the other model.
Point 2: If you have a non-white Nook there is no reason to use any system version besides 1.2.1
1.3.X on the white Nook is a mish-mash of old and new versions.
If we ever discover anything good about 1.3.X we can cherry-pick it out to add to 1.2.1
Point 3: Before you start modifying your Nook you should have a backup of the /rom/devconf directory.
You may not have any interest in doing business with B&N, but the MAC, serial number, battery info is important.
Point 4: I know nothing about either of these "managers".
If you are at 1.2.1 just use whatever manager thingie you want to.
Renate:
Thanks again for your prompt reply.
Renate NST said:
Point 1: There is no brick scenario for the Nook.
Whatever you can do can be undone using a system booted off the SD card.
For the white Nook, which has no SD card, there is the boot over USB to resuscitate it.
Boot over USB also works for all the other model.
Click to expand...
Click to collapse
How's that "booting form USB" works? BTW, I have a Nook Simple Touch "original"; the one sold with the 1.0.0 firmware.
Renate NST said:
Point 2: If you have a non-white Nook there is no reason to use any system version besides 1.2.1
1.3.X on the white Nook is a mish-mash of old and new versions.
If we ever discover anything good about 1.3.X we can cherry-pick it out to add to 1.2.1
Click to expand...
Click to collapse
Er... if you say so. I'm only posting what I know about TocuhNooter 2.1.31. I'm merelñy and able user, not an expert, per se.
Renate NST said:
Point 3: Before you start modifying your Nook you should have a backup of the /rom/devconf directory.
You may not have any interest in doing business with B&N, but the MAC, serial number, battery info is important.
Click to expand...
Click to collapse
OK, I do believe that the NookManager root method/tools/boot includes it's own backup manager, so that would be a "plan b" scenario.
Do you recommend an other nook backup utility?
Renate NST said:
Point 4: I know nothing about either of these "managers".
If you are at 1.2.1 just use whatever manager thingie you want to.
Click to expand...
Click to collapse
Hmm... What root method do you currently use with your Nook? Is it a N2E, N2E with GlowLight, other?
Awaiting your kind comments,
OK, here's how you fix your issue...
1. Insert Nook Manager microSD, boot it, select Restore Factory Image (or something like that...). This will restore your Nook to version 1.0 (I believe, I have done this 2 or 3 times, it's 1.0 or 1.1). Follow the instructions. In the end you will remove the Nook Manager card, and reboot.
This should, if I understand correctly, re-install the factory image that is stored on your Nook. Unless TouchNooter (or something else you did) modified that, you should be good to go from here. If something has modified the factory image, then it gets way more complicated, because part of that image is data that is unique to your Nook. So, you can't just get someone elses factory image, as it would have their unique data in it.
That said, if anything did modify your factory image, I for one want to know, that needs to be stopped.
2. Download the update for 1.2.1 from B&N (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175) and follow the instructions to install it.
3. Re-insert the Nook Manager card, and root with Nook Manager.
MildBill
MildBill said:
OK, here's how you fix your issue...
Click to expand...
Click to collapse
Bill, this sounds simple enough for me
I'll try it and post the results here.
Very gratefully yours,
sarmasm said:
I'll try it and post the results here.
Click to expand...
Click to collapse
It worked like a charm! Updated to 1.2.1 and rooted OK with NookManager.
Renate and Bill, thank you for your patience and kind advice
Very gratefully yours,