Got my gTab yesterday. [VERY EXCITED!]
Plugged in wall outlet, waited 4 hours to charge.
Connected to WiFi.
Updated TapnTap, as instructed.
My Vist Ultimate computer didn't see the gTab when I plugged it in, at least not so I could get to the root directory.
So I went to an old XP and tried that. It worked.
Wanted to Root it, so I installed (sorry if that's not the correct word) ClockworkMod v08.
So far so good.
Then rooted TnT Lite v 4.2
Still good.
Then rooted TnT Lite suppl 4.25
STILL okay.
Then went to gMail. Added my gMail account. (An account I use for business.) It took a LONG time to do whatever it was doing. So I went to do something else, thinking it would continue doing it's thing in the background. I was wrong. It messed up, and I kept getting error messages.
Next thing I know, I'm somehow in that infinite boot loop.
It was about 2 am, and I was tired, and... panicked!
Next thing you know I'm freaking out and went hog-wild (while following directions to the letter), to get my brand new toy to work.
I did nvflash windows, still infinite boot loop. I tried putting the vanilla recovery 3588 on there. Still infinite boot loop.
Kept at things, trying everything I read, and STILL... infinite boot loop.
Then I figured it was time to try to get my Vista computer working so I wouldn't have to keep transferring stuff from the Vista to the XP to the miscroSD card to the gTab, and followed directions about APX mode.
I was delirious, exhausted and scared, and kind of went postal (in a frenzied OCD sort-of way), trying everything and anything to get rid of the infinite boot loop.
Now it won't even power up. (AT ALL!) I think I gave it a heart attack, or possibly a stroke. And that's with not even owning it for 24 hours!
I've tried the long 45 second power hold, then the short one. [Did that about 37 times.] I've tried power and Vol+. Nope. Then did a few power and Vol-, just to really freak the poor sick, dead thing out. [Like kicking the proverbial dead horse, I guess. Trying to see if there was any life left in it.] I even read to turn off the lights to see if there was a faint glow. But nope. No glow.
I will now follow the directions from another post, and will let it just sit for 24 hours (if I can survive the wait) to let the battery discharge and then see if it will boot. [After this nightmare, there is no WAY I will take off the back and hit the reset button--thereby definitely voiding my warranty.] But I hope I'm not like the woman from the forum thread: http://forum.xda-developers.com/showthread.php?t=968177
If I am, and can't get this thing to power up, do you think WOOT will let me return it???? I'm so upset that I broke my new toy so quickly. If anyone has any suggestions about getting this thing to boot up, I'd appreciate it. [at this point, I'd be happy to have it boot up in the infinite boot loop!]
Oh, and one last question, how does having it turned off (because I can't turn it on) and sitting there drain the battery to the point that it needs to start fresh after a mere 24 hours with no activity? Is that typical for tablets?
THANK YOU to anyone who can offer advice on what to try next or how to remedy this problem. Please keep in mind that I am good with PCs and laptops/netbooks, but am VERY new to this whole android and tablet things, so if you send instructions, please give implicit directions (as though you are instructing a 3-year-old), without feeling as if you are insulting me. [Please believe it's what I need, and will appreciate. As will the other wooters who just turned their gTabs into brinks] And know that you will be helping Roebeet by answering my questions, because the poor guy must be exhausted from all of us lay-peoples' foibles and mess-ups. [The man seems to be a God at this site!]
Did you do what is mentioned right after step 10 in this thread?
http://forum.xda-developers.com/showthread.php?t=865245
"If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups."
But first... switch to decaf and get some rest... ;-)
Panic doesn't help.
It might actually be powering up but staying in APX mode. I've seen one do that. If that's the case you can still nvflash it back to normal. Let it charge for 15-20 minutes and leave it on the charger. Try to start it up and see if your pc can see it.
You maybe got the bootloop because your tab had sleep death while syncing. Was the error you got by chance something like process.acore? If so that is a classic error that happens after syncing contacts, sometimes there are empty contacts with no data that make the tab go nuts. Simply deleting the bad contacts solves the problem.
A simple wipe data/cash/davlic would have been the first place to start. Breathing helps when stuff goes wonky.
If you can get it to recovery a repartition is totally necessary. Deffinetly... and maybe some whiskey ....
Good luck.
good luck with woot return, dont even think they do it.
I wouldn't worry about the warranty. You already voided it when you rooted the device.
I'm so sorry, guys, I didn't check off the subscribe notification, so I didn't know that anyone had written.
cdavisccs28, I didn't do that while the tablet was boot looping, but somehow it went from bootlooping to complete death.
K J Rad, it wasn't charging, and wouldn't boot. [And you can probably guess, I tried numerous times.]
Mantara, the death in the middle of syncing certainly didn't help it, and, as you suggested, might have been the last nail in the coffin. The whiskey suggestion was funny! Actually I, personally don't drink, but as you might have deduced, I'm a carrier. [AKA: I've been told that I drive people to drink.]
spike378 & filterking: Yup, I think you are both correct. How I managed to spike from "excited as a schoolgirl" to "completely tanking" in less than 24 hours amazes even ME! [And I know me, and am used to me! I think that was a personal record!] [If I don't laugh about it, I'll cry!]
THANK YOU ALL for replying! Your time and concern meant a lot to me, but I think this baby is totally bricked! Elvis has DEFINITELY left the building! If I do get another one (I'll have to start saving again), I might be too afraid to play with it. I really am good with PCs and notebooks, so I might just keep staying with what I know. YOU GUYS ROCK, for trying to help me, and I really appreciate it!
Same problem. I booted the device up, and connected it to WiFi. Then it gave a popup where it asked to update to the newest version. I said okay, and let it do its thing. Then it restarted into a bootloop. So, I turned the device off, and tried to turn it back on, except -- nothing. With the USB plugged in, it's not recognized by the computer at any time after I press the power button. I've been trying to get it to boot for an hour now and it's still just sitting there with a black screen. Not even a backlight is showing. Anyone know of any solution? Or is it time to ask for an RMA from Woot!?
h.nocturna, WOW, you didn't even get to the part where you started doing everything and anything (in a frenzy) to get it to work properly! That might be a good thing, h.nocturna, because you haven't voided your warranty! You might need to send it to Viewsonic to be fixed (since it messed up while you were doing their update), but at least you can do THAT! I mailed my brand new brick to my son up in college and gave him this site, and told him to have a blast, and do whatever he wanted with it. [He's known me his whole life, and said even HE "can't fathom my destroying something so completely in less than 10 hours."] I wish you luck!
Oh, one more question that will help the masses, I'm sure. So how do you get your computer to recognize the device as a hard drive, when it is plugged in to a Windows PC (without voiding the warrenty, of course)? [Vista Ultimate does not recognize it, and neither did Windows 7.] Please give step-by-step instructions for the lay-person. [By answering this question, at least we will solve THAT problem for folks!]
badtypist,
I wrote you a fix last night and when I went to save it the Forums had been shut down and do it didn't save to post --
and I had been on the road and was exhausted and just couldn't stay up long enough to redo it if and when they came back up. Sorry.
You simply needed to find one solution and then let us get down the procedure to follow to fix it.
Several people in the past have gotten to the point where you were. I read two fixes.
One was some people were able to get the tab to start again by playing with the
power switch -- hold it for long, long times and then press a short startup, etc. Somehow they got that to reset and start.
Somewhere else in the forums -- and I have never done this with either of my tablets --
there are a few threads where someone in this kind of situation opened up
the tablet card and simply unplugged the battery for 10- or more seconds. There also
is a reset button inside the case as shown in an old thread where someone opened a
G-Tab up and took pictures.
If any of those three choices get to where you can either use power / volume - to get
into NVFlash more ---- or to where we can load CWM -- then you are in fair shape.
LOTS AND LOTS OF BOOT LOOPS ARE ASSOCIATED WITH PARTITIONING. Simply
getting into CWM and re-partitioning to 2048 and 0 and then using CWM to "Fix
Permissions" will get it working. CWM also will let you wipe the cache and wipe the
factory data, which sometimes will allow and NVFlash to come on up and work right.
You see, we were not dead by any stretch.
You might pass this on to the recipient of the tablet.
Also, so many people are trying to do so much that is over their heads -- and so many
people are borking their tablets -- that this site and the folks that can help -- just can't communicate. Sad day.
I wish you luck. Hope this helps.
Rev
EDIT: Well, I guess we missed the boat completely. Evidently she mailed of the G-Tab and checked
out for good!!!
Hi Rev! Sorry I didn't get back to you sooner. I TRIED to get back to you sooner, but I think this site was down, because it kept timing out and wouldn't let me get to the site OR the conversation thread! I tried a few times, then tried later, and now just tried again!
I think you guys are getting BLASTED with desperate lay-people from the over 10,000 tablets sold on Woot who have "borked" their tablets. (That's a funny word, Rev! I hope I'm using it properly! And please note, although the WORD is funny, the actual situation is NOT funny!)
Yes, I mailed the offending frustration-linked object to my son, and can't "take it back," but perhaps I will beg for and borrow enough money to try again, sometime soon! If I do, I will come back here again sine I feel I have bonded with the wonderful, sharing folks on this site. (I'm a she, by the way, not a "he.") I admire (okay, worship) the folks who help us lay-people out so we don't sit alone crying and trying to power/Vol+ in solitude!
I've read your other posts previously, Rev, and you are so wonderful to help us n00bs! So please remember "badtypist" (hopefully with good thoughts) and when you hear my name again, let's hope it's to say... THIS TIME I ROOTED IT CORRECTLY!!!!
Thanks again, for your time, Rev AND the rest of you, which wasn't wasted, because I sent my son this link and he will (in his spare time) read through it to fix HIS new tablet. [I think he kind of liked that his mom messed up! He got a VERY expensive new toy, if he can fix it.]
Perhaps I'll talk with you soon...
badtypist (and bad ROOTER. Or is it ROOTERIST? Or maybe ROOTIST? Whatever the proper term, I think we can all agree that I AM bad at it!)
Gtab Update Problems
So, I would agree with some of the posts above. I would also point out that you have two options (or some combination of the two):
1. Try to return the tablet, or put in a warranty claim (the warranty specifically does not cover modification\rooting)
2. Try to fix it yourself
I tend to choose #2 f I think the chances are better than 50/50 in my favor. Also, if the hardware is okay, you can have it fixed in 20 minutes.
The experience that the OP went through is EXACTLY why I discourage newer g-tablet owners from rushing in and flashing alternate firmware to their tablet. I am often chided for this recommendation, but I believe that it is unwise to modify a brand new tablet.
If you still want to mod it, you should have a backup plan. I save my update file to an external USB drive. You should then be able to re-install the stock update by placing it on a microSD card. You need to rename it to update.zip, and add a file that tells it to look at the microSD card for an update. I am a but fuzzy on the specifics, but that file is named "command", and I found it somewhere here in the forums.
As I plan on modding my newer woot tablet (or maybe my older Sears one). I will first set this up, and will work out the details.
Hi buzzzard, thanks for the great info! VERY helpful. I did see that video while researching the gTab, but didn't bookmark it, so I appreciate your adding it here! My son will see all your posts and will use all of your suggestions to try to raise my brand new gTab from the dead! [It wasn't even in zombie mode when I shipped it to my son, so we'll see what happens! I'll keep ya'll informed.]
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS? [I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
buzzzard,
I have always understood -- and I don't want to know bad enough to spend the time
researching it -- that the warranty is void when you load non-standard software.
And even if it were not, I have real questions about messing up a computer and then
taking it back to the seller as if it were faulty. Seems to me there is a dishonesty
component in that equation.
I think modders SHOULD accept the risk that they can trash their tablets -- and that
if they do then the loss is theirs.
Rev
P. S. -- I've tried to say this much without starting a flame war -- if you do I won't
answer you and will ask the moderator to close and hide the thread.
badtypist said:
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS?
Click to expand...
Click to collapse
For one, this will give you time to read up and learn more. I can tell that you are confused by all of this. You don't "root it to a faster OS". Rooting is a method to gain root privileges on the tablet. To you windows users, root is the equivalent of Administrator. There also is only one OS available for this tablet, and that is Android. Some have made modified/customized versions of Android, but it is still Android.
[I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
Click to expand...
Click to collapse
There seems to be the misperception that you have to install a custom firmware to get root privileges or Android Market access. This can be done on the stock firmware, and then makes the tablet much more useful.
butchconner, I know you weren't talking to me, but I am taking full responsibility, and am hoping my son can resurrect my gTab, and I DO hope there will be no flaming, as well. ["There's no need for flaming. It's unsportsmanlike, kind-of rude and unproductive," said the mom to all reading this thread. So please don't flame so this won't get deleted for other poor people who "bork" their gTabs.]
badtypist,
wasserkapf was around when I got my first G-Tablet -- when we were all getting started last November.
You have no idea how bad the software was back then and the things we had to do to make things work.
It wasn't a question of 10 different ROMS and whether it was fast or not -- it was a question of making it work.
But I agree with wasserkapf (and I don't mean this comment particularly at you ) that
people are trying to do too much to fast. In addition to being a minister, I also was
an exec in the IT field for 30 years. I learned to read the docs, to move slow, to make sure each step was
successfully completed before moving on, to test things that
I'm not sure of -- and a whole host of other things that IT people use to operate their
company's systems without crashing it and losing data.
I helped a guy along the way who said he was inexperienced and that his tablet was in
the same kind of situation yours ways. He had gotten his G-Tab, charged it up, and had loaded EVERYTHING he could find on it.
Three or four different ROMS including an
experimental ROM he had been warned was risky. Yet he was having to ask what
recovery was and where to look for files and other basic questions.
I think everybody should get their tablet, upgrade to the latest version of stock, install z4root and
Titanium Backup and learn to use them, then install the latest version of Angry Birds and whatever useful software they need -- and then enjoy
that for a while while they learn the ins and outs of modding.
I help people because of the kind of person I am and because I am retired and have
some time to devote. But I also will be honest and tell you this -- I don't suffer
obnoxious, foolish people well -- and there are folks I just don't help because someone gave them good advice
and they didn't listen........I help folks who need and deserve to be helped.
The alternate ROMs are nice. And it's neat to add market and other useful stuff to
your tablet. But none of those kinds of things are so important that they are worth
what some folks do.
Nuff said. I don't respond to flames. And when you have been helping people as long
as I have, then you can have your opinion.
Peace,
Rev
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.
Hello guys,
I have (had) a transformer prime with stock android 4.1.
I tried to flash my Prime with Goomanager and TWRP.
I found out that I had to install twrp manually to do this. (it was disabled by goomanager for the prime)
So I rooted my tablet with motor chopper, unlocked my bootloader with the asus apk and followed these instructions http://www.youtube.com/watch?v=0-KLPDu2sos
They looked pretty straight forward, so I thought I'd give it a try.
I downloaded the file and relocated it to /twrp.blob and typed "reboot".
After rebooting I used goomanagers "Restore Recovery" button and after that it wouldn't boot.
It always freezes at the boot screen. (the one with the asus Logo in the center and Nvidia logo in the right bottom corner)
It also says "The device is unlocked." in the left upper corner.
I didn't know that I would need ADB (i didn't even know at that time, what that was) or fastboot on my laptop. Maybe this is my problem.
I tried the follwing things:
- press power and lower volume:
the tablets just turns off and on to this same splash screen
- I thought about trying option 1 from here (http://forum.xda-developers.com/showthread.php?t=1514088), but I had to install adb and fastboot, but when I type "adb devices" in the console, it says "list of devices attached", but there aren't any.
(my tablet is connected and is turned on [at least to this splash screen])
I hope you guys can help me and I didn't brick my tablet completely.
thanks
Simon
Same exact thing happened to me. Tried to reboot into recovery and now I can't get past the splash screen. No option for fastboot and adb does not show my device. I had to send mine in to Asus and that was three weeks ago. They have informed me that there will be a charge (have not said how much yet) but other than that no response from them. The issue we are having is a hard brick and unless you backed your prime up with nvflash? tool before upgrading to Jeallybean there is no way to recover it.
Hi @slatonyam,
thank you very much for your answer.
Could you please be so kind to tell me what it cost to repair it, after you got it back?
I just want to make sure it is worth the trouble and money.
Isn't there another way by using a micro sd with a build or similar?
best regards
slatonyam said:
Same exact thing happened to me. Tried to reboot into recovery and now I can't get past the splash screen. No option for fastboot and adb does not show my device. I had to send mine in to Asus and that was three weeks ago. They have informed me that there will be a charge (have not said how much yet) but other than that no response from them. The issue we are having is a hard brick and unless you backed your prime up with nvflash? tool before upgrading to Jeallybean there is no way to recover it.
Click to expand...
Click to collapse
Simon after three weeks of sitting on my tablet and numerous phone calls and emails from me, Asus finally got back to me with a quote. I believe the only reason they got back to me is because I told them to ship my tablet back to me and forget the repairs. This is the quote they gave me:
$213 for the motherboard
$65 for labor
I had already told them to ship my tablet back to me so I wasn't interested in getting it repaired and the cost is too much. I only paid $249 for the tablet through New Egg. So I think I just might buy a motherboard off ebay and try to repair it myself, I figure I have nothing to lose.
SimonErich said:
Hi @slatonyam,
thank you very much for your answer.
Could you please be so kind to tell me what it cost to repair it, after you got it back?
I just want to make sure it is worth the trouble and money.
Isn't there another way by using a micro sd with a build or similar?
best regards
Click to expand...
Click to collapse
Update after 3 days or so waiting for them to ship my tablet. I received a email Tuesday stating that they were finally shipping my tablet back. But under the serial number I noticed that the device they are sending begins with CA whereas the one I sent in begins with a C1. Maybe they replaced my tablet after all. Will let everyone know when I receive it Tuesday.
Hi @slatonyam
I did sent my Transformer to Asus exactly 7 days ago and just got it back.
(had to send it to Asus Czeck, because I live in Austria - but it was pretty fast)
it is working again (got the same device) and it seems like they repaired it on warranty, because they didn't sent me a payment information or anything.
just got a working device back today.
I'm happy and I wish you good luck with your device.
best regards
Thanks for your kind words but I received the tablet back today and it was not repaired. But so happy that you received a repair for yours. I guess I will just lean on my Nook HD+ for now until a solution is released.
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.
Hello, hope someone can point me in the right direction.
My TF201 was fully updated to latest asus OTA and rooted.
I decided to unlock it and install TWRP
Unlock went fine
fastbooted TWRP and command window on PC was success.
Rebooted and OS loaded.
shut it down to reboot into TWRP receovery and it just hangs on ASUS screen with "This device is unlocked"
Can no longer pwr/volume down
I can pwr/volume up (but can't get APX drivers to load on win 7 64 PC)
Any ideas of next step?
Welcome
Welcom to Club "My TF201 is stuck" :=( I wanted to do a bit more and rooted it. Everything went according to plan, and then I wanted to install recovery in order to flash other ROMS, and everything went south. SO many people have this experience, the guy/girl who solves this problem will be nominated for some Nobel prize, even if we have to invent one. I am following this thread, I had mine for 3 weeks and though: "Hmm, flashing another ROM could be fun", and now I have a shiny bright paper weight. Please let me know if you get any closer to progress, please..... please! I even let it run out of battery like some guy suggested because that should interrupt the update it was stuck in, but had no luck. Too bad, it is a fabulous piece of technology that I had no idea could be so addictive :=(
mcdanishdk said:
Welcom to Club "My TF201 is stuck" :=( I wanted to do a bit more and rooted it. Everything went according to plan, and then I wanted to install recovery in order to flash other ROMS, and everything went south. SO many people have this experience, the guy/girl who solves this problem will be nominated for some Nobel prize, even if we have to invent one. I am following this thread, I had mine for 3 weeks and though: "Hmm, flashing another ROM could be fun", and now I have a shiny bright paper weight. Please let me know if you get any closer to progress, please..... please! I even let it run out of battery like some guy suggested because that should interrupt the update it was stuck in, but had no luck. Too bad, it is a fabulous piece of technology that I had no idea could be so addictive :=(
Click to expand...
Click to collapse
Sorry to hear your troubles as well. I have say I have 1.5 years of enjoyment out of mine (got it on release day). I waited as long as I could to unlock it.
I have no choice but to let the power drain as it will not turn off. From what I have read it is hard bricked. But I hope someone has another answer.
I have the same problem.
I am stuck on TWRP boot if I press Power and VOlume Down buttons.
Unless I have only the Asus screen.
Do we have anything new?