Database Develop

Root the Nexus with ROM Links *Updated*

Root the Nexus with ROM Links *Updated*
-------Notes--------
1. This does void your warranty.
2. The root image auto installs the superusers permission app
3. I am in no way responsible for anything that goes wrong.
4. Once you unlock the bootloader it does a factory reset on your phone.
5. I don't mind people posting this tutorial on their sites for others to see and use but I do ask that I'm at least given credit for my work.
1. Download fastboot and adb files:
Here
2. Extract tools.zip to a folder and Open a command window in that folder by holding down your shift key and right clicking anywhere in the window and select open command prompt here
3. Then with your phone turned off hold the power and trackball to access the bootloader.
3b. Type this command to make sure your phone is connected and reconized. "fastboot.exe devices"
4. Once in the bootloader type this command in your command prompt "fastboot.exe oem unlock"
6. Follow what that sceen says.
7. Flash Amons RA Recovery Image from here
---------------Now to root your phone.---------------
1. Once you've flashed the recovery image turn your phone off.
2. Then power on by holding power button and trackball then tap the power button to access the bootloader.
3. From there use your volume keys to go down to recovery and hit power button again to access the recovery console.
4. Enjoy rooted phone
---------------Now to Flash a Radio and a Rom---------------
1-Download Radio(s):
Preferred:
RADIO UPDATE - 4.03.00.21_2 (from ERE27 update)
Original Radio image 4.02.02.14 (from ERD79) in an update.zip
2. Download a Rom:
A-[ROM] Enomther's TheOfficial Nexus1
B-[ROM] CyanogenMod
C-[ROM]MoDaCo Custom ROM with Desire/Sense
D-MoDaCo Enhanced ROM
2. put both the radio and update zips on your sdcard
3. power down your phone
4. Using the volume down key and power button to get to bootloader/recovery option screen
4a Use volume key to scroll and power button to pick
5. Go to flash zip from sdcard
6. Flash radio update zip first
7. After that is complete and you've restarted when it told you to do so.
7a. In recovery..direct to wipe menu and wipe phone.
8. Flash Rom zip
9. To get root again simply reflash the nexus-addon-0.1-signed.zip (instructions above.

Followings are instructions for OSX or any *nix platform.
Android SDK is nice to have but not needed.
You can download the Android SDK here.
I take no responsibility for what you do to your phone or your computer.
Step 1. Download the file from above post and unzip the file to your desktop.
Step 2. Open Terminal.
Step 3. Go to the folder that you zipped.
command:
cd ~ <enter>
cd Desktop/ <enter>
cd 1.1-nexusone-superboot/ <enter>
step 3. Load into fastboot on your phone.
<option 1> first power off, then power on while holding down the trackball.
or
<option 2>You can also hold down volume down while powering on and then select fastboot and press power.
step 4. Make sure fastboot can connect to your device.
command:
./fastboot-mac devices <enter>
if you can see the serial number of the phone with fastboot next to it, you are good. If not, repeat step 3.
step 5. Enter the following in your terminal screen
./fastboot-mac oem unlock (if you are on a mac)
./fastboot-linux oem unlock (if you are on a linux based machine)
step 6. If you do not want to void warranty or if you have not save your settings and contact etc, do not press yes. Save those first.
Follow instructions on screen. (use the volume up/down to switch and power to select).
Phone will reboot with unlock icon on the bottom of the X logo. Kiss your original setup goodby.
step 7. Enter the follow command:
./fastboot-mac flash boot nexusone.superboot.1.1.img <for mac>
./fastboot-linux flash boot nexusone.superboot.1.1.img <for linux>
step 8. Reboot phone by pressing volume down and pressing power. You are done!

i vote for a sticky!

i want to root so bad but i just cant bring myself to void the warranty on this 530$ device

melterx12 said:
i want to root so bad but i just cant bring myself to void the warranty on this 530$ device
Click to expand...
Click to collapse
577+change but who's counting right But I agree I don't know if I want to void the warranty just yet

aad4321 said:
CONFIRMED WORKING. Thank you. NOTE: THIS WILL RESET the DEVICE!!!
Click to expand...
Click to collapse
Can you LOCK the bootloader after unlocking it using the same steps? That would be a first step in restoring to normal if warrenty work is required.

What is this underclocked 2?

If nobody else gives it a try by the time mine arrives tomorrow, I will root my device and then see if I can't reverse it for the sake of warranty preservation.
Glad we are already at this step on Day 2

I did this and I can't see protected apps on the market anymore.. anyone else experience this issue?
A way to check is to try to find Twidroid on the market or really any paid app

djunio said:
What is this underclocked 2?
Click to expand...
Click to collapse
its not underclocked. its 1ghz.

im too scared to do it eventhough i knows its easy and no big deal

i think i'll wait until there is a reason to root the phone other then saying its rooted when there's a feature or ROM i can add that's useful like multi touch then ill root my phone.dont get me wrong i got this phone to root it but theres no point rite now

I'm getting mine in the mail tomorrow . I'm not going to root it right away though.. just in case something goes wrong ):

melterx12 said:
its not underclocked. its 1ghz.
Click to expand...
Click to collapse
did u root n check it?

aad4321 said:
I can see them still, and mine is rooted.
Also, I try to open the superuser permissions app and it freezes every time..This is also both with and without debugging enabled. Anyone else have this problem>?
Click to expand...
Click to collapse
Same issue here.

well maybe it is underclocked but I doubt it. Google advertises the phone at 1Ghz.

my permisson app doesnt freeze for me but what you can do is remove it and use something like astro to go to your phones root dir theres a folder in there called superroot with the apk for it so you can reinstall it.

Is there a unroot tutotial as well?

Paid Market Apps
I had a feeling, and it seems to have been confirmed, that rooting will not allow me to download paid apps. I know that this was an issue when the G1 was first rooted and it was "fixed." Can someone confirm this issue? This is a big one for me.

AndroidAppCritic said:
I had a feeling, and it seems to have been confirmed, that rooting will not allow me to download paid apps. I know that this was an issue when the G1 was first rooted and it was "fixed." Can someone confirm this issue? This is a big one for me.
Click to expand...
Click to collapse
I can still see paid apps.
Also, reinstalling the superuser apk fixed the blank screen issue.

Clockwork from Ubuntu

Install Andrioid sdk
(I renamed the Android folder sdk to simplify things)
Install ADB
(see Karolis post... thanks)
Now I have make some corrections to the standard install and this has worked flawlessly for me.
1. Unzip "Root.zip". Place "ota.zip" & "update.zip" into Android SDK.
(You wont need loop)
2. I started with the 2gig sd provided, formatted it in windows and copied attn1's ROM to it (leave it zipped).
3. Then I downloaded Clockwork_Aria_MT3GS.zip and placed that and a copy of the above ROM in the android sdk/tools folder.
4. Open terminal in Ubuntu and type cd /sdk/tools and hit enter
5. Heres where the differences start. Plug the phone in to you pc powered on WITHOUT the sd card in it. When the phone asks select charge only.
6. In the terminal type sudo ./adb devices and hit enter
(your device should show up)
7. In terminal type sudo ./adb reboot bootloader and hit enter
8. Now the phone should have rebooted showing the white screen. Select BOOTLOADER and hit the power button on the phone. Wait for the text to change to "HBOOT USB Plug. This is the tricky part use volume down on the phone to select "Recovery" but DONT hit the power button until you are ready to push the sd card in after you hit the power button.
9. You should come to the red triangle screen now. In terminal type sudo ./adb devices again and your devise should show up. If not eject the sd card switch to the terminal and type sudo ./adb reboot bootloader again.
10. If your device showed up Hit Volume up and the power button on your phone.
11. Now use volume down to select Apply sdcard:update.zip and push the power button to execute. Let that run trough, finish and go back to the screen you started at.
12. In terminal type adb push ota.zip /sdcard/update.zip and hit enter.
13. in terminal type adb push update.zip /sdcard/update.zip but do NOT press enter yet.In recovery, again scroll down with power down to select sdcard:update.zip but do not execute yet.Press the power button and then watch phone to say "verifying" and then press enter IMMEDIATELY on the keyboard. If timed right, Clockwork recovery should load. If not, start back at step push ota.zip /sdcard/update.zip and repeat from there until clockwork loads.
14. From Clockwork Recovery, do a Nandroid backup. From Clockwork Recovery, select install zip from sdcard, and execute, then choose zip from sdcard and execute, and then you can scroll down to your pre-rooted rom of choice and execute that to flash it. In Clockwork you can scroll with trackpad or volume buttons, and you can execute with either the power button or a trackpad button push.
Thanks to attn1. I stole alot of what you typed, your ROM and for getting this working in the first place.

Let me know if I screwed anything up. Its been a long day : )

I think that your method works well, but I find that of attn and eugene is easier to manage, since plugin a usb cable is easier than popin a sd card.
Anyway, great summary. But you don't really need step 1 if you are using attn's ROMs.
sd73ta said:
Let me know if I screwed anything up. Its been a long day : )
Click to expand...
Click to collapse

I'll edit the first part out when I get home. This worked for me because I couldn't get it to find my device the other way and this way found the device first try each time i did it. Thanks for the input

plutino99 said:
I think that your method works well, but I find that of attn and eugene is easier to manage, since plugin a usb cable is easier than popin a sd card.
Anyway, great summary. But you don't really need step 1 if you are using attn's ROMs.
Click to expand...
Click to collapse
if you dont mind Im still kinda new to this which step should I take out?

After hours of failing to get things to work on my Win7 machine, this saved the day. Thanks!

I was unable to success with the SD card method, so I cannot really comment on which steps are unnecessary. But now the almighty unrevoked has automated the whole process and we don't need to chase the bear any longer.
sd73ta said:
if you dont mind Im still kinda new to this which step should I take out?
Click to expand...
Click to collapse

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705

danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)

hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.

danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.

hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)

I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!

danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

[SOLVED] Can't enter safe mode

The phone doesn't start after installing EdXposed and the Riru Core Magisk module.
I want to enter Safe mode, but it doesn't work. I somehow managed to enter safe mode previously out of pure coincidence (no idea what I did, I pressed some buttons and i got there during a boot sequence, but it was nothing like the tutorial that Google gives you on how to do it properly).
So, I read you can do it like this:
https://support.google.com/pixelphone/answer/2852139?hl=en
However, this doesn't work for me, here's my boot process:
Power on
Unlocked bootloader warning (I skip it)
Google logo shows up
Screen color calibration changes slightly
Google animation starts (i press volume down)
Google animation ends
Normal Google logo stays there for a few seconds
Loading bar appears
Loading bar stayed there overnight (phone doesn't get hot or anything)
Is there any way to:
Enter safe mode properly
Start a terminal in recovery mode (like TWRP) to use the mm module to disable Magisk
Have an on device file manager (like TWRP) to manually delete the app
Delete files using adb
Get a normal adb shell (not sideload)
EDIT 1:
Starting "rescue mode" via fastboot shows the bootloader warning again, then the Google logo and then it's stuck (no color shift, no animation). Same for "recovery mode".
I cannot connect via adb/fastboot while the Logo is showing.
EDIT 2:
I managed to start "rescue mode" by doing the following:
Press power button
Press power button again (Entry selected: "Start")
Press both volume buttons and don't release them (I'm getting desperate here lol)
Bootloader warning (not skipped)
Rescue mode shows up (opened up Android, says "No command")
I can connect via adb, but "adb shell" or any other useful command says "error: closed"
EDIT 3:
Wtf, I got an adb shell by doing the following inside rescue mode:
"adb shell" -> Error
"adb pull /system/" -> Error
"adb pull /etc/hosts" -> Error
Phone restarted
Bootloader warning (skipped it)
Google logo, Animation & loading bar
adb connected
EDIT 4:
I entered the adb shell and used "setprop persist.sys.safemode 1" (source) (which registered correctly), but after rebooting, the phone still loads forever.
EDIT 5:
Turns out Safe mode didn't work because of Magisk/Riru/EdExposed or whatever, so I disabled Magisk by "touch /cache/.disable_magisk" (source) and now I successfully booted into safe mode.

Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!

cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Using this will most likely get you booted up to fix what you need...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557

cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Where are you stuck?

Revisiting key combinations, and getting to fastbootD

[Sorry, this belongs in the Q & A area, but there's no option to delete or move it.]
Here are the hardware button combinations that work on my OnePlus 6T:
[volume up + power] hold until you see the red dot logo, then release theyour phone will boot to system.
[volume down + power] hold for a few seconds until the black and white keyboard appears (maybe the keyboard is only if you have a login PIN set up?) this will boot the phone to recovery mode.
[volume up + volume down + power] hold for a few seconds until you see the Fastboot label then release. This will put the in bootloader mode.
Starting with the phone powered off and NOT connected to your computer, press and hold [volume up + volume down] as you plug the phone into your computer. This will put the phone into EDL mode, which is required in order to use the MSM tool. The screen of the phone will be black but if you followed the procedure the Qualcomm device should appear under the Ports section of Windows Device Manager.
I was unable to get to FastbootD. Here's what happened when I tried various commands:
1.) when in regular fastboot (bootloader) mode and connected to my PC via USB, from a command prompt I typed "fastboot reboot fastboot" the phone only rebooted to the operating system and not to the fastbootD screen.
2.) when in bootloader, as above, I typed "fastboot reboot bootloader", the phone rebooted to the regular fastboot screen. However, I suspected this was not the same thing as "fastboot reboot fastboot" because why would there be 2 identical commands?
3.) the "adb reboot" command would not work when I was in bootloader mode. Duh! I needed to be in ADB mode for ADB commands to work. In bootloader mode I needed to use a Fastboot command. Still, I had downloaded and unzipped the latest adb/fastboot tools and set up the Windows PATH to point to the unzipped folder. Also, I checked the version numbers of both from the command prompt but still [fastboot reboot fastboot] only rebooted my phone to system. What the heck!?
4.) this all seemed to happen after booting into EDL mode the day before. I booted into EDL mode so I could check if I had the proper Qualcomm driver installed (incase I had to use the MSM tool --yes the driver was installed and functioning). I didn't actually need to use the MSM tool at that time so I didn't ever run it but I'd had some difficulty getting the phone to reboot to system so I assumed my trouble with fastbootD originated with that. Wrong!
SOLUTION: It turned out to be a hidden instance of outdated adb/fastboot that kept running in lieu of the newly downloaded copies, in spite of my having correctly set up the Windows PATH. (more on this below in my reply of Jan 9, 2022).

So adb reboot recovery
And
adb reboot bootloader
Dosent work?

Kenora_I said:
So adb reboot recovery
And
adb reboot bootloader
Dosent work?
Click to expand...
Click to collapse
adb reboot recovery does work. Weirdly, adb reboot bootloader will work ONCE then if I try to issue the command a second time, adb can't see my device. If I unplug the phone from USB, restart the phone then plug it back in, I can again use adb once.

Fastboot logo is showing?

Kenora_I said:
Fastboot logo is showing?
Click to expand...
Click to collapse
what would a fastboot logo look like?

The words fastboot. Will be shown

Kenora_I said:
The words fastboot. Will be shown
Click to expand...
Click to collapse
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.

Can you check if System>Developer Options>Advanced Reboot is enabled?

FakeGemstone said:
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.
Click to expand...
Click to collapse
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.

psychen6 said:
Can you check if System>Developer Options>Advanced Reboot is enabled?
Click to expand...
Click to collapse
Yes, I have this option enabled. Using this method is one of the ways I am able to get to fastboot. I am just not able to get to fastboot using [fastboot reboot fastboot] from a command prompt (used to work just fine) and I am not able to get to fastboot by holding the [volume up + power] (this also used to work just fine).

hartleyshc said:
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.
Click to expand...
Click to collapse
I don't know about that. A few days ago volume up + power used to work just fine. Also a few days ago, I also used to be able to issue fastboot reboot fastboot from a command line and have it work fine.
Now what happens when issue the command fastboot reboot fastboot is that my phone appears to begin the reboot cycle. A message in the command window appears, "rebooting into fastboot" then on the next line, "< waiting for any device >" and meanwhile my phone just boots into the Oxygen OS. If at that point I select "bootloader" from the advanced power button menu, the phone reboots into fastboot and the message in the command window reads, "fastboot: error: failed to boot into userspace fastboot; one or more components might be unbootable."
If I then issue the command, fastboot reboot bootloader, that reboots promptly into fastboot, but I don't believe "bootloader fastboot" is the same thing as "userspace fastboot", although the states look identical on the screen.

After revisiting this issue again and reading every post I could find I realized the only explanation was outdated fastboot, and since they're packaged together, adb also. This time I did a extra thorough search of all the drives and sure enough there was a super old instance of adb.exe & fastboot.exe in a place I'd never thought to look. So I deleted those files and now adb and fastboot work as expected.
I know, it seems obvious now. But there were references to those old files in windows system settings that took precedence over my PATH setting that I didn't realize were there. Ive since deleted those other references but I wanted to mention this in case other people are wondering why the PATH they set up isn't working.