Search results

The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is. If you still didn't find the correct drivers, you should try...

If you have all the files in C:/adb folder try holding shift and right click inside the folder and choose open command window here. From the pic you've sent, you were trying to execute the command from the wrong folder.

You can try it like this: Thanks to Gumka1977

Flashing base means to flash stock firmware :) In this case it's 10.0.3.0. as mentioned in the first post ;)

In my case taking a backup would cause a very long startup time, so for now I try to live without it :) When I flashed back stock, everything was ok.

Did you go to Settings - About phone and enabled Developer options (tap 7 times on Build number)? After you enable dev options, tap on enable usb debuging, allow OEM unlock and you should be able to unlock your bootloader via adb. Note: take a backup because unlockig erases all your data.

Hi, OEM unlock option in settings is just a switch that enables/disables the unlocking of the bootloader. You must first enable OEM unlock in settings and then proceed with the actual unlocking of the bootloader ;)

Thanks for the feedback. I guess I'll just have to wait a little more for a GAPPS-less ROM :)

Thanks :) Do you maybe know if we delete gapps instead of disabling them have any sideffects like FC's?

It happened to me too, boot time is so long that I thought it was in a bootlop. It has something to do with TWRP. I did a stock flash and it went away. WARNING: do not try to restore the backup with twrp or you'll get a soft brick. Twrp is still not working correctly for our devices, but...

Thank you for the great work :) Could you maybe make a build without GAPPS ?

Could you try going to settings - system - about phone - and tapping te build number entry 7 times again and see if anything changes? ---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ---------- Thats indeed a possibility. It would also mean that the bootloader is...

Just remembered:silly: Do you have the search settings option when you first get to settings? Should be right on top. If you do, can you try typing oem in the search and see if there's anything listed?

Yeah, saw it the second time i looked :confused: It sais security update from December 2018 but the build is 9.6.6.0 :eek: My screenshots:

Strange :confused: I'm on 9.6.11.0 version and it's there. You're on 9.6.6.0 version. Maybe there's someone who had experience with 9.6.6.0 and OEM unlocking but if not there's always the option to do an OTA update to a newer firmware version. Just don't update to a 10.x.x.x version (Pie) if you...

Could it be that the OEM unlock option is under Development tools?

Could you post a screenshot of your System menu under settings?

When you unlock the bootloader the data is lost and sometimes it takes around 5 minutes or more to boot in the system ( at least thats how it was in my case ) You can try and wait for 5-10 minutes to see if it finaly boots or in the worst case scenario flash stock Pie again

Did you click on trust this device on your PC? When I first plugged my device with USB debuging enabled I got a notification from my system (I'm using Win 10)

You could try to use a different charger (I know it's stupid but trying to eliminate all the small issues like that sometimes gives good results). Waiting for another update might fix the issue if it's a ROM thing, naturaly if you want to wait. Worst case scenario would be to try and rollback to...

Do you have access to the data on the card while it's charging? If you change USB options to e.g. MTP storage instead of charging, does it change anything?

Sorry to hear that. I personaly don't use adoptable storage so can't help more. Only thing that comes to mind is to try and clear the app data from apps that were on adoptable storage if moving back to internal memory.

How did you format your card? Did you use internal or external option? Saw few posts with same issues and strange enough all with Sandisk cards.

Do you have MIFlash installed? I had the same automatic reebots while in fastboot regardless of the input but that was because i had the wrong drivers :p When I installed MIFlash the right drivers were also installed ;) Hope this helps.

You said you've migrated all the apps to the SD card which is formated as adoptable. Did you try to move the apps back to internal memory to check if that's the issue?

Glad to hear it :laugh:

For the issue in the first post try clearing the data from every file manager you use, it seems a little strange that the file manager reports external device error when you converted to internal (basically you told the system that the external memory doesn't exists and it should only look at...

Take a look at this thread: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 you can find pretty much all ota's and fastboot rom links. All full ROMs end with .tgz extension like this one...

Backup up everything first ;) Download MiFlash and the correct ROM (not OTA version) Then you can flash the Stock ROM which will remove everything ;) You can also choose to leave unlocked or lock the bootloader (re-lock is selected by default) As this is a somewhat new device I wouldn't tick the...