Related
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
k1llacanon said:
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
All I know is that I downloaded the ROM from here, used CWM to flash it on, phone said update installed and rebooted the phone. I waited for an hour and it still did nothing past the bootload screen. Also, yes I'm t-mobile.
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
If I can't get into recovery, how do I do this, or what can I use to do this?
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
I have hboot 1.14
Can get ur phone into bootloader mode or fastboot...if yea...then u cn save ur phone...i faced the same problem some days back...and successfully recovered my phone and nw i am using energy rom...
Sent from my HTC VLE_U using xda app-developers app
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
Ok, I downloaded the sdk and my computer recognizes the phone, and I can get into recovery mode, I did a factory reset but it did nothing.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
It keeps telling me device not ready
marcus8141981 said:
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
Click to expand...
Click to collapse
I git it fixed. I thank everyone for their help.
marcus8141981 said:
It keeps telling me device not ready
Click to expand...
Click to collapse
Can you give me more details? Where do you see that message and when exactly? Maybe an ADB logcat?
If you can get into fastboot usb, you can easily google for flashing solutions using fastboot.
always good to say how you fixed it for others who may have similar issue--
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
I do that and my phone just keeps flickering and goes back in to cwm recovery. Please any ideas?
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 am not sure if I can ask about upgrading to CM here? Today I tried to follow their guide from their wiki and now my I can't access anything but recovery, and adb won't work.
I installed the recovery using fastboot and unlocked the device. That worked.
After that, I wiped data/factory reset and the next stage is to push CM to my device, but the device isn't recognized by the PC (when I type adb devices no devices appear).
Now I don't have an os and cannot do anything outside of recovery. I tried clicking on mount USB storage but it doesn't open my storage on my computer. When I connect the device my computer makes sound that a USB is connected.
I tried to /mount data and pretty much everything.
Any ideas?
Sorry for bad English.
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
schmos said:
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
Click to expand...
Click to collapse
No, I have CW recovery (I thought I wrote that, sorry).
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
beekay201 said:
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
Click to expand...
Click to collapse
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Mr Light said:
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Click to expand...
Click to collapse
You previously wrote, and I quote, "I installed the recovery using fastboot and unlocked the device. That worked."
^ This means to me that the connection between your bootloader (fastboot client) and your computer (fastboot host/server) is working, from which we can assume drivers FOR FASTBOOT are correctly setup.
You previously wrote, and I quote, "but the device isn't recognized by the PC (when I type adb devices no devices appear)"
^ This means to me that the connection between adb (on the phone) and adb (on the pc) is not working.
Now, if you are in a custom recovery, hook up the usb to the pc, start adb server on the pc, and you still don't see your device sn appear on the output of 'adb devices', then it means that the drivers FOR ADB aren't setup correctly.
Running a tool and then coming back saying it didn't work... That's not helpful at all. How did it not work? What version of the tool did you use? 1.4.2? 1.3? Keep in mind that you need (more likely than not, since you're probably running latest recovery versions) updated adb and fastboot binaries to API 21 version (Android 5.0). v1.3 of that tool doesn't seem to support API 21 yet.
Learn how to ask for help, please. Also, read the entire first post of this thread please: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If you still can't get it to work, there's a thread to help out troubleshooting drivers stuff, check it out at http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Ok... Sorry for making you confused, it's not easy for me to communicate in English.
Anyway I managed to flash twrp which is much friendlier than CWM, and then I had access to my storage again. Thanks (solved).
hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
is it possible to root using adb sideload or install twrp using adb sideload?
articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence