Hello,
I'm trying to unlock bootloader and here is and that's what I did:
1) Checked that there is a rule in /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dff", MODE="0600", OWNER="lessless"
the lsusb output is
Bus 002 Device 018: ID 0bb4:0ff0 High Tech Computer Corp.
2) reboot into fastboot mode with adb reboot-bootloader
and when my phone is on the fastboot usb mode fastboot utility do not recognize it:
$fastboot devices
no permissions fastboot
$fastboot oem get_identifier_token
< waiting for device >
Maybe you need to backport the MTP support first?
Do a Google search for the terminal commands.. When I was running Elementary OS (based on 12.04) I remember having to do this as the OS wouldn't see my phone.
Sent from my thumbs
what do you mean exactly? I'am able to mount my phone using this lines:
alias android-on="mtpfs -o allow_other /media/Android"
alias android-off="fusermount -u /media/Android"
Related
I've decided to play around with Ubuntu again.. but my question is this.. when I plug my phone in, ADB isn't there.. How to I get my phone to connect to Ubuntu x64 (latest version, not sure number) as it did in Windows 7 .. Fastboot.. be able to transfer files to the internal storage... What gives?
jbarcus81 said:
I've decided to play around with Ubuntu again.. but my question is this.. when I plug my phone in, ADB isn't there.. How to I get my phone to connect to Ubuntu x64 (latest version, not sure number) as it did in Windows 7 .. Fastboot.. be able to transfer files to the internal storage... What gives?
Click to expand...
Click to collapse
This is the easiest way to install adb/fastboot that will work in any directory on linux (ubuntu) so you dont have to place the files in the platform-tools/ dir.
Code:
sudo apt-get install android-tools-adb && sudo apt-get install android-tools-fastboot
that will install adb and fastboot then,
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
a blank screen will pop up and add this, then change where it says <username> to your linux username and hit save (do NOT include the <>)
Code:
# adb protocol on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dff", MODE="0600", OWNER="<username>"
# fastboot protocol on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0ff0", MODE="0600", OWNER="<username>"
# adb sideload on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0cf9", MODE="0600", OWNER="<username>"
after you've saved that do a
Code:
sudo restart udev
if that doesnt work you may have to uncheck and recheck USB debugging in the settings on the phone...
or
when the phone is plugged in and adb is enabled in the terminal type
Code:
lsusb
Then you will get a bunch of stuff that looks like:
Code:
Bus 002 Device 006: ID [B]0bb4[/B]:[U]0dff[/U] HTC (High Tech Computer Corp.)
Those 8 numbers are what you put in the the idVendor:idProduct
Do that for adb, fastboot(you have to be booted into the bootloader), and adb while in recovery (for sideload featuer)
.torrented said:
This is the easiest way to install adb/fastboot that will work in any directory on linux (ubuntu) so you dont have to place the files in the platform-tools/ dir.
Code:
sudo apt-get install android-tools-adb && sudo apt-get install android-tools-fastboot
that will install adb and fastboot then,
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
a blank screen will pop up and add this, then change where it says <username> to your linux username and hit save (do NOT include the <>)
Code:
# adb protocol on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dff", MODE="0600", OWNER="<username>"
# fastboot protocol on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0ff0", MODE="0600", OWNER="<username>"
# adb sideload on DNA (dlx)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0cf9", MODE="0600", OWNER="<username>"
after you've saved that do a
Code:
sudo restart udev
if that doesnt work you may have to uncheck and recheck USB debugging in the settings on the phone...
or
when the phone is plugged in and adb is enabled in the terminal type
Code:
lsusb
Then you will get a bunch of stuff that looks like:
Code:
Bus 002 Device 006: ID [B]0bb4[/B]:[U]0dff[/U] HTC (High Tech Computer Corp.)
Those 8 numbers are what you put in the the idVendor:idProduct
Do that for adb, fastboot(you have to be booted into the bootloader), and adb while in recovery (for sideload featuer)
Click to expand...
Click to collapse
Beautiful.. Thanks!!! Will post a final reply once it's all working after I get off work... Hey!
Well.. I got too excited too quick... You lost me here...
after you've saved that do a
Code:
sudo restart udev
if that doesnt work you may have to uncheck and recheck USB debugging in the settings on the phone...
or
when the phone is plugged in and adb is enabled in the terminal type
Code:
lsusb
Then you will get a bunch of stuff that looks like:
Code:
Bus 002 Device 006: ID 0bb4:0dff HTC (High Tech Computer Corp.)
Those 8 numbers are what you put in the the idVendor:idProduct
Do that for adb, fastboot(you have to be booted into the bootloader), and adb while in recovery (for sideload featuer)
Click to expand...
Click to collapse
how are you lost?
It didn't work.. I'll try again.. I had to step away from it for some time.. I'll try it all again today...
[email protected]:~$ lsubs
No command 'lsubs' found, did you mean:
Command 'subs' from package 'libsubtitles-perl' (universe)
Command 'lsusb' from package 'usbutils' (main)
lsubs: command not found
Click to expand...
Click to collapse
This where I get stuck.. also before that..
[email protected]:~$ sudo restart udev
udev start/running, process 11814
Click to expand...
Click to collapse
you spelled lsubs instead of lsusb. I'm pretty sure that message for reloading udev is normal.
Now my issue is with Fastboot... Does this not enable me to flash recoveries? I am trying and just says <Waiting for device>
you must do the same for fastboot as for adb
issue lsusb while in fastboot mode and get id number for fastboot and add that to ur android rules file also
issue lsusb while in recovery for proper ids
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”aaaa″, ATTRS{idProduct}==”aaaa″, MODE=”0666″ <<< with id for adb
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”bbbb″, ATTRS{idProduct}==”bbbb″, MODE=”0666″ <<< id for fastboot:bootloader
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”cccc″, ATTRS{idProduct}==”cccc″, MODE=”0666″ <<< id for recovery
t1gartist said:
you must do the same for fastboot as for adb
issue lsusb while in fastboot mode and get id number for fastboot and add that to ur android rules file also
issue lsusb while in recovery for proper ids
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”aaaa″, ATTRS{idProduct}==”aaaa″, MODE=”0666″ <<< with id for adb
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”bbbb″, ATTRS{idProduct}==”bbbb″, MODE=”0666″ <<< id for fastboot:bootloader
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”cccc″, ATTRS{idProduct}==”cccc″, MODE=”0666″ <<< id for recovery
Click to expand...
Click to collapse
Got it!! Thanks... the help was great!!
I keep getting an error that states ... "Unable to mount Android Phone; unable to open MTP device '[usb:002,014]'"
Hello,
do you use rockchip based Android device with linux?
I've just bought Rockchip rk3066 based AllFine Fine10 tablet, and have trouble setting it up to work with adb on my linux instalation.
I presume problem is with udev rules, I use some giant package of udev rules but it does not contain rule for my tablet.
I have tried to manually define udev rule by inputing device ID listed by lsusb utility.
lsub: Bus 002 Device 004: ID 2207:0010
Click to expand...
Click to collapse
Thus creating:
# AllFine
ATTR{idVendor}=="2207", ATTR{idProduct}=="0010", SYMLINK+="android_adb"
Click to expand...
Click to collapse
But still device is not recognized by adb.
I could use some assistance, thank you.
from http://linux-rockchip.info/mw/index.php?title=ADB_shell_with_RK3066
You need to add those Udev rules in order to obtain an ADB shell on your RK3066/RK3188 device:
In terminal run "lsusb", you should see a device with a device ID starting by "2207", the USB VendorID of Rockchip:
$ lsusb
Bus 002 Device 023: ID 2207:0010
In this case, the description of the device was left empty.
Download and install the Android SDK or, just download adb from an Ubuntu Linux with this command:
sudo apt-get install android-tools-adb
Run "sudo gedit /etc/udev/rules.d/51-android.rules" from the terminal and add this to the file and save:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
Then restart udev with "sudo udevadm control --reload-rules"
Run (not using sudo) "gedit ~/.android/adb_usb.ini", add 0x2207 at the end of the file
Restart the adb server with "adb kill-server; adb start-server" from terminal, you should be able to list your device with "adb devices"
Enable "USB Debugging" on your device and adb should be fine now.
i am on macosx and installed android studio
the adb and fastboot and driver (kext) for android are broken in such the following ways
1. adb
it is not detecting even virtual machine , tried all the version
when i run ./adb usb or ./adb devices for the first time
it is not showing thing like
Dameon starting up bla bla
and run quietly and freezes
sudo ./adb devices
List of devices attached
*** it freezes i.e keep waiting
sudo ./adb usb
** it freezes and waiting
even
sudo ./adb kill-server
**8 it is freezing and waiting
sudo ./adb start-server
** it is waiting
i have given it all permission
chmod 777 adb
platform-tools Prodesign$ sudo ./adb start-server ** it is waiting
2. fastboot
./fastboot-mac devices
ERROR: could not get pipe properties
HQ65XBS32030 fastboot
fastboot oem get_identifier_token
ERROR: could not get pipe properties
... // i tired a htc android
not a single android in adb pr fastboot is working correctly
there is not adb_usb.ini file in sdk folder of adb also new adb does not uses adb_usb.ini file
also i added that file and device if like 0x1368 even though it is not working
Please help
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
Code:
$ adb devices
List of devices attached
NX529J device
$ adb reboot-bootloader
$ fastboot devices
$
I am using Ubuntu 16.04 and installed adb and fastboot with
Code:
sudo apt install android-tools-adb android-tools-fastboot
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
I found a Chinese TWRP on Chinese website (but the download link is now broken)
http://bbs.nubia.cn/forum.php?mod=viewthread&tid=647594&extra=page=1&filter=typeid&typeid=443
http://www.microsofttranslator.com/...tra=page%3D1%26filter%3Dtypeid%26typeid%3D443
However, I found it mirrored on a Polish website
http://telchina.pl/nubia-z11-mini-nx529j-t28452-24.html
which links to https://drive.google.com/file/d/0B0hidJ2sijwIb0ctdk9kaWFGSmc/view
Inside was a bat file that had an extra parameter command
Code:
fastboot -i 0x19d2 boot NX529J_TWRP_3.0.2-0-521.img
According to the fastboot docs you can force fastboot to work with a device even if the vendor ID is unknown by the fastboot binary by using the -i parameter
http://elinux.org/Android_Fastboot#Commands
Code:
-i <vendor id> specify a custom USB vendor id
You can find the vendor ID of devices using lsusb
e.g.
Code:
lsusb |grep ZTE|cut -d: -f2
ID 19d2
That enabled fastboot to work and TWRP started.
It was in Chinese but there is an English button that says Change Language and you can change to English.
He has also packaged SuperSu in the Advanced menu under "Stalence Tools" in order to root your phone.
opticyclic said:
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
Code:
$ adb devices
List of devices attached
NX529J device
$ adb reboot-bootloader
$ fastboot devices
$
I am using Ubuntu 16.04 and installed adb and fastboot with
Code:
sudo apt install android-tools-adb android-tools-fastboot
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
Click to expand...
Click to collapse
type this first fastboot oem unlock-go to unlock bootloader
before that you need to enable oem unlock and usb debugging in options
and I use this twrp
Interestingly I didn't need to unlock the bootloader.
The fastboot oem unlock command didn't work like that though because of my fastboot binary not being aware of the vendor as mentioned in the previous post).
The TWRP you linked to (NX529J-TWRP_3.0.2.3_CUOCO92) is the Italian one.
Is the source available?
Is there an English menu in it?
yes, it is in English but maybe not at first run. to set English follow procedures on pictures
OK.
That is a bit weird though.
Why is an Italian compiling TWRP in Chinese?
The one by Stalance/Silent Star has a button on the first page in English that jumps you to the language section.
I'm trying to compile it myself atm but I don't know how to specify the blobs to extract to create a vendor tree.
The other issue was because I installed adb from the repos.
That was version 1.0.32 but the version at https://developer.android.com/studio/releases/platform-tools.html is 1.0.36.
When I download, unzip and run
Code:
sudo fastboot devices
this time it recognises the device and I don't have to pass the vendor id.
opticyclic said:
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
I am using Ubuntu 16.04 and installed adb and fastboot with
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
Click to expand...
Click to collapse
i don't have to unlock, i was already unlocked, should i replace the device
i need qcn NX529J my phone empty imei, but i dont backup
Hi guys, just a disclaimer here but I’m a newb when it comes to flashing ROM’s. I’m trying to flash Calyxos but I’m not having any luck. I get a very quick CMD window (using file flash-all.bat) that appears and then disappears and then… nothing. I’ve tried updating and installing adb drivers, downloading the latest adb fastboot (minimal_adb_fastboot_1.4.3_portable), re-downloading Calyxos (crosshatch-factory-2020.09.22.12) and setting the environment variables to reflect the location of the Caylxos files. I’ve already unlocked the phones bootloader and have USB debugging and OEM unlock enabled. When I run “adb devices” using cmd.exe, it’s able to detect the phone, but this is as far as I can get. If anyone has any advice for me, I’d really appreciated it!
Phone has also been updated to Android 11 and has the latest security patches installed
Anybody?
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Awesome! I'll try it again this evening and report back. Thank you very much for the help
jwoegerbauer said:
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Click to expand...
Click to collapse
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools>fastboot flash "C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin"
unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
fastboot: error: cannot determine image filename for 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
I feel like I'm almost there! Not sure if it matters... but the "avb_pkmd.bin" file is only 1 KB in size. Anyhow, I'm not really sure how to fix this error. Would you be willing to help me out again?
jspicket1111 said:
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
...
Unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
Click to expand...
Click to collapse
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
jwoegerbauer said:
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
Click to expand...
Click to collapse
I finally got it! Thank you very much for the help!