Hello, I am trying to degoogle my first phone, Wileyfox Swift.
Unfortunately I got into problems straight away.
Adb recognises my device, but as soon as input 'adb reboot bootloader', the device just crack. See the image below.
Indeed the fastboot is not recognised either.
I am stuck at the beginning, I don't understand why.. Does someone have an idea about it, please?
If it helps, my bootloader version is: crackling-12-ge9dcde6
Can this be the problem?
I also created a Create a new rules for 51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", MODE="0666", GROUP="plugdev"
but as soon as I execute the file with this command:
chmod a+r /etc/udev/rules.d/51-android.rules
I get back that the operation is not permitted..
I am clearly a nub, but is there someone out there able to help, please?
Thank you very much.
I may give it up altogether otherwise, I have been spending days on this..
Hello, Ggraja33, welcome to the club.
If it helps, my bootloader version is: crackling-12-ge9dcde6
Can this be the problem?
Click to expand...
Click to collapse
I think it is.
Did you look at these installation instructions:
https://wiki.lineageos.org/devices/crackling/install?
There is written:
Special requirements
Warning: Your device must be on bootloader version crackling-13-ge86e772 , otherwise the instructions found in this page will not work. The current bootloader version can be checked by running the command getprop ro.bootloader in a terminal app or an adb shell from a command prompt (on Windows) or terminal (on Linux or macOS) window.
Click to expand...
Click to collapse
But you can fix this just with an unlocked bootloader.
Have you tried various USB-Sockets, maybe an USB-Hub?
You can get also into Fastboot while powering down and then then push "power" and "Volumen up".
Good luck,
wowi63
Thank you so much for your reply, wowi63.
Yes, I read the instructions but I couldn't find the way to solve the problem of the different version of bootloader. Could you address me please to some resources to read on how to unlock bootloaders, please?
I also tried two different USBs.
Thank you. Maybe I have a hope!
Hmm - i unlocked 5 Swifts and had no problem - but the last is now 2 years ago.
I do not know any other instructions.
Maybe you try other USB-Cables?
Shut the device down, remove the battery ca. 10 min and try again?
Are you sure you choosed "Enable OEM unlock in the Developer options under device Settings, if present"?
.
Related
Hi .. would really like some help as I got a replacement G2 and I need to return my broken phone back tmrw and would like to root it.
I actually rooted my first g2 using temp root/visionary about a year ago...
but now I can't seem to understand the wiki's or any guides on how to root my phone again. . help!
Tried the AMT way, says device is not connected
Currently trying to use this guide : http://forum.xda-developers.com/showthread.php?t=1107911
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
any help would be appreciated.. sorry I am a complete noob at this
ahan421 said:
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Do you have Android debugging enabled on your phone? I don't know if it matters but I think your sdcard shouldn't be mounted when you connect it to your PC.
With the above things done, you should be able to type
adb devices
And it should list your device and its serial number.
You probably need to install drivers. I'm assuming you're using windows?
You can get the driver package here
You'll need to downgrade first with this guide
Then I recommend the wiki method to root
-Nipqer
I just downloaded the HTC drivers
i'm following the downgrade guide now
i downloaded the 2 files and put them in the platform-tools folder
already having trouble with the first step
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
> adb shell cat /dev/msm_rotator"
where do i type this command?
"> adb shell cat /dev/msm_rotator"
sorry if i sound like an complete idiot.. i have no clue what to do.
alright, i read through some of the adb for dummies
when i type in adb devices i do not see a serial number.. but i've installed the htc drivers already
is there something else i need to install? thanks
edit:* Yay i just got the drivers working, serial number is now showing!
edit 2: i had no idea what i was doing... somehow got through the instructions, downloaded some pda drivers, followed the guides and now my phone is rooted!
i felt like Neo typing in the codes... Thank you guys. Thank you XDA!!
Glad to hear you got it sorted out. Sounds like a good learning experience
Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.
sirgen said:
Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.
Click to expand...
Click to collapse
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin
ruscan.calin said:
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin
Click to expand...
Click to collapse
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
sirgen said:
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?
Click to expand...
Click to collapse
It seems you have adb.exe tool already installed but you get error because you do not have enough rights on your phone so get the rights by these lines..
by terminal here I mean cmd.exe from Windows
so enter cmd Start/Run/cmd.exe
then to start adb server enter this
Code:
adb devices
then in cmd enter
"adb shell" press Enter (in fact this is "terminal" - a way to get access on your phone and enter commands)
then "su" press Enter
and so on..
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
lastly enter
Code:
adb pull /efs/nv_data.bin
now you get nv_data.bin on your PC check for this file in the folder where adb.exe is located usually ~\android-sdk\platform-tools\adb.exe
You have the advantage of a well-known phone so there are solutions for everything
by example look here for a tutorial to unlock your phone
If you do not understand something let me know about
This is the case you want to work from scratch the easy way is to search on Market/ Google Play for an app to unlock this phone
Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.
sirgen said:
Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.
Click to expand...
Click to collapse
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?
ruscan.calin said:
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?
Click to expand...
Click to collapse
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?
sirgen said:
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?
Click to expand...
Click to collapse
root is very important if not you can not play with nv_data.bin file...
what link ? and how did you do what steps I can't guess show me some logs screenshots anyway more info !
[QUOTE su
chmod 777 /efs/nv_data.bin
exit
exit
Then from the DOS command prompt:
adb pull /efs/nv_data.bin
Step 5: Select the file on the main Samsung Galaxy S Unlocker & Repair page
Step 6: Enter your desired Unlock and Unfreeze Codes and click the SUBMIT button
Step 7: Download the new file that is generated for you
Step 8: From ADB shell (Type "adb shell" at the DOS command prompt) or a terminal on your phone, enter the following commands to backup your current EFS related files, in case something goes wrong. ![/QUOTE]
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is. I included two pics of tmy adb shell (adb pull /efs/nv_data.bin)
I also copied an efs folder from my phone onto my pc.
sirgen said:
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is.
Click to expand...
Click to collapse
here is it http://www.communityhosting.net/sgsunlock/
ruscan.calin said:
here is it http://www.communityhosting.net/sgsunlock/
Click to expand...
Click to collapse
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.
problem solved
sirgen said:
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.
Click to expand...
Click to collapse
I like your answer this is like 100 thanks for me !
also as Vertron said there are apps in Market to unlock this well-known phone
Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
My sincere apologies to you my friend. I was able to unlocked my SGS after I followed your advice of downgrading to froyo and then I continued with the tutorial I got through Member ruscan.calin. So excess amount of thanks to you both. I will make sure to properly BACKUP my SGS3 before I touch it. I have learnt my lesson. Thanks again.
aarlene said:
Hi,
You can unlock your Samsung Galaxy S I9000 using unlock codes!! Unlocking using codes is easy and also safe!! You can get the codes from your service provider or from reliable online sites!!!Personally, I would suggest prounlocking.com , here they provide accurate codes at reasonable price!!!
Click to expand...
Click to collapse
Thanks for the heads up, but I did it with the help of XDA
Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Thanks
I have been on this for 5 hours and i just cant seem to get anywhere.
I want to root my HOX i know you have to go to http://htcdev.com/ to unlock the bootloader but there isnt enough information from htc how to do it with linux and am still learing it i have follwed instructions from all over the web but i get no were. I have placed the Fastboot file from HTC in android/sdk/platform-tools i then go to type this command in terminal cd android/sdk/platform-tools i then get bash: cd: android/sdk/platform-tools: No such file or directory i have tried it via SU but i get the same.
elsworth1983 said:
I have been on this for 5 hours and i just cant seem to get anywhere.
I want to root my HOX i know you have to go to http://htcdev.com/ to unlock the bootloader but there isnt enough information from htc how to do it with linux and am still learing it i have follwed instructions from all over the web but i get no were. I have placed the Fastboot file from HTC in android/sdk/platform-tools i then go to type this command in terminal cd android/sdk/platform-tools i then get bash: cd: android/sdk/platform-tools: No such file or directory i have tried it via SU but i get the same.
Click to expand...
Click to collapse
Did you map the .zip or .bat? It needs to be unzipped into the folder to work.
vodka7 said:
Did you map the .zip or .bat? It needs to be unzipped into the folder to work.
Click to expand...
Click to collapse
Cheers for the reply i did unzip it and i was just coming to update my progress lol i finally got to the token part but it just waiting for device i typed in adb devices and it comes up with no info but if i boot the phone up normally a get a device number.
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
[email protected]:~$ fastboot oem get_identifier_token
< waiting for device >
On linux, sometimes you need to mess with one of the virtual filesystems for it to see the device. I can't remember how it works now, but you add a file with the manufacturer id and product id.
BenPope said:
On linux, sometimes you need to mess with one of the virtual filesystems for it to see the device. I can't remember how it works now, but you add a file with the manufacturer id and product id.
Click to expand...
Click to collapse
Cheers for the info is it this what you are on about sudo adb kill-server if so i have tried it and it only shows the device when powerd on i have had a little play this morning before going to work still no joy I really want to unlock this device and flash a better rom than uk's O2 rubbuish but it feels like i am hitting my head against a brick wall. Any how thanks again this community rocks well of to work i go
hello,
I did it last week...
try
Code:
./adb reboot bootloader
the important part if you just unzip the "android/sdk/platform-tools" it that you put "./" before adb and fastboot commands and eventually before folders's paths
Give it a try.
Cheers will give it a try tonight when I get home @ work now and knackered lol
Sent from my HTC One X using xda app-developers app
You may also need to add your device ID to your udev rules. There are plenty of guides of you Google it
Michealtbh said:
You may also need to add your device ID to your udev rules. There are plenty of guides of you Google it
Click to expand...
Click to collapse
This is what I was talking about, stupid brain couldn't think of "udev".
RIght Back Home now lets have a play :laugh: thanks to every 1 for the help.
Just got fastboot flash unlocktoken Unlock_code.bin
BOOTLOADER UNLOCKED
Thanks again
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
TioNacho said:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
Click to expand...
Click to collapse
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.
ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!
Just root your phone using Magisk and execute these commands using adb on your PC/laptop:
Things to note before you start executing commands below:
1. Make sure that USB debugging in your phone is turned on.
2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.
3. After "su" command, you have to grant root access to adb shell within 10 seconds.
4. "adb reboot" command will immediately reboot your phone, don't panic.
5. You are doing this at your own risk.
Code:
adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot
Commands have been used from this thread: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Good morning!
Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
This happens because the device drivers are not completely installed.
CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Thank you for the replies.
I tried to use adb/fastboot on a Win7 desktop after I posted the above, and I cannot get the phone and win7 to see each other at all.
I have since tried to get into recovery mode but get "No Command".
What can I do to move forward? Phone boots and works fine once I get out of recovery.
This phone is fresh from Google, never had a sim in it.
Thank you for the detailed answer. I am having difficulty implementing the mods you listed. I have been a Linux user on and off for several years but I do not have deep knowledge of the inner workings.
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS) This returns "permission denied"
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev" <-- I have no rules.d file, just an empty folder named rules.d in that location
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Yes, r28.0.3.
Update:
CruelSun said:
Thank you for the replies.
I have since tried to get into recovery mode but get "No Command". I found out how t get past this, I'm going to do a factory reset and start over.
This phone is fresh from Google, never had a sim in it.
Click to expand...
Click to collapse
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
CruelSun said:
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
Click to expand...
Click to collapse
Glad you figured it out.
Sent from my Pixel 3 XL
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
STALKER18 said:
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
Click to expand...
Click to collapse
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Sent from my Pixel 3 XL using Tapatalk
CruelSun said:
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Click to expand...
Click to collapse
Windows has to update. The 30 minutes was probably the update in the background. My windows 10 did the same thing. Linux doesnt work anymore. I used ubuntu with latest adb and fastboot packages. Manually installed newest tools zip. Nothing. I got it to work a few times. Windows 10 is a little buggy too. Only fastboot I found to work on the pixel 3 xl without and or little errors was my MacBook. Which I have dual booted to chromeos and Ubuntu in chromeos. Also restarting on windows anything puts it into the loop of things. You can install adb and fastboot on windows but they need a restart to work. Unless just mounting the file folder and using it that way.
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
Click to expand...
Click to collapse
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
uicnren said:
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
Click to expand...
Click to collapse
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
uicnren said:
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
CruelSun said:
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
Click to expand...
Click to collapse
Simplest method: https://github.com/corbindavenport/nexus-tools
CruelSun said:
...
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
...
Click to expand...
Click to collapse
I realize this is a bit old now, but, in case it's helpful for someone in the future...
Often the /etc/used/rules.d directory is empty. You just need to add the file 51-android.rules into that directory.
Code:
sudo touch /etc/used/rules.d/51-android.rules
You need to run that command as root which is why it's prefaced with sudo.
Then you can edit the file as described in the first post. As stated earlier, much better to type into your editor rather than cut and paste because you want to make sure no weird html characters get introduced.