Need Help with Unlocking Bootloader for OPPO AX5 - General Questions and Answers

Hello guys hopefully old faithful XDA can save me again but i have a oppo ax5 i currently am trying to downgrade but im having no luck with the thing.
Im mainly trying to root the phone as i really like the phone and it would be such a shame.
a big issue is i cannot get into fastboot with this phone, i remember a while ago i was able to get into fastboot with another phone but it took a lot of work and QFIL.
i have extracted the firehose file for the OPPO AX5 as well along with a few other firmware files so if that helps at all.
Thank you

Oppo has removed fastboot ability from all their phones since 2016:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com
You can still unlock the bootloader by following this tutorial which uses MTKclient:
(Note: When connecting the phone, try holding all volume buttons + power button, this combination worked for my Oppo Ax5s)

Related

[Completed] [Q] Cubot P9 bricked after firmware update - next step help needed

Our Cubot P9 has apparently bricked after a manufacturer firmware upgrade.
The firmware was downloaded from the official website, copied to a uSD card and then installed from via the Android System Recovery menu (accessed after cold boot by pressing volume-up & power buttons together).
Having followed Cubots instructions to the letter, we can only think that they have provided a link to the wrong image, despite it ostensibly being the correct one.
Current symptons are: phone still powers but not off again (requires battery removal). There is no ability to enter the fastboot or firmware recovery menus. The display lights-up but with a random/incoherent output.
All the threads, thus far, have included putting the device into fastboot or firmware recovery mode - which is not an option for us.
We'd like to know if this a recoverable situation? If so, what's the next step?
Hi,
If you can't enter recovery or fastboot mode, you won't be able to do much I'm afraid....but I suggest you ask in this discussion thread about your device....
http://forum.xda-developers.com/showthread.php?t=2612234
Good luck!
KJ said:
Hi,
If you can't enter recovery or fastboot mode, you won't be able to do much I'm afraid....but I suggest you ask in this discussion thread about your device....
http://forum.xda-developers.com/showthread.php?t=2612234
Good luck!
Click to expand...
Click to collapse
Thanks for the reply.
To put the question another way: in general, when the firmware in an Android
device goes awry, is there any way to recover the device using tools available on the user?
The way we see it is thus:-
In our case it's a Cubot P9 phone but it could just as easily be any other, or even a tablet.
Presumably during development and factory manufacture, there is a means to either load firmware in the first instance or reload it when desired. Short of hardware failure, we're sure that the original device developers have done exactly what we have done a dozen times on the bench.
Given the whole nature of the 'eco-system' is much less proprietary than it used to be (remember Nokia S40 anyone?) perhaps devices like ours are entirely lost to scrap heap?
Considering our device though: it still boots with the brand logo displayed, after which, while the display is completely distorted, the wallpaper and menus are visible. Even the volume & power buttons evoke a response. Atop this are its recognition as removable storage under Windows. Surely this indicates some potential for recovery?
Thanks again.
Perhaps, but if you can't flash anything to the device, you can't do anything. Please ask the folks in the thread I linked....or consult a service centre. ?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
If the thread I linked doesn't appeal to you, you can ask here....
>Android Development and Hacking >Android Q&A, Help & Troubleshooting
Thread closed. Thank you.

[Completed] android graft...

Hello,
I think I have semi hard bricked my phone, and have been surfing since then, to find a solution :
I un rooted via kingoroot in order to change the glass that was on warranty.
I decided then to execute ART instead of dalvik, and the phone won't boot till then.
It charges, the boot sequence stops at the logo.
I'm unable to use the recovery or download modes.
The phone is not recognised on windows .
--> using a FEL Mode, I guess, the device is recognised as an external SD ith 22 partitions.
I don't have the images of my phone (CAT s50), but the specs are similar to the LG G3 Vigor :
CPU/GPU etc...
I know that it is written everywhere that you can't intall a rom not suitable for your phone, because I think it leads to a bricked device.
The fact is I don't know the level of inutility of my ex-phone.
Did someone ever grafted a ROM from another brand?
Has someone an information to recover my old and functionnal cat s50 from the FEL mode?
XDA Visitor said:
Hello,
I think I have semi hard bricked my phone, and have been surfing since then, to find a solution :
I un rooted via kingoroot in order to change the glass that was on warranty.
I decided then to execute ART instead of dalvik, and the phone won't boot till then.
It charges, the boot sequence stops at the logo.
I'm unable to use the recovery or download modes.
The phone is not recognised on windows .
--> using a FEL Mode, I guess, the device is recognised as an external SD ith 22 partitions.
I don't have the images of my phone (CAT s50), but the specs are similar to the LG G3 Vigor :
CPU/GPU etc...
I know that it is written everywhere that you can't intall a rom not suitable for your phone, because I think it leads to a bricked device.
The fact is I don't know the level of inutility of my ex-phone.
Did someone ever grafted a ROM from another brand?
Has someone an information to recover my old and functionnal cat s50 from the FEL mode?
Click to expand...
Click to collapse
Hello,
Please register for a XDA account.
You may try posting your query here Android Q&A, the experts there maybe able to assist you.
-Vatsal

My Oppo A33f stuck on logo

hi to all senior and members,
would like to ask any method to repair my oppo a33f as she's stuck at logo at boot, and not get able to work in normal after using flashify apps, to let know in advance my oppo device cant get into recovery mode (pressing low volume button), and im even tried check available fastboot mode in command prompt which is negative.
please any moderator / members here to help me, tq
hi, if anyone still interested therre is a way to revive oppo a33f.

[Completed] Non-typical bricking of ZTE Nubia Z5s

Hello!
I have been trying to flash a new ROM into my ZTE Nubia Z5s phone. I have tried many versions, but the majority of installations didn't end successfully. However, after the last try, the phone got stuck on showing the logo. After waiting for nearly an hour, I started to think that it's not going to change and shut the phone down. However, after turning it back on, the screen started to show weird color combinations (similar to how a physically damaged screen behaves) after the logo. Physical damage is rather impossible, because both the logo and the battery indicator look fine. The problem is, I can't reach recovery mode by pressing VOL+ and Power, and I also can't sideload a new ROM (ADB can't find the device, and the phone is being treated by my PC as a flash drive). What can I do now? Any help would be much appreciated.
Wojtek
Hi there and welcome to assist,
Unfortunately there is nothing about your question/device on XDA forum. Try a Google search first or contact the manufacturer for stock firmware and flashing instructions.
You'll have to create an account to post in the main forums if you have any other questions.
Good luck

Question [CLOSED] Recover hard brick after trying to install TWRP

Hey guys, I recently rooted my stylus 5g and went to install TWRP. I was able to get it to boot to TWRP, but I believe within TWRP I did the flash wrong as now my device is hard bricked. I cannot get it to show the initial logo, get to the bootloader or I think even EDL. I've tried the Lenovo recovery tool and the Moto all-in-one tool, but essentially all I get now is a black screen.
Any input on what I can do to either diagnose and possibly recover my device? I have the original firmware downloaded, but without being able to get to the bootloader, recovery, or even EDL, I'm at a loss as to how to proceed. I did grab a blankflash for the device, but I'm not clear on how to begin to use that to move forward.
Thanks for any advice you can provide.
-Ryan
@dagey Thread closed as duplicate of
Recover bricked moto stylus 5g after flashing TWRP
Hey guys, I recently rooted my stylus 5g and went to install TWRP. I was able to get it to boot to TWRP, but I believe within TWRP I did the flash wrong as now my device is hard bricked. I cannot get it to show the initial logo, get to the...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! You'd initially posted the still open thread in the "Moto G Stylus (2021)" device forum, out of which I've moved it. If you realise that you posted something wrongly just report it, and we're happy to support.
By the way: Usually, I'd even to close the still open thread as even that is a simple duplicate of your post here!
Regards
Oswald Boelcke
Senior Moderator

Categories

Resources