Related
Hi there,
I need your help urgently.
I received a brand new TF700T and did make it work to support root.
I also did unlock the bootrom protection.
When I tried to install a custom ROM manager (Clockwork Mod) image from:here
The device didn't want to start any more - showing message:
The Device ist Unlocked.
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
But nothing happens anymore (
I can wait for the battery to run empty in this mode.
There' no chance to boot from Micro SD.
The only thing what works at the moment is to connect the device via APX drivers.
I tried to communicate with device via NVFLASH tool
But when trying this - I get the message:
Nvflash started
Unknown Device found
Does any one have an idea where to find appropriate drivers for Nvflash?
Or the parameters to match TF700T?
Thanks in advance!
if you are able to access APX then you still have hope, first of all you need to push custom recovery like TWRP via fastboot mode and then install custom ROM. Most likelly you were to lazy to read a lot information on this forum how to install stuff properlly.
EDIT: if Tf700t has pin hole you should turn it off despite waiting for it to discharge...
nikoltu said:
if you are able to access APX then you still have hope, first of all you need to push custom recovery like TWRP via fastboot mode and then install custom ROM. Most likelly you were to lazy to read a lot information on this forum how to install stuff properlly.
EDIT: if Tf700t has pin hole you should turn it off despite waiting for it to discharge...
Click to expand...
Click to collapse
I did already read a lot - for hours and nights.
But my main problem is: UNKNOWN DEVICE
What does TWRP mean? How do I get fastboot to work?
I'm even not allowed to enter recovery mode.
The device is just recognized as an APX -device...
I can't push or download any custom ROM since I can't communicate with the device in both directions...
For those who messed up really bad and can't boot but are unlocked.
EDIT: I didn't see that you are not unlocked. then you should Power on + volume down, wait, see two icons select wipe, pray to god it helped or not. And if it doesn't boot and you are not unlocked last thing to do is RMA.
You are not allowed to enter recovery because you have stock one with droid dead and red triangle I guess.This is TWRP site and all instructions are here TWRP - Team Win Recovery Project is alternative to ClockworkMod Recovery but better. to get to fast boot turn on your tab holding power on + volume down and then do nothing while it asks to pres up. if you are unlocked you will see 3 icons select usb drive icon. FASTBOOT mode. now follow instructions from TWRP site. after that youl need custom rom zip. if recovery instaled successfuly and you can get into it you'll need to put custom ro into microSD or if you can into internal storage. if you can't conect to pc via cable and start cmd if Windows or terminal if Linux or mac. type
Code:
adb shell
mount /dev/block/mmcblk1p1 /data/media
you will be able to access microSD via recovery (unless it is different than Prime tf201 you will need different command, but give it a try)
nikoltu said:
EDIT: I didn't see that you are not unlocked. then you should Power on + volume down, wait, see two icons select wipe, pray to god it helped or not. And if it doesn't boot and you are not unlocked last thing to do is RMA.
You are not allowed to enter recovery because you have stock one with droid dead and red triangle I guess.This is TWRP site and all instructions are here TWRP - Team Win Recovery Project is alternative to ClockworkMod Recovery but better. to get to fast boot turn on your tab holding power on + volume down and then do nothing while it asks to pres up. if you are unlocked you will see 3 icons select usb drive icon. FASTBOOT mode. now follow instructions from TWRP site. after that youl need custom rom zip. if recovery instaled successfuly and you can get into it you'll need to put custom ro into microSD or if you can into internal storage. if you can't conect to pc via cable and start cmd if Windows or terminal if Linux or mac. type
Code:
adb shell
mount /dev/block/mmcblk1p1 /data/media
you will be able to access microSD via recovery (unless it is different than Prime tf201 you will need different command, but give it a try)
Click to expand...
Click to collapse
Thanks for advise - BUT
I have no choice like selecting Fastboot or USB etc. with volume buttons.
These options unfortunately do not come up anymore.
My device is definetly unlocked. It shows up "Device unlocked" when trying to boot normally.
When trying to go to recovery, with Volume - hold, the device tries to launch to recovery but hangs in status:
Device is Unlocked
Android cardhu-user bootloader (2.10 e) released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel.
I have NO option to go to fastboot! Only way will be APX but nvflas always tell me unknown device.
So I was looking for any other version of nvflash.
In other forum I did find hint for nvflash ICS but didn't find right version yet.
If I only could get communication via APX worked to my device, then I could send data via nvflash and APX...
I assume you can't even go to rom as it bootloops on EEE pad screen not on rom splash screen
1. Did you try Wipe option in (power + volume down, wait 5 sec.)? [it is esential in all situations of trying to recover]
2.ammm... when you enter "adb devices" in your cmd on PC doesn't it show anything (do it while your tablet is on and hangs anywhere, just make sure it is on)? list is empty? if not it shows your device with some random letters and numbers.
Try manually setting your pc. Download android SDK and all packages for Android 4.x then in Device Manager (Control panel) find your Tablet and update your driver to Android ADB interface (you can experiment, till your device is shown correctly via adb devices command).
But first of all make sure you do or did first step. it is common issue among Prime users so maybe it can help you.
nikoltu said:
I assume you can't even go to rom as it bootloops on EEE pad screen not on rom splash screen
1. Did you try Wipe option in (power + volume down, wait 5 sec.)? [it is esential in all situations of trying to recover]
2.ammm... when you enter "adb devices" in your cmd on PC doesn't it show anything (do it while your tablet is on and hangs anywhere, just make sure it is on)? list is empty? if not it shows your device with some random letters and numbers.
Try manually setting your pc. Download android SDK and all packages for Android 4.x then in Device Manager (Control panel) find your Tablet and update your driver to Android ADB interface (you can experiment, till your device is shown correctly via adb devices command).
But first of all make sure you do or did first step. it is common issue among Prime users so maybe it can help you.
Click to expand...
Click to collapse
I would like to exchange email-adresses to enhance communication.
You could also send email to [email protected]
I did try with button combination (power & + button) as well, but device did not wipe.
For now - I'm about to update Android SDK )
Hopefully this works to recognize my TF700T...
If you manage to unbrick please post the information back here it may be helpful to others.
t-liner said:
My device is definetly unlocked. It shows up "Device unlocked" when trying to boot normally.
Click to expand...
Click to collapse
How did you get your TF700 unlocked? Asus hasn't posted an unlock tool for it yet that I could find.
Asus devices have the same unlock tool
Sent from my Transformer Prime TF201 using xda app-developers app
nikoltu said:
Asus devices have the same unlock tool
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
Unlock + Root was never a problem.
I managed it to unlock the device using the TF300T tool / link.
Boot loop was big problem.
I did raise RMA in the meantime. New device is on the way.
Thanks to all repliers.
I will keep off doing this again / wait until xda-experts will provide a working way to CWM TF700T.
My Transformer Infinity isn't bricked, I just can't get it to boot into recovery. (I'm unlocked and rooted, but no custom ROM.) I have tried both CWM and TWRP 2.2.0 with GooManager. The tablet just won't boot into recovery mode. I can hold the Down Volume key and Power button to have the initial boot up menu display. When I press the Up Volume button to boot into recovery mode, it just hangs like the OP talks about. I then have to hold the power button for about five or so seconds to get it to power down again. I can turn it back on and it will boot normally.
I thought maybe something was messed up because I installed busybox, or hacked the Flash Player to work in desktop mode, or tweaked the build.prop file or something. I've put the build.prop file back to default, and removed the busybox apps, but that hasn't resolved the problem. I've tried re-running the unlock tool, but it fails halfway through. I'm not sure if that's normal or not after you've run it once, or an indication of something messed up.
Any suggestions on what else to try or look at are appreciated.
---------- Post added at 06:06 PM ---------- Previous post was at 05:13 PM ----------
UPDATE: I finally got TWRP 2.2.2.0 to work using the following option from the Instruction Page (http teamw.in/project/twrp2/105):
Download - ADB / Terminal method:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
stuck at boot logo
Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced
dough30i said:
Im having the same issue, i was playing around with black baked bean roms i just installed early that day and i wanted to switch twrp to cwm and by deleting goo manger to get roms manger and install the recovery mod but damn i notice it say asus transformer prime and not infinity noe that think about i thats the reason i cant get into reboot recovery mode damn i fuk up bad. okay so i did the stock recovery boot mode got into that i i remember seeing in this post that someone say try to wipe data and i did that and now im juss stuck asus logo and with
(The Device ist Unlocked.)
Android cardhu-user bootloader <2.10 e> released by "TW_epad-9.4.5.22-20120615" A03
Checking for android ota recovery
Booting recovery kernel image
im just there and when i try to plug into my pc it shut down by self, i even wait till the battery die and hope to god that it well reboot itself and pwaw it reboot nope that ****..can any one please tell what i did wrong or didnt do it would help me alot .THanks a million in advanced
Click to expand...
Click to collapse
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.
gaxiolafm said:
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.
Click to expand...
Click to collapse
Damn u too huh. **** I just got mine for only 2 week old and neva thought I go through this IDK what to do but wait gracefully for the senior member to help or come up with a way for us noobie to unbrick my 650 table...Oh BTW leave it alone then u still lucky if can go thru fast boot mode
I have the exact same problem
anyone has a solution to this problem
gaxiolafm said:
Trying to flash the new CWM recovery, too. Mine gets stuck in the bootloader menu (where you have to choose between Wipe, fastboot mode, and cold startup). Every time I select fastboot it says "starting fastboot usb protocol" and just hangs there.
Click to expand...
Click to collapse
That is what it says when you are in fastboot mode, the rest of the job you do with a computer. Also we have had major issues with cwm on the Prime, I would recommend TWRP!
Sent from my Transformer Prime TF201 using xda premium
Same problem
israodin said:
I have the exact same problem
anyone has a solution to this problem
Click to expand...
Click to collapse
Same problem.
Any help? Please! :crying:
I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.
there is a way on the TWRP instructions using terminal when you are in system
nitsuj79 said:
I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.
Click to expand...
Click to collapse
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me
mikaole said:
there is a way on the TWRP instructions using terminal when you are in system
Click to expand...
Click to collapse
You must have root permission for that method
imp3r10 said:
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me
Click to expand...
Click to collapse
No when I try to flash recovery it says waiting for device and nothing ever happens.
I seamed to have got it. I down graded to 10.4.2.9 and back to 13. plugged it to the computer and this time it installed drivers and that time I was able to flash recovery. I don't know what happened and it was probably something that I was doing wrong. But just incase that is what did the trick and it helps someone else, i wanted to be sure and follow up.
Hello I went to install the new update 4.2.1 and it did not go well and now my tablet will not even enter the usb protocol its gone so I cant flash a system blob. any suggestions
tcoleminnie said:
Hello I went to install the new update 4.2.1 and it did not go well and now my tablet will not even enter the usb protocol its gone so I cant flash a system blob. any suggestions
Click to expand...
Click to collapse
No one here is a mind reader/psychic you would have to provide more information on what you did and how you tried to do it inorder for anyone to help.
before installing the update I went into bootloader and wiped data and when I went to reboot to do a fastboot flash everything was gone if I hold down power and volume down it just goes right to twrp recovery. there are no options power and volume down does not work anymore.
if you can see your device in adb from cwm try to type
adb reboot bootloader
can you point me in the direction of a how to for adb
tcoleminnie said:
can you point me in the direction of a how to for adb
Click to expand...
Click to collapse
Try this guide here
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Downloaded the latest firmware that came out today from the asus site which is the version you just upgraded too
If you can get it to the bootloader you can try using fastboot to flash the blob image and see if it boots
Good luck
Hello everyone, it's my first time that I'm stuck in this stupid way. now I'm with JB not-root and Team Win recovery in boot loop. he asks for the password to decrypt data and you can not wipe or mount anything. I can do reboot but he goes right into recovery without being able to get into fastboot. what i can do now for return to stock. boot loader are unlocked.thz for all help.:highfive:
What bootloader & what recovery?
Ti2 said:
What bootloader & what recovery?
Click to expand...
Click to collapse
Team Win 2,4,4,0 boot loader version i cant see
4.2.1 rom?
Ti2 said:
4.2.1 rom?
Click to expand...
Click to collapse
the last JB official from site.
pierpa86 said:
Team Win 2,4,4,0 boot loader version i cant see
Click to expand...
Click to collapse
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
lk2l said:
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
Click to expand...
Click to collapse
i can't
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
pierpa86 said:
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
Click to expand...
Click to collapse
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
lk2l said:
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
Click to expand...
Click to collapse
no i can't i push power + up or down nothing same story. stupid error:silly:
pierpa86 said:
no i can't i push power + up or down nothing same story. stupid error:silly:
Click to expand...
Click to collapse
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
lk2l said:
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
Click to expand...
Click to collapse
It will only work on UNLOCKED devices
It requires access to Fastboot to prepare device first time
It won’t work on fully bricked devices (See 2.)
You need to keep files safe!
If you upgraded to Offiical JB it *won’t* work!
i'm not have fastboot and i'm on Official JB
i have try to enter on APX mode but i can't
did you try to install the asus pc sync (it shoul install the driver for use adb & fastboot) and after boot into recovery
from prompt you should be able to use adb
write adb devices
and if you can see the code of the devices may you can still have a possibility to flash troght adb
ok man i understand the problem today
i have flashed the last TeamWin Recovery but not compatible with 4.2.1 but 4.1 stock rom and now all partition can't be mounted in recovery, i have found adb in broken recovery and push recovery img for flash with dd command and all done in shell but nothing flashed !! then "adb reboot bootloader" for try to reflash with fastboot, same story all done in shell but nothing flashed !! ok no problem i try to boot android in boot menu and damn partition is ok and android booting !!!!!!! :laugh:
ok remain 2 way. use dd in terminal emulator but can't without root permission and use nvflash but it's not work with JB confirm ?
waiting for a tool using an exploit for root from internal android and try dd or next update for nvflash.
any idea ? and sorry for my very bad english
Key driver not found.. Booting OS
Android cardhU-User bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
[RCK] [ANDROID] [WIPE DATA]
when try flash in fast boot get freeze !!
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and what do you think about ?
if you can boot the system may you can verify again the bootloader whit asus tool from the website maybe for any unsense reason it's locked....
ops wrong tread
Ok, I just tried some stuff and:
1. I can also access fastboot and OS.
2. Trying to flash modified TWRP with fastboot freezes bootloader.
3. In-system can't open .RAR files.
4. After manually transfering unpacked V8 unlocker from PC it says there's an "unknown problem" when trying to install unlocker. It supposedly upgraded from V7 to V8 app without problem.
In bootloader it says at the top of the screen that "Key driver not found... Booting OS". After that it lists bootloader info ( v. 1.00 e ).
Looks like recovery's bricked with some further issues in the OS itself.
EDIT:
Bricked the OS. Tried reflashing stock system and now bootloader freezes when trying to boot OS. My guess would be that fastboot can still erase stuff but most likely can't write ( at least not properly ). Google/Asus probably know of a way to restore our tablets but Asus clearly prefers to replace motherboards.
I have to think whether it's worth it for me to replace the MB but most likely will just sell the thing for parts.
whan you try to re-flash the system somthing goes in the wrong way? do you still have fastbooy access? was the usb debug on?
sorry but which rar you can't open?
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.