yashsingh1/xdaforums huggingface dataset:
[Epic 4G Q&A, Help & Troubleshooting] Crwly:
Please post the answer if you figure it out. I'm having the same problem.
[Epic 4G Q&A, Help & Troubleshooting] atharchian:
Have you tried fixing permissions followed by a reboot after pushing the apk?
[Epic 4G Q&A, Help & Troubleshooting] lviv73:
Never minnd,it appears that i removed apk needed fornmarket to function now they all work.
[Atrix 4G Themes and Apps] Bracemg:
Has anyone ported the WP7 keyboard to the atrix? I like the tall buttons.
[Atrix 4G Themes and Apps] neer2005:
https://market.android.com/details?id=com.aitype.android&feature=search_result

That has a WP7 skin
[Atrix 4G Themes and Apps] Bracemg:
Yea thanks. I tried that one out and its pretty good - but it doesn't have the ability to save words down that you type like the gingerbread keyboard does.
[Droid Eris Android Development] phrite:
i moved on to a new phone, still have my eris and im willing to test roms. just pm me if you need a tester.

might be willing to sale it.
[Droid Eris Android Development] orkillakilla:
I just dug my old Eris out of the closet and am rooting it now. I'm willing to test as well. Just note that I wont have service other than wifi

Sent from my HTC GingerBolt powered by the lastest Synergy ROM
[Droid Eris Android Development] sunilromy:
Test mine, DeadlySense and help me in improving it ;)
[Droid Incredible General] patsfan1130:
I just filed a claim with Asurian for my daughter's Dinc expecting to be told a Dinc 2 would be sent but I didnt. She's a bit bummed as she was hoping for a Dinc 2. Oh well. Just thought I would share for those of us who still love the original.
[Droid Incredible General] DustinBooyah:
Yeah, my GF's daughter just got one after she saltwatered her phone and made a claim. Perhaps there are different distributors for different regions, and a few of them still have some left in stock
[Droid Incredible General] tolymatev:
I got inc2 with froyo. Rooted the same night running miui. Sooo freaking fast.
[Droid Incredible General] Kiboe:
i got mine from wallmart for 20 bucks, i guess they have a large backstock of them at the store's wireless center and just trying to get rid of them.
[Droid Incredible General] Tyuteo148:
Buying

Hmmm...interesting, I've been wanting to buy a droid incredible but cant find it anywhere other than ebay. When I called Verizon they told me they had no more in stock... :-( yet apparently they do? I'd like to buy one if anyone is selling or if someone could help me find out how to get one from verizon it would be great. thanks in advance

edit: not looking to buy one without contract, way too expensive lol
[Droid Incredible General] cpuspeed:
Is this a joke? What city? New subscriber or price without plan?
[Droid Incredible General] Kiboe:
my mom has multiple lines on her account (can't get rid of them, my sister and me were on her plan until we broke off to our own a year ago, so they've been sitting)

she let me use her rebate on one, and no, not a joke, Grand Island Nebraska, the wallmart on Diers Avenue bewteen the gamestop and office max.

so, new subcriber plan, yes
[Nook Touch General] ceterumcenseo:
I hope I'm posting in the correct place.

I think I've bricked my Nook Touch (tell me it isn't so!). The problem is as stated in the subject line. Now it won't turn off or respond at all to hardware or touch. Is there at least a way to get the screen back to "Read Forever"?

Please help, and let me know if you need more information!

I'll be so grateful if this problem can be at least partially solved.
[Nook Touch General] doom_ft:
try to remove sd-card and reboot it
[Nook Touch General] ceterumcenseo:
I tried that; the Nook Touch will not reboot. Thanks for replying. :p

Would the zip file Nook Simple Touch Full_Factory_Restore.zip work for me in this scenario? If so, where can I get the file?
[Nook Touch General] Aridon:
Its almost impossible to brick this device. Try this first.

Hold power firmly for 30 seconds.

let it go

Wait 10 seconds

Hold power again for about 10 or so seconds the screen should change and you should reboot.

Try this with the SD card in and out. You can also try and repeat the step of writing the .img to your SD card. Download the file again or verify the checksum in case you got a bad download.

The screens will not necessarily change if you are stuck in a boot loop and power down. Regardless if it doesn't boot 8 times it will revert its pretty much impossible to brick the unit. You can also try to power off via ADB and or try the script that forces the 8 failed reboots.

____________________

Edit I missed that it appears you intentionally formatted the device? What exactly did you do?

Also if you made a back up of the partition prior to formatting (not sure exactly what you did or why you did it) but that should have been your first step prior to doing anything exotic so you can replace the files necessary. I'm not at home otherwise I'd post the partition contents for your restore I'm sure you can find them on the net somewhere or here. I think the nook color root wiki may have the Nook touch back up files I'm not sure though. Either way its trivial to pull them and post them. Those of you that may do this make sure your account information is wiped first prior to making the back up for him.
[Nook Touch General] nikiiv:
Exactly which partition you formatted? The one normally exposed during USB connection? In this case power it off (by holding the power button for few seconds and selecting power off) and then do a hard reset

Hold power button and the bottom two side buttons until the screen starts to flicker. Release power button but hold the side bottom buttons until you see a hard reset screen

After reset the data partition will be as good as new.
[Nook Touch General] Kurukshetr:
Rooted Foreve screen - the brick

Hello everyone. I'm from Russia. And I have the same problem: Rooted Forever on the screen (I have formatted sd card by Mini Tool Partitition Wizard - Delete all partititions) when the SD card was into Nook and my Nook is the brick. And i can't send my Nook to B&N. None of your advices did not work. But I still have some hope. Maybe my experience will be usefull for you.

I have pushed 2 bottom buttons & power button for 30 seconds. Then 10 seconds pause. Then I have pushed 2buttons+pwr for 30 seconds again. And Nook has turned off. But the screen was completely dark. Then I turned it on and saw Rooted Forever. After that I repeated 3 buttons holding and turned the nook off. Right now my screen is completely white.

And one other thing. I also have tried nookrestorer program . I've mount an image on SD. Put it into nook. Turned it on. Script on the screen: wait for 10 sec, turn off yor nook. Take out SD. But it does not work.
[Nook Touch General] Drakkim:
I managed to lock my Nook up on boot right after I rooted it, but got it to unlock and revert to factory settings. Mine was frozen on the "Read Forever" screen and would only flash when I turned it off (something I've not read anywhere else) but this may help some of you... Don't try to do a factory reset and immediately root it again, because you may have to update the Nook again first!

First, remove the SD card, then power it off (hold the power button for 20 seconds until the screen flashed) then, letting go of the power button and immediately pressing and holding the power button again and the two bottom side buttons (I think for 10 seconds?)

The Nook would still sit on the "Read Forever" screen a minute or so, then started doing a factory reset, wiped everything including the data section and the updated software.

I had to re-update the Nook to 1.1 and then could re-root it.

---

Edit:

I realized after I posted this that I lied. Sorry. That didn't work for me, but I discovered that I could still access ADB over USB with my Nook while it was frozen on the loading screen... so I did this from my PC:

adb shell

echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt

reboot

Credit to page nookdevs dot com/Flash_back_to_clean_stock_ROM (Not enough posts to post links yet, sorry!)

Note that you do have to have the ADB installed, but I think that's key to a lot of the root methods...
[Nook Touch General] ros87:
Bricking the NST is quite easy, just boot with Noogie and write some garbage onto the flash.

Lots of people do this by trying to write incomplete backups back to their NST.

If what you write is big enough to reach the /rom partition you're basically hosed.

This is a very bad advice, the /rom and /factory partition contains data unique to every NST such as MAC address, serial, board serial, EAN, private and public keys, etc..

Using a backup from another NST can and will cause troubles for you and the person owning the NST the backup came from.
[Nook Touch General] jack ng:
My NST was bricked as well, after a Salsicha-image write session failed. Permanently stuck in the "Rooted forever" screen no matter what I pressed. Prior to the write, I have deleted ALL the partitions on my NST and then it wouldn't boot, so it seemed gone forever.

Yet it turned out that my NST can still boot with the Nookie image on a microSD

( from the BACKUP/RESTORE N2E Win7 thread). Connect it via USB to the PC and managed to restore it using my backup image. Eventually I did did the Salsicha root successfully. My NST is now rooted with 1.1.

I don't have specific advices, but the NST does seemed hard to be properly bricked. Given my experiences, I actually wonder if the NST hardware could bootstrap itself entirely from the microSD, irrespective of the state of its internal flash.
[Nook Touch General] HinDMosT:
Just solved this thing: formatted microSD with Noogie Image, then deleted all partitions and than flashed my backup image back and Nook is working fine now!
[Nook Touch General] ros87:
Yes it can.
[Nook Touch General] aknas22:
Bricked Nook

I've also formatted my Nook when I was thinking that I was formatting the sdc. I've tried installing the nookRestore img and nT2-Recovery but both of these get to the screen where it says to wait but then the Nook won't reboot. My Nook can no longer be seen by my computer so isn't showing up in device manager. I've also tried the various boot tricks manually. I also lost my backup of my Nook when I had to reinstall Windows a week ago. If anyone could help that would be great!

Thanks.

Edit---

I've found my backup image but it says Install Failed: Please power off and back on. I do this but it says the same thing. It shows up for a few seconds in device manager right after I power it on but the device id is wrong, USBSTOR\DISK&VEN_B&N&PROD_EBOOK_DISK&REV_0100\11223344556677&0. And then it disconnects in a few seconds.
[Nook Touch General] ros87:
If you formatted your NST, Factory Restore (and thus n2T-Recovery) will not work as you removed the partition containing the actual Restore image (partition 3)

What size is your backup image?

The unknown device you see for a split second at boot can be ignored, this is normal behavior.
[Nook Touch General] aknas22:
It's 77.5 megabytes, I made it with Roadkill but I'm not sure if I did it right. I got it best the install fail screen. I'm not absolutely sure that I formatted the Nook but since none of the recovery methods or other images work that's the only thing I can think of. Also its no longer communicating with my computer properly.

Thank you for your reply.
[Nook Touch General] zholy:
I remember that there was a file(image) that works on the same principle as Noogie, but it will start the factory reset instead. Have you tried that ??? Unfortunately I don't know whether it uses/refers to the "formated" factory partition or it makes it's own. I think yo might find it in one of the threads, about rooting the Nook.

P.S. : the size of your backup file is too small :( ... it has to be about 1.8G
[Nook Touch General] ros87:
Your backup is worthless, don't bother with it.

Also Factory Restore, n2T-Recovery etc won't help you.

Check your PM in a few mins.
[Nook Touch General] aknas22:
Thanks for your reply, yea my backup is missing something, I thought I found a my good one but it doesn't seem to be. I found those other images but as ros87 said they don't work either.
[Nook Touch General] ajjdowning:
Keep getting "Install failed" screen

Well, I seem to have bricked my NST as well.

I was trying to unroot from TouchNooter by restoring what I now know was a bad backup image (only 77MB). I am also certain that the NST was reformatted as well. :(

When there is no SD card in the NST it is stuck in the "Install Failed" screen. It can reboot but just goes back to the "Install Failed" screen.

I have located the original backup image of the NST when it was fresh out of the box and think it's a good one (1.92GB), but I am unable to restore it while the nookie image is mounted in the SD drive. I have also tried the two manual restore images (NST-Recovery) and although they ran succesully they did not fix the problem.

Is there anything else I can try to get my NST working again or is it bricked forever?

UPDATE: SUCCESS!

Just in case anyone else runs into this problem:

I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.

Note: When disk imager was finished restoring it gave me an error, but I went ahead and booted up the NST anyways. My Simple Touch is back to it's factory-fresh state and all is well again :D

*Many* thanks to everyone who posts in this forum. Going through all the posts helped me troubleshoot and eventually unbrick my Nook SimpleTouch.
[Nook Touch General] erics88:
Life saver!!!! Thank you!!!

THANK YOU soooo much!!! lockdismount.exe save my NOOK. Couldn't restore my backup img using roadkil's utility but after reading your post I'm all set. :D

Thanks again.
[Nook Touch General] acz1970:
overwritten rom and factory partition

Hello, i am one of those unlucky/incompetent user who overwrite those partition. My experience is this: I can use (read, browse etc) other device's ROM (with different serial etc) on my NOOK, but if I want to deregister/or re-register my device at B&N, the process leads me to an ERROR message at the end.

I have no idea how to solve this problem. Maybe editing several files on Boot partition and Factory partition. Or maybe there is a way to erease these data from these file (resetting) I d not know. Or maybe there is an ORIGINAL rom without any device specific data, I don't know... and I am a bit hopeless.

Do You have any idea?

People at B&N do not understand the problem at all...

Thanks in advance for any help!

Tamas
[Nook Touch General] roustabout:
You're in a position to try an experiment, assuming:

- you have access to linux (a vm will do) so that you can read and write files on your Nook partitions while booted from Noogie (this may be possible in Windows, but I know it works in linux)

- you either are comfortable using a linux text editor or care to install notepad++ (which will save the files you need to edit in the right format)

- you know how to pull the MAC address of your nook off of your wireless access point

- you would go into the /rom partition and look at the devconf files.

Basically, you need to try locating the file that *tells* the Nook what it's MAC address is, and the file that tells it what it's serial number is, and correct them.

Right now, they are both describing the source nook that your image was pulled from.

I have been curious but not curious enough to devote the time to the experiment to see what would happen if a Nook was imaged from one of the recovery images floating around, booted to noogie, and had those two files updated to reflect the actual state of play on the Nook.

(the real serial number for the device is located below the flap holding the sdcard)

Even if this didn't work for you, I don't think you'd be worse off - worst case, you'd need to reimage with the not-working-right recovery you tried to use and you'd be left not-working-right as you are now.

Best case, you would do that, then register your device back to the email you first set it up for and the reg would go through.
[Nook Touch General] Paarc:
Help with Nook Glowlight

I accidentally deleted nook software using Mini Partition tool wizard.

Then i tried to copy factory zip 1.1.5 to my SDcard, and I.ve restored it in my Nook, but nothing happened, I keep receiving message Your NOOK encountered a problem that requires a system restart, and he keeps restarting.

After that read that I need to restore it with Roadkil's Disk image, but my SD card and NOOK says Disk not ready, or something like that, and my SDcard keeps formating...

What to do now, I've bought nook un US and I have nobody to help me bout Nook in this ****in Croatia...

I am desperate..

Please help..
[Nook Touch General] roustabout:
OK, were it me:

- I'd pull the SD card and see if the nook could restore itself from the onboard recovery image

Assuming that didn't work:

- I wouldn't try to install the factory zipfile from microSD

- I would get a linux box going, either with a physical linux box or using vmware player

- I would instsall testdisk on the linux box

- I would boot from noogie, connect the noogie-booted device to the linux box, and run testdisk against the Nook to see if I could recover the original partition table (tehre are 8 partitions in the original table)

- if I thought that had worked, I'd reboot the nook still into noogie mode and the linux install, then try to get the contents of the original ROM partition copied out - this contains some unique device identifiers

- I'd then power off the nook, pull the SD card, and let it try to boot. If the testdisk recovery worked, it might be possible to trigger the onboard restore, which is the best possible outcome

- if that didn't work, I'd try using dd to restore a backup first to an SD card (to confirm that

dd if=mybackup.img of=/dev/sdX bs=1M

did indeed give me an SD card with 8 correct-looking partitions, then with

dd if=mybackup.img of=/dev/sdZ bs=1M

where Z is the disk number linux assigns to the noogie-booted NST

Good luck - hopefully, a partition recovery can work for you to recover your original partition table and files
[Nook Touch General] FerdiBen:
Backup image

Hello everyone,

I've got the same problem of deleting all partition using "MiniTool Partition" and now the only back up I have is not working (only 76 MB).

Could you tell me were I can found a backup of all partitions (about 2 GB)?

Thanks in advance.

PS: Sorry for my English, I'm Italian.
[Nook Touch General] cy80rg:
Bricked NST? Valid backup - 1.82 Gb?

Morning guys,

Have rooted all my HTC phones from here over the years, so pretty savvy at this (I like to think!).

Tried to root my GF's new NST using this guide on LifeHacker...

http://www.google.com/url?sa=t&rct=...tNwGX3LqXuUIPr5kBcqug&bvm=bv.1355534169,d.d2k

Didnt work (sat at TouchNooter screen for HOURS), so gave up and tried to flash backup of original image to the unit (1.82 gb).

That didnt work either.

Tried to reinstall using Touch-Formatter V2 (from here... http://xdaforums.com/showthread.php?t=1475613 ).

Install "worked" - but refused to reboot (sits there saying it is, but doesnt).

NB - as part of the guide I found to reflash the backup image I took, I deleted *all* the partitions on the Nook.

TFV2 (as above) installed fine (apparently) but couldnt read any of the "Log" files on E: - looks like it's not rebuilt the partitions?

UPDATE

I've now gone and bought my GF a new NST - taken out of the box a few minutes ago, sitting there charging.

QUESTION: Can I take an image of this new NST (unregistered etc) and rebuild the partitions from that? Anything of use on the new NST (bearining in mind it's literally "Factory clean") - and that I've got the image of my GF's registered device?

Found this in a post on here...

"

I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.

"

I must say I didnt have this issue, but I'll give it a try anyway (I am running Win 7).

Any help guys?

Thanks in advance! :)

---------- Post added at 09:53 AM ---------- Previous post was at 09:43 AM ----------

UPDATE

I think my problem was I didnt check the original FW version, I've tried to update using "TouchNooter 2.1.31" - of course if the original FW was " 1.0.0 or 1.0.1", I should have used the older version of TouchNooter, as below?

Hope this gives you NST guru's some more clues as to what I've jiggered up here! :)

"

Don't assume that a newly purchased N2E will not have the 1.1 upgrade already installed. Check Settings->Device Info->About Your Nook Simple Touch'

To install the update, place the zip file in the root folder of your Nook Simple Touch. Ensure its name has not been changed (nook_1_1_update.zip). Then eject the Nook and put it to sleep. It should then update itself.

for 1.0.0 or 1.0.1 Download GabrialDestruir's TouchNooter 1.6.24 file 24 Jun 2011.

for 1.1 Download GabrialDestruir's TouchNooter 2.1.31 file 31 Jan 2012.

"

Read more: http://nookdevs.com/Nook_Simple_Touch/Rooting#ixzz2GcbYd9oa

Under Creative Commons License: Attribution Non-Commercial Share Alike
[Nook Touch General] idoraz:
Same problem here :(

Hey Ros87, I'm experiencing the same issue I'm afraid.

Any chance you can send me the restore solution too? PLEEEEASE! :)

Thanks.
[Nook Touch General] Nookienoob2:
I'm similarly pickled, I need a working image to get back my reader (I promise not to use it with B&N; I scrapped that and use(d) it for reading Gutenburg books). ATM my nook shows the CWM icon but is hosed (obviously writing that ROM wasn't a good idea). Even Nookie just shows the SD card from Partition Wizard. Clockwork can boot but gives errors as it can't see the cache (cos it's not there) and the repartitioning tools I've seen don't create /boot /rom or /cache.
[Nook Touch General] Renate:
For everybody with the same problem.

The first question is: Did you try to fix it by using an update or by writing a raw 1.9GB image to your Nook?

If you wrote any sort of 1.9 GB image then all is gone.

If you (in a fit of madness) repartitioned or deleted partitions there may be hope.

Updates do not regenerate partitioning.

If you have not overwritten your Nook with 1.9 GB image, then take the time now to backup whatever you may have on it.

Put noogie on an SD card, boot up, use Win32DiskImager to make a copy.

It might make sense to try to recover the files in the /rom partition even if you don't think that you'll be needing them.

imagefix mybackup.img /pnst /x 2

You can try repartitioning with nookpart.sh script to be run under ADB on CWM.

imagefix.exe and nookpart.sh are in the signature.
[Nook Touch General] Nookienoob2:
small progress

Yup, it's gone.

This morning before reading this I booted my PC to puppy linux, (the nook to nookie) and repartitioned the Nook's storage using gparted.

I may well have the layout wrong, so your "nookpart.sh" will help there.

I have copies of the BOOT partition files, but not ROM; so I looks as if I'm a bit stuck; I think I read that one could use someone else's image, as long as you amended the mac address, and serial number (for wifi & B&N's registration).