Related
Hello,
I have my TF700 bricked. In the Devicemanager I can see only a APX device. I cannot connect the tablet via fastboot neither adb.
I have download the Universal_Naked_Driver_0.7_tf700 apx driver, but I cannot install the driver. In the internet I found the following link:
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
I hope when I install the apx driver I can flash the Device. I hope anybody can help me.
If it is already bricked and you dont have a nvflash backup, there is no way out. Also this needs to be in Q&A
its a pain in the ass.because for some reason when you unistall the drivers there is no way to remove them complitely from the system.so i did this.you uninstall the device from device manager, then diasble internet connection .unplag the usb and plug it again .then unistall again the drivers.now it won't recognise the tablet like it used but just like mstb device.now when you rebbot into fastboot the device should be recognised like asus tablet fastboot. you are good to go..also when you reach the step to reboot into apx mode you must reinstall the same driver but this time the device would be recognised like asus...apx 700.
i hope this guide will help you.
edit.just saw youre bricked so from what i know even if you succed loading apx drivers there is for now at least no way to reupload the files neccecery to unbrick it.those files are unique per device generated
If you're already bricked, try giving this a shot:
http://forum.xda-developers.com/showthread.php?t=1903134
or if you can get the drivers to work, you can extract the blob and install it using fastboot by doing:
fastboot -i 0x0b05 flash staging blob
If you haven't upgraded to .30, make sure you download version .26 so that you can create the nvflash files for your tab.
If you have already upgraded to .30, you must use version .30, you cannot downgrade to a previous version even with an unlocked tab(unless you have the nvflash files), and you cannot create the nvflash files for your tab, and therefore will not be able to use nvflash in the future.
Also what error are you getting while trying to install the drivers? I had issues with installing the drivers that was resolved by using a different computer.
Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
acelaw said:
Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
Click to expand...
Click to collapse
You flashed a PRIME rom to your tf300?
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
ppmeis said:
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
Click to expand...
Click to collapse
but fastboot need a unlocked bootloader, no?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Yes, that's right, but I suppost if he tries to flash a custom rom he has already unlocked his device. You can't flash any rom without unlock bootloader.
I cant do anything apart from get on to apx mode, from apx mode how do I use command to flash back.
My tf300 is ics, unlock.
when i connect usb to pc. i press power and volume up. thats only things i can do.
so what do i do next?
thanks.
The same problem.
I only see: "device is unlocked" or something like that. And nothing go on.
Is it totaly bicked or is there any chance to restore it?
Please advice.
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
bigworm82 said:
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
Click to expand...
Click to collapse
Try this link.
http://forum.xda-developers.com/showthread.php?t=2034866
no way to unbrick tf300t
Funny, I bricked my tf300t without doing anything. One day it just got stuck in asus screen.
tried to recover, nothing happended.
tried hard reset. Nothing.
Wipe data: result: bricked tablet.
I'm looking for information it is defintely impossible to unbrick it.
Anybody else with the same situation can tell you that.
Nobody has even been able to do it.
If you send it to Asus they provide a new tablet.
Conclusion:
TF300T is a terrible product, as any other asus product i assume. Amazing that you can brick a tablet without even trying to flash it or without even being connected to a computer.
It bricks by itself. Hundreds of other users can confirm it.
My advice: dont by asus products
If you already have one, dont use wipe data as anybody who has done it has ended up with an expensive useless brick.
Odp: [Q] How to unbrick my tf300
I don't agree witch this, only think what you not should use is t the wipe data from bootloader menu - I already flashed many times not working kernel, get really often bootloop - the problem is - much users going to made stupid things when the get a soft bootloop - If you get this first try wipe data from recovery, if this won't help, try to format data from recovery - often happends that the ext4 filessystem get broken. Recovery should allowa us to run fsck on data - I fixed my bootloops many times with it without loosing my data.
Sent from my GALAXY Cooper
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
opethfan89 said:
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
Click to expand...
Click to collapse
I have problem that my partitions won't mount at all. I have access to fastboot, CWM, and adb but no matter what i cannot access my partitions and so i cannot install zip from CWM. When i try blob within fastboot my tablet just freezes.....
Hi, what happens if I have no access to fastboot? It loops in the ASUS logo and what ever I do, can't gain access to recovery because it doesn't get into fastboot. So how to solve it via APX? Thank you.
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
unbrick tf300
ilyuha1108 said:
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
Click to expand...
Click to collapse
Hi,
I am having a similar problem to the one described. I have unvblocked my TF300T and installed CWM recovery (v. 6.0.2.3), but it can't mount any filesystem, so I can not flash anything. The boot menu is gone (RCK, wipe tablet, android) and when I switch the tablet on It just goes to CWM. If I connect the tablet to a PC, I can send commands with adb from my win 7 PC (for instance "adb reboot" will reboot the tablet), but fastboot doesn't work (it keeps "waiting for device"). Prior to this my android version was JB 4.2. I didn't make any backup, so I am fearing the worst outcome. Did I brick my tablet for good?
Thanks a lot for any reply.
TF300T blocked on boot screen
hello everybody,
my name is jonathan, and i have a very big problem.
My Asus TF300t is blocked on boot screen after try to install a new rom on JB 4.2.2.
>My clockworkMod reconvery is v6.0.1.0.
I tried to install several roms, offical or not but the problem is the same, "The device is unlocked" on the boot screen Asus...
I read the previously posts and :
- i installed on my pc the sdk
- i dowload the "blob" file and i placed it on tools directory
- but, the actually problem is whis the lign "fastboot -i OxOBO5.... (i have copied and paste it on schell command) and enter
load_file: could not allocate 820157833 bytes
error: cannot load "blob": not enough space
can you help me please ?
i want to resolve this problem with you to install the best rom for this model.
Thank you very much and sorry for my english, i am french but i understand your paragraph.
See you soon
Jonathan
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
same problem of space
Buster99 said:
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
Click to expand...
Click to collapse
Hello man,
I try your method but the problem is the same when i want to copy the blob file, "not enough space ..."
fastboot erase system OK
fastboot erase recovery OK
fastboot erase userdata OK
fastboot erase boot OK
fastboot erase misc OK
fastboot erase cache OK
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob PROBLEM
The message is the same like previously, always the problem of space.
I tries the method by copy the blob file on different directory on my computer and on a usb key too.
Always the same problem of space
I think the problem is the space on the tablet but i dont' understand. I erase system, recovery, userdata, boot, misc, cache, i think the tablet is empty.
Can you help me please ?
Thank you very much
Jonathan
which blob file did you use? Was the zip appropriate for your region? also what was the last stock rom version you ran - you said you wanted to update to 4.2.2 - what was the old version?
-Buster
My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?
It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back
So I got somebody to help me out with the $25 on Sunshine, S-off, unlocked, rooted. I go to Google Play and get TWRP and go to "TWRP install" select my phone type, the newest build and I install it, says it installed fine and asked to boot into recovery mode which just takes me to a triangle and an exclamation point. I vol -/+ power to restart and it sticks me on the "HTC" boot up screen, I vol + and power with a quick transition to vol - to try and do a factory reset and start over again and it won't even allow me to do that. Now what? Did I brick it? Does anybody have a link that'll get me out of this mess and get a custom rom flashed on here?
Thank you!
I'm still at it trying to get an older version of TWRP on it via ADB which I installed on my Mac but I can't get the Mac to recognize the M8 so I am messing something up along the way. Does anybody know how to get this done?
I always do my best to document my progress so that it's solved for the next person that has an issue. I'm still stuck and have tried installing the SDK tools on both Mac and Windows and I can't get ADB to pick up the device in fastboot mode on either. I'm typing this on a Linux machine, I guess I could try it from here for fun but I'm guessing there's some other issue going on. I'm just trying to figure out how to get TWRP flashed on at this point so I can get out of my soft brick issue.
Tucson85743 said:
I always do my best to document my progress so that it's solved for the next person that has an issue. I'm still stuck and have tried installing the SDK tools on both Mac and Windows and I can't get ADB to pick up the device in fastboot mode on either. I'm typing this on a Linux machine, I guess I could try it from here for fun but I'm guessing there's some other issue going on. I'm just trying to figure out how to get TWRP flashed on at this point so I can get out of my soft brick issue.
Click to expand...
Click to collapse
While phone is in fastboot, you need to use fastboot commands, adb won't work. Connect phone to pc while in fastboot mode then try typing in "fastboot devices" and hit enter. If it shows you device S/N then you are good to go. To flash recovery you normally use "fastboot flash recovery recovery.img" assuming you renamed the twrp file to recovery.img
If you cant get that to work, you might try looking for the RUU file for your device to reset your device back to completely stock firmware and start over.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
While phone is in fastboot, you need to use fastboot commands, adb won't work. Connect phone to pc while in fastboot mode then try typing in "fastboot devices" and hit enter. If it shows you device S/N then you are good to go. To flash recovery you normally use "fastboot flash recovery recovery.img" assuming you renamed the twrp file to recovery.img
If you cant get that to work, you might try looking for the RUU file for your device to reset your device back to completely stock firmware and start over.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
That was a HUGE help actually and this is way easier on my Linux box. It's communicating in fastboot but won't boot into TWRP when I go to recovery yet. I'm trying to fastboot a custom rom to it now to see if that works but am having some issues thus far but will keep at it.
****Edit So I think it was the version of TWRP I was using that was the issue this entire time. I tried 2.8.7 which caused the issues, then to flash 2.8.3 and 2.7.0.1 to try and get something to recover from with no luck and finially I used fastboot on Linux to get 2.8.0.0 on it and it's going into recovery find from that.
****Edit 2.0 I have TWRP working but can't wipe or install and keep getting an error "twrp unable to mount /system" so I need to address that somehow, how sure what the issue is but I'm worn out on it so any help or ROM suggestions to use from here would be amazing!
****Edit 3.0 After retrying with 2.8.7 and it not working at all I tried with 2.8.0.1 and had the same issue so I went up to 2.8.0.2 and that fixed it now I just need to find the right rom to download and flash.
****Edit 4.0 Okay I am all set and figured out the issues and have SlimKat running on it now. Thanks for that little nudge in the right direction!
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.