Related
Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.
Did you try ADB fastboot method?
Not sure how to try that
I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.
ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>
also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.
TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.
I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.
You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.
Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.
Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.
The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.
Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Moved.
mathiash98 said:
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Click to expand...
Click to collapse
Apx is a method provided by the cpu manufacture for recovery. Due to the way asus has handled locking the unit apx is only available if nvflash is installed while on ICS (4.0).
Reset may be a good option for you. Power on unit. Hold volume down and insert a small paperclip to into into the reset hole. This may get you into the bootloader.
Reset: A small hole about 25mm or 1inch below the sdcard slot.
Note: If this fails you could do the same but hold volume up and hope.
Beyond this running the battery down has worked for some or remove the back cover and disconnect the battery. Leave it disconnected for thirty minutes, then reconnect.
Also see my signature for other methods to get into the bootloader. Don't bother with apx as it is useless for us.
We are looking for any change in the unit. With a change may come use of adb, fastboot, or recovery.
Try do each thing in turn and repeat this sequence twice more.
Thanks for the explanation and fir the tips! I'm going to try this
mathiash98 said:
Thanks for the explanation and fir the tips! I'm going to try this
Click to expand...
Click to collapse
Good Luck!
tobdaryl said:
Good Luck!
Click to expand...
Click to collapse
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
mathiash98 said:
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
Click to expand...
Click to collapse
I understand. If still in warranty I wouldn't remove it either.
I'm sorry that is all I have for your situation.
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
goldenval said:
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
Click to expand...
Click to collapse
Which tablet do you have? You show TF300T but using TF300TG twrp.
The bootloader changed again with 4.2 firmware and requires twrp especially for that version. I have been told the openrecovery-twrp-2.5.0.0-tf300t-4.2.blob does not work properly so you should have used openrecovery-twrp-2.4.4.0-tf300t-4.2.blob if you have a tf300t.
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
goldenval said:
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Click to expand...
Click to collapse
Ok...
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
n3tm0nk said:
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
Click to expand...
Click to collapse
My suggestion is use stock recovery to replace the encrypted os (probably JB 4.2) with JB 4.1 (10.4.2.20). You can download here [INDEX]25 Apr 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides-. Look in firmware TF300T. Use the proper sku (ww, us, etc) for your country. Please give philos64 a thanks while there he spent much time creating that post, supporting the downloads, and updating.
Unzip the downloaded file once - rename to EP201_768_SDUPDATE.zip. Place the file on your internal sdcard if possible if not place on your micro sdcard. Boot into the recovery console and make the hungry android happy. This will probably take ten plus minutes.
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
tobdaryl said:
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
Click to expand...
Click to collapse
goldenval said:
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
Click to expand...
Click to collapse
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
tobdaryl said:
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
Click to expand...
Click to collapse
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
goldenval said:
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
Click to expand...
Click to collapse
Go manager does not have the proper twrp for our tablet.
Rooting is no longer required to flash twrp. Motochopper will root with just adb.
I suggest we try to get everything working properly with stock before changing or adding anything.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot. Verify everything works properly before making any other changes.
Thank you for the donation offer.
I don't have a method to receive donations. A simple click on thanks will be good.
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
tobdaryl said:
Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot
Click to expand...
Click to collapse
goldenval said:
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
Click to expand...
Click to collapse
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
May I ask you then? My ROM number is: JOP40D.WW_epad-10.6.1.15.3-20130416 & as I can see from numbers you are offerring me to downgrade (from 4.2 to 4.1). Will this not kill the device? And why can't we re-install existing ROM through ADB? I'm not arguing, just trying to understand.
tobdaryl said:
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
Click to expand...
Click to collapse
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Unlock unlocks the boot loader allowing you to load custom roms via additional boot loader as per rom instructions, it does not give root access. You will need to search to a process to root the tablet, I used Kingo root, some do not like using this......although I had no problems. Using custom roms and rooting is at your own risk!
So this is the process that ive Followed... I ran the unlock tool, everything completes without issue. Nexissue the command adb reboot bootload to get my tablet into correct mode. Once the tablet is ready I flash a recovery image (TeamWin TWRP) to the device and boot the recovery. From here, it seems that recovery does not permission to mount any of the drives/folders. I look at the log file and see errors sayin unable to find partitions and unable to mount folders/drives. Below is a link to an image of the errors.
I am not sure if this link will get posted correctly to this thread: https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing
BTW, thanks for your quick reply.
FYI, for the link above, there is a space between the HTTPS:// and the word drive which start the web address. The forum would not allow me to post a link since I am new.
Sorry, I'm no expert. When I installed Kang TWRP for KatKiss Lollipop, I did lots of research before diving in. Carefully followed instructions and all went well. When you flashed TWRP did you then reboot into bootloader?
fastboot reboot-bootloader
I think you will have to give all the steps you took, then perhaps someone will come along with more guidance.
Just to add some clarity to my situation, in hopes that someone can help shine a light:
1) Installed and ran Unlock device app V8 on the Asus webiste. It claims this is compatible with android version 4.2, i have version 4.2.1. Unlock ran then needed to reboot device. Upon reboot I saw the message "This device is unlocked" in the top right of the screen.
2) Once device rebooted, I installed adb/fastboot on my pc and ran it using CMD.
3) Connect tablet to PC using usb cable.
4) Ran the command "adb reboot bootloader" to get the device into required mode.
5) Next I run the command "fastboot devices" to verify the PC can see the tablet.
6) Run the command "fastboot -i 0xb05 flash recovery Recovery.img" to flash over the Recovery image file I have. Flashing goes through without any errors.
7) Once flash completes, I press up volume button to go into recovery.
8) Recovery boots and I am at the screen with the various options to install, backup, restore, wipe, etc.... I have Team win recovery project v2.8.7.0
9) If i try to use the backup option, it shows my internal storage as (0MB). I look at the log file (https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing) and see that it cant find or mount various drives. If you want to view link, copy url and remove the space between https:// and the word drive.
**** ALSO, if you have a better or proven method, please feel free to suggest.*****
imnotorginal said:
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Click to expand...
Click to collapse
This issue has been resolved. It looks like the version of TWRP I was using (2.8.7.0) was not getting access to the file systems to be able to make changes or install.
I downloaded version 2.8.7.2 and everyone went flawlessly after that.
Special thanks to bonzoe for telling me that he was using Kang TWRP which led me to google that and get a new version.
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.
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.