Trying to root my sprint galaxy s3.
As a new user I am blocked from properly posting the link for the instructions I'm following, so you'll have to copy/paste. They are here:
galaxys3root.com/galaxy-s3-root/how-to-root-u-s-canadian-dual-core-galaxy-s3-on-mac-osx/
(I'm using linux not mac, but anyway)
When I plug in the phone, I can see in linux dmesg that it is connected. (I did enable USB debugging in the developer options)
However when I run adb-linux, it does not detect the device
# ./adb-linux wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
(hangs forever)
# ./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
#
So adb-linux is not detecting the phone-- the list of devices is empty
I'm using debian with linux kernel 3.2.0 (I also tried with kernels 2.6.38 and 2.6.32, same result. I'm running as root, note the # prompt)
Someone posted about a similar problem, and a helpful person recommended "Did you try the kext fix?" - but I have not been able to figure out what the kext fix is and if it is applicable-- the only place I found it mentioned was in relation to Odin.
http://m.youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=/watch?v=7Soapch0c5U
Riding the Uni on the GSIII
jwitt418 said:
youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=%2Fwatch%3Fv%3D7Soapch0c5U
Riding the Uni on the GSIII
Click to expand...
Click to collapse
thanks, but not helpful since it's a windows-only solution.
However I found a newer version of ADB (stands for Android Debug Bridge) and it is seeing my device! So I'll post back with an update as to how the root goes.
btw - running e.g. ./adb-linux version will show the version. 1.0.25 failed, and 1.0.29 seems to be working
success! Rooted my phone. upgrading from adb 1.0.25 to adb 1.0.29 made the difference.
Related
I keep getting this error message when clicking the root button on Super one click, can anyone help??
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
error: closed
FAILED
Have the exact same problem, anyone have a fix?
Removing the SD card and running SOC 1.5.5 was the answer for me. 1.5.5 didn't work until the SD card was removed. It is possible that 1.6.5 would work without the SD card, but I'm not unrooting my phone to test.
Did you also enable/check "Allow mock locations", which is necessary for a root to work properly.
Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr
adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today
danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.
Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?
Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:
I have been struggling for the last 3 weeks to unlock my new Mi5s plus so I can flash the correct ROM and get a couple of problems (camera and sound not working) fixed.
I got the phone from Gearbest and they are refusing to refund the full cost of the phone, so I would rather get it fixed and keep it.
I've tried all possible ways of upgrading: Updater app, recovery mode, fastboot, miflash, special cable and whatever other forum ideas I could find. Everything so far has failed and I think it comes down to the locked bootloader.
I have gained permission and using the unlocking software I get to 99% before I get told "current account is not bound to this device", so I head off to the MI Unlock status to bind phone to account and get the "86023: hardwareid abnormal" message. I think this might have something to do with the wrong ROM being on the phone.
So my questions are: how can I bind my phone to my account, or at least make it look like it is bound? Or is there another way to flash the correct ROM without unlocking?
Please help!!
Go to paypal and ask for refund.
pr0x2 said:
Go to paypal and ask for refund.
Click to expand...
Click to collapse
Good suggestion.
I paid with credit card, so I have asked the credit card to get me a refund under section 75 of the consumer credit act, I'm waiting for the outcome. However, I suspect I will not get a full refund, including delivery costs and the cost of the return delivery, so I would still rather fix the phone than return it.
If it's not fixed by the time I get a reply from the credit card, I will have to give in and return it, accepting the financial loss.
I might be able to help you. First remember that you can always flash your device in emergency download mode by connecting the test points on the motherboard and using miflash and fastboot rom (just google "mi5s plus test points"). But if you don't want to open your device I could find a way to flash a natrium (mi5s plus) rom on your device. If you want to try this "software way" to do that, just follow this passages:
- Download and install my tool on your windows pc: www.xiaomitool.com/latest
- Connect your device and put it in recovery mode (hold vol+ and power button, if a menu appears press the third option ("connect to mi assistant"))
- You don't need to run the tool, just run cmd (command prompt) on your pc and send the following commands:
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getsn
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getversion
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getcodebase
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getdevice
Post the output of the commands here and I will see if there is a way to flash the device and eventually with further instructions.
Thanks for your assistance.
franztesca said:
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getsn
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getversion
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getcodebase
C:\xiaomi\XiaoMiTool\tools\adbsl.exe getdevice
Click to expand...
Click to collapse
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getsn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0xc6d1e19f
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getversion
V8.5.4.0.MAGMIED
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getcodebase
6.0.1
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getdevice
capricorn_global
What's the next step?
bug_bloke said:
Thanks for your assistance.
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getsn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0xc6d1e19f
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getversion
V8.5.4.0.MAGMIED
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getcodebase
6.0.1
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getdevice
capricorn_global
What's the next step?
Click to expand...
Click to collapse
Now download this rom:
Code:
[URL="http://bigota.d.miui.com/V8.5.3.0.MBGMIED/miui_MI5SPlusGlobal_V8.5.3.0.MBGMIED_9fc665c2e7_6.0.zip"]http://bigota.d.miui.com/V8.5.3.0.MBGMIED/miui_MI5SPlusGlobal_V8.5.3.0.MBGMIED_9fc665c2e7_6.0.zip[/URL]
Connect your device in recovery mode to your pc, from windows prompt run this command:
Code:
C:\xiaomi\XiaoMiTool\tools\adbsl.exe sideload location_where_you_saved_the_rom cia64dIkk4zPvlqW2rqGGgE3cGa81fqEE67yWRZrdyivLLOto67HjL+60Z7FnPqIx2g+8QQL7aqBtuuHlzTogoMdYRziqtcRAIC24Ao3XgDxy04JI1sph+C4URwHfENUzQV7v79e0JVPfvDEstYzQdW4/+VtYajYkuHBj7W2xHQalb9oIaPWIRt1liH7kOJhOU47Es1Xqn5RPb4iUXy+YybUlgRqZ3I8Yv90/fgXhWUk1Daq1QYrrQGskCSyNmPM6nIl5KbYNh+ZLU8pAi4F7uaZTW+6USEdoFGzY0oJm/lKOPjoYMgif5Q8lA8UtXKcx34GYYT8yLq5pgI7wKq6MQ==
replacing location_where_you_saved_the_rom with the full path location of your downloaded file (for me it would be C:\Users\Franz\Downloads\miui_MI5SPlusGlobal_V8.5.3.0.MBGMIED_9fc665c2e7_6.0.zip )
You should then see a progress bar on your device, just wait for the installation to complete. After that run:
Code:
C:\xiaomi\XiaoMiTool\tools\adbsl.exe format-data
to wipe data partition (aka make a clean install) and finally
Code:
C:\xiaomi\XiaoMiTool\tools\adbsl.exe reboot
to reboot your device
Remeber that this procedure has not been tested yet (as far as I know) and it might work or not work, or even brick your device. In this case, the only way to continue is by using test points.
Make a backup of your data before proceeding
F### me, it worked!!
C:\XiaoMi\XiaoMiTool\tools>adbsl.exe sideload C:\miui_MI5SPlusGlobal_V8.5.3.0.MBGMIED_9fc665c2e7_6.0.zip cia64dIkk4zPvlqW2rqGGgE3cGa81fqEE67yWRZrdyivLLOto67HjL+60Z7FnPqIx2g+8QQL7aqBtuuHlzTogoMdYRziqtcRAIC24Ao3XgDxy04JI1sph+C4URwHfENUzQV7v79e0JVPfvDEstYzQdW4/+VtYajYkuHBj7W2xHQalb9oIaPWIRt1liH7kOJhOU47Es1Xqn5RPb4iUXy+YybUlgRqZ3I8Yv90/fgXhWUk1Daq1QYrrQGskCSyNmPM6nIl5KbYNh+ZLU8pAi4F7uaZTW+6USEdoFGzY0oJm/lKOPjoYMgif5Q8lA8UtXKcx34GYYT8yLq5pgI7wKq6MQ==
sending:[ 2293760/2 bytes] C:\miui_MI5SPlusGlobal_V8.5.3.0.MBGMIED_9fc665c2e7_6.0.zip' (~66%)
sending doneInstallation_complete.
C:\XiaoMi\XiaoMiTool\tools>adbsl.exe format-data
Format_data_success.
C:\XiaoMi\XiaoMiTool\tools>adbsl.exe reboot
reboot.
I now have Mi5s plus on a Mi5s plus device, with working camera and speakers. Thanks to franztesca for the fast, efficient and accurate assistance. I will sing your praises wherever I go and share your knowledge with anyone else in trouble.
With after sales service as bad a gearbest - 'send it back and we will give you most of your money back', what you have achieved is far and beyond my expectations.
Thank you!
Hello! I need your help. I ran into a similar problem. Only I have a phone Mi5s 4gb/128gb and firmware in it Mi5s plus, as a result does not work camera and speaker sound. How can I change my phone to Mi5s?
That's what I found out.
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getsn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0xfcb9a950
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getversion
V9.1.1.0 NBGMIEI
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adbsl.exe getcodebase
7.0
C:\WINDOWS\system32>C:\xiaomi\XiaoMiTool\tools\adb sl.exe getdevice
natrium_global
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Triscuit said:
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Click to expand...
Click to collapse
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Tulsadiver said:
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Click to expand...
Click to collapse
The first two commands are to install adb and fastboot, which I've done. The third command is to add a new product id in adb_usb.ini which I got "permission denied" so I entered it manually for ****s and giggles but it didn't help. Thank you though!
I was finally able to get the device to authorize, I did a few things but I'm not sure which one corrected the problem, first. I deleted the adbkey file from /home/.android folder, I also changed permissions of the folder to rw-rw-rw and finally I hit "Revoke USB debugging authorizations" under development settings WHILE the phone was plugged into the computer. Every other time I had done it after unplugging the device. Not sure which one worked but it did, now I can get back to flashing again!
Sent from my Pixel 2 XL using XDA Labs
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
jbarcus81 said:
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
Click to expand...
Click to collapse
Yep I honestly think my problem was that I was unplugging my device before revoking authorizations..... Silly me haha
Sent from my Pixel 2 XL using XDA Labs
Hello!
I have massive issues with connecting by sdb to my watch.
Actually I downgarded my sm-800 from 4.0.0.7 to 4.0.0.4 with firmware R800XXU1CSI1 to change my CSC to XAR.
Downgrade by net odin worked well. Flashed AP und CSC.
But I am not able to connect the watch be sdb (version 2.2.60). I turned off BT, enabled devloper and debugging. I started install.bat, then sdb.exe and then ansicon.exe.
When sending the command I get:
sdb connect 192.168.0.33
* server not running. starting it now on port 26099 *
* server started successfully *
connecting to 192.168.0.33:26101 ...
failed to connect to 192.168.0.33:26101
Additionally:
sdb devices
List of devices attached
192.168.0.33:26101 offline <unknown>
sdb root on
device unauthorized. Please check the confirmation dialog on your device.
Actually I also don't receive the authorization request on the watch (which typically appears).
Any ideas??
Thanks!!
I'm no expert but have you tried connecting without port?
1.
Flashed AP und CSC.
Click to expand...
Click to collapse
I am from Germany.
1.1
But BL you also flashed?
Only to be sure you select 3 files inside netOdin, not only 2 of 3...
2.
Delete these 2 files... or if you wish backup...
Code:
sdbkey
sdbkey.pub
Try to look into C...
Code:
user\yourPCname\[B].tizen[/B]
Best Regards
Actually I didn't flash BL.
I deleted the files in .tizen ... but without difference.
sdb connect 192.168.0.33
* server not running. starting it now on port 26099 *
* server started successfully *
connecting to 192.168.0.33:26101 ...
failed to connect to 192.168.0.33:26101
sdb connect 192.168.0.33
¼☺
-> Interesting reply on second connect ..
sdb devices
List of devices attached
192.168.0.33:26101 offline <unknown>
Any other ideas?
Actually I didn't flash BL.
Click to expand...
Click to collapse
Why?
It contains Kernel... not only Bootloader...
Better you choose ALL 3 files in netOdin...
Best Regards
Try to restart your device after enabling developer mode. I had same issue and restarting the watch helped me. And use admin cmd.
For some reason (even before flashing BL) after some tries and rebooting watch and computer the authorization request came up.
But on sdb root on I get "permission denied". Is this OK??
Other question: There is a app called myRound from taylormade not available in my region. Can I somehow install this app by tricking the region??
had the same trouble.just did several reboots, then download https://download.tizen.org/sdk/tizenstudio/official/binary/sdb_2.2.89_windows-32.zip . run ansi term from there and then adb connect blabla.
C:\sd229\tools>ansicon.exe Microsoft Windows [Version 10.0.19044.2486]
C:\sd229\tools>
C:\sd229\tools>sdb connect 192.168.0.112
* The version of SDB client (2.2.88) is not same with that of SDB server (2.2.69).
It may cause version compatibility problems.
It is recommended to use SDB server with version 2.2.88. *
└☺
C:\sd229\tools>sdb kill-server
C:\sd229\tools>sdb connect 192.168.0.112
* server not running. starting it now on port 26099 *
* server started successfully *
connecting to 192.168.0.112:26101 ...
failed to connect to 192.168.0.112:26101
C:\sd229\tools>sdb shell
sh-3.2$
sh-3.2$ ls
apps_rw data media share
C:\sd229\tools>sdb version
Smart Development Bridge version 2.2.88