Since there is no proper information about unlocking the bootloader for the newer versions of Oneplus Nord 2, this is how I got it to unlock and actually work.
For my system it did reset the device, clearing all the files and factory restoring the device, just make sure to make a backup before you do anything.
Just like any other post, no warranties or anything, this is all at your own risk.
1: Make sure to enable OEM unlocking and ADB Debugging in the developer options
1.1: To have these options, first go to About phone > Version
1.2: Keep tapping the "Build number" to unlock the developer options
1.3: Navigate back to settings and open Additional Settings. There you will find the Developer Options.
2: Install: Platform tools: https://androidfilehost.com/?fid=17248734326145690420
3: Install: MediaTek Preloader USB VCOM drivers: https://drive.google.com/file/d/1TPbW-v9-yOrzH15OaHmsPQad420mULeF/view
4: CMD to the root of the platform tools and use the command "adb reboot bootloader"
5: While in the weird tiny screen, validate that your device is there by typing "fastboot devices"
6: If so, type fastboot flashing unlock
7: Profit.
Hope this helps any other people searching for a proper way to do this.
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
meterpreter said:
OMG I spent hours searching for a working fastboot driver. Unlocked successfully! I owe you a beer man drop me your paypal
Click to expand...
Click to collapse
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Eastw1ng said:
The cheers is already great, hope they release a working stock rom soon so we can finally have some custom roms going!
Click to expand...
Click to collapse
I hope so too. I would really like to put lineage on this thing, probably the only os that can make a usable device out of this actually very good phone
Unlocking the bootloader requires two settings to be made in Android's Developer Options:
ADB Debugging
Allow OEM Unlock
@Eastw1ng, as obvious as this may be once you remember, unlocking the bootloader is something most people don't do very often - it might make sense to include that in the OP
@NetSoerfer, you're not wrong, quickly added it to the start.
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
CapnRene said:
I have a issue, Fastboot cant't find mobiledevice in win10. Adb commands working great. Debugging and oem unlock options enabled.
Tried:
1. different usb ports, cables and PC
2. Oneplus, Google and Mediatek USB drivers. With ADB or Bootloader interface.
3. Reinstalling PC USB drivers.
Am i missing out something?
Click to expand...
Click to collapse
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
HofaTheRipper said:
use latest platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
CapnRene said:
Hmmm, it worked, I think last one was ver. 30. Last year I downloaded "15 second ADB". It seems it made a mess in my ADB directories. Had to delete few folders and path from win10 Environment Variables. Made new folder and added new path.
I think it is last time when I use some kind "ADB installer".
I wonder if Android Studios didn't come with it automatically? Because I reinstalled that and it didn't work?(it might be that 15 sec installer messed up paths)
Click to expand...
Click to collapse
Can you tell me how to install these drivers I tried but still not detecting
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
X:\Users\XXX>where adb
X:\platform-tools\adb.exe
And system variables
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
CapnRene said:
You have same issue that adb is detecting phones but fastboot not?
There is no installer by google. You just replace files for updating.
For first make sure CMD doesn't find multiple locations for ADB. Type in CMD where adb. Be sure that it finds correct folder where is platform tools ver 31.0.3!
If it's wrong then you need insert new Path in system variables or changes whole folder where 'where adb' indcates. Also double check that oem unlocking is enabled in developer options on phone.
This is my CMD exaple:
C:\Users\Rene>where adb
C:\platform-tools\adb.exe
And system variables
View attachment 5420349
Click to expand...
Click to collapse
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
pankspoo said:
I have done all the things still it's not detecting but surprisingly it's detecting my old one plus 6 easily.
On another lappy where I . using zorin os ubuntu based os simple terminal commands installed android platform tool on Linux and I got easily detected Nord with same commands.
But anyway thanks
Click to expand...
Click to collapse
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
pankspoo said:
Can you tell me twrp given in another thread is working on oos11.3 v10 ?
Click to expand...
Click to collapse
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Eastw1ng said:
Have you tried installing these "MediaTek Preloader USB VCOM drivers"? Quite often it's a driver issue and you'll be able to see in the device manager if something's not properly loading the drivers.
Click to expand...
Click to collapse
Yes installed
Eastw1ng said:
It is working for me on v10, just make sure to have the v10 bootloader on hand, it might require a reflash of that after the recovery patch
Click to expand...
Click to collapse
V10 bootloader means boot.img? If you have that please send me
pankspoo said:
V10 bootloader means boot.img? If you have that please send me
Click to expand...
Click to collapse
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
pankspoo said:
Yes installed
Click to expand...
Click to collapse
Alright, well just put it into fastboot mode and check your device manager, does it show any devices that are not properly installed? If so, try to resolve it from there
Eastw1ng said:
You can find the images sakarya posted before: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
Click to expand...
Click to collapse
Thanks
Related
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
christophermaisch said:
Hi all I'm having problems with getting ADB to see my device and was hoping someone with more brains can help me to solve this problem. I've searched this as much as I can on XDA and Google in general but nothing I find works device specifically.
First setup: I'm running the brilliant ARHD 11.0 JB with build.prop tweaks on top of Siya 1.6.8 and I don't think that Mike and GM need any introduction since they are both household names in our forums.
My machine OS: 7 Ultimate 64
The drivers I've installed: (this might be a factor in the problem)
Latest Kies. I've also installed the s3 drivers when connecting the device in download mode. I have uninstalled Kies because it's unless after the device drivers have been installed IMHO.
The ADB I am trying to use: I downloaded the generic ADB since I think the bridge is generic and mentioning the platform is irrelevant. But it was not the one bundled into the SDK since its not necessary. I have run it as Admin
My problem: I have connected my phone with debug enabled and disabled Auto play but as soon as I "adb shell" in cmd (after cd the adb directory) I still get the "error: device not found" message.
I've tried what I can but can figure it out could someone with the brain. I wish I had please slap me around the room and point out my obvious error and set me on the right path or at least cry with me in my frustration.
If I could get a devs input it would be awesome but if anyone could help me out, I would greatly appreciate it.
Please tell me if I've ommited any important info.
Thanx guys!
CM
Click to expand...
Click to collapse
Your problem determinated drivers , install drivers for samsung devices, reboot your pc, connect your device to your pc , expect driver installation , then check if updated , then if the sdk is installed correctly , adb devices.... USB Debugging enabled ......
i had an isssue last night with adb...
unplug phone from pc and turn off and then on usb debuging on the phone...
enter cmd mode on pc, then
adb kill-server
adb start-server
adb devices
then hopefully it will show the device is connected....
p.s. drivers should be installed and checked, this step it is mandatory....
hope it helps ...
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
May this help connect your usb to direct motherboard port. Do not use usb hub if you are
Sent from my GT-I9300 using xda premium
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Debug/test apps on device over the air, no cable. Must-have developer tool. WiFi ADB
You just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny
When you have USB Debugging mode turned on on your phone and you connect to the computer and you look at Device Manager (Win+R, devmgmt.msc) do you see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you get Unknown Devices automatically expanded, then you haven't got the correct drivers installed.
You don't need to install Kies to have the latest drivers installed; you can extract them from the setup itself:
Download KIES and run the setup but don't do anything with it
Open up your Temporary Files folder: Win+R, %TEMP%
Look for the folders that start with a '{' and end with a '}' and have a bunch of letters, numbers and 4 hyphens in them and within this selection of folders find the folder that has its Date Modified timestamp matching the time you opened the KIES installer exe (in my case it was {44A91F3A-3D8C-43DE-A0BC-04E01C756397}). If you're in the right place, you'll find "Samsung Kies.msi".
Grab Less MSIérables, point it to Samsung Kies.msi and extract SAMSUNG_USB_Driver_for_Mobile_Phones.exe somewhere. lessmsi is a little slow...
You'll see a new folder "SourceDir" wherever you chose to extract the file, navigate through it until you find the EXE. Close the KIES installer and run the driver setup
Oh, rather than using some random version of ADB off the Internet, get it from Google themselves. The latest versions can be found in the platform-tools ZIPs for the SDK, but you don't need to install the SDK just for ADB: Open http://dl.google.com/android/repository/platform-tools_r14-windows.zip (14 is the latest version as of this post) and extract the three adb files from the ZIP and place them somewhere. This way you know it's not a problem of using an old ADB version.
You can also check to see if adbd is actually running on the phone when you plug it in by grabbing Terminal Emulator off the market and running: "/system/bin/ps | grep adbd" (note: you only get grep if you have BusyBox instaled)
Finally, if you really can't get USB connections to work, then use https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en :\
christophermaisch said:
Thank you both for you input but nothing works unfortunately. I'll continue the search thanx again though
Click to expand...
Click to collapse
Hey,
I had the exact same problem. This Tutorial : http://goo.gl/OS3Vi worked for me.
Hope it helps
I am having some problem remove an Nandroid backup; (it is impossible to remove it either with Root Exporer or in the terminal as root (rm -rf blah)).
However, now I am trying to use ADB to get rid of it I installed adb and some new drivers for my I9300.
Looked through my phone debug-settings, checked if ADB found my phone (adb start-server, adb devices). Then I rebooted my phone into recovery via CWM - however - now my phone does not want to be found.
Windows Device Manager recognize the phone, but the drivers-icon are yellow-ish (not sure if this is how they are supposed to look). adb devices gives me nothing.
I could really use some help over here.
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Please help please help!!!!!!
coachpete said:
i rooted my at&t htc one and when i was going to flash a rom i accidentally wiped the phone completely. I can go into twrp but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a usb otg cable but the phone didnt seem to recognize it. Please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
can someone please help me!!!!!!
HTC One not recognized by Windows 7 or Windows 8
coachpete said:
I rooted my AT&T HTC One and when i was going to flash a rom I accidentally wiped the phone completely. I can go into TWRP but cant move files into the phone. When i try plugging it into my computer all i hear is the little ring that windows does when you plug in something into the usb but i cant access the phones storage. I also tried buying a USB otg cable but the phone didnt seem to recognize it. please help. I've been stuck without a phone for about a week now.
Click to expand...
Click to collapse
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
coachpete said:
I am baby stepping through the trouble shooting process to try to get an image over to the phone so I can reimage through TWRP v2.7.0.0 but neither my Windows 7 machine nor my Windows 8 machine are recognizing the HTC One as a media device. I have tried the updated drivers with no luck. PLEASE HELP!!
Click to expand...
Click to collapse
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Computer doesn't recognize my HTC ONE
alray said:
you can use ADB from twrp recovery to push a rom to your /sdcard
follow this guide step by step and quote me here if you have question.
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Click to expand...
Click to collapse
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
coachpete said:
Thank you but my computer does not recognize my HTC one. I have tried installing the drivers from various sources but still no go! please help @alray
Click to expand...
Click to collapse
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Still no luck with the drivers
alray said:
check step 4 of the above prerequisites, click on ''show content'' then you'll find the instruction how to correctly install drivers.
Click to expand...
Click to collapse
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
coachpete said:
Followed the detailed instructions for downloading and installing the correct drivers and my Windows 7 machine still does not recognize the HTC One correctly.
Click to expand...
Click to collapse
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
FINALLY
alray said:
boot your phone in twrp, go in windows device manager and take a screenshot and post it here
when your phone is in twrp main menu, open a cmd prompt and do this command:
Code:
adb devices
what is the output?
Click to expand...
Click to collapse
Thanks for all your help I am now up and running!!!!!!
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
reserved if needed
Or you can install just adb and fastboot from http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my HTC One_M8 using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Rojax said:
Or you can install just adb and fastboot from http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for pointing that out but it is kind of unnecessary to do after I put all this together, it took time.
This is easy as that period and it's constantly updated, all you have to do is run sdk manager and run updates, nothing else required once set up. This is streamlined for just our devices since it also has directions for drivers for our device. Otherwise I would have put it under Android and general...
The tool you suggest by the way is awesome. Appreciate you taking the time to share it, FYI it's updated via sdk, the op stated where he pulls the updates for adb from.
So tomatoe, tomato, please let the users decide which tool they would like to use.
Thanks
Sent from my HTC6525LVW using Tapatalk
The guide is great, I was just listing an alternative (much smaller) download. Thanks for sharing this to help our community grow
Sent from my HTC One_M8 using Tapatalk
Rojax said:
The guide is great, I was just listing an alternative (much smaller) download. Thanks for sharing this to help our community grow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
No problem and thanks for sharing. Appreciate it
Sent from my HTC6525LVW using Tapatalk
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
Is it an easy process? Ive been rooting since 2011 so i can't imagine rooting a chrome book would be too hard?
Sent from my LG-H811 using XDA Free mobile app
I don't think it's that hard but I've only tried it when testing it for a netbook. You will have to search that model as it varies. Usually called developer mode and dual booting with another Linux distribution.
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
kibmikey1 said:
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
Click to expand...
Click to collapse
Hi, I'm trying to flash Marshmallow on my Nexus 7 using my Dell Chromebook. I'm almost there but my N7 says I have to update my ADB to 1.0.32. Unfortunately Ubuntu hasn't updated their repositories so any idea how I can update ADB on my chromebook?
thanks
Sent from my D6503 using Tapatalk
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
if i do this will it "root" my phone so I can get apps that require root?
Also, I have a galaxy j3 eclipse, will this work on my phone
rickyiswhite said:
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can root a phone on a chromebook just put it in developer mode and use your crosh shell to run adb and fastboot.
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
phone not connecting
What do i do if phone does not connect?
how do i put the TWRP.img file into the same folder where the fastboot and adb files are? or how do i type the command to flash it to my oneplus 7 pro in my crosh shell window.
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
lonnie89 said:
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
Click to expand...
Click to collapse
On my pixelbook with the beta Linux installed copy the downloadet twrp.img file to the linux folder that's located in the files app. Should then show up in your home Linux directory.
How do I get access to that file system in croots and flash it to the phone.
How do I get access to the file and move to the phone in croots what are the commands. It's my my downloads folder.
garretts228 said:
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
Click to expand...
Click to collapse
Hi. Thanks for a working method. I have tried each step and Crosh gave me error:
bash: /usr/local/bin/adb: cannot execute binary file: Exec format error
One question - do i have to be on "developer channel" in Chromebook?
Coz then i will have to reinstall Chromebook.
Best Regards
Nick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
eurovive said:
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
Click to expand...
Click to collapse
Sorry I didn't leave that detail behind for you, but yes that method does indeed require dev mode. However there are other methods that don't require it now using Linux. I have not done them so I am only forwarding this information:
https://www.reddit.com/r/chromeos/comments/dtwfpm
Thats a nice suggestion too. As someone says Chromebook should be Intel-ready to run Android apps, thats why i was thinking whats wrong. I have Arm based Tegra K1 with saying some how limited support of updates, therefore having support for Crostini feature. Will try later.
Guide has been reworked to be more clear and based on comments.
[Part One]
Backup Data
Update phone to latest version
[Part Two]
Download the Firmware for the Zenfone 9 https://www.asus.com/mobile/phones/zenfone/zenfone-9/helpdesk_download/
Download Payload GUI. https://forum.xda-developers.com/attachments/payload-dumper-gui-v2-3-zip.5758127/ (Hermann2306 credit for mentioning)
Extract the Payload Dumper GUI zip file, as well as the UL-ASUS Firmware zip file
Run the Payload Dumper GUI program in the unzipped folder. A file explorer window will pop up; open the unzipped UL-ASUS Firmware folder and select the payload.bin file. Another file explorer window will pop up; select the UL-ASUS Firmware folder if not already selected, then click select folder in the bottom right.
Click Dump on the Payload Dumper GUI Application. The files will be output to the UL-ASUS Firmware folder.
[Part Three]
Download Magisk and install onto phone via APK. https://magiskmanager.com/downloading-magisk-manager/
Plug phone into computer and allow file transfer.
Within the UL-ASUS Firmware folder there will be a boot.img file. Move this file onto the phone.
Open the Magisk application and follow image below, select the boot.img to patch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A file will be output with magisk. Move this file back onto the PC, and rename to boot.img
[Part Four]
Unlock Zenfone 9 Bootloader. Asus provides a bootloader unlock tool on their website. Below is the link directly to the apk. https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Install the drivers listed below for the phones recovery mode https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Asus Driver Xanker commented. Thank you again)
[Part Five]
Download Minimal ADB and extract files https://androidfilehost.com/?fid=962187416754459552
Move Boot.img file into Minimal ADB extracted folder.
Put Zenfone into recovery mode and connect to PC. Recovery mode can be achieved by turning off the phone and then powering on whilst holding the volume up button. Release when the ASUS logo pops on screen.
Run cmd-here.exe in the Minimal ADB folder; a command window will open
As a test run the command listed below and it should output a device fastboot devices
If that test succeeded run the final command to flash, fastboot flash boot boot.img
The command prompt command didn't run. Said it was not recognized. Is there a specific place the .exe need to be in the directory?
NVM...got it.
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
bighit101 said:
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
Click to expand...
Click to collapse
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
The image version that I just downloaded seems to be at a higher version (WW-32.2030.2030.26 as opposed to WW-32.2004.2004.84 on my phone) and the phone doesn't have that version available (I haven't unlocked the bootloader yet). Should I update locally or download the earlier version of the image instead?
If your phone has the 2004 version installed extract the boot.img from the downloaded 2004 Payload.bin. Or you can update your phone and use the 2030 boot.img.
For me it works with the 2030 version. Root installed, everything ok (AdAway, Postbank (BankingApp)).
If you want to pass SafetyNet just install the magisk module from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1 and reboot.
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Hermann2306 said:
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Click to expand...
Click to collapse
Doesn't work, the guide asks for denying google system apps which doesn't work because they are always off deny list (this is intended behaviour)
For the record, every other payment apps I am using, even the ones that check for safetynet are working. YASNAC returns a both pass basic.
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Hermann2306 said:
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Click to expand...
Click to collapse
Wallet is configurable, it's just that when you save your card details and it starts contacting the bank it would jump to an error saying that the system is modified.
Maybe try this? (I think you have already read/tried it)
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Does someone rooted a 16GB ram Zenfone 9? My software is 32.2004.2004.74.
Can not find this software at Asus website.
I have rooted the 16gb version (32.2030.2030.26).
Why dont make an update before root?
xanker said:
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
Click to expand...
Click to collapse
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
williamcll said:
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
Click to expand...
Click to collapse
Try this: https://github.com/kdrag0n/safetynet-fix
Veiranx said:
Try this: https://github.com/kdrag0n/safetynet-fix
Click to expand...
Click to collapse
Safetynet fix is running, it's just that it's not enough, still going through the prop fix.
bighit101 said:
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
Click to expand...
Click to collapse
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
xanker said:
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
Click to expand...
Click to collapse
Yeah coffee is life!
You're too nice. Will donate in you're name.
Thanks man!!!