Database Users

LED control on stock with any app!

Thanks to an idea from the dev of GravityBox, we can now have full LED control on stock with almost any LED control app. I tested it with GravityBox, and a few ghetto LED control apps from the play store and they all worked perfectly!
This also enables the LED to light up when charging.
You can either use the flashable zip, or replace the file manually. To replace it manually download the file attached to this post, place it in /system/lib/hw/ and replace the file that is already there. Make sure it has the same permissions as the other files, and then reboot.
This has only been tested on 5.1.1 (I'm running LYZ28E).
And no, it doesn't blink. Either the CM team hasn't cracked it yet or the LED drivers are just not there to make it blink.
A flashable ZIP has also been added to this post. ZIP created by @spacetaxi

Thanks! Seems to be working fine on LMY47Z as well. :good: Did some quick tests on my Nexus 6 and will try to regularly use it now instead of LightFlow Pro.

Does led blinking work without light flow?

Unfortunately it doesn't seem so.

So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.

OKAstro said:
So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.
Click to expand...
Click to collapse
Because a lot of people have issues with LightFlow since you have to do some really ghetto things to make it work. This guarantees that it will work and allows you to use any app you want.

OKAstro said:
So you still need to install an LED apk besides this?
Click to expand...
Click to collapse
No, this is my setup: Stock rom, rooted, modified lights.shamu.so installed, Xposed installed, GravityBox installed. But: All LED related functions in GravityBox are disabled, so I don't think that GravityBox or Xposed has to be installed. I can enable LED notifications e. g. in K-9 settings - and it just works! No GravityBox, Xposed or LightFlow involved. So if the regarding app supports LED notifications there is no need to use a "LED contol app".
Edit: The led *blinking* does not work. Instead the led is switched on permanently during a notification.

OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.

OKAstro said:
OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.
Click to expand...
Click to collapse
I believe it supports charging indication as well. I thought it was GravityBox doing it but apparently it is the OS.

Your title is a little misleading.
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.

vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.

I am running Gravity Box and yes it does work, although LED on N6 sucks

vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?

spacetaxi said:
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?
Click to expand...
Click to collapse
That's a very good point. You could actually just do it in recovery if it supports ADB. You can push files over ADB really easily.

Just a tip. In order to get acurate red green blue colors for LED, instead of picking it, use exact hex value then its not going to mix with over colors
Blue #0000ff
Green #00ff00
Red #ff0000

Will this work in Android M?

jodvova said:
Will this work in Android M?
Click to expand...
Click to collapse
I went ahead and pushed it over using ADB and recovery on my phone running Android M. So far it seems to be working fine, though you won't be able to alter the light without an application that supports it.

A few reasons.
GrayBoltWolf said:
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.
Click to expand...
Click to collapse
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.

vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Who was denied warranty with unlocked bootloader? I haven't experienced that on any of my phones yet, even none Nexus devices

vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Google has absolutely no way to tell if you unlocked your bootloader unless you either 1. tell them or 2. send you phone in unlocked.
There have been 0 reports of anyone being denied warranty service on a Nexus device and any that may exist were because the user told Google they were unlocked.
At any rate this mod does not require root, as you can flash it through recovery or over ADB.

A question about rooting my device

I want to root my 6p because I want to enable miracast streaming to my TV. I know theres a line or so I need to add to the bottom in order for that to work.
My question is this: If i root is there some kind of other upkeep I would need to do to make sure my phone works and gets updated as normal while it's rooted? I'm not a tinkerer when it comes to this, I just saw I could achieve miracast if I went with this method, so figured it was worth it to find out what Id be getting myself into if I rooted the phone.

you cannot update your phone OTA while rooted.
so if you're not a tinkerer, you need to learn to be if you root.

TheNamelessMan said:
I want to root my 6p because I want to enable miracast streaming to my TV. I know theres a line or so I need to add to the bottom in order for that to work.
My question is this: If i root is there some kind of other upkeep I would need to do to make sure my phone works and gets updated as normal while it's rooted? I'm not a tinkerer when it comes to this, I just saw I could achieve miracast if I went with this method, so figured it was worth it to find out what Id be getting myself into if I rooted the phone.
Click to expand...
Click to collapse
I read someone was able to get around it by unchecking OEM unlock in dev settings and doing the update then re enabling it after update. I assume they also had systemless root and lost that during the update. But I have not tried this myself.

Gizmoe said:
I read someone was able to get around it by unchecking OEM unlock in dev settings and doing the update then re enabling it after update. I assume they also had systemless root and lost that during the update. But I have not tried this myself.
Click to expand...
Click to collapse
This is not true, once you root your phone, you will be unable to accept OTA update unless you revert back to stock, ie;
Stock Recovery
Stock Boot
Stock System
If you are at all uncomfortable attempting I suggest you do not root.

dratsablive said:
If you are at all uncomfortable attempting I suggest you do not root.
Click to expand...
Click to collapse
I'm completely comfortable rooting. Not sure where you're getting that. I was just sharing something I read.
---------- Post added at 10:21 AM ---------- Previous post was at 10:09 AM ----------
Here is a link to what I read. It wouldn't be hard to remove root and flash stock recovery if you wanted to upgrade. As long as you are still stock obviously.
http://forum.xda-developers.com/showthread.php?p=64974439

Gizmoe said:
I read someone was able to get around it by unchecking OEM unlock in dev settings and doing the update then re enabling it after update. I assume they also had systemless root and lost that during the update. But I have not tried this myself.
Click to expand...
Click to collapse
No.
To root you need to use a custom recovery, TWRP.
As long as you have TWRP installed no OTA.
Just download and flash the updates.

tech_head said:
No.
To root you need to use a custom recovery, TWRP.
As long as you have TWRP installed no OTA.
Just download and flash the updates.
Click to expand...
Click to collapse
Look right above your post...

1050F: OTA Update #S100256_160119

Received this yesterday evening and am wondering if anyone has a good idea of what this update entails. It states is security patch and stability fix, if I'm not mistaken. Probably just a regular non-major update, then?

I am in the middle of returning my tab back to stock to then update to this update... Will report back in a while. @all
If you have unlocked your bootloader to use a custom recovery DO NOT UPDATE. It will soft brick!!! I tried in vain and am having to resort to 'back to stock' as, like a pleb, I don't backup before I tinkered
Sent from my SM-G901F using Tapatalk

I happens to the best of us, man. Sorry to hear. I'm currently not rooted, but at some point will, so that possibility of messing up will ALWAYS be there.

i have just updated my yoga 830LC. But i forgot my bootloader is unlocked. It's soft brick. Can you help me how to back to stock Lollipop ROM. please help me! thanks

Do you have a backup? When I first tried to update I think it did update part of the rom. I reflashed the patched esp (which you should still have if you have unlocked you boot-loader)
It then let me in to recovery and to restore.
Try that and report back
Sent from my SM-G901F using Tapatalk

Hi. I have this update from lenovo too, my 1050F is rooted, how I do a backup ? and you flash which stock rom, before upgrading ?
If possible, I want to keep my data.
Thank you.

I think the only way to keep you data is with something like Titanium backup saved to an external source and then whenever the update is finished re-root and restore selected backed up data

If you have unlocked you boot-loader you must have flashed a customers recovery. I did a twrp back up and selected what I want to restore.
Edit - get the files you need from this post
corasman said:
Hi Rob
These files I copied from various threads on here.
They are on my g/drive,if they are any good to you or anyone else.
http://tinyurl.com/zdr92pf
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo
http://tinyurl.com/hjy4kks
http://tinyurl.com/jhrjscj
Click to expand...
Click to collapse
Sent from my SM-G901F using Tapatalk

I have the 8 inch version of this tablet (830F) and received a similar update notification.
I just used the temp recovery trick to root and disable some bloat but left it otherwise stock. The tablet is currently in the process of backing up with temp TWRP and I was thinking of unrooting and giving this update a shot.
But it's not worth losing root over it...
Did anyone apply the patch in the meantime? Were you able to root again?
Thanks.

Yeah I have rooted, unlocked the boot-loader and flash twrp... All is good.
Have you flashed the patched boot-loader? If so you will need to flash the stock 830F ROM

Soft Brick
I'm just leaving my experience in case anyone does the same mistake as I.
I tried to use de "Hide root" option of SuperSu before upgrading, I have a locked bootloader, so I thought that it would be enough but I well... it didn't even boot after de lenovo screen
So I had to returno to stock, after reading what other peole did I manage to finally flash it back to stock lollipop.
I download this stock rom from lenovo-forums.ru
1050f_s100196_151123_row_lос-50
Click to expand...
Click to collapse
[As rookie, cannot post links :silly:]
Before flashing, the flash.xml has to be edited. Find
<string>fastboot flash system $system_file</string>
Click to expand...
Click to collapse
and add -s 1G to the command
<string>fastboot -S 1G flash system $system_file</string>
Click to expand...
Click to collapse
Then, enter on bootloader mode. I did it from de Recovery Mode (PWR on, and after de "lenovo" press both volume keys)
And just flash it with Phone Flash Tool
Everything it's probably pretty obvious for many of you but I leave this here for noobies like me! :victory:

Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.

Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.

-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)

-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
Ok, this was a success -
1. Unroot through the SU app (just to be safe)
2. Restart
3. Apply the update through the regular system/settings UI and wait for it to finish
4. Re-root as before (using IntelAndroid-FBRL-07-24-2015 and BETA-SuperSU-v2.67-20160121175247)
Keep in mind that I was on stock bootloader and didn't alter much besides disabling crapware. Deeper modifications may cramp your style.
Cheers
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
dingers01 said:
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
Click to expand...
Click to collapse
Yes, this worked fine. See my other follow up post. Good luck.

saupiquet said:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Click to expand...
Click to collapse
Sorry for the delay, but no. Everything within the internal storage will be lost.

BL1 - Rooted - Update system / Not loose root?

This may have been addressed, but I haven't been in this game in a few.
I have G950U1UEU1AQE3 on VZW. Currently I am rooted with SafeStrap and TWRP. I have been looking at updating to ANY latest firmware, but fear losing root. I figured that I could update to at least G950U1UEU1AQH3 since it is still BL1, but wanted to try Oreo (8.0). Assuming going to Oreo will cause me to lose every ability to return to an older release, will I still be able to keep root? I know this may be basic, but I need a refresher. Thanks!

nitro66215 said:
This may have been addressed, but I haven't been in this game in a few.
I have G950U1UEU1AQE3 on VZW. Currently I am rooted with SafeStrap and TWRP. I have been looking at updating to ANY latest firmware, but fear losing root. I figured that I could update to at least G950U1UEU1AQH3 since it is still BL1, but wanted to try Oreo (8.0). Assuming going to Oreo will cause me to lose every ability to return to an older release, will I still be able to keep root? I know this may be basic, but I need a refresher. Thanks!
Click to expand...
Click to collapse
I have a stock rom setup to flash in safe strap somewhere in dev section its the latest rootable firmware
https://forum.xda-developers.com/galaxy-s8/how-to/950u-stock-rom-blq1-optional-root-t3812012

HoosierDaddy said:
I have a stock rom setup to flash in safe strap somewhere in dev section its the latest rootable firmware
https://forum.xda-developers.com/galaxy-s8/how-to/950u-stock-rom-blq1-optional-root-t3812012
Click to expand...
Click to collapse
Thanks. After playing around with different things, what I found that worked for me was loading PartCyborgRom getting me to BL2 and then loading the UserData file from the G950USQS2BQL1 VZW rom. I will be monitoring the phone for LTE errors that I used to get and may re-load CP / CSC if that's the case. So far, I'm back with SafeStrap/TWRP and root. Once 8.0 has a good confirmed root, then I might work on going to that.
Does anyone know if there is a configuration setting to remove the diagnostic type information from the boot screen? All that text in the upper corner is more of a nuisance to me than what it's worth.

nitro66215 said:
Thanks. After playing around with different things, what I found that worked for me was loading PartCyborgRom getting me to BL2 and then loading the UserData file from the G950USQS2BQL1 VZW rom. I will be monitoring the phone for LTE errors that I used to get and may re-load CP / CSC if that's the case. So far, I'm back with SafeStrap/TWRP and root. Once 8.0 has a good confirmed root, then I might work on going to that.
Does anyone know if there is a configuration setting to remove the diagnostic type information from the boot screen? All that text in the upper corner is more of a nuisance to me than what it's worth.
Click to expand...
Click to collapse
Oreo probably will never be rooted I have a another s8 on revision 3 bootloader I have been picking the brains of the guys who did root for this device....
I tried several different methods all in fail
I have a small telegram group for advanced users,But telegram links are not allowed
most of the discussions are on there.... We tried a modified samfail on the FA70 Factory combo but no go
I got a working combo boot img I made
No combo system behind it
The only issue now is the previous roots all have native 7.0 systems to push su and junk to...On bootloader 3 We still need the combo boot img,Which unfort is a 7.0 combo,Which means all the rest of the Bit 3 systems out are oreo which wont obviously boot on 7.0 kernel
---------- Post added at 08:25 AM ---------- Previous post was at 08:12 AM ----------
nitro66215 said:
Thanks. After playing around with different things, what I found that worked for me was loading PartCyborgRom getting me to BL2 and then loading the UserData file from the G950USQS2BQL1 VZW rom. I will be monitoring the phone for LTE errors that I used to get and may re-load CP / CSC if that's the case. So far, I'm back with SafeStrap/TWRP and root. Once 8.0 has a good confirmed root, then I might work on going to that.
Does anyone know if there is a configuration setting to remove the diagnostic type information from the boot screen? All that text in the upper corner is more of a nuisance to me than what it's worth.
Click to expand...
Click to collapse
Also the info in the top of boot is part of the kernel thats used to gain root That cannot be gotten rid of,But there is a adb code you can run if you ever get the scrolling lines of debug code on boot animation similar to the app liveboot

HoosierDaddy said:
Also the info in the top of boot is part of the kernel thats used to gain root That cannot be gotten rid of,But there is a adb code you can run if you ever get the scrolling lines of debug code on boot animation similar to the app liveboot
Click to expand...
Click to collapse
Right on. Thanks!

Mi A1 Downgrade from Pie to Oreo questions

EDIT 2: ISSUE SOLVED. Go to the bottom of this comment for how to get it done right. Credits to @rizkyxculture and @orma1
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
EDIT 2: Sorry for necroing this thread, but just to clear things up a bit, from my own experience, and include and clarify what @orma1 said below in this thread so you don't have to scroll down. Before all this, make sure you have SYSTEM WIDE ADB AND FASTBOOT INSTALLED for simplicity's sake.
All credits go to @orma1 and @rizkyxculture for your amazing efforts into this <3. None of it is mine, so thank them in their respective comments/threads if you wish to.
1. REMOVE ALL PASSWORDS AND FINGERPRINTS BEFORE PROCEEDING WHILE IN PIE, and do CLEAN DATA WIPE (do not choose the relock bootloader in Mi Flash Tool).
2. Do everything in that guide sent, and at the end, where rizky mentions flashing November update after the TWRP restore, don't do it. Instead, re-flash the March update. Thanks @orma1 for your comment. If your phone just straight up boots like mine did, without bootlooping, just power it off and go to fastboot again. Link to guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624.
3. Once your phone boots normally, go to developer options, and uncheck the automatic system updates to prevent it from going to pie automatically later on. in the future. Install GCam at this stage if you wish (follow manual installation guide on XDA). Link: https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
4. After you've installed GCam (which is why you're probably doing all this in the first place, or not, regardless), chances are you still want to keep your warranty (and for security reasons) and therefore you should relock your bootloader, else the servicemen are just going to see that BIG warning at your phone's boot, and are likely revoke any warranty straight up. To do this, simply go back to fastboot and type the command below in Command Prompt and WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON (or copy paste the line below WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON):
fastboot oem lock
Once it says okay, type the following command:
fastboot reboot
Done. Now reboot, go to system update, and download and install the November update. Enjoy your still in warranty Mi A1 with Oreo and/or GCam (just make sure you uninstall the apk when giving it to the service center should you ever need to service it). Also, the power down button press prevents the auto data wipe function from activating. Have fun.
Also I have verified this works even on the April 2019 update. Just don't update any further, else I can't be sure.

Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk

Droidriven said:
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Guess I'll just stick to pie and bite the sand and live with it till someone gets a solid, working method...
As a second thought, if I make a backup of everything (system, boot, etc. etc.) in TWRP and then carry out the flashing process, will reflashing those backups restore my device in case of a brick?

Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
Just flashing oreo from pie should cause IMEI loss.
I used the method from here: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
although I had to do his method a little differently.
also make sure if you can to backup your data as you can lose it in the process.
first of all, after oreo march update flash, my phone did boot but with no IMEI.
second of all, flashing November update after restoring IMEI caused bootloop, instead you need to flash march update again. afterwards your phone should boot with the correct IMEI (you can double check with the one on your phone's box) . worked for me with two Mi A1s.
after all of this I was able to update to 8.1 November update via system update in the settings.
and lastly I made sure to disable automatic system update from developer settings.
Good luck!

Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)

Meme :D said:
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Click to expand...
Click to collapse
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.

orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Thanks, will see about all this.

orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?

Nafis-ul-Islam said:
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Click to expand...
Click to collapse
I used the backup from this thread
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
It's a backup of someone else's efs and boot patiotions. At first I thought too that restoring someone else's backup should result in me getting his IMEI.
But after trying to restore through this backup My IMEI changed from 0 to the one on my phone's original box meaning I got my own IMEI. the method there worked perfectly for me and now I am rocking 8.1 Oreo November update with Magisk and TWRP. the only thing is that following step 10 in the tutorial there resulted in a bootloop for me. Instead I followed the suggestion of one of the comments saying that instead of flashing November update after restoring IMEI you need to flash the same March update you flashed before. this time my phone booted with IMEI and I updated to 8.1 November through OTA.

Did you downgraded succesfully?

Meme :D said:
Did you downgraded succesfully?
Click to expand...
Click to collapse
I was able to downgrade successfully following this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
In step 10 you need to flash oreo march update again and not November update as mentioned as flashing November update caused me bootloop.
afterwards you can update to November update via System update in the settings.
besides this I followed the tutorial exactly and was able to downgrade two Mi A1s.

I have successfully downgraded my Mi A1 with this thread
"Tutorial Downgrade 9.0 to 8.1 No EDL, No IMEI Problem & No Signal Problem"
Also im a 14 Yr old nearly 15 on April 20.

I was afraid too, now I'm on Nougat )
Just follow this tutorial : https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Before doing anything, boot TWRP and create a full backup of your system, after that transfer it to your PC. Probably you don't need it but better safe than sorry.
After you will flash March firmware, your phone will boot but you will not have signal, it's okay. Thing is, you don't lose the IMEI, it's still there, but somehow you lose the signal. Boot TWRP again, create a backup of your boot and EFS, you will see TWRP folder in your phone, go there and you will see a backup. Remove your backup files and replace them with the one from the guide, then you can restore them without issues (you will see a modem error, ignore it). Restart and let it boot a bit, then go to bootloader again, flash March firmware again (don't flash the November one! ignore that from the guide) and the signal will be back. If you do this, I doubt you will lose your IMEI somehow. I never lost mine, it's the same from the box.
Good luck! Make sure you go in developer settings after and disable automatic updates or you will be back to Pie. I rooted my phone so it can't update.

Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3

Nafis-ul-Islam said:
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Click to expand...
Click to collapse
I'm happy to help
but all the credit goes to rizkyxculture for finding this method and ibooth2004 for correcting us to flash March update again instead of the November one.

so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.

Marcos OC said:
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Click to expand...
Click to collapse
I agree the system's performance on pie is horrible and also the mic volume is low which is very annoying.