Hello,
I finally can connect my TF201 to adb but when I type adb shell I got the following message:
adb shell
error: protocol fault <status 73 68 65 6c?!>
Any help?
This is the 101 form not the 201 but you might want to try
adb kill-server
adb start-server
adb devices
adb shell
and see if that fixes it
unfortunately, no difference...
Adb remount?
might be a stupid question but usb debugging and root access over adb enabled?
It's ok now. I'm using Win XP into Virtualbox and after disabling USB 2.0 in the settings, it worked.
My TF201 is rooted!
But still with build .15? No .21 update automatically coming afterwards?
You need to manually flash stock rooted or a custom ROM, head over to the prime section to get you a recovery and ROM. You can't take OTAs when rooted.
Strange, some said they could upgrade? I tried CM9 but it did not convince me. IPS mode, and handy menu by hitting the notification area do not exist.
Sent from my Transformer Prime TF201 using xda premium
Related
I have never rooted an android device before and this is my first time. The reason I'm rooting is so I can enable the Virtuous Prime ROM (the guide for Virtuous Prime suggested to use ViperMOD to root first)
[ROOT] [TOOL][Updated 2.22.12]viperMOD PrimeTime v4.5 | Auto Root/Unroot/Busybox/CMW - xda-developers
^I'm following the instructions from the link above word for word. So far I've met the following Criteria:
-Enabled USB Debugging
-Running build 9.4.2.15
-Have "ASUS Android Composite ADB Interface" drivers installed and updated
I downloaded the ViperMOD 4.5 zip and extracted it to my PC. I opened the folder and right clicked on "viperMOD Primer Tool v4.5 - copy.bat". A cmd popped up with several different options; I pressed 1 to root, and pressed enter to skip the following two prompts (that ask if USB debugging is enabled and asus usb drivers are installed).
The CMD then showed the following message:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
However the CMD just stopped there. It didn't show the following flood of text that should show up when rooting w/ ViperMod (like shown in this video: http://www.youtube.com/watch?v=C3OQkxmUyLc at 2:35)
I'm not sure if I'm missing something here. The guide however did say that I needed to "Kill Asus Sync and Splashtop" though I'm not exactly sure what it means by "kill". I don't have Splashtop running on my Prime nor Splashtop remote running on my PC. I also don't have ASUS Sync software installed on my PC and I disabled Auto-Sync on my Prime (HOWEVER, the ASUS Sync icon is still visible in my Prime's notification bar when I connect it via USB to my PC).
Any advice?
I had a similar problem
I tried to use superoneclick to root my Samsung Gravity and it hung on waiting for phone. I used the adb commands to load the zergRush exploit. So you need to find which exploit works on your phone, adb push the exploit, busybox, and su to your phone and use adb shell to do the root.
** DISCLAIMER: I'm pulling this command sequence out of my memory... you should find a better guide but this stuff may give you clues as to what to google for, or if you're familiar with shell you may see the gist of what you're trying to do **
The commands will look something like this:
adb push exploitfilename
adb push busybox.apk
adb push su
adb shell
chmod 755 exploitfilename
./exploitfilename
(wait for the exploit to finish)
pm install busybox.apk
pm install su.apk
reboot
Once it rebooted, I installed terminal through the market so I could do cool stuf like so:
su
mount -o remount,rw /dev/whateverdevhasyoursystemfolder /system
rm /system/app/Vendorgarbagebloatapp.apk
and so forth. Knowledge of linux and shell commands is your friend here for sure. Basically, you should know what you're doing or don't do it. I'm no fan of one-clicks for anything like this, it's too hard to figure out what went wrong if it goes wrong, plus this way you can learn new skills.
Can't seem to run Vipermod
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
sasori563 said:
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
Click to expand...
Click to collapse
U should tried on another comp with windows seven imo
I would if i had one but my laptop got stolen so my only computer besides my desktop is my transformer, Are their any .bat files out their that i can use to run it from? I found out that its a problem with windows 8 not allowing .exe files to open command prompts, but if its a .bat file it will run.
so my tf300 is rooted and unlocked bootloader, im trying to do the disabling journaling
im already at twrp and my tablet is connected to my pc
but everytime im trying the adb shell it says:
daemon could not start, starting at port 5037
daemon started succesfully
error: device not found
what seems to be the problem here? i tried to install my sdk, still no luck.
Using USBDeview (suggested here - comment 7 : http://code.google.com/p/android/issues/detail?id=2676 ) helped me get my TF300 to appear under 'adb devices'.
Still can't seem to access the device via localhost though.
(I'm trying to get access for web-dev purposes - see here : http://forum.xda-developers.com/showthread.php?t=1966358 )
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop what do i do now??
beahrr77 said:
i feel useless... after i run the batch file from the extracted motochopper folder, it starts in terminal and says not found followed by daemon started and nothing happens.. i checked usb debug and the unknown source security boxes on the tablet and since im running windows 7, i ran the batch file as administrator. please anything will help kind of afraid to pull usb cable out of laptop what do i do now??
Click to expand...
Click to collapse
Sounds like your ADB is not working. Can you connect to your device thru ADB from a PC?
Code:
adb devices
Should echo your S/N. If it says "List of devices attached" followed by blank (nothing) then your ADB is not working and you need drivers for W7, W8. You also have to add the path to platform tools to your Windows system environment variables path so the system can find it.
Code:
which adb
Should echo "/system/bin/adb" otherwise you don't have the adb binary installed on your device.
Code:
adb version
Should echo 1.0.29 for 4.1.1
Should echo 1.0.30 or 1.0.31 for 4.2.1 (secure adb)
elfaure said:
Sounds like your ADB is not working. Can you connect to your device thru ADB from a PC?
Code:
adb devices
Should echo your S/N. If it says "List of devices attached" followed by blank (nothing) then your ADB is not working and you need drivers for W7, W8. You also have to add the path to platform tools to your Windows system environment variables path so the system can find it.
Code:
which adb
Should echo "/system/bin/adb" otherwise you don't have the adb binary installed on your device.
Code:
adb version
Should echo 1.0.29 for 4.1.1
Should echo 1.0.30 or 1.0.31 for 4.2.1 (secure adb)
Click to expand...
Click to collapse
Thanks man, btw how do you thank on here to make ur thank meter grow
I ran into the same problem with win7. When I plugged in my tablet, it seemed like it would lose the connection shortly after connecting it. I eventually got it to root by running motochopper, and then plugging in my tablet. This was the only thing that worked, even after installing every Asus USB driver know lol.
Hope this helps
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
so im trying to get into adb shell on my device. i have twrp 2.5.0.0 installed and when hooked up to my pc the "adb devices" command shows nothing. the reason im trying to use the adb shell through twrp is because im pretty sure i have some file system corruption and want to run e2fsck to fix it. ive tried unplugging the device from my pc, killing the adb server, restarting it, and plugging my device back in. im running windows 7 ultimate 64bit on my pc with the asus drivers. what can i do to either get into adb shell through twrp or fix my filesystem another way? im in dire need of some help
alb-o said:
so im trying to get into adb shell on my device. i have twrp 2.5.0.0 installed and when hooked up to my pc the "adb devices" command shows nothing. the reason im trying to use the adb shell through twrp is because im pretty sure i have some file system corruption and want to run e2fsck to fix it. ive tried unplugging the device from my pc, killing the adb server, restarting it, and plugging my device back in. im running windows 7 ultimate 64bit on my pc with the asus drivers. what can i do to either get into adb shell through twrp or fix my filesystem another way? im in dire need of some help
Click to expand...
Click to collapse
You can run commands directly from twrp terminal and there is no difference between adb shell and terminal on the tablet.
So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$
Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.
Its fastboot flash recovery not adb flash
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk