Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this >?
ilko83 said:
Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this >?
Click to expand...
Click to collapse
I answered this in the other place you posted but adding here as well:
ilko83 said:
Need Help. My tablet got into bootloop after installing > TWRP 3.0.0.1. and i cant get into > Recovery. I was running marshmallow. I cant connect to fastboot, i got the fastboot drivers installed but i cant turn usb debugging on.....
How can i fix this ****>?
Click to expand...
Click to collapse
TWRP 3.0.0-1 is for A 5.x and Earlier (Lollipop and earlier)
zarish said:
These are the versions I recommend (in order of current and prior versions that I have tested on an Original 2014 Shield Tablet):
NVIDIA 1.x to 3.x - Android 4.x to 5.x (KitKat to Lollipop) -- Untested by me but should match for K1 NVIDIA 0.0.0 - Android 5.1.1:
TWRP 3.0.0-1 lj50036 - http://forum.xda-developers.com/showpost.php?p=65249195&postcount=94
TWRP 2.8.7.1 romracer - http://forum.xda-developers.com/showpost.php?p=55446061&postcount=2
NVIDIA 4.0 - Android 6.0 (Marshmallow) -- Untested by me but should match for K1 NVIDIA 1.0 to 1.1 - Android 6.0:
TWRP 3.0.0-0 romracer - http://forum.xda-developers.com/showpost.php?p=55446061&postcount=2
TWRP Experimental Steel01 - http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
Click to expand...
Click to collapse
As for how to fix.
Hold power button until device turns off completely
release power button
Hold volume down button, while continuing to hold volume down, press power until device turns on and menu appears.
Once the fastboot menu appears, connect to the PC.
use fastboot to flash a recovery compatible with marshmallow (e.g. - fastboot flash recovery twrp-3.0.0-0-shieldtablet.img ) (NOTE: Use romracer's Marshmallow 3.0.0-0 here if on A6.0 or above)
select Reboot Recovery on the device just to prime it and go in once (this is what I do, you could just reboot if you like).
zarish said:
I answered this in the other place you posted but adding here as well:
TWRP 3.0.0-1 is for A 5.x and Earlier (Lollipop and earlier)
As for how to fix.
Hold power button until device turns off completely
release power button
Hold volume down button, while continuing to hold volume down, press power until device turns on and menu appears.
Once the fastboot menu appears, connect to the PC.
use fastboot to flash a recovery compatible with marshmallow (e.g. - fastboot flash recovery twrp-3.0.0-0-shieldtablet.img ) (NOTE: Use romracer's Marshmallow 3.0.0-0 here if on A6.0 or above)
select Reboot Recovery on the device just to prime it and go in once (this is what I do, you could just reboot if you like).
Click to expand...
Click to collapse
I tried that- it shows 'waiting for device' , im in fastboot menu on the device, and i gt the usb drivers instaled, and yes i tried different usb port. Is the usb drive different for W10>?
Have you tried selecting fastboot on the device (should pretty much reboot the bootloader screen and end up right back at the same menu?
It sounds like your drivers are installed wrong and/or you selected the wrong driver if the device is not showing in Windows.
If the above doesn't work, I would disconnect the device from the PC.
Open device manager.
Connect the device to the PC, and watch what the device gets recognized as.
Then forcibly update the driver and point it to the one from this package and select the fastboot one: http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201506.zip
zarish said:
Have you tried selecting fastboot on the device (should pretty much reboot the bootloader screen and end up right back at the same menu?
I tried that. It still shows 'waiting for device'
It sounds like your drivers are installed wrong and/or you selected the wrong driver if the device is not showing in Windows.
If the above doesn't work, I would disconnect the device from the PC.
Open device manager.
Connect the device to the PC, and watch what the device gets recognized as.
Then forcibly update the driver and point it to the one from this package and select the fastboot one: http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201506.zip
Click to expand...
Click to collapse
When I forcibly update the driver and point it to the one from this package it shows 'the folder you specified doesn't contain a compatible software driver for you device'.... The tablet boots to the rom and then goes to a bootloop , and i didn't have developer mode turnd on. Maybe that's y i cant connect to ADB -fastboot.
Any suggestions>?
I can't speak to Windows 10 as I refuse to use that OS.
I can say the driver package is right and should most certainly contain the fastboot driver for all version of the Shield Tablet.
You should not be seeing the NVIDIA logo if doing things right. It should turn on to the bootloader menu. If you see the NVIDIA logo, then start over as it didn't register you turning it on and holding the volume down at the same time. Generally I keep holding volume down until I see the bootloader menu.
The bootloader and fastboot mode have nothing to do with if you have enabled USB debugging or not as it is well before that level of OS.
Where is the link twrp 3.0.0.1 cheers
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:
Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...
What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.
huy_lonewolf said:
What firmware are you on? That guide is not updated for newer firmwares as newer firmwares have already removed that usb icon in the bootloader screen. In order to enter fastboot mode, all you need to do is power + volume down (holding down both buttons) and you should already be inside fastboot mode, no other button needed. Otherwise, through adb, you can try "adb reboot bootloader", which should take you to fastboot mode as well.
Click to expand...
Click to collapse
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers
tf700tTRANSF said:
Ah this explains a lot. Now when I connect it to my PC it is recognized, but when i run a 'fastboot devices' (eveything is set properly with paths etc) my tablet isn't recognized. Should I install a different driver? As for now my PC says it has APX drivers
Click to expand...
Click to collapse
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.
huy_lonewolf said:
It most likely means that you have the wrong fastboot driver. You should follow the instructions here (http://forum.xda-developers.com/showthread.php?t=2263822) to install the correct fastboot driver from the Universal Naked Driver pack. If you install the driver correctly, the tablet should appear as "ASUS fastboot device" in Windows' Device Manager. Then fastboot commands should work. As a quick reminder, the fastboot driver is a different driver from the adb driver. Windows will only see the fastboot device when you connect your tablet to your PC while the tablet is in fastboot mode, hence a separate driver is needed.
Moreover, when you flash the recovery later, you need to remove the dock and connect your tablet directly to your PC. In my case, even though fastboot recognized my tablet, the flash recovery command failed if the dock was connected.
Click to expand...
Click to collapse
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?
tf700tTRANSF said:
I tried many drivers from the universal naked driver pack. But still, wen i type in 'fastboot devices' nothing happens, and with getvar i only get 'waiting for device'.....I really dont get it, what am I not seeing her....
But then again I cant seem to get "ASUS fastboot device" in windows device manager. Only Asus fastboot interface and some others with ADB etc. Am I looking at the wrong drivers?
Click to expand...
Click to collapse
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.
huy_lonewolf said:
Let me try to recall the exact steps that I did to get the driver installed. I am using Windows 8.1, so the first step for me was to boot into troubleshooting mode of Windows to disable driver verification, but you won't have to do that if you use windows 7 or earlier. After that, open Device Manager, right click on ASUS bootloader interface (or a different name with the yellow question mark, but I remember when I first connected my tablet to my PC, the name was "ASUS bootloader interface"), choose Update Driver Software, then choose "Browse my computer for driver software", and click on "Let me pick from a list of device drivers on my computer". At the next screen choose "Have Disk", browse to the Universal Naked Driver folder and select the file "android_apxusb.inf". From the list you should be able to find "ASUS Fastboot Interface" and install it.
Click to expand...
Click to collapse
I really dont get it....It just wont work. Fastboot still wont recognize my tablet.
If i get my hands on another Windows PC I will make a second attempt.
If someone knows a different solution, please tell me. Fastboot on the pc is properly installed for whats it worth....
Try Goo manager Open Recovery Script
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
tf700tTRANSF said:
Hello everyone,
I am new to XDA but not new to the Android rooting, flashing industry. I've flashed and rooted several phones, aswell as my own phone with a custom ROM. So I figured, since mine tf700t hasnt any warranty anymore that I will install Cromi due to the lag of the original software.
In order to install Cromi you need an unlocked bootloader and TWRP installed. The unlocking of the bootloader was like stealing candy from a baby. Then i wen't on to install TWRP with this guide: http://forum.xda-developers.com/showthread.php?t=1833212
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
At step 4 I ran into some problems. No matter what I do, i can't seem to boot the device into fastboot where you will see the three icons, among them the USB icon. I watched several youtube videos and read everything i could find but still no solution. What am I doing wrong at this point? What I did noticed was that the volume up and down buttons in some videos where at a different place then mine are. I have a Tf700t, when it is in landscape the volume buttons are at the top right corner on the edge of the device, the power button is on the top left on the edge of the device. At some videos the volume button was on the left side and on the top right side. Does this maybe have anything to do with it?
Thanks for the help in advance. I feel kinda stupid to not get it into fastboot mode, this never was a problem with other devices...
Click to expand...
Click to collapse
mustafa_droid said:
I am not sure if this will help you because I am also new to this but I unlocked and rooted my tf201 prime using the steps you did. I rooted my Tf700T a few days ago and my unlocked didnt work until yesterday using unlocker 8 from the Asus site but I still could not make changes to my recovery with Clockwork Mod or TWRP until I used Goo manager and ran the Open recovery script. It worked on my TF700T with build number JOP40D.US_epad-10.6.1.14.8-20130514 which has Android 4.2.1. Give it a try it is easy.
Peace. I hope this helps
Click to expand...
Click to collapse
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?
TWRP
berndblb said:
Oh! GooManager works again? Which TWRP version did it flash when you ran the Open Recovery script?
Click to expand...
Click to collapse
I had to flash it with openrecovery-twrp-2.6.3.2-tf700t.blob. using the platform-tools because I could not use the one with Open Recovery script by that time I wiped the entire device! It could have been my fat fingers but I just installed CM 11-20131221 (Kit Kat 4.4.2) on my tablet today without any issues. I have not done much with it yet but I will let you know later.
hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)
nasiroddin said:
hi.
I didn't use my tf700 for one year and after one year i forgot my pattern(password).
my tablet was unlock and root and twrp or cmw (i didn't remember exactly) was installed on my device
then i turn my device off , when it was connected with my computer then hold power button and volume down
and then i go to RCK for going to recovery twrp but then an android image with red dangerous sign ( ! in a red traiangel )
so i choose wipe data sign.and all of things in my device deleted also my password.
now i can use my device but i want to install a custom rom. there is a problem that i haven't usb icon for fastboot(when power up with volume down)
how i can fix it or installing twrp for rooting and installing custom rom?
(excuse me if my english language isn't good)
Click to expand...
Click to collapse
If you see three icons on your bootloader menu, you have a newer bootloader version than ICS. You can ckeck the bootloader version when you are in it and it is in the upper left corner with a small tiny prints. You are also already in the the fastboot mode if you are in the bootloader menu. You can check your fastboot by typing "fastboot devices" to see if your PC can communicate with your device. Good luck...:fingers-crossed:
on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?
nasiroddin said:
on the top left corner writes: "key driver not found.. booting os
android cardhu-user bootloader..............
starting fastboot USB download protocol"
now where i should write "fastboot device" ?
Click to expand...
Click to collapse
sbdags created a zip installer for twrp and you can check out the script here:
http://forum.xda-developers.com/showthread.php?t=2646279
This is a very nice tutorial for installing adb/fastboot and you can find out more information on this post:
http://forum.xda-developers.com/showthread.php?t=2688891
Please read through these two posts before proceeding with installing your new twrp, good luck...:fingers-crossed:
So, I've got an XT1032, It has no OS on it, has TWRP 2.8.7, and I'm trying to install CM 13(Failed to install, not the main issue right now) on it.
Now here's the issue: With TWRP 2.8.7, I am unable to navigate ( there is no text. I've read that it is some issue with the theme). And because I can't navigate, I can't mount the file system to drop a ROM on it that I can install. I can't get the MotoTool to see the device because there is no OS to turn USB debugging on, and I've been unable to get fastboot to see the device.
To sum it up:
No OS - Unable to turn on USB debugging
TWRP 2.8.7 - Version with the theme that causes no text to show up -- Unable to navigate
Unable to mount device due to above issue
Computer doesn't see device when in bootloader. No option for fastboot in bootloader
Bootloader DOES say "AP Fastboot Flash Mode (S)" and "Transfer mode: USB Connected"
If anyone could advise me as to what I should do next, that would be great. I just want to get a working ROM on it, and I can work from there.
Just a daft thought. Get a hold of another device with TWRP installed to figure out which buttons to press and try installing an unthemed version of TWRP or even a ROM over OTG if that's working.
My phone. - Galaxy A51, One UI Version is 4.1, Android version is 12, Product Name – SM-A515F.
Stock ROM up to date.
I can boot into download mode, +/- volume, connect to pc. Works just fine.
But + volume & power boots into safe mode; - volume & power boots into safe mode; +/- volume & power boots into safe mode; +/- volume only boots into safe mode. I have ran out of button sequences to try.
What is wrong with my phone, is it impossoble to boot into recovery mode on my model of phone. This is why I cannot install TWRP as when I install via Odin, it will not boot into recovery post installation.
I am stumped.
Hello!
What is about phone: is it bootlooping or is it in downloading mode?
Other question: from what source did you download the twrp.tar file?
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
vmirrimv said:
Other question: from what source did you download the twrp.tar file?
Click to expand...
Click to collapse
It's in Stock now. But it was stuck in a bootloop, but could boot into download mode. These are the recovery's which all installed but I could not boot into. I cannot boot into recovery now I am in Stock. It's as if there is no recovery option for my A51.
Twrp+vbmeta_A11.tar,
TWRP-11-3.6.0-a51-20220210-1636.tar,
TWRP-11-3.6.1-a51-20220228-2050.tar,
TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar,
TWRP-11-3.6.2-a51-20220602-0515.tar,
twrp-a51-3.5.0_10-1_ianmacd.tar
vmirrimv said:
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
Click to expand...
Click to collapse
I was stuck in a bootloop and could not boot into TWRP..
Unless there is a way to flash Disable_Dm-Verity_ForceEncrypt in downlad mode using Odin?
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Hello, can you say what version of Android your phone on?
If it is on 12th, then I would say, that the problem is, that this version may not fully supported for TWRP working
Because as I tried, there was a fail in the procces.
Sorry, i did not see that you have already written about it
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Sign1 said:
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Click to expand...
Click to collapse
ADB commands must be issued in system. The alternative would be from fastboot but it doesn't seem you can access that.
Try flashing TWRP again, but immediately hold Volume Up during boot to force booting into TWRP. Newer Samsung firmware does seem to have some sort of security measure that will replace a custom recovery, so you'll have to flash the Multidisabler to disable stock recovery auto-restoration.
Sign1 said:
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Click to expand...
Click to collapse
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Other problems are, as I think, that you may forgot to enable USB Debugging on your phone and authorize it with your computer, you may forgot to set the default USB Configuration as data transfer (MTP), or even you may not unlocked the bootloader.
I think they are the reasons because of which you could not enter TWRP, because, as I have tried to flash One UI 4.1 Android 12 according to this thread recently: https://forum.xda-developers.com/t/...ecovery-project-v3-6-2-android-11-12.4400869/
everything has been sucessful, both flashing and entering and following rebooting to Stock system.
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
vmirrimv said:
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Click to expand...
Click to collapse
Cheers for that, just downloaded Android 10, took me twelve hours to download, so its no use to me. I need to download Android 11.
vmirrimv said:
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
Click to expand...
Click to collapse
Yep did that.