Hi everyone!
Got my Transformer just today and everything worked fine in the beginning. Updated to 3.2, got everything setup...
Now that the tablet was unused for a couple of hourse while i was at work(shut it down before i went) i cant turn it on again. Before i shut it down it was at about 90 % Battery.
Tried everything that was recommended on the forums(multiple times).
Press Power >10 Seconds than try to turn on the tab -> Nothing Happens
Press Power > 30 Seconds than try to turn on the tab -> Nothing Happens
Power + Volume Down -> Nothing Happens
Power + Volume Up -> Nothing Happens, except when i plugin the usb into my pc. "Device doesnt work properly..." Pops up for a second, then nothing happens. TF doesnt appear in Device Manager at any time.
Tried charging with the AC charger for last 1,5 hours but that didnt work. Now im trying to charge it with the usb port of my pc as this was recommended somewhere on the net.
Anyone got any Hints on what i should do?
Return it for another
^x2 ESPECIALLY if you havent even tried rooting or modding it. send that puppy back asap!
The only thing i did was set up wireless lan and my google account. Then i had to get to work.
Too bad, really liked it while it was working.
Ill try charging it over night and if nothing happens im gonna send it back tomorrow morning.
there are ways to flash rom again ofcourse but if it is that new and you did not root it or any thing like that I think for sure it is better to send it back, good luck
same thing happen to me. unfortunately i'd already rooted and flashed Prime 1.8.4. please help me
caterpiez said:
same thing happen to me. unfortunately i'd already rooted and flashed Prime 1.8.4. please help me
Click to expand...
Click to collapse
use nvflash : http://forum.xda-developers.com/showthread.php?t=1123429
It works for me there are revolver roms and prime roms you can flash with this
depulle87 said:
use nvflash : http://forum.xda-developers.com/showthread.php?t=1123429
It works for me there are revolver roms and prime roms you can flash with this
Click to expand...
Click to collapse
not working.I can't enter APX mode.Tried with 1 PC and 3 laptops.All can't detected the USB
do you have the apx drivers installed ? it has special drivers in apx mode
I used it from here : http://forum.xda-developers.com/showthread.php?t=1125714 (step 3 )
depulle87 said:
do you have the apx drivers installed ? it has special drivers in apx mode
I used it from here : http://forum.xda-developers.com/showthread.php?t=1125714 (step 3 )
Click to expand...
Click to collapse
Failed at this bold step
3a. Shut your TF off and while plugged into your PC, hold the volume UP and Power button until your PC makes that USB device plugged in sound and there is a notification about installing drivers.
Already tested at 3 laptops still can't detected the USB.First I suspect cable problem, but I'm still can use the cable to charge the dock. Now I'm thinking maybe my physical power button "damaged"
that sucks and you cant enter CWM tto do a hardware button test either I guess ?
The carge uses other wires than comunication trough the same cable so it still can be the cable
had the same thing. never got it to work again. realy strange thing, i thought APX should always work when you have a brick. At the end i decided to try and return it to the lab so they will give me a different one.
that was my post
[Q] help! got a real brick, cant go APX
num1gever said:
had the same thing. never got it to work again. realy strange thing, i thought APX should always work when you have a brick. At the end i decided to try and return it to the lab so they will give me a different one.
that was my post
[Q] help! got a real brick, cant go APX
Click to expand...
Click to collapse
really? then i going try to send back to service center.i hope they will never succeed it make it alive and detect it already been rooted
---------- Post added at 06:01 PM ---------- Previous post was at 05:37 PM ----------
Finally, it alive again. I managed go to APX mode and NVFlash back to the stock but when I shutdown and press Vol- and Power to erase the data, it happen again. I guess this TF don't want to be turned off by its owner
caterpiez said:
really? then i going try to send back to service center.i hope they will never succeed it make it alive and detect it already been rooted
---------- Post added at 06:01 PM ---------- Previous post was at 05:37 PM ----------
Finally, it alive again. I managed go to APX mode and NVFlash back to the stock but when I shutdown and press Vol- and Power to erase the data, it happen again. I guess this TF don't want to be turned off by its owner
Click to expand...
Click to collapse
What you have is a classic case of a permanent apx bootloop.
There are actually a few of those circulating as "new" devices from the manufacturer. What happens is a user would brick it, return it to the store, the store would return it to the asus, asus people would nvflash it, then they would send it out again as a "new" transformer.
Permanent apx bootloop is almost impossible to fix. Many people, including myself, have worked on several tegra 2 tablets that somehow got stuck in permanent apx bootloop by their owners. So far, we have not found a definite pattern to how these devices got there. And so far, we have not found a consistent way to bring them out of permanent apx bootloop. Doing random things to it seems to be the only way to bring a device out of a permanent apx bootloop.
When a device is stuck in permanent apx bootloop, no amount of nvflash, wiping data, etc. will bring it out of apx bootloop. After every nvflash, you can boot it up once only then it goes into apx bootloop.
Trust me, some people, including myself, have tried some weird ways to try to bring a tegra 2 tablet out of permanent apx bootloop.
What you wanna do right now is return it immediately and exchange for another one. Why? Because we have also found that once a device is in a permanent apx bootloop, if you ever manage to fix it it will randomly go back into a permanent apx bootloop again at some point.
So far as we know, there is no real explanation as to why some of these devices would go into permanent apx bootloop. You're going to hear a lot of theories, though. LOL
goodintentions said:
So far as we know, there is no real explanation as to why some of these devices would go into permanent apx bootloop. You're going to hear a lot of theories, though. LOL
Click to expand...
Click to collapse
hi. thanx for the info. never knew that.
but for the OP. how did you finally managed to go into APX? did the pc just happen to recognize the APX mode instead of calling it "unknown device" or as you sayed "device doesnt work properly"?
did you press other buttons when you did it?
i think i've really tried everything and several computers and still didnt work
Related
powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in 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.
Hi,
I got this tablet from a friend, and it's stuck at the boot logo. I've tried hard reset, reset via recovery, nothing seems to work.
How can I flash the latest official rom?
Can't seem to find a tool for it, and Asus suggest to flash with the tablet itself, but that's not possible for now.
Anyone?
Thx!
http://forum.xda-developers.com/showthread.php?t=1688012
Easyflasher to flash TWRP recovery > copy ROM to MicroSD card, flash ROM
Thanks! I can't seem to get him into APX mode, what is the exact procedure?
Connect the tab to USB > PC first
Power Off the Tab
Hold Volume Up & Power
Nothing will appear on the Tab screen, but the PC should sound the USB connect noise / device manager will show it has connected - only takes a few seconds to enter APX mode
I've tried that, doesn't seem to recognize it . Would you help me via IM of some sort?
It`ll be the drivers most likely, open device manager when its connected and in APX mode, and manually update the drivers using the Universal Naked Driver from the Easyflasher site
I don't have any IM installed unfortunately but I`ll help you out here
Ok, that would be wonderful. The problem is, I don't know when it's off. I can't get it to shut down, it keeps rebooting. I'm monitoring dev manager with sound high, but it's not coming up. Cable is working, because it will charge. Using the original cable. (Windows 7 x64)
Best thing to do would be connect it to the PC, then press and hold Power until it shuts off, then try for APX mode - you might even be able to enter APX from a powered on state by holding the same button combo, but Ive not tested that myself
And a cable that charges doesn't automatically mean it will work for Data, they use different pins, some for power and some for data, if the data pins are damaged, it will still charge
I can't seem to get it working . Any other ways to flash it?
Not without being able to get it to boot - you'll need APX mode to do anything in the state it's in now
A bad cable is a common problem though, might be worth grabbing another one from eBay
To bad. I'll try and let it drain till it's empty, and fully charge it then. Just ordered another cable.
Thx for the help!
If the System / Data partitions are corrupted, which generally causes the boot loop, then draining and recharging won't help
Plus be careful not to drain the battery to 0%, their design prevents them from recharging if they hit 0% - many people have had to buy new batteries after not using their tab for a few months and letting it drain completely
Good luck, so long as there is no hardware damage, once you have a working cable it should be pretty straight forward to get TWRP recovery and a new ROM flashed to it
Might be worth trying your current cable on another PC too
Thanks for the headsup! Will try!
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of a couple of days ago it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TEAMWIN logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle.
I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. Tried different installed drivers as well. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a days now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Jayster0966 said:
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Click to expand...
Click to collapse
Have you tried a different / new cable in-case that's the reason all the flashing attempts and computer recognising the unit are failing ?
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh
lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh
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: