So, I originally had this posted under the Nook Color section, but apparently I was wrong in thinking what I had was a Nook Color (despite the box it was purchased in saying Tablet (color) and google telling me the same thing). Regardless, here is my problem.
I recently received a used Nook from a family member. They had bought a new tablet, and didn't need the Nook any longer. The problem with the Nook, however, is it would no longer turn on or even charge. After opening the back (and thus voiding the warranty), I discovered the wires connected to the power button had come loose. I reattached them, put the Nook back together, plugged in the charger and turned it on. Everything seemed fine, until I tried to erase it.
I've tried several different attempts, from simply tapping 'erase and deregister' to holding the power and home buttons, and pretty much every other way B&N's tech support told me. Each time, I get the same error message telling me to try again or contact customer support.
Likewise, any changes I make to the Nook (wallpaper, deleting some of the previous owner's books, etc) revert back to the way they were before each failed attempt as well as after simply turning the Nook off and back on.
I even tried connecting the Nook to my computer via usb cable to delete the old books, however once I eject and disconnect the nook, all the books that were deleted remain, and the books I attempted to add weren't there.
Finally, a problem with the SD card. If I have any .epub books on it, after a few minutes the Nook blackscreens and remains unresponsive until I hold the power button for 20 seconds, release, then press again to turn it back on.
The model number is BNTV250-A. And I have tried every option I can find through google search to repair this thing myself, and am at an utter loss. Though, most of those attempts were from when I thought this was a Nook Color, so perhaps I've just been trying the wrong methods, but I've attempted the 8 failed reboots, as well as attempting to boot from the SD card. Neither of which worked.
Now, B&N tells me the Nook is pretty much trashed and that I need to upgrade to a new one. I refuse to believe this until I've tried every option I can find. So, if someone can give me any help on trying to get this thing fixed, I'd be greatly appreciated, or if I'd just be better off buying a new tablet altogether.
I will continue to google possible solutions while waiting for someone to come up with something here.
sounds like you'd be better off buying a different unit. the model you stated (BNTV250-A) is indeed a Nook Tablet, probably a 16GB model (i have the same one) but yeah it sounds as though it's pretty much FUBAR at this point. sorry.
I was afraid of that. I mean, it's still good for playing movies and reading pdf files and such. But loading epub files onto the sd card causes it to go all crazy and such.
The thing that gets me is the rooting issue. I just tried rooting again, and absolutely nothing changes. It just keeps going right back to the way it was when my mother gave it to me. I even attempted to use the recovery mod to completely wipe all user data from the NT, with the same result.
I am at a complete loss and am willing to go with your pretty accurate description. This thing is FUBAR.
It's a known issue. Your only option is to boot from sdcard. Here you can find recent images
Related
I am having a repeated issue I was hoping someone has seen or could help me with.
I'm on the default rom w/ the TnT Enhancement pack and overall I LOVE the device. One thing that is literally killing me is trying to get data to/from my device.
I have tried USB linking to my Win7 64bit system as well as copying data to/from with Astro and the microSD card and more times than not either during or after any file copy/move activity the device locks up, needs to be hard booted and then I'll get the 'scanning SD card' message in the notifications and the tablet locks up hard, and becomes unuseable until I reboot about 10xs and finally it starts to return to normal.
I've tried formatting EVERYTHING and re partitioning to 2048 & 0 w/ clockwork and doing a fresh NVflash and reupdating/TnT Enhancement, etc...with similar results, so I'm not sure at this point if it's my microSD the internal card, some sort of hardware or overall software issue.
I love this device, but I'm borderline frustrated enough to return it, only problem is ALL the other tabs are WAY too expensive for what you get! ($400 is reasonable $600+ is stupid - I can get a laptop for that much - which I already have, and the tablet isn't nearly as capable/more just convenient)...
tullywork said:
I am having a repeated issue I was hoping someone has seen or could help me with.
I'm on the default rom w/ the TnT Enhancement pack and overall I LOVE the device. One thing that is literally killing me is trying to get data to/from my device.
I have tried USB linking to my Win7 64bit system as well as copying data to/from with Astro and the microSD card and more times than not either during or after any file copy/move activity the device locks up, needs to be hard booted and then I'll get the 'scanning SD card' message in the notifications and the tablet locks up hard, and becomes unuseable until I reboot about 10xs and finally it starts to return to normal.
I've tried formatting EVERYTHING and re partitioning to 2048 & 0 w/ clockwork and doing a fresh NVflash and reupdating/TnT Enhancement, etc...with similar results, so I'm not sure at this point if it's my microSD the internal card, some sort of hardware or overall software issue.
I love this device, but I'm borderline frustrated enough to return it, only problem is ALL the other tabs are WAY too expensive for what you get! ($400 is reasonable $600+ is stupid - I can get a laptop for that much - which I already have, and the tablet isn't nearly as capable/more just convenient)...
Click to expand...
Click to collapse
I'm kind if unclear about your problem. Is it hanging only when you're copying stuff between /sdcard and /sdcard2?
I'm asking because you mentioned USB, but I didn't think you could xfer directly to/from /sdcard2 over USB.
If that is the case, have you tried a different microSD card?
Jim
I've tried USB xfer from computer to /sdcard as well as using multiple microsd cards to transfer data to the internal gtab memory, all seem to have the same results, when moveing external data to the gtab, it suddenly seems to cause some sort of file system corruption (as best I could guess). last round forced me to go as far as re-doing the entire device to bring it back to a stable state!
Since you mentioned returning it I would suggest exchange as this sounds like a problem with your device. Could have a bad card reader or the card is just not seating correctly
Hi,
A couple of comments:
- does the enhancement pack you have have that dataloop thing? I've seen some posts mentioning corruption w dataloop. Maybe try w/o the enhancements?
- for the scanning /sdcard2 thing, maybe try adding a file named .nomedia (period followed by nomedia) in /sdcard2. That's suppose to prevent the mediascanner from scanning the dir plus subdirs.
Jim
I'm about done with this thing. I've tried everything I can think of and I can't get away from the thing locking up (from full stock OTA gtab to the TnT custom ROMs).
1)The first Gtab I had the screen wasn't responsive to touch (had to hit it two or three times to get it to recognize you wanted to open an App. returned to SEARS
2)The second Gtab I got, when I powered it on for the first time it had a line across the entire screen in the LCD of bad pixels (dead pixels/whatever - something was wrong with the screen) - took it back AGAIN
3)This Gtab locks up whenever I use the microSD or USB transfering files to the thing. WILL BE RETURNED
I'm convinced that these things are the biggest pieces of sh!t on the planet. I've spent (and I'm not even stretching the truth) probably 40 to 60 hours trying to get this thing to work LIKE A NORMAL DEVICE - all I want is something to: browse the web, view videos and read epubs on - I'M NOT ASKING FOR MUCH, a simple device that can't accomplish THOSE SIMPLE TASKS - SUCKS.
I'm happy to think that the money viewsonic (or whomever) spend to build these three BAD devices is out whatever it cost them, given my trouble. TiD!
how to fix
Go to settings, applications, system applications, media storage and clear data. It worked for me.
tullywork said:
I'm about done with this thing. I've tried everything I can think of and I can't get away from the thing locking up (from full stock OTA gtab to the TnT custom ROMs).
1)The first Gtab I had the screen wasn't responsive to touch (had to hit it two or three times to get it to recognize you wanted to open an App. returned to SEARS
2)The second Gtab I got, when I powered it on for the first time it had a line across the entire screen in the LCD of bad pixels (dead pixels/whatever - something was wrong with the screen) - took it back AGAIN
3)This Gtab locks up whenever I use the microSD or USB transfering files to the thing. WILL BE RETURNED
I'm convinced that these things are the biggest pieces of sh!t on the planet. I've spent (and I'm not even stretching the truth) probably 40 to 60 hours trying to get this thing to work LIKE A NORMAL DEVICE - all I want is something to: browse the web, view videos and read epubs on - I'M NOT ASKING FOR MUCH, a simple device that can't accomplish THOSE SIMPLE TASKS - SUCKS.
I'm happy to think that the money viewsonic (or whomever) spend to build these three BAD devices is out whatever it cost them, given my trouble. TiD!
Click to expand...
Click to collapse
Dude, I've been telling people on here for days. Go buy an ipad and leave us gtab fans alone. My benchmark is at 3000's while having half a dozen apps running and I'm happy with it. My screen is too sensitive to say the least.
So I have a bad feeling here. I was fixing my ad hoc problem and accidentally renamed my /system/bin folder to "bin - Copy" not sure how I did it, a finger swype n boom it was that way. Could not change it back. Rebooted and now I can't get passed the Eee Pad boot screen. Any one know how to fix this?
I've got a similar problem.
There should be a sollution where you start up, holding the powerbutton and volume up. You feel a vibrate and the screen stays black.
with this way you can connect your transformer, and access it. But I don't know how.
Windows reconiges the device as and APX (under linux as an Nvidia device) But I can't connect to it, don't have the drivers and so.
So is anyone knows how to access the prime trough this method, our problem could be solved using adb pulling and pushing these folders.
Greets
If you connect it to your computer can adb access it??
Nope. Going to try a couple more things this evening.
Sent from my PC36100 using XDA App
Well, I tried a bunch of different things: microsd recovery, wipe data, recovery, "up volume/pwr button", broke down n called Asus. So here's what happened in case anyone else comes across this thread: microsd method to flash firmware=nothing, anytime I entered recovery Andy laid down and opened his chest cavity and red triangle !, wipe data done. signature match=freeze up at that screen, no reboot. hard reset with paper clip=nada just reset to frozen eee pad screen. I have linux 11.10 and 10.04BT on another hdd so I booted to both b/c I read a post somewhere about booting the prime by holding up volume/pwr and its supposed to be some kind of nvidia diagnostic mode. Interestingly in windows it changed from an unknown MTP usb to APX device doing this, in Linux it never even came up either way. I don't know enough about this, so I tried searching and reading=nothing fruitful. I'm a Linux and ADB noob so I read and read and read some more, but after trying a few walk throughs, my Prime just seems to be dead. So I called Asus and played dumb, said it froze after trying to update to ICS. He walked me through these other steps I mentioned to no avail. Then he gave me an RMA# so I went ahead and mentioned the excessive light bleed and non-functioning GPS. He noted those issues and now I'm sending it in apparently. I was REALLY hoping to avoid this b/c this was my fault, but my experience with the Prime has prompted me to ad my 2 cents/rant in the general thread.
I wish this had a better outcome, but with the bootloader locked I and many others have been unnecessarily doomed to RMA.
Well that sucks big time... hope you get another soon
hoping to hear about an update to this other than sending it in. unfortunatley i have just done the exact same thing.
There are APX drivers in the dev section. My Prime changed from APX device to Asus Transformer prime APX mode when I installed them. After that I don't know what to do; I think we need an nvflash for the Prime or something.
Mine went into APX mode after the last OTA update failed and won't leave APX mode for anything, so I was looking for a way to connect to it to flash an update or something, but no luck so far. Maybe Asus will release a tool for us to fix a failed OTA update, would be a lot better than sending my tablet away for a month so they can do it.
I searched and searched for this too. Couldn't get anything to work.
As for an update, as of about a couple hours ago, looks like they are sending me a new tablet. Has a different serial number listed as "ready to ship" and states "original serial number: C1O....." which is the s/n of the tab I sent in.
So we'll see if this one comes with no light bleed and working gps. Don't think I'll be screwing this one up! Gonna be extra careful...
I was in the same situation, stuck. I tried everything you did as well and nothing. "Doktaphex" gave me this link http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119 in my post and it worked perfectly. I was sooo damn happy to see Andy actually working instead of laying down when I entered RCK
Oops...shoulda read through. Hehe sorry bout that :/
That would've been just one more thing to try on top of all the other things I tried. If it actually works, then ALL the other ppl that say to use this microsd recovery method need to read your link and actually know what they are talking about. I read method after method and tried them all to no avail.
I did this and that worked for me : http://forum.xda-developers.com/showpost.php?p=22857274&postcount=21
Got my replacement Prime today. Putting it through the paces now. GPS isn't noted on the box, but I don't remember if it was on my first one. Still a C1O serial. Went ahead and updated first, bc I don't care about HC.
GPS: Can see 4 but signal stays under 35, no locks. will try again tom from Dallas
BT/Wifi issue: None, Does not degrade
Wifi range: Not bad, little better than my phone
Light bleed: Better than last, but still 5 spots along bottom and right side
Side Note: put a 64gb microsd in the tab and a 64gb microsd w adapter in dock. Both work fine, now up to 192gb.
I'm very happy Asus replaced this so quick (week and 1 day). I'm not a picky person so I am fine w the lesser light bleed, I will never use gps but it would be nice to have as an option. I bricked my first tab and would gladly have paid for them to reflash it, heck if they called me even now and said, "hey, we found that you bricked your own tab, here's a bill to reflash" I'd gladly pay it. So far I have to agree w everybody's sides to every issue, which is crazy to think, but everyone has legitimate points. Except ppl that expect Asus to still warrant after unlocking n flashing roms, that's ridiculous.
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
First, sorry for my bad English. Hope I make myself clear enough for you to understand me.
Second, to the moderators: feel free to move this topic if I posted it on the wrong session. But as you will see reading the following, I believe that the issue I will describe is directly related with the Neatrom - correct me if I'm wrong, but I have reasons to believe that.
So, here it goes:
I have a Samsung Galaxy S2 (i9100), running XXLSJ Neatrom Lite v4.0, and this kernell: 3.0.31-Siyah-s2-v6.0b4+
In december 2012, I bought a MicroSD card (model Sandisk Ultra 32Gb class 10) to install in my i9100, and it rocks.
But 4 weeks ago, when I was playing some games on the phone, I ignored the first battery low warning messages, and kept playing to a point that the phone simply turned off. Completely. I recharged the battery and, after powering the phone on again, it showed a message saying something like "blank sdcard" or something. I had many pictures and important movies on that card, so I decided to not format it; instead, I searched for a way to fix it.
I tried to access the files from my computer - on Windows, no success; on Ubuntu, no success; on Mint, no success. Windows and Linux showed the icon representing the sdcard, but when I tried to open it under Windows, it showed a message saying "this disk is not formated. Do you want to format it?". Linux didn't show any message, and didn't opne a single window to show its content. Nothing. Nada.
Then, my cousin (a geek genius) took my card to test it on his own notebook. He made some long research on the net, and installed a software called TestDisk (http://www.cgsecurity.org/wiki/TestDisk - linux version) to try to recover the partition (or the MBR, I don't know exactly the tech name of this stuff...). He even entered on the software the number of cylinders, sectors and all that stuff to try to achieve sometuing... But after almost two hours reading tutorials, and trying hard to bring that card back to life with no success, he finally gave up, telling me to RMA the sdcard.
Then, I took the card from his hands, and put it aside, giving up too. Half an hour later, accepting the fact that my files was gone forever, I decided to try to format the card on my phone, to see if it would work after being formated. So, I put the card on the phone again, and powered the phone on... And, for my surprise, the card was back to life! For no reason, it decided to work again! With all the movies, all the pictures, all the games, everything was there, untouched!!!!
So, it worked great in the last 4 weeks, fast and nice - recording long HD movies, taking hundreds of pictures, installing huge data games, etc. It worked fine - until two days ago.
Because, two days ago, I was playing again, and again I ignored the low battery warnings, and it happened again! In the middle of the game, the battery ran out, and the phone turned off. Guess what? Yeah, after recharging it and turning it on again, there came that same message, telling me that my sdcard was blank! Again, no success trying to access it from Windows or Linux. And no geek cousin nearby...
(Of course, I had a backup of my files, created just after that first "death").
so, I sent an e-mail to my cousin, asking him about the software he used, and how it used it. He told me about that testdisk software. I downloaded the Windows version of the software, and give a try - no success. The program didn't recognize the drive letter of my "blank" sdcard, because the filesystem was simply not listed by the program. So, I went to the site, and I read that, under Linux, it was possible to force Testdisk to try to repair filesystems that was not shown in the list, by using a command line telling the software to look for the device through this mounting point (a folder inside /dev/). Linux stuff, I wont go any deep on this here.
So, I decided to restart my notebook, to boot on Linux to try that method. Guess what again? Suddenly, Windows recognized the sdcard again! I just ran the TestDisk utility, with no success - no command was used, I just ran the program, and since it didn't recognize the card, I closed the program. Nothing was done.
But, given the fact that the card was dead twice in the exact circumstantes (battery wearing completely off), and given the fact that the card came back to life after a simple run of the software TestDisk, I refuse to believe that it was a simple coincidence; I am not a geek, not a linux or android expert, nor a hardware wizzard, but my little experience tells me that it is possible that the android system locked the SDcard filesystem in a way that, after a sudden energy cut, it needed some sort of "logical shock" (made by TestDisk, even without any changes or command being called by the user, thats me).
I believe that this issue is part NeatRom's (or maybe kernell's) fault, because in stock roms, the system would close the app and close all sdcard access before turning the phone off to prevent issues like this one.
Again, I must repeat: I am not a technician, not an expert, so chances are I am wrong - very wrong. But I believe that my suspicions makes some sense, and woths to be investigated - or cleared out. And, of course, chances are that the card is deffective - and I already called RMA service from Sandisk. And I made another backup right now. But, I insist: everything is working: no movie corrupted, not a single file is corrupted... So, I still have a doubt here: was this issue cause by a deffective card, or was it cause by the sudden turn-offs?
Before you ask: no, I didn't test playing to the end of battery using another sdcard. By the way, I will never play to this point anymore. And yes, the card is still working!
Sorry for the VERY LONG POST. But I think that this testimonial may be of some value to the rom and kernell developpers.
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Galaxy s2 said:
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Click to expand...
Click to collapse
Not the rom itself, but possibly some "features" of this or any other rom related to how it handles battery. I will try to make myself as clear as possible...
I know that in stock roms it is not possible to shoot photographs using flash when battery level is under 15% - this is to prevent sudden turn-off of the phone. And I know that some roms uses some tweaks that allows the user to take pictures using flash under this 15%. This is a thing that most users can think is an improvement - but we know that it is dangerous to use battery in a not-so-controled way. The history I told on the first post is a prove of it!
So, my suspictions is that, in some way, some rom configurations (or kernell configurations) may be allowing the user to play a high-power-demanding game or app to the end of battery charge - when, instead, it should close all the apps after the first warning, and before shutting down the phone. In other words, some roms let the decision up to the user - and if the user is (like me) distracted with some game, and forgot or bypass the first warning, he becomes a victim of this own distraction, wearing all the juice without thinking about closing the apk and shuting down the phone in the correct manner.
So, the question is: are there some rom tweaks that could POSSIBLY be the reason for this kind of issue?
Hope I made myself clear now, despite my horrible "engrich"...
this worked for me. it may work for you but I can't guarantee it. let's start with some history. so I rooted with condi's awesome root tool. everything was great. one day while web browsing, the thing turned off. I was wondering, what the heck? rebooting only got me to the part where the golden ribbon flowed constantly. I guess they call it a bootloop. resetting and wiping data only got me into a worst scenario
so there it was. only had it for 4 months and the thing kaput on me. that's ok, got my receipt. even though it was rooted, I planned on sending it in without a doubt. I had bought as an opened item at frys. I'll just blame it on the 1st owner. anywho, couple of visits to Sony stores revealed that they were remodeling. they couldn't accept the tablet (I guess theres one near san jose, lucky me). Anyways, I even made attempts to contact through the web but nothing. I had just bought a galaxy s3 so I was like, oh well. its just a tablet. I left it sitting there collecting dust. One day my girl nags me to death to get it done. its almost been a year and I need to claim the warranty. Well, LOL. I lose the receipt. Yes, SOL.
What did I have left to resort to? Begging the crap out of condi to do whatever is in his power to help me. It didn't get me far. I gave up. So its been over a year since I bought the thing and I decided to give it another whack because I swear I had gone through the process of making sure I installed the boot loop protection condi had created. well, I can't find the charging cable. Wow, those things are hard to find and very expensive. I give up again.
Today, I was digging through my storage and what do you know, I find the charger. I was confident I could fix the tablet. This is what I did. After sitting there for so long, I charged it up a bit. I knew that I couldn't allow it to charge for too long. I noticed that if I ever ran into a situation that got me stuck at the sony logo and not allowing me to go anywhere, and the only thing I could do was to do a manual power off, the only way to get out of that is to let the tablet die.
So tip. If you get stuck at the sony logo, just let it sit there until it dies. only way I found to fix that.
I also, in the past, ran into the infamous E:verification failed yadda yadda yadda. something about not being able to mount the sd or some crap. I hated that error. I couldn't understand why it did that. well, today, I decided to try something totally outside the box. I figure it couldn't hurt. Prior to even booting up my tablet for the first time in 10 months, I inserted the sd card directly into a slot in my laptop and always noticed the drive letter came up (in my case) as J:. Now I kind of realize that the drive letter may or may not make any bit of a difference since its just a drive letter that the computer assigns, and in some cases, if inserted into another computer and that letter is taken, it then sets a different letter up for that SD. well, again, I'd figure what's the harm in trying so I went into control panel. administrative tools, computer management. on the tabs on the left, I went for the disk management under storage and decided to change the drive letter that my computer sees the sd card to E. Well of course I had a virtual drive set as E but with a little change here and there, I finally get the SD to show up on my laptop as E. I copied the nbx signature file that condi recommends that you copy to try and flash it during these "soft brick" situations, even copied my decrypted and signed update files just in case my first attempt fails.
as soon as I boot it up, I go into recovery mode. I select the file that condi suggested. right away it started saying it was updating. Nice. No e:verification failure messages. so I grin and watched it as it was actually flashing it. wowzers. and of course, towards the end after the 3rd bullet has been highlighted, I get ready to hold the Vol +, so that I can wipe data or else have to face this process again. Boom, wiped data and waited. Of course I was nervous as I watched the dancing golden ribbons, which I have seen dance in front of me endlessly before in the past. Then, the setup screen pops up. YES. I got it fixed!
On what android O.S did your tablet last had?
nbx signature file?
numbaonenewb said:
this worked for me. it may work for you but I can't guarantee it. let's start with some history. so I rooted with condi's awesome root tool. everything was great. one day while web browsing, the thing turned off. I was wondering, what the heck? rebooting only got me to the part where the golden ribbon flowed constantly. I guess they call it a bootloop. resetting and wiping data only got me into a worst scenario
so there it was. only had it for 4 months and the thing kaput on me. that's ok, got my receipt. even though it was rooted, I planned on sending it in without a doubt. I had bought as an opened item at frys. I'll just blame it on the 1st owner. anywho, couple of visits to Sony stores revealed that they were remodeling. they couldn't accept the tablet (I guess theres one near san jose, lucky me). Anyways, I even made attempts to contact through the web but nothing. I had just bought a galaxy s3 so I was like, oh well. its just a tablet. I left it sitting there collecting dust. One day my girl nags me to death to get it done. its almost been a year and I need to claim the warranty. Well, LOL. I lose the receipt. Yes, SOL.
What did I have left to resort to? Begging the crap out of condi to do whatever is in his power to help me. It didn't get me far. I gave up. So its been over a year since I bought the thing and I decided to give it another whack because I swear I had gone through the process of making sure I installed the boot loop protection condi had created. well, I can't find the charging cable. Wow, those things are hard to find and very expensive. I give up again.
Today, I was digging through my storage and what do you know, I find the charger. I was confident I could fix the tablet. This is what I did. After sitting there for so long, I charged it up a bit. I knew that I couldn't allow it to charge for too long. I noticed that if I ever ran into a situation that got me stuck at the sony logo and not allowing me to go anywhere, and the only thing I could do was to do a manual power off, the only way to get out of that is to let the tablet die.
So tip. If you get stuck at the sony logo, just let it sit there until it dies. only way I found to fix that.
I also, in the past, ran into the infamous E:verification failed yadda yadda yadda. something about not being able to mount the sd or some crap. I hated that error. I couldn't understand why it did that. well, today, I decided to try something totally outside the box. I figure it couldn't hurt. Prior to even booting up my tablet for the first time in 10 months, I inserted the sd card directly into a slot in my laptop and always noticed the drive letter came up (in my case) as J:. Now I kind of realize that the drive letter may or may not make any bit of a difference since its just a drive letter that the computer assigns, and in some cases, if inserted into another computer and that letter is taken, it then sets a different letter up for that SD. well, again, I'd figure what's the harm in trying so I went into control panel. administrative tools, computer management. on the tabs on the left, I went for the disk management under storage and decided to change the drive letter that my computer sees the sd card to E. Well of course I had a virtual drive set as E but with a little change here and there, I finally get the SD to show up on my laptop as E. I copied the nbx signature file that condi recommends that you copy to try and flash it during these "soft brick" situations, even copied my decrypted and signed update files just in case my first attempt fails.
as soon as I boot it up, I go into recovery mode. I select the file that condi suggested. right away it started saying it was updating. Nice. No e:verification failure messages. so I grin and watched it as it was actually flashing it. wowzers. and of course, towards the end after the 3rd bullet has been highlighted, I get ready to hold the Vol +, so that I can wipe data or else have to face this process again. Boom, wiped data and waited. Of course I was nervous as I watched the dancing golden ribbons, which I have seen dance in front of me endlessly before in the past. Then, the setup screen pops up. YES. I got it fixed!
Click to expand...
Click to collapse
Where can I find this nbx signature file? Sony Tablet *111GB/s. I've bricked it.