Database Info

Stuck! Hep! Won't get past Asus screen or go into apx mode

Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!

nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.

Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.

Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!

..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.

scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~

The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.

I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.

Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.

Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......

scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver

You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.

Got so frustrated with it I just went and bought a tf-300

c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one

Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...

People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.

Bricked and Stuck

Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans

If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:

Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh

Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans

[Q] I accidentally everything (TWRP)

Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?

JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?

So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)

Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.

UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this

JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...

Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus

JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......

[Q] Bricked TF700

Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.

Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!

Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.

Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.

Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.

Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...

Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.

berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash

Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?

sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock

zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...

berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.

[Q] Tried installing Drivers for Shield Tablet, is it bricked?

All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?

If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.

BareGrizzly said:
All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?
Click to expand...
Click to collapse
Seems quite strange that it would get bricked since you seem to have not done any operations to the tablet at all. Did you try to flash anything while in adb or fastboot? Are you holding down the power button long enough to power on? You need to hold that mushy button for what might seem like forever. There are tools like Win Droid that do what you're trying to do.
But yes, seems like you might need to send it in if the tablet is actually bricked.

Fustigador said:
If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.
Click to expand...
Click to collapse
That was the one I started with, but I had to follow the breadcrumbs through the separate tool threads.
I factory reset the device before beginning this process, I hadn't entrenched myself in the tablet since I've only had it since last Thursday. Doubt that has bearing.
I'd noticed software issues, freezing in and out of the lock screen. This was high among the reasons I decided to root it. Its possible I got a lemon, and if I didn't muck up the bootloader its still under factory warranty, correct? Should I contact Amazon who I bought it from before contacting Nvidia?

If it doesn't turn on maybe it as nothing to do with unlocking the bootloader.
Just activate the waranty.

I charged it overnight, and turned it on via recovery (down volume and power). It seems to be running fine now. Thanks for the advice, and I'll continue the process in the appropriate threads.
:good: