HI to all
I got my phone back from service, latest version installed (DN2103_11_A.14 EU).
I will flash TWRP and root, so do I need A.14 vbmeta or can I just use vbmeta from same post I will download TWRP?
If I need A.14 vbmeta, does anyone have it?
Thanks
There is no difference, the same one can be used for all versions.
you can use the vbmeta from TWRP Thread.
Zombnombs said:
There is no difference, the same one can be used for all versions.
Click to expand...
Click to collapse
HI and thank you.
HofaTheRipper said:
you can use the vbmeta from TWRP Thread.
Click to expand...
Click to collapse
HI and thank you.
How do you enter fastboot mode? There is no option from power button, and when I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit.
In recovery there is no "Advanced" option to reboot to fastboot.
krugm0f0 said:
I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit
Click to expand...
Click to collapse
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Zombnombs said:
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Click to expand...
Click to collapse
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
krugm0f0 said:
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
Click to expand...
Click to collapse
Seems like you just don't have the right drivers installed. Sure it looks different but that doesn't mean it has to work differently.
Windows can get the drivers automatically for you, connect in fastboot mode, then check for updates in windows, then they should either get installed or show up in optional updates as Mediatek ADB something.
Related
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Tintom1 said:
Hi!
I recently got my new Acer Tablet A3-A30. After unlocking developer options and activating debugging I was able to use adb. So I rebooted into bootloader to see if fastboot works - it did not! The output of fastboot devices was empty (this and the following commands were typed as root).
So I killed adb with adb kill-server, disconnected it from my computer and turned it off. After a few moments I turned it on by pressing power while holding Vol[-]-Key. Again the tablet booted into fastboot mode. Now I connected it with my computer and hoped fastboot will recognize the device now. Again, the output was empty.
I noticed, that after connecting the tablet, the text fastboot mode on the display didn't change - all other devices I put into fastboot mode showed fastboot usb mode or similar after I connected them with my computer.
I tried different USB ports - nothing changed.
I'm just wondering, since I'm not familiar with acer devices: Is there a hidden key sequence to get into fastboot usb mode?
Thanks,
Tintom1
Click to expand...
Click to collapse
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
RAZERZDAHACKER said:
I have an a1-830 and it can be a real pain in the ass to get anything working on them. Try this, since you got adb working, adb reboot bootloader, then wait till it says fastboot cmd waiting or something. If that din't work, reply!
Click to expand...
Click to collapse
It worked, I got the fastboot mode with fastboot cmd waiting message!
Tintom1 said:
It worked, I got the fastboot mode with fastboot cmd waiting message!
Click to expand...
Click to collapse
Ayyy, hit thanks if I helped
RAZERZDAHACKER said:
Ayyy, hit thanks if I helped
Click to expand...
Click to collapse
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Tintom1 said:
But this is what I already got. It says fastboot mode (now with the waiting message), but not fastboot usb, so fastboot still doesn't see the device
Click to expand...
Click to collapse
And fastboot devices shows...?
RAZERZDAHACKER said:
And fastboot devices shows...?
Click to expand...
Click to collapse
Nothing:
# fastboot devices
#
Tintom1 said:
Nothing:
# fastboot devices
#
Click to expand...
Click to collapse
If you are using Linux, try running fastboot with the sudo command. Also, the drivers might not be properly installed, check out this to download them.
I am trying to root my OPPO A72. After successfully configuring the adb and USB Debugging I was trying to fastboot it using 'adb reboot bootloader', because 'adb reboot fastboot' reboots it to recovery, which I do not want. After rebooting the phone using 'adb reboot bootloader' for half a second there is chinese text with the text 'FASTBOOT', then it just reboots the phone into android. The OEM Unlocking option does not help. Any ideas why that is / how to fix?
randomizedhex said:
I am trying to root my OPPO A72. After successfully configuring the adb and USB Debugging I was trying to fastboot it using 'adb reboot bootloader', because 'adb reboot fastboot' reboots it to recovery, which I do not want. After rebooting the phone using 'adb reboot bootloader' for half a second there is chinese text with the text 'FASTBOOT', then it just reboots the phone into android. The OEM Unlocking option does not help. Any ideas why that is / how to fix?
Click to expand...
Click to collapse
The A72 cannot be rooted at the moment.
with phone on if you enter adb reboot fastboot , it takes you too a screen similar to the recovery screen but you can access phone by fastboot devices etc ... BUT it's a very limited fastboot and hardly any use at all , and will not allow you to unlock bootloader.
linccracker said:
The A72 cannot be rooted at the moment.
with phone on if you enter adb reboot fastboot , it takes you too a screen similar to the recovery screen but you can access phone by fastboot devices etc ... BUT it's a very limited fastboot and hardly any use at all , and will not allow you to unlock bootloader.
Click to expand...
Click to collapse
I can't even get into this limited fastboot. Any idea why?
Bobgle said:
I can't even get into this limited fastboot. Any idea why?
Click to expand...
Click to collapse
Have you tried adb reboot fastboot
linccracker said:
Have you tried adb reboot fastboot
Click to expand...
Click to collapse
What happens when you type this command
linccracker said:
What happens when you type this command
Click to expand...
Click to collapse
It reboots immediately. No device detected by fastboot or adb during that.
Bobgle said:
It reboots immediately. No device detected by fastboot or adb during that.
Click to expand...
Click to collapse
What firmware version is it running
linccracker said:
What firmware version is it running
Click to expand...
Click to collapse
v1.2, but I just managed to get into fastbootd mode. It seems like there are no commands available though, just as you said. Is EDL worth anything? What would be the steps to flashing this phone if there is no support by OPPO?
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.
Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
Don't own this device but try: "adb reboot bootloader" instead and test fastboot commands from there (don't navigate to Fasboot from bootloader).
krugm0f0 said:
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Click to expand...
Click to collapse
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Zombnombs said:
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Click to expand...
Click to collapse
I am unable to send fastboot commands. Is not recognized by "fastboot devices". And this fastboot mode looks nothing like my previous phones. 2, X, 5T and Nord 5G. <waiting for device>
I want to do my "usual routine" with my new phones. Unlock, flash twrp or other recovery, and flash magisk for root.
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
nothing. only recovery mode
vol down+ power =recovery mode
vol up + power = normal boot
I finaly boot into fastboot mode with adb command only (adb reboot bootloader)
With buttons wont work.
But i can't enable Volte/Vowifi (thats why i wanted to boot there).
Can you send adb commands when in recovery mode ?
I'm trying to enable VoLTE too, but adb only detect phone when powered normaly, not when in recovery mode.
i don't know about adb but in fastboot you can.
I can't enable volte/vowifi in fastboot with this commands.
https://androplus.org/wp/wp-content/uploads/2021/08/onr12.jpg
Fastboot commands start with fastboot, those are adb commands.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
i am having the same issue can any one help
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
pls contact me in 9650930525 in this number and help me how u did it
drkanurag said:
i am having the same issue can any one help
Click to expand...
Click to collapse
pankspoo said:
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
Click to expand...
Click to collapse
roldev said:
Downgrade to latest A11. Unlock via fastboot. Do what you want, then. All explained here or/and telegram group. Sorry, don't have time to do step by step guide now. Cheers.
Click to expand...
Click to collapse
Follow this guide to downgrade to A11 https://community.oneplus.com/thread/1596759
Then you should be able to access fastboot.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
Could you go into more detail on what you did in the entire process exactly? Did you use the drivers and adb install from the 15 sec installer? Did you simply uninstall them in the Windows Device Manager and click on "update drivers" to find the local drivers from the 15 sec installer? Which ones did you choose? Sorry, these might be dumb questions, but I'm admittedly very stupid when it comes to Windows and drivers in particular.
I did the exact thing I described above but I'm still just getting that message. Additionally, "fastboot devices" won't list anything and "fastboot oem unlock" will wait for the device for eternaty. "adb devices" on the other hand will list my device while not in Fastboot.