Related
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
If you know there are answers why not use the search function and find them? There is a thorough guide made by mike1986 so I suggest you find that and go from there...
whitetiger_0603 said:
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
Click to expand...
Click to collapse
Open android-sdk and click on sdk manager and update adb to the latest version.
Here is a thread to undo s-off and lock your bootloader http://forum.xda-developers.com/showthread.php?t=2314582, firstly change cid http://forum.xda-developers.com/showthread.php?t=2317536.
gee2012 said:
Open android-sdk and click on sdk manager and update adb to the latest version.
Here is a thread to undo s-off and lock your bootloader http://forum.xda-developers.com/showthread.php?t=2314582, firstly change cid http://forum.xda-developers.com/showthread.php?t=2317536.
Click to expand...
Click to collapse
Thank you very much.
Edit: so I downloaded Android sdk to this comp but something isn't working right? Should i have gotten the one in the "other platforms" list? The one i downloaded didn't say it's was Windows 8 compatible, however the DL in the other list is not OS specific, just says it's for Widows 32 or 64 bit.
EddyOS said:
If you know there are answers why not use the search function and find them? There is a thorough guide made by mike1986 so I suggest you find that and go from there...
Click to expand...
Click to collapse
Why are you talking? This is a troubleshooting forum. Not a "go ahead and ask a question and maybe we'll be nice about giving you an answer forum".
whitetiger_0603 said:
Why are you talking? This is a troubleshooting forum. Not a "go ahead and ask a question and maybe we'll be nice about giving you an answer forum".
Click to expand...
Click to collapse
I'm afraid you're wrong. Rule 1 from the forum Rules:
"1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news"
http://forum.xda-developers.com/announcement.php?a=81
Basically, search first. Chances are it has already been asked and answered - as proven in gee2012's post...
Reading your OP would indicate you know the answer is out there but can't be bothered to search - hence my first reply
EddyOS said:
I'm afraid you're wrong. Rule 1 from the forum Rules:
"1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news"
http://forum.xda-developers.com/announcement.php?a=81
Basically, search first. Chances are it has already been asked and answered - as proven in gee2012's post...
Reading your OP would indicate you know the answer is out there but can't be bothered to search - hence my first reply
Click to expand...
Click to collapse
Learn to read an comprehend. Obviously when I said I know i can search, then gave an indication of what was found, then that means I did search, and of course, that's what i found. But instead, you prefer to go the route that i also indicated, and chose to be snarky and rude, rather than just no answer the question at all. But thank you very much for wasting your time and mine by being as such.
Easy method: flash RUU and use revone to relock and
fastboot oem writesecureflag 3
More tricky
adb getvar version-main
Post answer here.
whitetiger_0603 said:
Learn to read an comprehend. Obviously when I said I know i can search, then gave an indication of what was found, then that means I did search, and of course, that's what i found. But instead, you prefer to go the route that i also indicated, and chose to be snarky and rude, rather than just no answer the question at all. But thank you very much for wasting your time and mine by being as such.
Click to expand...
Click to collapse
Thing is, though, I did answer your question. mike1986 has a thorough guide on how to go back to stock so searching for that would've given you the answers you required
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.
I'm having some problems following the instructions from http://developer.sonymobile.com/ regarding setting up Android Studios and the recommended 'fastboot' drivers on Win 10. I have done some vocoder development in the past and have a background in tech development and dedicated microprocessor programming, but i'm in over my head here. I could use a little help.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
Their instructions read in part, "1. Download and install the Android SDK."; which I did, including loading the Google USB drivers.
2. If you’re running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can’t find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
Note: Google USB Driver Packager is ver. 11
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.
Download an install flashtool, you'll find a link here in the forum. Can't search myself right now as I'm on the phone with slow Internet. In the thread is everything explained and it's very simple to use.
Oops
The correct folder is \AppData\Local\Android\sdk\platform-tools. No wonder it wouldn't load fastboot. Ultimately however, fastboot with the OEM unlock code didn't work. "FAILED (remote: Command not allowed)". BUMMER!
Thanks anyway. Now I'm off to flash what I can...
Best mehod is to install 15 second adb install-it installs adb and fastboot and can be open anywhere
give it a try
http://forum.xda-developers.com/showthread.php?p=48915118
ManagementCritic said:
....Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.....
Click to expand...
Click to collapse
Your bootloader cannot be unlocked. Blame your operator...
Hey ptmaniac,
Thanks for the response.
Yeah, I get that. I wrote in another thread how I had attempted to negotiate a remedy through both the OEM and the carrier; not that I expected a good result, but probing for what was left unsaid. I wanted to see if I could determine their reasons and motivation and whether they would consider any alternatives. The only admission was that they could, but would not. Best guess? It has to do with existing agreements they are unwilling to revisit.
ptmaniac said:
Your bootloader cannot be unlocked. Blame your operator...
Click to expand...
Click to collapse
@ManagementCritic
No problem,
In my country it's the same endless loop unfortunately... the carrier says i should talk to the oem, the oem says the phone was locked at carrier request and they can't do anything about it so i should talk to the carrier instead
I still blame myself from buying a full priced device locked to the carrier, i thought all of them could be unlocked anyway by submitting imei to the sony developer website... if i had researched a bit more i would have figured out that i should have bought it unlocked directly from the oem... lesson learned i guess.
I'm attempting to root my Pixel 4 XL with magisk, but am getting hung up on one part. So far I have:
downloaded and patched the system's boot image
installed adb and fastboot on my pc
turned on OEM unlock and USB debugging
gotten into fastboot mode both by using ADB on my computer, as well as using the device buttons (power + vol down)
when I'm in fastboot, though, the device's state is "locked" regardless of OEM unlock is on or not, so I am unable to flash the magisk image. I've read around that it might be a drivers issue on my Windows 11 PC, but I am unable to find a reliable way to get the correct drivers for this task. Is there a good way for me to fix this?
The phone is an unlocked google pixel 4 XL that I bought refurbished after my initial one died. I've read that some random unlocked pixels have permanently locked bootloaders (to pixel users' chagrin), and I'm a little worried that that's the case. I tried looking up my devices IEMI to double check that it's an unlocked phone, and I didn't see anything out of the ordinary there.
the exact issue I'm facing is: When I type ".\fastboot flashing unlock" into command prompt, I get < waiting for any device > as a response which softlocks the powershell as far as I can tell.
As stated above, I have tried searching around for this issue and have come to the conclusion that it's likely a driver issue, but I am unable to figure out how to get the necessary drivers.
thank you for any help in advance!
coltonious said:
I'm attempting to root my Pixel 4 XL with magisk, but am getting hung up on one part. So far I have:
downloaded and patched the system's boot image
installed adb and fastboot on my pc
turned on OEM unlock and USB debugging
gotten into fastboot mode both by using ADB on my computer, as well as using the device buttons (power + vol down)
when I'm in fastboot, though, the device's state is "locked" regardless of OEM unlock is on or not, so I am unable to flash the magisk image. I've read around that it might be a drivers issue on my Windows 11 PC, but I am unable to find a reliable way to get the correct drivers for this task. Is there a good way for me to fix this?
The phone is an unlocked google pixel 4 XL that I bought refurbished after my initial one died. I've read that some random unlocked pixels have permanently locked bootloaders (to pixel users' chagrin), and I'm a little worried that that's the case. I tried looking up my devices IEMI to double check that it's an unlocked phone, and I didn't see anything out of the ordinary there.
the exact issue I'm facing is: When I type ".\fastboot flashing unlock" into command prompt, I get < waiting for any device > as a response which softlocks the powershell as far as I can tell.
As stated above, I have tried searching around for this issue and have come to the conclusion that it's likely a driver issue, but I am unable to figure out how to get the necessary drivers.
thank you for any help in advance!
Click to expand...
Click to collapse
Hello and good morning, @coltonious
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to
Google Pixel 4 XL Questions & Answers
Ask your questions about the Google Pixel 4 XL and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Hello!
First of all: I know I am asking about the Lite, not the Pro - but there was no dedicated device listing for it, so I went for the next best thing I could find. I apologize in advance.
I have a highly visually impaired friend for whom reading a lot of text is very taxing. I, too, am visually impaired, but I practically live in a terminal - it's totally fine for me. However, we live all across the country (Germany). Basically, he lives in Berlin and I in Frankfurt. Thats a long way apart. So, the best I can help him with is by logging in via Parsec; hence, I have to ask him to do any hardware-related handling.
The TL;DR is: His device defaults to fastbootD, refuses both "flashing unlock" and "oem unlock" after toggling it in Developer options. Variations of adb/fastboot "reboot bootloader/recovery" all did not result in full fastboot. We were trying to extract the boot image to use with Magisk.
The long story: Late last year, he bought the phone off eBay once he heared that Oppo phones were no longer allowed to be sold in stores here in Germany and wanted to root it to see what he could do with it. Since it is a MediaTek device, I told him that hopes for a LineageOS port would be slim, considering MediaTek's history with OSS. So first we went on a hunt for the stock ROM to just grab the boot image off there. No luck; the only seemingly viable listing - a Google Drive link - has become completely unavailable (traffic limit reached). So the next best thought was to grab it off the device itself.
So I went to his maschine via Parsec and set up adb and fastboot and configured the proper Fastboot driver (the official Google one) and made sure the device was recognized as an Android Bootloader Device. Fastboot could also list it, so I was all set up. From there I made a dump of "get-var all" and sure enough, "unlock" was "no". So I sent his phone to reboot and him on his merry way to head into the Developer options and find OEM Unlock. And, it is indeed there. Once he enabled that, I attempted to unlock that bootloader. But I always get errors that the HAL can not be loaded or that the command would not be found. And, whilst researching more, I learned that fastboot can also load in userspace as fastbootd. Sure enough, I had him send me a photo of what the bootloader looked like, and in big bold letters it does indeed read "FASTBOOTD".
After looking up several guides and information, I have not managed to get anywhere at all untill I found this post: https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I could not find any verification that his phone is also affected, meaning that he might have a "castrated" bootloader alltogether - or fastboot, at least.
The model identifies itself as: CPH2371
If you have any possible ideas, please do let me know. Personally, I am at the end of my ideas. Rooting, and sub-sequently installing LineageOS, was astoutly simpler on my Razer Phone 2.
Thank you very much in advance - and, again, apologies for posting in the wrong thread, a proper X5 Lite one was nowhere to be seen.
Kind regards,
Ingwie
PS: The "vars.txt" attached was pre-OEM unlock setting.
any news? root possible?
I've forgot me pattern lock, when I tried to enter in recovery mode, my phone keep restarting again & Again what should I do, I need to reset my pattern, GMAIL ID method also not working....