yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] winstonma:
Hi all,

I just bricked my N2T without any backup (in bootloop) . Is it possible for anyone who can post a copy of backup so I can restore mine.

Thanks in advance.
[Nook Touch Android Development] ros87:
This has been repeated over and over again..

You cannot use a backup from another NST as every NST contains unique data used, amongst other things, to register with B&N.

If someone is dumb enough to give you a copy of their backup, then you'll both risk ending up being unable to register your NST with B&N.

Have a look here and see if that can be of any help, if not, feel free to PM me for further assistance.
[Nook Touch Android Development] CRACING:
Hello all,

I got a new Nook Simple Touch and it has pre-updated or pre-installed v1.1

I would like to root the device so I took backup of the device ROM. One from Win32 Disk Imager and two from Roadkil's Disk Image.

Following are the file sizes. Please let me know whether its right or wrong. I don't like to end up the device bricked when I try to restore. The device values me more. :o

Image from Win32 Disk Imager is 1,998,743,040 bytes

Image from Roadkil's Disk Image is 2,000,683,008 bytes

I have followed rooting guide from nookdev site (of course also from this thread), but yet not replaced the uRamdisk. Coz want to be sure the backup image is correct.

Thanks...

Best Regards
[Nook Touch Android Development] ros87:
Looks fine to me :)

As long as the backup is bigger than the sum of the actual NST partitions (which I've posted earlier in this thread) you should be on the safe side.
[Nook Touch Android Development] CRACING:
Thats good. Now I can safely play with my nook. :)

Thanks a lot...

Best Regards
[Nook Touch Android Development] CRACING:
Hello again,

I guess I missed something. Do I need to Erase & Deregister Device before taking backup?

I have removed all my files from main memory but device is registered.

Thanks...

Best Regards
[Nook Touch Android Development] Fulkerson:
Instead of dumping a 2 Gb big file directly to hd you could pipe it through a compression tool:

Dumping:
dd if=/dev/sdX bs=1M | gzip > blob.img.gz

Restoring:
gzip -dc | dd of=/dev/sdX bs=1M

Replace gzip with whatever compression tools is wanted.

lzop -- extremely high throughput, very low compression rate.

gzip -- high throughput, low compression rate.

xz -- low throughput, totally awesome compression rate.

Dumping a pretty much stock v1.1 nook with xz results in a img of around 500mb.
[Nook Touch Android Development] case-sensitive:
I ran RoadKill as administrator (under XP), but I still got a physical disk 1 of size 239.98MB. I also tried to backup under linxu using dd, and I ended up with a backup file of size 252MB.

Under linux, when I typed "df -h" the nook touch appears as /dev/sdd and NOT (e.g.) /dev/sdd1. I booted with noogie.img first and then plug the nook touch into my laptop.

I must have done something wrong but I couldn't figured out why... Help, and thanks!
[Nook Touch Android Development] albertorrent:
HI, I succefully wrote the noogie on my SD with roadkil's but I t is impossible to get to the "rooted forever" screen.

I shut down the NST

then I put my SD (with noogies wrote by roadkils) in it

Then I turned it on

Then it booted as a normal boot

I tried several times with differents microSD cards I have always the same result.

I also tried to put in the usb cable at different times as I didn't get the good screen but with no success.

Any advice to help me please ?

---------- Post added at 08:22 PM ---------- Previous post was at 07:41 PM ----------

Ok I found something :

I tried to write the noogies with winimage and not with roadkil's and it worked.

Then I get the rooted forever screen

then I made an image with roadkil's(.img) : 1 953 792 Ko

then I made an image with winimage (.ima) : 1 953 792 Ko

So I gess it worked for me and I can now try to root my device.
[Nook Touch Android Development] brendan10211:
Roadkill doesn't like to work (it is dead after all). Glad you got it working!
[Nook Touch Android Development] bobcdy:
I backup up my rooted Nook Simple Touch according to directions using Noogie and DiskImager. Today I had a major problem with my NST (it had spontaneously done a restore and I thought it was ok, but it wasn't). So I tried a restore using MiniToolPartition Wizard and Diskimager. All seemed to go ok - I deleted all partitions on the Nook, using Partition Wizard to create a partition on it so it would show on my Win 7, and used Diskimager to restore my backup img. Write as 'successful' but it wasn't. The restored Nook would not boot - gave an error and indicated I should reboot. Tried that repeately but did not work. Looks like there is something wrong with the boot file.

I tried a system recovery using n2T-Recovery_0.2.img but that won't work. After 2 minutes when I reboot the message 'Wait 2 minutes..." repeats with each reboot. I looks like I've totally bricked the reader.

OK, I realize what the mistake was, and I know what has to be done.
[Nook Touch Android Development] imachine:
Well, I haven't backed mine up.

The way I see it is:

1) Make an update.zip with /rom/devconf for particular device for CWM usage

2) Obtain an update-system.zip that restores everything else using CWM

When I try to cp /rom to /media I get an error message:

# busybox cp -R /rom .

busybox: remote access failed

# pwd

/media

Any ideas? Google shows windows errors when asked about the error message.

*edit*

It seems I have found the source of the issue ;)

# pwd

/system/xbin

# ls -l busybox

busybox: Stale NFS file handle

So I did this:

# dd if=/dev/block/mmcblk0p2 of=/media/rom.img

32768+0 records in

32768+0 records out

16777216 bytes transferred in 10.548 secs (1590558 bytes/sec)

So I feel safe :-) Now, can someone point me to the contents of:

/dev/block/mmcblk0p1

/dev/block/mmcblk0p5

/dev/block/mmcblk0p7

/dev/block/mmcblk0p8

for 1.1.0 or whatever is the latest?

Are there any more? busybox doesn't run here, and I can't find fdisk inside the nook using toolbox.

Cheers!
[Nook Touch Android Development] Sun_Cat:
Help restoring .ima

Like this post, I couldn't make Diskimager work right so I resorted to WinImage. When I backed up the NST, I ended up with a .ima file of 1,958,739,968 bytes.

Now I'd like to restore my NST to stock. When I open the .ima in WinImage, it doesn't let me open the whole thing at once for copying. The first thing it asks me is to choose one of seven partitions to open. Here's the list of available partitions:

Disk 0, size 77808 MB, FAT32

Disk 0, size 16384 MB, FAT32

Disk 0, size 194560 MB, Linux

Disk 0, size 294896 MB, Linux

Disk 0, size 245744 MB, FAT32

Disk 0, size 245744 MB, Linux

Disk 0, size 821232 MB, Linux

I can supply the internal structures and contents of any of these if that will help.

So my question is how can I restore this backup reliably? I've thought of a few possibilities:

Rename the .ima to .img and try the standard restore procedure with Diskimager. I think the trouble I had with Diskimager in the first place was that it didn't recognize my computer's built-in card reader. That shouldn't matter with the Nook attached. But I'm not sure whether or not Diskimager will read the renamed .ima correctly, and by the time I find out with the standard procedure, my NST will be a brick.

Use WinImage and restore each partition separately, one at a time. This would mean not wiping the partitions currently on the NST, and it would mean that those had better match the originals or I'll be screwed.

Use a generic stock .img with the standard instructions, and then use WinImage to restore just the content that differs for each individual Nook. (I don't know where to find that unique content, so I would need help with that.)

Does anyone have a better idea or care to comment on mine? I could really use some help. TIA.

ETA: I was a little confused when I wrote the above. I had actually tried to use Diskimager (I got that part right, but I was also confusing it with Diskimage, which is not the same program and which didn't work at all). I did a trial restore using Diskimager from the renamed .ima (to .img) onto an SD card, and it appears to have worked fine, at least the progress bar was consistent with restoring the whole thing and Partition Wizard reports all the right partition sizes. (Windows can only see the first one.) So assuming there are no other gotchas, the standard instructions ought to work, just substituting Diskimager for Diskimage. Right? (I'd really appreciate some reassurance before I wipe out all the partitions on the NST!)
[Nook Touch Android Development] ApokrifX:
I’m 100% windows guy, so I use dd. The good thing, you know exactly what you doing

dd --list

Find you nook.

Than do backup:

dd if=\\?\Device\Harddisk1\Partition0 of=c:\nook-2012-06-22.img bs=1M --size –progress

And opposite for restore
[Nook Touch Android Development] Sun_Cat:
Here's a follow-up report, FWIW. After that successful trial restore, I went ahead and used Diskimager to write the .img directly to the NST. All seemed to be fine until I tried to refresh the library. After spinning for a while, it reported an internal error, exception while trying this operation. All other wi-fi functionality was intact.

To fix this, the first thing I tried was Touch-Formatter via CWM. That seemed to run successfully. It reverted the NST to firmware 1.1.0 and required me to re-register. All okay. But then when I tried to connect via USB to install the 1.1.2 update, I couldn't get a stable USB connection. The "USB Mode" window never displayed on the NST, and Windows would see the attached devices, but the contents would only be visible occasionally for a few seconds. The rest of the time it would say "no media." Not cool.

So I thought it couldn't get much worse, and I fiddled around with a couple of the other things on the CWM thread, including ROM-backup (in case of having to reflash a total stock image), and ending with install_stock_1.1_recovery.

Now finally everything seems all right. I do get the USB Mode pop-up and a stable connection. I was able to copy the 1.1.2 update file onto the device, and it updated normally.

I've no idea why the initial restore didn't quite work or what little tweaks actually happened on the way to total recovery, but maybe someone can learn from my odyssey.
[Nook Touch Android Development] ApokrifX:
If I read it right, you installed stock_1.1_recovery and that alone fixed USB connection issues?

Or you did something else as well?
[Nook Touch Android Development] Sun_Cat:
Here are the things I remember doing between having a flaky USB connection and having a consistently good one. I didn't retry the connection after each of these actions, so I can't really say which one or ones made the difference.

Booted into CWM, installed ROM Backup, rebooted.

Booted into CWM, installed stock_1.1_recovery, rebooted.

It's possible I may have cleared the Dalvik cache in there somewhere, but I think I only did that before I saw the flaky USB connection. I should have taken notes. :laugh:
[Nook Touch Android Development] ApokrifX:
Booted into CWM, installed ROM Backup, rebooted.

Does "installed ROM Backup" == restore from backup?

Booted into CWM, installed stock_1.1_recovery, rebooted.

IMO, that's nothing, you just replaced CWM recovery with stock one.
[Nook Touch Android Development] sebastienbo:
Unable to backup with nook glowlight firmware 1.1.5

Hi,

I'm unable to backup with this procedure.

Can anyone help with another procedure ?

After writing nooki.img to microsd:

The microsd card seems to have no effect, it just boots normally and i cant see the internal memory for diskimaging it.
[Nook Touch Android Development] Sun_Cat:
No. I installed the rom_backup.zip file from this post, which copies the content of the /rom partition onto the sdcard.

I agree. I don't see why either of these actions would have fixed the USB problem. But apparently something did. Maybe it just wanted to be rebooted several times. Maybe it needed time to settle down from all its adventures. :D I have no clue.
[Nook Touch Android Development] cy80rg:
Help needed - backed up ok, cant restore? Sits at "Your nook is starting up"...

Also, doesnt want to turn off... holding the power button in *usually* gets it to "flash black" (sometimes not) but it still stays on - with the "Your Nook is starting" screen.

---------- Post added at 07:10 PM ---------- Previous post was at 07:06 PM ----------

..

Also doesnt want to turn off fully. Holding the power button in *sometimes* get it to "flash black" - not always, and it just sits at "Your NOOK is starting" rather than actually turning off to blank screen.
[Nook Touch Android Development] TripleEYE:
Please & Thank You... ^_^;

First of all thank you (I've also tapped the Thanks button of course :) ).

Now forgive me for asking, but... Can this please be added to the main post?

I had to look through 7 pages of comments to find it, and I'm sure the lack of this link on the main post discouraged a few people from using this guide :angel:

Best wishes,

TripleEYE

EDIT:

Just noticed that on the Linux instructions the link is updated. So my request shrinks down to: Please update on the Windows post too. Thank you :)
[Nook Touch Android Development] TripleEYE:
Image Creation Failed with Roadkiler's DiskImager

So I've tried making a backup, and stumbled upon two issues (both can be seen in the attached image):

The Physical Disk size is 239.98MB and not 1.82GB (I've confirmed that Windows Explorer sees that same 239.98MB size).

I get an "Image Creation Failed (see attached image)

Please help :(

And thank you.

P.S.

I don't know if this helps, but DiskImager also recognizes my main SSD (of 476.94GB) under Physical Disk 0, and another unknown device (I have nothing else connected, but I'm using a Cintiq Companion and it's a special complicated designers' device [by Wacom] so I have no way of knowing if this is an internal disk of some sort... like, for example, the Recovery Partition that comes with this OEM system by default on the computer). This "unknown device" is showing as "Physical Disk 2 (Not Read)".

Hope you can help me find a solution.
[Nook Touch Android Development] ZenM:
Nook Simple Touch with Glowlight BNRV350 Noogie backup size

Model=BNRV350

Firmware_Ver=1.2.1

Firmware_Original_Ver=1.2.0

Backup image size=2000683008 bytes

I did the backup on two different PCs one running Windows (using Roadkil's Disk Imager) the other Linux (using DD).

---------- Post added at 08:41 PM ---------- Previous post was at 08:27 PM ----------

Hi I know i'm super late, but who knows may be this will help someone else. This is a guide I made for my own use, its important to understand that the Nook must be properly connected and

powered off

, plugging it to the PC should wake it. Also do not eject the drive, there is a difference between the device being UNmounted or ejected, in this case u can UNmount all partitions but you should not eject the Nook.

NOTE2 describes how I turn the device off.

4.2 - Noogie
SOURCE=http://xdaforums.com/showthread.php?t=1142983
NOTE1="What Noogie does is to grant access the Nook's disk thru USB, following instructions are to make a full drive image."
NOTE2="Noogie does not seam to have a Power Off or Exit option one must first unmount and eject then disconnect. Press the Nook's Power button to restart, one might need to press it more than once and for up to 20s, if done correctly the screen will flash doing like a negative image. Remove the SD Card then hold Power to restart it yet again, and lastly if needed turn it off again from the Nook's OS."
NOTE3="Backup Image Size for Nook Simple Touch Glowlight Firmware 1.2.1 MUST BE 2000683008 bytes."
4.2.1 - Burn noogie.img to SD Card.
4.2.2 - With the Nook turned off insert SD Card.
4.2.3 - With the Nook turned off connect to the PC.
4.2.4 - Make the Image, any software may be used:
Windows:
4.2.4.1 - Roadkil Disk Imager > Tab Store Image:
4.2.4.1.1 - Choose the correct physical disk holding 1.86GBs, do not pick a unit by its drive letter.
4.2.4.1.2 - Choose the save path.
4.2.4.1.3 - Press Start.
Linux:
4.2.4.2 - dd
4.2.4.2.1 - Find the Nook's dev, sudo mount or sudo df -h.
4.2.4.2.1 - sdb will be used as the dev address.
4.2.4.2.1 - sudo umount /dev/sdb*
This is not the same as ejecting the drive with KDE.
4.2.4.2.1 - dd if=/dev/sdb of=noogie_1.2.1.img bs=1M

4.2.5 - Reset Nook, see 4.2 NOTE2.
[Nook Touch Android Development] ingramsmith:
[MENTION=2718012]jocala[/MENTION] nvm
[Nook Touch Android Development] buf22783:
Tell me please, can I make backup/restore full-image file of my rooted NGP?

I remember procedure with "noogie" and disk image for Nook Simple Touch.

Is it possible in principle? (I know no sd-card on NGP)
[HTC EVO 3D] samrozzi:
so after reading a few posts about people emailing htc about the flashlight app, the clear ui at the bottom and the pano cam. for the hell of it, I emailed them and this is what I got back, if you find it useful cool, if not ignore it

Dear ...,

The Flashlight application and batterty widget were removed in a software update. We are currently looking into getting it back.

While the Panaromic Camera and Transparent Rosie were shown at CTIA or other sources, we have not developed those applications for production models at this time. Whether or not they will eventually be included has not yet been decided.

While we are planning to unlock the bootloader for the phone, we have no ETA on when the update that does that will be released.

We appreciate your continued patience in these matters.

To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number ...

Sincerely,

Travis

HTC

Want to see what others are saying? Have a question to ask other HTC fans?

Become a fan of HTC facebook.com/htc

Follow us on Twitter twitter.com/htc

Subscribe to our YouTube Channel youtube.com/htc

Explore our development resources developer.htc.com

We are unable to receive replies to this email account. Please visit us at htc.com if you have any questions or need further assistance.
[G Tablet Q&A, Help & Troubleshooting] GodsMoon:
I started getting a boot loop with VEGAn-TAB GB so I decided to downgrade to Beta 5.1 and now it won't boot.

adb won't recognize it, I can't get into Recovery, the screen will turn on, but its just black and will turn off after about 1 minute.

I've run the power down completely and recharged it, but still nothing.

Am I completely screwed?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
You're probably in an APX loop. Nvflash will fix you right up.
[G Tablet Q&A, Help & Troubleshooting] GodsMoon:
Thanks!

That did it. I appreciate the help.

For others I followed this tutorial: http://xdaforums.com/showthread.php?t=861950
[G Tablet Q&A, Help & Troubleshooting] goodintentions:
You appear to be new at this. I encourage you to go to my website linked in my signature.
[G Tablet Q&A, Help & Troubleshooting] GodsMoon:
Thanks goodintentions. I'm checking out your site now.

I re-flashed NVFlash (1.2 this time) and I can now boot into CWM.
[Vibrant General] hitman818:
Ive tested my dads sensation and it was very good the first few days. After about a week or so it lagged and became unresponsive. Whdn I ever I tried to flick the screen for tye corossal tye screen didnt move it all, it sometimes just moves a little and goes back. The lockscreen ring becomes unresponsive. When I pick it up it bounces back down. I know this a vibrant, but I just had to say it.
[Vibrant General] Dattack:
I was about to order it tonight but I will have to wait and see then.:(
[Vibrant General] hitman818:
The phone is pretty good, but after a week it slows down and becomes unresponsive drastically. There are barely a few third party apps installed on it.
[Vibrant General] hitman818:
Ive just tried to use the phone app and after I type in a number it took a while for the screen to respond to it.
[Vibrant General] jmcghee1973:
I ve had absolutely no problems with it at all.. I did learn to turn fastboot off because if you dont, when you power down your phone, its like its in hibernate instead of actually turning off. I think this is the majority of peoples problem with this phone.
[Vibrant General] VeryCoolAlan:
I guess you should root and install custom ROM then use it for a week.
[Vibrant General] VICosPhi:
Unfortunately he'll have to wait until HTC unlocks the bootloader for Sensation.
[Vibrant General] hitman818:
That will probably be a while.
[Vibrant General] suchavibrantthang:
cmon, is it really that bad after a week with those specs? i know its the first batch of phones and all. maybe a simple reboot may help once in awhile but i can't imagine all the phones being unresponsive after minimal use.
[Vibrant General] cpittman:
No problems here either ;-)
[Vibrant General] larryvand:
No problems with my Sensation.

No problems with my Sensation. It is super fast. You may want to try turning off fast boot and rebooting the phone. I've had it since day 1 that has been available and has been super fast ever since. No lag whatsoever.
[Vibrant General] xhausted:
HTC ranting

me and one of my friends were on HTC's facebook page blasting them and on they responded to our ranting.
[Vibrant General] Paging Dr B:
Correct. Turned off fastboot and the system started behaving the way it should. I've had mine since Friday and don't regret it one bit. I think this thread is not titled correctly. I love my Vibrant, but i'm liking the Sensation even more. The Sensation isn't a huge jump performance wise from the Vibrant, but it overall feels more powerful. It doesn't get bogged down, and browsing on it feels nice and solid. I'd buy it again.
[Vibrant General] archie53:
Hows the size difference compared to the Vibrant? Meaning is it a huge difference in size or just minor. Haven't had a chance to lay with one and wonder if its too big.
[Vibrant General] gun:
I had both side by side same size, sensation is thicker but it is round and you don't feel the thickness it feels better in hand than vibrant I hate screen on sennsation colors are washed compared to vibrant and vibrant is lighter and a lot cheaper too.
[Vibrant General] archie53:
Cool, thanks.
[Vibrant General] Paging Dr B:
Lol, the last thing you want to do is to compare any non-SAMOLED screen to a SAMOLED. I miss the vibrants screen (not pixel density), but by itself the sensation does have a nice screen. It's black aren't as black, and it's viewing angles are the best but it's still good.
[Vibrant General] kawika:
I liked the sensation when I played with it. That sense3.0 or whatever looked pretty cool and I'm not really a sense kinda guy.
[Vibrant Q&A, Help & Troubleshooting] forest2087:
I just recently flashed phiremod Vibrant V3.0.1, everything working great, but clock has no timer and stop watch anymore...

Anyway to add the original froyo clock back? or restore it to the stock one?
[Vibrant Q&A, Help & Troubleshooting] yalkowni:
you should try downloading bloater ....it downloads and installs all the stock apps

THanks button if i helped
[Vibrant Q&A, Help & Troubleshooting] forest2087:
great stuff, worked like a charm, thx
[Galaxy 3 General] 2Triangle:
I downloaded InDroid v4.3 and flashed SG3 to InDroid v4.

When i downloaded InDroid 4.3 there was no update.zip but there was InDroid v4.3 Big_Update.

So when i went into recovery mode (I put the Big_update on the 2-primary partitioned SDCard) and tried installing update.zip from the sdcard.

But it said E:cant mount sdcard

And now im stuck with a phone which keeps on looping InDroidv4!!!! whenever i boot it...

My question is... What do I do to make the update work?
[Galaxy 3 General] brajesh.sharma87:
first of all there is no CWM recovery in indroid 4.0 if u have flashed the 4.1 version then go to recovery > install from sd > choose zip file (indroid 4.3_big update)

*u r currently doing "SD card:update.zip"

for more info, please refer to the video posted on both indroid thread for update.