Can't root my device - Vivo V20 SE Questions & Answers

Anyone help how can I root my device?
I am running on andriod 11 with latest security patch. Adb and fastboot working fine while device is turned on when I give command to adb reboot bootloader then phone come in fastboot then device not showing in adb devices list when I turned on phone its showing there but not in fastboot menu. Kindly help.

Because u rebooted into fastboot mode now u are on fastboot. Try running the command: fastboot devices

XakedowX said:
Because u rebooted into fastboot mode now u are on fastboot. Try running the command: fastboot devices
Click to expand...
Click to collapse
Tried but not working. When phone is running adb worked when phone is in fastboot adb is not working (list of available devices) blank.

gmkhamisani786 said:
Tried but not working. When phone is running adb worked when phone is in fastboot adb is not working (list of available devices) blank.
Click to expand...
Click to collapse
because as i said u are not in adb when u are in fastboot adb devices will NOT RETURN and results. it will be blank. You should try the command: fastboot devices
it will show up there.

Brother I can't unlock bootloader that's why I am having issues. Can you please help to unlock bootloader?

Related

Cant use fastboot or mfastboot

Im trying to flash back to stock rom but the device is not responding, i already have try on mfastboot and on fastboot but it just say "waiting for device" when i try some comand, i have motorola drivers, i've tryed a program called PDAnet too, i have usb debug on, can someone help-me?
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
zitronenmelissa said:
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
Click to expand...
Click to collapse
i have tryed all, but no response, i give it up and install other custom rom but thanks for trying help

"waiting for devices" in ADB While trying to install TWRP?

Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
arachniac1 said:
Updated today to OB14. Now trying to re-flash twrp. Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Just kill adb.exe with Taskmanager... And try again..
arachniac1 said:
Type "adb devices" and it showes connected to my OP3T. Go to flash the twrp file and says "waiting on devices"??? Why won't it flash? (using cmd fastboot flash recovery <file. Img> Yes, I'm in fastboot mode. Do I need to reinstall abd drivers?
Click to expand...
Click to collapse
Something is not quite right. adb and fastboot have different requirements, and will never work at the same time.
adb = works in OS or TWRP, will not work in fastboot mode. Debugging must also be enabled
fastboot = only works in fastboot mode. Debugging enabled not needed.
So adb working, and fastboot not working is expected, but to me, means you are not in fastboot mode. Or your are changing modes/states between commands (which is really confusing).
Go into fastboot mode and type: fastboot devices
And see if it returns the phone ID.

adb works but not fastboot

I rooted my Note 8 and when I'm in the TWRP bootloader, I can issue adb commands, but no fastboot command (list of devices empty). How can I get the phone into a state where fastboot works?
TauTau said:
I rooted my Note 8 and when I'm in the TWRP bootloader, I can issue adb commands, but no fastboot command (list of devices empty). How can I get the phone into a state where fastboot works?
Click to expand...
Click to collapse
Samsung doesn't use fastboot!
They lock it out in favor of their Odin flash tool.
so there's no way to use fastboot commands? There goes my hope on making it boot on power connect

ADB fastboot

Has anyone tried using adb fastboot on Samsung Galaxy Note 8 recently.
I have tried unsuccessfully to get the fastboot work using Windows and Macbook with the latest Samsung Samsung drivers for fastboot. Even installed the fastboot drivers from Android Development platform but still no luck beyond <waiting for device>.
I read on another forum that Samsung no longer allows fastboot to work with their devices. Is it correct?
Fastboot as I understand it is an extension of Android recovery.
If you have USB Debugging enabled on your device, you should be able to issue commands: adb reboot fastboot
Fastboot commands also work in bootloader.
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Prof_Shekhar said:
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Click to expand...
Click to collapse
The appropriate command to flash /boot would be:
Code:
fastboot flash boot <boot image>

Question [Resolved] No connection with pc in fastboot mode.

Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!

Categories

Resources