as i've posted on another forum here:
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Click to expand...
Click to collapse
new things: i know that usb support in wine is nonexistent, thus i need to know how to get wine to see my device if i need to use odin (with kies for the drivers). adb works only intermittently; it sometimes doesn't see my device. i'm not sure if i can use mac osx in a vm, either.
can i get samsung drivers for linux at all? or am i hopelessly screwed? all i wanna do is root, get twrp, get xposed and then work from there.
Hi!
I answered your previous thread, but now I understand your problem
I see you are trying with vmware
would you use virtualbox?
Related
Hello all,
I've searched and found reference to people having the issue, but couldn't find any resolution and wanted to see if anything new has come up.
I prefer the manual method of rooting, and need to get adb working with this device.
Nexus 10 running 4.3, factory unlocked manually using fastboot (which works fine). I updated all of the relevant stuff in SDKmanager, but still can't get my Nexus 10 to come up in "adb devices" even after killing and restarting adb server. This is on a mac, for the record.
My rooted nexus 4 comes up in adb without issue.
Any thoughts?
Thanks
Did you remember to check "USB Debugging" on Developer Settings?
To unlock Developer Setting you must press many times Build Number, then there you can turn on USB Debugging . Hope it works!
Sorry, should have mentioned that I did put it in USB Debugging mode. I've tried it with the "Verify apps over USB" setting in the Debugging section both checked and unchecked, killing and restarting ADB server each time.
As far as I know I'm doing everything correctly...
Any other ideas?
Did you try killing the server and starting it with sudo? When my adb gives me problem on my Fedora/Ubuntu I do it and solves the problem . Also try plugging in other USB Ports if it's the case.
Normally on Windows when you cant get the device to show up it is a driver issue, I would imagine the same is true for OS X as well. I cant really recommend an alternate driver though since I dont know much about installing this stuff and rooting when running Mac :/
EniGmA1987 said:
Normally on Windows when you cant get the device to show up it is a driver issue, I would imagine the same is true for OS X as well. I cant really recommend an alternate driver though since I dont know much about installing this stuff and rotting when running Mac :/
Click to expand...
Click to collapse
AFAIK Mac is like Linux, and in Linux we don't have this problem, although sometimes it's needed to modify the rules, I decided to keep this for later, only if the more simple methods doesn't work, as it's way harder than these ones I already pointed.
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Reyse said:
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Click to expand...
Click to collapse
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
thefailure said:
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
Click to expand...
Click to collapse
Did you debug (adb, fastboot) another phone already or is this your first one?
I was trying to install the October security updates on my rooted 6P and thought I did so successfully. However, when it rebooted, it just hung on the Google screen for an hour and I tried to investigate. It appears that I no longer have a recovery or OS and that all I can do is go into the bootloader and reboot the bootloader.
I'm using a Windows 10 64-bit laptop with two USB ports and a USB-A to USB-C cable from Anker. When I started this process, I was able to get my device to appear when using -adb devices-, but now it won't any longer. I've installed, uninstalled, and reinstalled the drivers, both manually and by using both Android Studio and SDK manager (like in Heisenburg's Rooting instructions, post 1, Prerequsites: paragraph 4), but nothing will help it appear on my devices list.
As I understand it, I need to enable USB debugging on my phone, but since I can't boot, that seems not to be possible.
Any help would be greatly appreciated. I've searched dozens of websites looking for suggestions but nothing I do seems to get my phone to appear on the devices list.
Use fastboot from the bootloader instead of ADB. Use fastboot to flash the factory image. Same thread you mentioned.
ADB does NOT work from the bootloader. Only fastboot does.
You use ADB while booted into Android or in recovery. From the bootloader, you use fastboot.
Try again with "fastboot devices" instead of "adb devices"
Hate to say it, but you wasted a lot of your time reinstalling those drivers. If you had it working earlier, I can't see it just stopping. You just used the wrong command. ADB will only ever work booted to the OS or in recovery. Never from the bootloader, even if correctly installed. Same for fastboot, only from the bootloader and never from recovery or booted into Android, even though everything is installed correctly.
Read over that thread you mentioned a few more times. :angel:
Amazing. I have no idea how I could have not known that. Thank you for your help.
Glad you got it sorted!
I know there are instructions (which I am following) and a similar thread (which doesn't provide a solution). Anyway, I am following the instructions and I'm stuck at the command for detecting fastboot devices. The command window shows nothing, not my serial number or an error message. The Fastboot Protocol option on the tablet's menu just loops back to the same menu. I followed all the instructions (undetailed as they are) correctly, but on the fastboot device step I am stuck. I can't use the CyanogenMod links anymore because they're down. Other websites only give me steps I've already done or don't apply to this.
Basically, I just want to know how to make my PC detect my tablet so I can then wipe and flash the images. I want to downgrade because some apps just don't work correctly with 2.0 and I don't really want to wait for an eventual fix (which may or may not fix all the app issues).
I should mention that I can detect the adb device when it's on normally ( I type adb devices and it shows up). But when i reboot into bootloader and type adb or fastboot devices it isn't detected, and when I try to use fastboot protocol (either before or after connecting) it doesn't do anything.
Had the same issue with fastboot myself. If you are running Windows 10, that could be the problem. The ususal about checking different USB ports etc. also applies.
The drivers are most important. The naked usb drivers seemed to help me the most. Also, if you are going to change the usb drivers you have, reboot between changes. Fastboot can be challenging, but you are on the right tack.
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)