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?
Related
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
EDIT:
here's the solution https://forum.xda-developers.com/android/general/tutorial-root-acer-liquid-zest-4g-z628-t3534746
flamendless said:
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
Click to expand...
Click to collapse
Can you give me any information about your phone? model,kernel,android version,etc.
Ziisehahvulon said:
Can you give me any information about your phone? model,kernel,android version,etc.
Click to expand...
Click to collapse
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
flamendless said:
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
Click to expand...
Click to collapse
Do you have any any custom recoveries for your phone so we can flash a supersu.zip?
If not could you boot this recoveries I repeat boot not flash or install.
How to Boot into recovery without flashing:https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Custom Recovery:https://www.androidfilehost.com/?fid=24591023225178597
The custom recovery may not be for your phone but I have tried booting random recoveries to my phone similar to its specs and it worked!
SuperSU download in attachment
Is it possible to brick my device by that procedure?
flamendless said:
Is it possible to brick my device by that procedure?
Click to expand...
Click to collapse
Not the device but maybe the recovery but since you are booting it and not flashing it maybe it won't.I did this procedure to my phone but the 3g T06 model of acer liquid zest and it worked. Well I changed some links so that the recovery would be compatible for your chipset which is mt6735 and kernel 3.18.19+
PS.you need unlocked bootloader and developer options on for oem unlocking
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
flamendless said:
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
Click to expand...
Click to collapse
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Ziisehahvulon said:
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Click to expand...
Click to collapse
How to know if the bootloader is unlocked?
flamendless said:
How to know if the bootloader is unlocked?
Click to expand...
Click to collapse
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
Im in fastboot mode, but the device is not listed in adb
flamendless said:
Im in fastboot mode, but the device is not listed in adb
Click to expand...
Click to collapse
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
It just says waiting for device
flamendless said:
It just says waiting for device
Click to expand...
Click to collapse
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Ziisehahvulon said:
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Click to expand...
Click to collapse
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
flamendless said:
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
Click to expand...
Click to collapse
Try the version of adb and fastboot that I used
Ziisehahvulon said:
Try the version of adb and fastboot that I used
Click to expand...
Click to collapse
still says waiting for device,
flamendless said:
still says waiting for device,
Click to expand...
Click to collapse
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Ziisehahvulon said:
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Click to expand...
Click to collapse
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
flamendless said:
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
Click to expand...
Click to collapse
I'll give you proper details later I need to go to school
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
vinny13 said:
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
Click to expand...
Click to collapse
How about this? adb shell reboot fastboot
If that doesn't work, then try this. https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
What does the code below do?
Code:
adb shell
reboot bootloader
You can always use manual mode, as it's explained in Anox link.
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
vinny13 said:
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
Click to expand...
Click to collapse
Fastboot mode should always be accessible.
That tool & others basically use the same command to access fastboot mode.
The manual method is supposed to be the last resort. I now have no idea, sorry.
Have you found a solution yet? I have exactly the same problem.
Gavros7 said:
Have you found a solution yet? I have exactly the same problem.
Click to expand...
Click to collapse
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
lfom said:
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
Click to expand...
Click to collapse
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
alexsouza said:
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
Click to expand...
Click to collapse
Using the button trick is the only way you have to enter into fastboot.
Saratoga79 said:
Using the button trick is the only way you have to enter into fastboot.
Click to expand...
Click to collapse
Thanks for your response, @Saratoga79. Has anyone seen any cases that the watch does not enter Fastboot or the button? I say this because the operating system of the clock was always crashing ... Now the only screens that appear to me are "A" and "No Command".
I will keep trying the button method. I confess it has been over 90 times.
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.
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.
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.