Hi People !!!
I had my OP2 showing in fastboot but not being able to show in adb devices though other devices were showing correctly there.So,drivers were perfect.Also,I was able to use adb over wifi on my OnePlus 2 but not adb through cable.So,I set up on my mission to get it show.And after 10 hrs of a lot hassle,I am successful.
So,here is the guide.
Open windows command prompt (Windows Key + R)
Ènter: %HOMEPATH%\.android
and then press OK
This will open the hidden .android folder within Home Folder of the current user.
There you will see a file called: adb_usb.ini
Edit the file using Notepad or Editplus/Notepad+
Just add the text: 0x2A70
without pressing any additional enter key/new line characters, save the file
now go to command prompt and restart adb:
adb kill-server
adb devices
Now the device will start showing up!
If you don't see any adb_usb.ini file (This happened for me.) , do this :-
Click the Start menu. ...
Type "folder options" (without the quotes). ...
A dialog box with the title "Folder Options" will appear. ...
Click to uncheck the box for "Hide extensions for known file types".
Click the "OK" button at the bottom of the dialog box.
In the .android folder ,create a notepad file with name adb_usb.ini (Make sure .ini is not in the name but in the extension.)
In the notepad file , enter this :-
Code:
# add your vendor IDs, one per line
0x1949
0x18D1
0x2A70
8.) Save the file and close it...ANd follow the remaining steps.
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Zeuscluts said:
I will be thankful to you a lot..
i have tried all the possible methods to connect via adb if this works..
ssly it will be awesome
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
Welcome. If you still have any issues connecting to adb, grant me Teamviewer access and I will help you out.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
yes sure,
can we chat on hangouts
you can contact me on
[email protected]
Sent from my OP5.
I had the same problem! Will surely try! Thanks
Keep up the great work Naman..!!
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
dansou901 said:
Did somebody got this to work on Linux? Probably you need to adjust udev rules there to get it to work. Will try out today and let you know how it goes.
Click to expand...
Click to collapse
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Thanks.
Sent from my ONE A2003 using Tapatalk
Naman Bhalla said:
You need to add a udev*rules file that contains a USB configuration. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up OP2 detection on Ubuntu Linux:
Log in as root and create this file:/etc/udev/rules.d/51-android.rules.
Use this format to add OP2 vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="2a70", MODE="0666", GROUP="plugdev"
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Done
I am 99.99 percent sure it will work.. But you should try and tell me.
Click to expand...
Click to collapse
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
marlow925 said:
Didn't fix it for me, until I found out, that there also exists a ˝/.android/adb_usb.ini file . Has the same format as the Windows file.
/M
Click to expand...
Click to collapse
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
coala-lumpur said:
Sorry for asking, but does this whole issue affect Oneplus two devices with original stock ROM (Oxygen OS 2.1.0), too?
Or does it just affect devices with custom firmware?
Click to expand...
Click to collapse
Probably both. I haven't tested stock Rom though.
/M
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
alankstiyo said:
I have the opposite problem, adb works after using your guide but fastboot just doesnt :S
Click to expand...
Click to collapse
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
Maybe worth reinstalling the fastboot packages.
/M
marlow925 said:
Fastboot should not be affected by CM at all, as it's in the bootloader. Did it work before you made the changes ?
/M
Click to expand...
Click to collapse
I had a wrong driver, cant root for the moment but havent unlocked the bootloader so think that is the problem
Well. Without unlocking the bootloader you won't get anywhere. Fastboot is a bootloader feature. You don't need root for fastboot.
/M
Sent from my SM-P905 using Tapatalk
Didn't work for me.
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
My ADB is working but the fastboot isn't working! Thank you for your help!
Still not detecting
I tried doing your steps but its not helping. My phone enters the fastboot mode but the pc never detects it.
Can u please help me out.
---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------
williamt31 said:
So found mine in my install folder
c:\android\.android\adb_usb.ini
After each change below I ran adb kill-server then adb devices.
I already have the line 0x2a70, I first changed it to 0x2A70 (just in case)
tried renaming it to adb_usb.ini.bak, to see if it would recreate, nope.
renamed the folder .android to .android.bak and it created the adbkey and adbkey.pub but not the .ini.
So looking at the .android folder, I think I learned something new tonight, I assume this is the public/private key pair store for adb to do it's work? So it truly is just a usb connection issue then if it works over network and not with the usb cable connected yes?
So I even tried re-running the '15 seconds ADB Installer' version 1.3 by Snoop05 that I used originally and still no change. Any advice appreciated.
Click to expand...
Click to collapse
Same here!!!!!
any help would be appreciated
My fix was:
turn on adb over TCP on phone in developer options.
At cmd type:
adb connect <ip.address>
adb devices (now shows device)
adb reboot bootloader
Open another cmd if you don't get your prompt back and continue
still not working
i tried all the steps and my op2 only shows when connected via wifi but that is too slow for an adb backup, it still doesnt show up when connected over usb
any ideas? or is any info needed?
Related
Like me I'm sure many of you were very surprised to log in today, as most have been doing everyday for the past month or so to find that not one, but two methods for obtaining s-off on the DNA were released within minutes of each other. First Revone and then, coincidentally enough, Moonshine was released minutes later. Somebody didn't want somebody else stealing their thunder I'm guessing. I'm just kidding...I'm sure both sides worked extremely hard on their respective methods and deserve mad props for the time spent on this and for waving a middle finger in the face of Verizon. Having said that I have tried both methods and have been unsuccessful so far at each one. I have to pose my questions here because I'm a new member and the development threads are off limits to me.
I tried the Revone Method first and like many were saying in the actual thread, my phone kept auto rebooting after the ./revone.dna -P step. I tried everything I could think of including all of the suggestions from the other users who finally got it to work by trying different things. Has anyone figured out what is causing the auto reboot? There has to be something specific causing this. One thing I have noticed with my phone is that USB Debugging has been very unreliable as of late. It turns itself off and on at random times and a lot of times the box is checked to enable it but it's not on. I don't know if this is playing a role in the process not working for me. I got the "success" message after every step several times but never actually achieved s-off.
I finally gave up on Revone to try Moonshine. I really didn't want to have to fo this route since I don't know a thing about Linux. I decided to go the boot from flash drive route so I downloaded 32 bit Ubuntu 13.04 iso and used universal USB installer to put it on my drive. I am using an external hard drive that is already formatted to fat32. I did NOT format the drive because I didn't think I had to since it was already fat32. Universal USB Installer was successful in putting Ubuntu on the external drive. I then went into my bios and changed the boot sequence to boot from the external drive first but when I rebooted it just loaded up Windows like normal. What am I doing wrong here? I'm running Windows 7 64bit but it was my understanding that this should not be a problem. Do I have to format and/or partition the external hard drive even though it is already fat32 before putting Ubuntu on it?
I'm dying to get one of these methods working but I'm currently stuck. Any newbies like me that can't post in the Development forums have any ideas as to what is going wrong here or would anyone else like to chime in with their own issues? Thanks in advance. I'm sure I'll get there eventually. :good:
Follow this guide for using an external USB device.
Modify the boot sequence like you were doing before, hopefully you'll get in to Ubuntu.
You say you don't have Linux experience, so I'll simplify the process for you:
Once at the desktop, press Control + Shift + T. This will open the Terminal, which is basically the Linux version of Windows' cmd.exe. Once inside, open up Mozilla Firefox (included) by using the side bar, the icon should be there. Download the version of Moonshine for the DNA, and then switch back to the terminal.
Type in these commands:
cd /home/Downloads
tar -zxf moonshine_dlx_2.06.605.1.tgz
sudo ./distiller
Click to expand...
Click to collapse
And then let Moonshine do its thing.
Modify the boot sequence like you were doing before said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
Oh and one other thing I forgot to mention regarding the revone method...the directory \data\local\temp did not exist on my device prior to me creating it when I pushed the revone.dna to my phone. Should I have had that directory on my phone already?
Sent from my HTC6435LVW using xda premium
I am in a similar boat. I am trying to use revone as I can't get ahold of linux. I downloaded the sdk and revone, moved adb to my C: with the revone file. Everything goes smoothly until i reach the -P step. Every single time it reboots after saying success. If I try to run the -s 0 -u command after that I get failed to map memory, success, revone failed = -1. If I try the -P command again, I get the same message with error code 2. If I try to reboot the bootloader, I get error device not found. I've been at this for hours, and Jerry from Android central even walked me through it, everything ended up successful ans when the bootloader rebooted, it was still locked and s on. Help please?
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Gorilla* said:
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Click to expand...
Click to collapse
I moved adb and its two counterparts in a folder named ADB_WIN, in my C: drive. From there, I typed cmd.exe in the search bar, it opened the command box. I typed in adb push revone.dna /data/local/tmp/ ENTER adb shell ENTER cd /data/local/tmp ENTER chmod 755 revone.dna ENTER ./revone.dna -P and that's where my error started coming in. You can try this, not sure if this right, but if its not, hopefully someone will correct me.
Krispenwah said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
32 bit should work fine. You need a DVD because a CD is too small. ~/Downloads directory is just the current user's downloads folder. So most likely it would get downloaded to there anyway.
Sent from my DNA using Tapatalk 2
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
michaelrager said:
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
Click to expand...
Click to collapse
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
michaelrager said:
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
Click to expand...
Click to collapse
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
michaelrager said:
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
Click to expand...
Click to collapse
add adb.exe to your command, instead of just adb
Gorilla* said:
add adb.exe to your command, instead of just adb
Click to expand...
Click to collapse
Thanks, but the same type of error came up.
michaelrager said:
Thanks, but the same type of error came up.
Click to expand...
Click to collapse
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Krispenwah said:
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
michaelrager said:
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
Click to expand...
Click to collapse
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Krispenwah said:
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Click to expand...
Click to collapse
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
michaelrager said:
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
Click to expand...
Click to collapse
Yeah looks like the file pushed successfully. Now u do "adb shell" then "cd data/local/tmp" then "chmod 755 revone.dna" ....and so forth. Make sure ur adding the extension ".dna" to revone (revone.dna) each time u type it. If u just put revone it won't work ull just get an error
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
Hello all
So here I am in my first topic :laugh:
For Mac users can be tough to work with commands, which most of it has to be done in order to perform stuff in our Moto X.
Instead of having to mount virtual machines in order to have access to Windows' stuff. Or the Android SDK has to be installed, browse to specific folders to run commands from them, etc.
We can work directly in our precious Terminal! :victory:
So, I made a little script that will allow Mac users to work directly on Terminal, no matter which folder we are working on. I've included the following files:
adb
fastboot
mfastboot (Motorola's modified version of fastboot)
To Install
Run Terminal (/Applications/Utilities/Terminal.app)
Browse to the folder in which the script resides, i.e., if it’s in Desktop, then type in Terminal “cd Desktop/ADBInstall” (without quotes).
To run the script type “./install.sh” (without quotes).
You will see input on the screen.
That’s it
To Uninstall
You can safely remove the 3 files in one command, just run the uninstall.sh script by following step 1 and 2 from the Install section. Instead of following step 3, type the following in Terminal: “./unistall.sh” (without quotes).
Hope you like it
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
HeroOfTime said:
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
Click to expand...
Click to collapse
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
MoisesPerez said:
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
Click to expand...
Click to collapse
Thanks for looking into this for me. Yes, it did ask for my password. Here is what I get after running the installer:
Jareds-MBP:ADBinstall Jared$ ./install.sh
This will install ADB, Fastboot and mFastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/Jared/Desktop/ADBinstall
Copying ADB...
ADB copied to /usr/bin/adb
Copying Fastboot...
Fastboot copied to /usr/bin/fastboot
Copying mFastboot...
mFastboot copied to /usr/bin/mfastboot
You may now run Android Debug Bridge, Fastboot and mFastboot commands
Have a nice day
I'm attaching a screenshot of the output as well, but that is the output I get, which seems correct.
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
MoisesPerez said:
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
Click to expand...
Click to collapse
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
HeroOfTime said:
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
Click to expand...
Click to collapse
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
MoisesPerez said:
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
Click to expand...
Click to collapse
Well thanks a lot for your help. Still a great resource. I will keep playing around with things and maybe get it to work.
Thanks again!
Not a problem my friend. Good luck!
worked great for me on 10.9!
worked for me as well on Yosemite 10.10.1. thanks!
Glad it did! Regards.
Hi I can't connect to the Wlan Network at our university, which is using wpa2 enterprise.
When I click on the network nothing happens. On askubuntu I found something, but I don't know in which file on my phone I have to put the text in.
http://askubuntu.com/questions/586300/creating-a-wpa2-enterprise-connection-on-ubuntu-touch
Yes, WPA2 Enterprise isn't supported by the GUI yet.
The file you need to save that to needs to be called
Code:
/etc/NetworkManager/system-connections/<your network's id>
Replace <your network's id> (including the brackets) with the ID of your Wifi network. In the example it would be "eduroam".
(Please note that you need to save the file as root, i.e. using sudo.)
I tried it yesterday with the file, but it didn't worked. But I am not sure if the file is correct for our network.
I followed this guide http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ and now I get a connection. Only username and password have to be changed.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Sorry if this is a semi-hijack, but this seems the most relevant place for my question. I can't get access to my uni's wi-fi either (aquaris ubuntu edition phone), and I was wondering if anyone knows if the functionality for wpa2 is going to be added in the near future? I don't have ubuntu on a desktop atm and I don't want to have to install it just to tinker with my phone, which also seems a little bit daunting to me, worried I will explode my phone or something.
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
jonny-boy said:
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
Click to expand...
Click to collapse
That'd be great, although I've no idea what I'm doing with this sort of thing, would it be possible for you to explain it to me in idiot terms? I'm not familiar with putty or this kind of exercise
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
jonny-boy said:
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
Click to expand...
Click to collapse
So far I can't get the adb shell to recognise the phone is there, it just keeps saying "error: device not found" so I'm kinda stumped right now
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
jonny-boy said:
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
Click to expand...
Click to collapse
Did that, still says Error: device not found =/
Garatolla said:
Did that, still says Error: device not found =/
Click to expand...
Click to collapse
Tried it on my friend's linux pc as well and it still says error device not found, guess I'm just going to have to wait for them to officially add in wpa2 functionality. Welp, back to my old phone for a while then, thanks for the help jonny-boy
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Yup, I managed to find out about that before I first started trying to figure out how to fix this unfortunate situation
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Garatolla said:
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Click to expand...
Click to collapse
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
nikwen said:
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
Click to expand...
Click to collapse
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Garatolla said:
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Click to expand...
Click to collapse
Great that it finally worked.
I am having trouble using the adb pull to root a brand new Samsung Galaxy Tab S7 with Android 11 using Magisk. I did the date change to get the OEM unlock available. I was then able to unlock the bootloader and turned on the USB debugging and get the message every time it starts that the bootloader is unlocked. I downloaded the Magisk from github.com v23.0. Then copied the AP TAR file for my stock firmware to do the patch in Magisk. I have a file in my download folder named “magisk_patched-23000_H5VRc.tar”. I am using the “adb pull /sdcard/download/magisk_patched_[random_strings].tar” but keep getting things like:
1) adb: error: failed to stat remote object '/sdcard/download/magisk_patched_[random_strings].tar': No such file or directory
2) adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Any ideas what I am doing wrong? I would be open to any sugestions.
Code:
adb pull
is used to copy files / directory from your phone to your computer
Synthax:
Code:
adb pull <device file location> <local file location>
To copy files / directory from computer to phone you have to use
Code:
adb push
why adb? just copy it by using windows file manager.
Ok so in the internal storage of my tab is a file called “download” in that file is something named “magisk_patched-23000_H5VRc.tar”.
So I guess my question is if I use “adb pull /sdcard/download/magisk_patched_[random_strings].tar” will the computer go to the internal storage on the tab in the download folder and get the “magisk_patched-23000_H5VRc.tar” file?
Or should I use “adb pull /internal storage/download/ magisk_patched-23000_H5VRc.tar”? If so do I need to use underscore between internal and storage?
Android's file / directoy names are case sensitive.
Knowing this the directory name in question is /sdcard/Download.
CXZa said:
why adb? just copy it by using windows file manager.
Click to expand...
Click to collapse
According to the instalation guide it could corrupt large files
Take note that also ADB's pull command is size-limited.
It might therefore be advantageous to first unpack the TAR file on the phone, and then transfer the desired files to the computer with adb pull
wolfyj1 said:
According to the instalation guide it could corrupt large files
Click to expand...
Click to collapse
Hardly. If in doubt check the tar with 7zip or whatever. Or compare file hashes...
jwoegerbauer said:
Android's file / directoy names are case sensitive.
Knowing this the directory name in question is /sdcard/Download.
Click to expand...
Click to collapse
I was hoping that it was as simple as the capitalization of Download. Here is the message now.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull /sdcard/Download/magisk_patched_[random_strings].tar
adb: error: failed to stat remote object '/sdcard/Download/magisk_patched_[random_strings].tar': No such file or directory
Is it possible that my adb and fastboot program is not working correctly? I was hoping that there would be a simple fix for this. Guess not.
/sdcard is a sym-link, try to use /storage/emulated/0 as file's actual path.
fastboot flash boot magisk_patched.img is the most common way.Be sure to use real ADB tools from Google.
I'm pretty sure that Samsung devices don't support fastboot mode. I've owned lots of them and fastboot has never been available. Instead we have download mode, which must be interfaced with via Odin or Heimdall, etc.
Of course, ADB should work, and is universally available on all Android devices.
AnonVendetta said:
I'm pretty sure that Samsung devices don't support fastboot mode. I've owned lots of them and fastboot has never been available. Instead we have download mode, which must be interfaced with via Odin or Heimdall, etc.
Of course, ADB should work, and is universally available on all Android devices.
Click to expand...
Click to collapse
Anon you are so correct. I've spent so many years flashing Pixels I forgot I was discussing a Sammy Tablet. Thank you.
Jonathanpeyton said:
Anon you are so correct. I've spent so many years flashing Pixels I forgot I was discussing a Sammy Tablet. Thank you.
Click to expand...
Click to collapse
I've only ever used fastboot once, it was on an HTC phone. I was just unlocking the bootloader and installing TWRP for a friend.
Never owned a Pixel/Nexus, I'm put off by them because they don't have MicroSD slots. But if they want to give us 1TB+ internal storage, I may reconsider. On the other hand, they do have lots of custom ROMs, lots of developers, and alot of users. So on that front, they have a ton of advantages if you're an Android enthusiast looking to get the most mileage out of your device for the longest time possible.
Samsung devices are what I prefer, but I'm open to trying new things. Almost all of my phones have been Samsung, with the exception of an LG v10, ZTE Axon 7, and a Huawei Honor. After using all those for quite awhile, I went back to what I know best.
I did run into device not authorized error today when I was trying to mod my S7.
Turns out that although I enabled USB debugging beforehand the tab wasn't able to ask for permission.
I had to disable and enable USB debugging again, revoke previous authorization, reconnect and wait for the popup to show up.