I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
hello forum users,
I bought the Samsung Galaxy S4 2 month ago and I want to run Backtrack 5 ARM version on it, but everytime is want to start BT there are mount errors or other issues so that backtrack wont start, and my question is what do i wrong ?? i rooted my phone already and tried to start linux with the complete linux installer from the playstore. I installed busybox and vnc viewer and terminal emulator already. Even tried to start BT with the boobt sh command but it failed to on mount issues etc. my phone
Samsung galaxy s4 GT-I9505 with 16 GB and 32 GB Sdcard
jelly bean 4.2.2 and rooted device
Can anyone help me ?
Backtrack on S4
itworksfine said:
hello forum users,
I bought the Samsung Galaxy S4 2 month ago and I want to run Backtrack 5 ARM version on it, but everytime is want to start BT there are mount errors or other issues so that backtrack wont start, and my question is what do i wrong ?? i rooted my phone already and tried to start linux with the complete linux installer from the playstore. I installed busybox and vnc viewer and terminal emulator already. Even tried to start BT with the boobt sh command but it failed to on mount issues etc. my phone
Samsung galaxy s4 GT-I9505 with 16 GB and 32 GB Sdcard
jelly bean 4.2.2 and rooted device
Can anyone help me ?
Click to expand...
Click to collapse
I'm having issues as well, however I can at least get it to boot. Have you tried setting it up by following these instructions? http://forum.xda-developers.com/showthread.php?t=1079898
My problem is starting the gui with vnc. All I get is a grey box. Also, I'm not sure why but I'm missing tools like airmon, aireplay etc. which should be in /sbin. Also when ever I attempt to run any of the programs from terminal emulator I get a message:
ifconfig is available in /sbin
The command could not be located because /sbin is not included in the PATH environment variable. This is most likely caused by the lack of admin priviledges associated with your user account.
i am sorry i tried to delete the poste (wrong adress ) but i can't
if any one tells me how to delete it
Ps : or how to make the script work on galaxy s4 it would be great, thanks
Hello all,
I'm having difficulty trying to run EFS Pro v2.0.70/v2.0.72 to backup my EFS folder on my GT-I9505. I get stuck at the part when it says "Initializing ADB server..." and it just sits there. I just want to point out that I had made a backup of my EFS folder on my GT-I9505 when I first got my phone (around May), but it seems to have been deleted! Anyway, I found some good steps in another thread, as follows:
Before starting, check the following:
Device is fully rooted
SuperSU (or equivalent) is active
USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)
Busybox downloaded AND installed (normal or smart) on your device
Microsoft .NET Framework 4.0 installed on your PC
Samsung USB driver is installed (either by installing Kies or just the driver alone.
Kies is not active (neither as application nor process, check Windows Taskmanager)
ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)
In case ADB is not running you need to install the ADB driver
Run EFS Professional as administrator.
Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.
Of course, your device should be on the home screen, not on the lock screen
I've followed all these steps, checking each methodically, and guess what, I'm still stuck at "initializing ADB server..."! I even go to cmd and type in "adb devices" and my phone shows up, I see on my phone that a shell has been granted, and yes, I am rooted, I have busybox, and Samsung drivers, .NET 4.0 framework and USB debugging, it's driving me mad, I've even tried different USB ports, and nothing!
If anyone has any suggestions, please fire away!
I have the exact same problem, but with my S3 (I9300) ...
No one who can help?
Did you get sorted my i9505 is the same and I have two phones but one wont work..
[GUIDE/TUTORIAL/HOWTO] Unlock/debrand/desimlock Samsung Galaxy S i9000
[GUIDE/TUTORIAL/HOWTO] Unlock/debrand/desimlock Samsung Galaxy S i9000 for free in 2021
This detailed step-by-step guide helps you remove the provider locked on your Galaxy S phone using a Windows 10 PC.
### Make sure you read EVERY message starting with ###
CHANGELOG OF TUTORIAL
v1. Initial release
1 ) DOWNLOAD
- djibe Galaxy S i9000 debrand pack (47 MB) v1 : http://bit.ly/djibe-i9000-desimlock-pack
(contains all the required elements: Samsung USB drivers, SuperOneClick 2.3.3, Busybox, Galaxy S Unlock.apk)
2 ) CONTROL SIMLOCK ON YOUR PHONE
On your phone, open the dialer (as if you wanted to call a phone number) and type these keys:
Code:
*#7465625#
Phone returns this message:
Network Lock
[ON]
xxx
### If Network Lock is OFF, you can leave this tutorial now !
This technique was tested with latest official OS for Galaxy S i9000: Android Froyo 2.2.
### Debrand/desimlock cannot be executed from a custom ROM, you need the original one !
On phone, go to Settings > Applications > check Unknown sources,
now go to Settings > Applications > Development > and check USB Debugging.
3 ) INSTALL USB DRIVERS
Install the Samsung USB drivers from my pack.
Connect phone to PC and wait phone drivers installation.
4 ) ROOT PHONE
Desactivate your antivirus (Bitdefender and Windows defender blocked SuperOneClick from running on my PC).
Run SuperOneClick.exe from my pack.
(Make sure phone is connected and USB debugging is written in Android menu. If not, see above for USB debugging)
Click on Root and wait during operations.
When prompted, install Busybox.
When success message appears, you can close SuperOneClick.
### If root fails, your Antivirus deleted files. Redownload SuperOneClick and root again.
Now on phone: Open the new superuser app.
Tap on bottom left menu of phone to reveal app menu > Preferences > Automatic response > tap on Allow.
superuser will accept all operations (and prevent fail on next step).
5 ) UNLOCK/DEBRAND/DESIMLOCK PHONE
Connect phone to PC again.
Connect the phone as Mass USB storage.
Copy the 2 APK from my pack on main folder of phone's storage (phone appears as a USB key in Windows explorer).
Now open My Files app (standard Samsung app).
Scroll until you see BusyBox_v40*.apk.
Tap on it and select Package installer, confirm install.
Restart phone.
Now launch your new app Busybox Free.
### It can crash multiple times, try again until it doesn't.
Tap on Install button at the bottom of screen and wait during Busybox install.
Now open My Files app again.
Tap on Galaxy S Unlock apk file.
Tap on it and select Package installer, confirm install and Open app.
Once in Galaxy S Unlock app.
Sceen may become black, app is laggy. Just be patient.
Go to Unlock tab.
Tap on Step 1 Backup files and wait during backup of phone's IMEI.
Tap on yes to backup actual efs partition (phone's IMEI)
Continue with Step 2 > yes
Test a phone call. Restart phone.
And finish with step 3.
Reboot phone.
Go back to the dialer, type again *#7465625#
Network Lock is now [OFF]
Bravo !
Connect phone to PC as Mass USB storage again and save the Galaxy_S_Unlock folder located in the main folder of Internal storage.
Save it to a safe place on your PC.
Enjoy your freely debranded Samsung Galaxy S.
--------------------------------------------------------------------------------------------------------------------------------
Everything here failed ?
You can try GalaxSim Unlock app (I didn't).
Download from Play Store https://play.google.com/store/apps/details?id=com.spocky.galaxsimunlock
Hi,
I bought another simlocked SGS to test this tuto again.
It went on very easily yesterday.