Database Info

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

[Q] Bricked tf300t, replaced motherboard...

So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?

n3tm0nk said:
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
Click to expand...
Click to collapse
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.

transformer pad tf300t
graphdarnell said:
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
Click to expand...
Click to collapse
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.

n3tm0nk said:
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
Click to expand...
Click to collapse
What happens when you follow the directions here by Tobdaryl (reverting back to official 104220 where 4.2 is encrypted)? Short of returning the MB, ain't much you can do hanging on to it, right? I've done this with my tab on official 4.2, and it went back to official 104220 without problems. Must warn you though, it took quite a few minutes and at times, looked as if it's frozen. Just leave it on till it says it's done. Patience counts.

[Q] Bricked TF300TG

Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!

jak4kaj said:
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
Click to expand...
Click to collapse
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster

Buster99 said:
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Click to expand...
Click to collapse
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4

jak4kaj said:
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
Click to expand...
Click to collapse
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster

Buster99 said:
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Click to expand...
Click to collapse
Yes I have fastboot and adb installed. They come with the Android SDK which I need for work.
jak4

I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!

coppervines said:
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
Click to expand...
Click to collapse
what recovery did you use for installing cm11?

Buster99 said:
what recovery did you use for installing cm11?
Click to expand...
Click to collapse
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster

Buster99 said:
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Click to expand...
Click to collapse
I would hate to think that my USB cable could be bad...it's been a LONG time since its done anything other than charge. Just need the pc to see the damn thing. ANY insight would be helpful.

APX
I was able to get to APX mode with the universal drivers (Vol +reset)...looking around to see if anyone else has had success. I never installed Nvflash...

in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What thread? Not sure I understand what you mean...

http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first

coppervines said:
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
Click to expand...
Click to collapse
So I'm assuming there is no solution to this problem without sending it to ASUS or getting a new Motherboard?
I'm in the exact same position...

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.

ebildude123 said:
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
Click to expand...
Click to collapse
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Boot loader wipe is a hard(ish) brick unless you have nvflash blobs since all you have access to is apx mode, no boot loader, no recovery, etc.
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4

not necessarily, I did it for cm10.1 (drunken flashing not advised ) and i don't have an NV backup.
and i had fastboot to work with.
but things may have changed since then.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] Do I need the USB cable to root?

Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.

bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.

It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.

Found one of the OEM chargers. $55 + shipping. Not planning to buy.

bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.

berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me

bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.

berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!

bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?

berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.

Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea

Failed to flash stock image (maybe full bricked?)

Hi all,
Today I tried to flash an older version of the stock rom (v1.2.1) and thought I didn't need to flash userdata.img. That was a big mistake..
Now the tablet stuck at a bootloop. After that I thought I could simply flash twrp over the bootloader to peform a /cache & /data wipe so that I can fix the bootloop.
And now we come to the other BIG problem. I can't access the bootloader. It directly boots up the tablet with the Nvidia logo. Is there any solution to fix the tablet?
I tried at the bootloop to enter via adb into the bootloader but my PC isn't recognize my device (probably no usb debugging).
There is no way to rescue it? No apx drivers out there?

Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.

amartolos said:
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
Click to expand...
Click to collapse
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.

ThunderArts said:
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
Click to expand...
Click to collapse
I notice in your sig that you do in fact seem to have a fully working new replacement tablet. That got me thinking along the following:
1. new tablet is fully functional, old one is not
2. both tablets have the same hardware spec
3. pull firmware from new one, and somehow get it onto the old one
4. hopefully old tablet should work!
The biggest problem is step 3... I only know of nvflash that might be able to help here, but I've never used it myself so I'm completely useless here. Maybe someone more knowledgeable could help out here, but otherwise it seems like you might be out of options.
If you do want to take a stab at nvflash yourself, THIS PAGE has a nice writeup of what some commands do, BUT BEWARE! It's not for our device, so don't just copy-paste commands! As long as you're not writing things to the new tablet, it couldn't hurt to try stuff, right?

It wish someone could help me with NvFlash because I have no knowledge with it.
So it's possible to make a copy of the system of my working tablet and flash it on my old tablet with NvFlash?
I hope someone helpful with NvFlash experience could help me out.
Btw I need to have an un-blob'd stock rom version to get it back alive? Afaik is there no public version.

NVflash is only useful if you have backed up using it BEFORE you brick it.

sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)

-deleted-

ThunderArts said:
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
Click to expand...
Click to collapse
No the blobs are specific to the device.

sbdags said:
No the blobs are specific to the device.
Click to expand...
Click to collapse
Okay. So it seems that there is no way to rescue it. Btw is there no accessible bootloader in OTA 1.2.1 because I flashed the boot.img without any error and I don't understand why I can't access it.

sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet

Bogdacutu said:
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Click to expand...
Click to collapse
Indeed - I was just talking about nvflash use in general. I haven't seen it used since tegra 3.