You all know that, now Mi phones will have anti rollback features while upgrading to MiUi 10.
Though A2 is stock androud, will it face any such kinds of restrictions somehow??
There is good post describing rollback policy in Android. Mi A2 was released with Android Oreo, so we need someone with phone who will check support of Verified Boot using adb commands provided in post:
Code:
adb shell
dumpsys package | grep "verified_boot"
OR
Code:
adb shell
getprop | grep "avb"
Click to expand...
Click to collapse
AlexX333BY said:
There is good post describing rollback policy in Android. Mi A2 was released with Android Oreo, so we need someone with phone who will check support of Verified Boot using adb commands provided in post:
Click to expand...
Click to collapse
PS E:\platform-tools> adb shell
>> dumpsys package | grep "verified_boot"
jasmine_sprout:/ $
this is output, every time i type the code
Syed Shahriar said:
PS E:\platform-tools> adb shell
>> dumpsys package | grep "verified_boot"
jasmine_sprout:/ $
this is output, every time i type the code
Click to expand...
Click to collapse
I suppose that means no Verified Boot. Try another command, just in case.
AlexX333BY said:
I suppose that means no Verified Boot. Try another command, just in case.
Click to expand...
Click to collapse
tried both, same result
Enter fastboot.
Type "fastboot getvar anti".
If none, the phone is not under Anti-Rollback policy.
If 2 or 3, it is under ARP, but is not yet activated.
If 4 or above, it is surely under ARP, and is already activated.
Sithu Htun said:
Enter fastboot.
Type "fastboot getvar anti".
If none, the phone is not under Anti-Rollback policy.
If 2 or 3, it is under ARP, but is not yet activated.
If 4 and/or above, it is surely under ARP, and is already activated.
Click to expand...
Click to collapse
it shows "2" on my device (4GB/64GB, HK).
matchung said:
it shows "2" on my device (4GB/64GB, HK).
Click to expand...
Click to collapse
Be sure to check it before downgrading. Upgrading is okay.
Didn't see this thread (need to del the one I started just now), but yeah, mine also says '2'.
Sad to see that, didn't think the A2 would have this.
I was on V9.6.10.0, installed the OTA update (v9.6.12.0), tried to root with Majisk and things gone wrong. So, I flashed v9.6.10.0 again.
This counts as a downgrade?
kadu20es said:
I was on V9.6.10.0, installed the OTA update (v9.6.12.0), tried to root with Majisk and things gone wrong. So, I flashed v9.6.10.0 again.
This counts as a downgrade?
Click to expand...
Click to collapse
Not sure, but knowing they've implemented this on the A2, I'd be ** extremely ** cautious. If it bricks, sounds like a serious pia to fix.
Boot to fastboot and type 'fastboot getvar anti'. If you get a number back, then it's been implemented on your phone. If you get nothing back then it's not yet implemented. It's possible this was just introduced?
If you flashed 9.6.10 successfully, try above command and see if it's implemented in that version.
That 2, 3, 4 is just the counter. Once you unlock the bootloader, ARB should be off in Android One phones.
Here's everything you need to know about it:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
ILA said:
That 2, 3, 4 is just the counter. Once you unlock the bootloader, ARB should be off in Android One phones.
Here's everything you need to know about it:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Click to expand...
Click to collapse
From the Frequently Asked Questions at the bottom of said article:
<quote> Why doesn’t Xiaomi disable anti-rollback protection when you unlock the bootloader?
That’s a good question. </quote>
In Other Words: the article indicates it does not disable ARB after an unlock. Where do you get that it's disabled on their Android One devices? Because the article doesn't say that. I certainly hope it's true though.
Maybe someone with an unlocked bootloader can verify the fastboot query does not return a number?
AsItLies said:
From the Frequently Asked Questions at the bottom of said article:
<quote> Why doesn’t Xiaomi disable anti-rollback protection when you unlock the bootloader?
That’s a good question. </quote>
In Other Words: the article indicates it does not disable ARB after an unlock. Where do you get that it's disabled on their Android One devices? Because the article doesn't say that. I certainly hope it's true though.
Maybe someone with an unlocked bootloader can verify the fastboot query does not return a number?
Click to expand...
Click to collapse
From here:
"The biggest difference between Google and Xiaomi’s implementation is that Google’s anti-rollback protection is disabled if you unlock the bootloader while Xiaomi’s can’t be disabled. Once you install a build with anti-rollback protection enabled on a Xiaomi device, there’s no going back.
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
Ok, so the XDA app just misfired and didn't post my (very) lengthy explanation... Will post tomorrow, I'm just too tired to re-explain again :/
I have a mobile Mi A2 that does not exit from the edl mode
AsItLies said:
Didn't see this thread (need to del the one I started just now), but yeah, mine also says '2'.
Sad to see that, didn't think the A2 would have this.
Click to expand...
Click to collapse
I have a mobile Mi A2 that does not exit from the edl mode and this is due to the installation of the ROM Mi 6X and urged that when I tried to restore it to the original ROM on Android, and if I repeatedly tried to restore it in more than one way, but to no avail, it does not exit from the edl mode even if before flashing
Ahmed 2009 said:
I have a mobile Mi A2 that does not exit from the edl mode and this is due to the installation of the ROM Mi 6X and urged that when I tried to restore it to the original ROM on Android, and if I repeatedly tried to restore it in more than one way, but to no avail, it does not exit from the edl mode even if before flashing
Click to expand...
Click to collapse
your problem is you can't return to mi A2 jasmine android 1 ..NEVER AGAIN ..you can only flash LATEST stock MIUI rom fastboot via miflash when edl ...or you can use custom rom after recovering phone ..search for my other posts on how to do it .
Sent from my wayne using XDA Labs
Related
Is root available for this device yet? i see that the kernel sources are already released by Honor.
I tried a lot but wasn´t able to install root yet. I killed me recovery though...
iroot and one-click-root don´t work yet. There is no wroking twrp. One thing I didn´t try yet is Framaroot.
phh's treble rom has root. our phone is treble-ready since it came with 8.0 out of the box.
gonna give it a shot. dont like emui anyway. too iphone-like
Do we have any developer for honor 9 lite??
https://forum.xda-developers.com/pr...opment/experimental-phh-treble-t3709659/page1
here is your root and also phh shows some interest in the honor 9 lite.
as a bonus u get clean aosp android with substratum and everything.
every one-click root solution is a hacky mess relying on some exploit. nothing i would ever do to my devices
Root
4RK4N said:
https://forum.xda-developers.com/pr...opment/experimental-phh-treble-t3709659/page1
here is your root and also phh shows some interest in the honor 9 lite.
as a bonus u get clean aosp android with substratum and everything.
every one-click root solution is a hacky mess relying on some exploit. nothing i would ever do to my devices
Click to expand...
Click to collapse
Were you able to install the rom?It says that the boot loader needs to be unlocked . If yes, is your model Indian or Chinese?
adriansiv said:
Were you able to install the rom?It says that the boot loader needs to be unlocked . If yes, is your model Indian or Chinese?
Click to expand...
Click to collapse
im running the rom for 4 days now with no problem except bluetooth not working which i dont use anyway.
bootloader unlocking is no problem. just make a huawei id and fill the unlocking webform to get your unlocking code. go to developer settings, enable "oem unlock" and "usb debugging", get "minimal adb and fastboot" working on your pc, plug phone into pc, change to "transfer files" on the phone if you are on charging only mode, open minimal adb and fasstboot on your pc, in the cmd prompt do "adb reboot-bootloader", wait for the phone to go bootloader mode (grey screen with green android and some text), do "fastboot oem unlock unlock_password" on the command prompt and accept on the phone. all your data is lost now btw.
just google smth like "honor bootloader unlock" if u need more details.
about flashing: go into bootloader again, do
Code:
fastboot flash system "C:\path\to\downloaded\system.img"
after that do: "fastboot format userdata" and "fastboot format cache" and reboot. if something crashes during android setup: reboot into recovery (volume up + power) and factory reset. if it still crashes do it again and maybe reflash. took me about 5 attempts. glhf.
oh and i have the european model i think. LLD-L31 3gb ram 32 gb storage. purchased via german amazon website. next day prime delivery so i doubt its imported.
Sent from my Honor 9 Lite using XDA Labs
4RK4N said:
im running the rom for 4 days now with no problem except bluetooth not working which i dont use anyway.
bootloader unlocking is no problem. just make a huawei id and fill the unlocking webform to get your unlocking code. go to developer settings, enable "oem unlock" and "usb debugging", get "minimal adb and fastboot" working on your pc, plug phone into pc, change to "transfer files" on the phone if you are on charging only mode, open minimal adb and fasstboot on your pc, in the cmd prompt do "adb reboot-bootloader", wait for the phone to go bootloader mode (grey screen with green android and some text), do "fastboot oem unlock unlock_password" on the command prompt and accept on the phone. all your data is lost now btw.
just google smth like "honor bootloader unlock" if u need more details.
about flashing: go into bootloader again, do
Code:
fastboot flash system "C:\path\to\downloaded\system.img"
after that do: "fastboot format userdata" and "fastboot format cache" and reboot. if something crashes during android setup: reboot into recovery (volume up + power) and factory reset. if it still crashes do it again and maybe reflash. took me about 5 attempts. glhf.
oh and i have the european model i think. LLD-L31 3gb ram 32 gb storage. purchased via german amazon website. next day prime delivery so i doubt its imported.
Sent from my Honor 9 Lite using XDA Labs
Click to expand...
Click to collapse
Hi 4RK4N,
Thanks for your detailed how to for project treble, that will be a good plan b for me. For reasons like xposed and stuff, what I try to achieve is working twrp and root. Since I bought mine in german amazon too, I think we're talking about the same model (LLD-L31). All I could find except one click root crap is an article on theleaker. Since this is my first post here i'm not allowed to link it. Guy claims after unlocking bootloader, twrp and root both working fine.
unlock-bootloader-install-twrp-root-huawei-honor-9-lite/
After theleakerdotcom ;
Have u or has anyone else owning the european honor 9 lite tried that method, or is it just click bait?
RobertBart said:
im running the rom for 4 days now with no problem except bluetooth not working which i dont use anyway.
bootloader unlocking is no problem. just make a huawei id and fill the unlocking webform to get your unlocking code. go to developer settings, enable "oem unlock" and "usb debugging", get "minimal adb and fastboot" working on your pc, plug phone into pc, change to "transfer files" on the phone if you are on charging only mode, open minimal adb and fasstboot on your pc, in the cmd prompt do "adb reboot-bootloader", wait for the phone to go bootloader mode (grey screen with green android and some text), do "fastboot oem unlock unlock_password" on the command prompt and accept on the phone. all your data is lost now btw.
just google smth like "honor bootloader unlock" if u need more details.
about flashing: go into bootloader again, do
Hi 4RK4N,
Thanks for your detailed how to for project treble, that will be a good plan b for me. For reasons like xposed and stuff, what I try to achieve is working twrp and root. Since I bought mine in german amazon too, I think we're talking about the same model (LLD-L31). All I could find except one click root crap is an article on theleaker. Since this is my first post here i'm not allowed to link it. Guy claims after unlocking bootloader, twrp and root both working fine.
unlock-bootloader-install-twrp-root-huawei-honor-9-lite/
After theleakerdotcom ;
Have u or has anyone else owning the european honor 9 lite tried that method, or is it just click bait?
Click to expand...
Click to collapse
most likely clickbait. there is no twrp (yet) for our device. the one linked in that article is for huawei p9 lite. that one will most likely brick your phone. found other articles with the exact same text and another wrong recovery.
if that recovery would be the correct one for our device, the supersu.zip would work.
phh explicitely advises against using magisk with this rom btw.
currently your only real option for rooting this phone is phh's treble rom in the pre-rooted version (with phhsuperuser btw).
Sent from my Honor 9 Lite using XDA Labs
4RK4N said:
most likely clickbait. there is no twrp (yet) for our device. the one linked in that article is for huawei p9 lite. that one will most likely brick your phone. found other articles with the exact same text and another wrong recovery.
if that recovery would be the correct one for our device, the supersu.zip would work.
phh explicitely advises against using magisk with this rom btw.
currently your only real option for rooting this phone is phh's treble rom in the pre-rooted version (with phhsuperuser btw).
Sent from my Honor 9 Lite using XDA Labs
Click to expand...
Click to collapse
Thanks again, this time for bewaring me from bricking my device . That was too good to be true.
Since u mentioned bluetooth is not working in treble rom and as there's no twrp, meaning no chance for xposed, I guess waiting for the awesome xda community is my only option now.
But maybe I give it a shot in case that needs too long
Cheers
When there will be root and twrp for honor 9 lite
Mitch fulcher said:
When there will be root and twrp for honor 9 lite
Click to expand...
Click to collapse
Once we get the full Firmware release for our device then we will have TWRP and root... Till then wait
please try this method, it's easy and easy to recover if you got it brick.
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
I'm on Mi A2 pie stable ..as expected xiomi not enabled camera2api still...if anyone has found any method for enabling camera 2 api on pie stable rom please help me...
It would be nice if someone can upload boot.img from latest pie, so we can patch it with magisk to gain root. After that we can edit build.prop to enable camera2 api.
Sent from my Mi A2 using Tapatalk
Mr.Nice.ba said:
It would be nice if someone can upload boot.img from latest pie, so we can patch it with magisk to gain root. After that we can edit build.prop to enable camera2 api.
Click to expand...
Click to collapse
The beta image is the same as the stock image. The beta patched boot.img has already been uploaded. Check the forums.
I read today this on searching in google to enable camera2api without root in mia2..
I'm in feb update (india).
I downloaded these patch boot file & trying to go in fastboot mode..
But when i connect my phone to laptop (windows 7), there is connecting sound i heard ..
I enabled already oem unlocking option & usb debugging in phone through tapping 7 times & all ..
But when after inserting commands in adb & entered , it's saying waiting for device..
& Nothing is shown in screen in mi a2 , other than fastboot bunny..
Can anyone help me what's going on wrong here ?
Link of that site :
https://www.the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
The *** is putted by xda automatically in link..
In actual in place of *** it is 'the custom Android' (without space)
Appar khandelwal said:
I read today this on searching in google to enable camera2api without root in mia2..
I'm in feb update (india).
I downloaded these patch boot file & trying to go in fastboot mode..
But when i connect my phone to laptop (windows 7), there is connecting sound i heard ..
I enabled already oem unlocking option & usb debugging in phone through tapping 7 times & all ..
But when after inserting commands in adb & entered , it's saying waiting for device..
& Nothing is shown in screen in mi a2 , other than fastboot bunny..
Can anyone help me what's going on wrong here ?
Link of that site :
https://www.the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
The *** is putted by xda automatically in link..
In actual in place of *** it is 'the custom Android' (without space)
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
Have you installed adb drivers?
mariosenta said:
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766
Have you installed adb drivers?
Click to expand...
Click to collapse
It's already in pc earlier.. let me reinstall it
Appar khandelwal said:
It's already in pc earlier.. let me reinstall it
Click to expand...
Click to collapse
Usually drivers create this problem
mariosenta said:
Usually drivers create this problem
Click to expand...
Click to collapse
Did you try any custom rom in MI A2 yet ?
Appar khandelwal said:
Did you try any custom rom in MI A2 yet ?
Click to expand...
Click to collapse
No, not yet, just enabled camera2api folowing tutorial from the link above.
mariosenta said:
No, not yet, just enabled camera2api folowing tutorial from the link above.
Click to expand...
Click to collapse
How's the camera quality after camera2api...
& Does using temporary root method also format phone data ?
Appar khandelwal said:
How's the camera quality after camera2api...
& Does using temporary root method also format phone data ?
Click to expand...
Click to collapse
With pixel camera, quality is superb. As for stock its a little better after the march update. Yes, it formated data but you have a tutorial for botloader unlock and rot without losing data.
mariosenta said:
With pixel camera, quality is superb. As for stock its a little better after the march update. Yes, it formated data but you have a tutorial for botloader unlock and rot without losing data.
Click to expand...
Click to collapse
Where is the tutorial ?
I'm not unlocking bootloader..
Just temporary rooting phone & unrooting on restart.
& Where to find these pixel camera ?
& March update already rolled back because of many bugs like always ..
Appar khandelwal said:
Where is the tutorial ?
I'm not unlocking bootloader..
Just temporary rooting phone & unrooting on restart.
& Where to find these pixel camera ?
& March update already rolled back because of many bugs like always ..
Click to expand...
Click to collapse
Well if you are just rooting, you wont lose data, you just need patched boot image to flash with cmd. You have tutorial in link I sent you, just skip the part with unlocking bootloader, and folow tutorial. You have all of needed tutorial here on xda, just dig a little.
Yeah i'm doing the same...
Just booting the patched image..
What about pixel camera ?
Do you have link for downloading that apk ?
Appar khandelwal said:
Yeah i'm doing the same...
Just booting the patched image..
What about pixel camera ?
Do you have link for downloading that apk ?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_BSG_Arnova_TlnNeun_V1.3.030119.0645.apk
But i think you will need to unlock bootloader for this to work
mariosenta said:
https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_BSG_Arnova_TlnNeun_V1.3.030119.0645.apk
But i think you will need to unlock bootloader for this to work
Click to expand...
Click to collapse
Yeah i did & it worked...
Adb drivers were missing for mi a2..
But for booting image it asked for unlocking bootloader..
But if i did this then i'm afraiding to lose data & warranty
Appar khandelwal said:
Yeah i did & it worked...
Adb drivers were missing for mi a2..
But for booting image it asked for unlocking bootloader..
But if i did this then i'm afraiding to lose data & warranty
Click to expand...
Click to collapse
This is for mi a2 lite, dont know if it work for a2 version https://www.google.com/amp/s/forum....ow-to-unlock-bootloader-erasing-t3878453/amp/
mariosenta said:
There is another way to unlock bootloader without wiping data, i saw it here on xda, just dig a little, bro. Explore
Click to expand...
Click to collapse
Did you left bootloader unlocked ?
Are you getting updates without locking it ?
Appar khandelwal said:
Did you left bootloader unlocked ?
Are you getting updates without looking it ?
Click to expand...
Click to collapse
Yeah, bro, all is working well. Updated to March OTA.
No problem so far. Just backup for safe reasons
mariosenta said:
Yeah, bro, all is working well. Updated to March OTA.
No problem so far. Just backup for safe reasons
Click to expand...
Click to collapse
March update already rolled back..
Okay i'll try that method to unlock bootloader..
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here, rest has been found and shared by me.
As the instructions and Qualcomm drivers are already available here , I don't feel a need to rewrite them.
You can ask questions here on how to use and issues, however I might not be able to answer immediately.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
OOS 9.0.4
OOS 9.0.5
OOS 9.0.6
OOS 9.0.11
OOS 9.0.12
OOS 9.0.13
OOS 9.0.15
OOS 9.0.16
ANDROID 10:
OOS 10.3.0
OOS 10.3.2
OOS 10.3.5
OOS 10.3.7
OOS 10.3.8
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Notes for T-Mobile version owners:
It is possible to use Pie EDL packages with patched tool made by @AnonymousTipster available at https://drive.google.com/open?id=1dYuVxnf_J97KPrRt6KEBOjau1BRvtnJQ (download link come from his thread ).
According to @fullofhell , the commands "fastboot erase modemst1" and "fastboot erase modemst2" will turn off SIM lock definitely and allow OEM unlock option to stop being greyed out in developer options (behaviour introduced in OOS versions superior to 9.0.11). That will allow to unlock bootloader and then root/flash custom roms.
Credits:
@Titokhan for giving advice on how to present thread
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost
@AndroidFileHost for the hosting
OnePlus for the device and OS
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I managed to find out 9.0.12 one (which is as of writing the latest available) but also the first one released for OOS 9.0.4 and linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here
You can find instructions and Qualcomm drivers here.
This is not a support thread: if you have questions on how to use tool or issues please ask in the relevant thread.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
DECRYPTED OOS 9.0.12
DECRYPTED OOS 9.0.11
DECRYPTED OOS 9.0.6
DECRYPTED OOS 9.0.5
DECRYPTED OOS 9.0.4
Click to expand...
Click to collapse
Decrypted. Wot?
ZeroKool76 said:
Decrypted. Wot?
Click to expand...
Click to collapse
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Some_Random_Username said:
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Click to expand...
Click to collapse
Awesome. Thank you for the clarification
Added 9.0.13 unbrick tool
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Some_Random_Username said:
Added 9.0.13 unbrick tool
Click to expand...
Click to collapse
Where is it?!
gasroca said:
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Click to expand...
Click to collapse
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
kermex said:
Where is it?!
Click to expand...
Click to collapse
In the first post perhaps?
Some_Random_Username said:
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
In the first post perhaps?
Click to expand...
Click to collapse
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Some_Random_Username said:
In the first post perhaps?
Click to expand...
Click to collapse
That DECRYPTED OOS 9.0.13 link?
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Thanks man
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
kermex said:
That DECRYPTED OOS 9.0.13 link?
Click to expand...
Click to collapse
Yes
fullofhell said:
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Click to expand...
Click to collapse
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Click to expand...
Click to collapse
Yeah thanks. I've managed to fix it after almost 2 days of messing about with it its now back to normal ?
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Yes
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Click to expand...
Click to collapse
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
Click to expand...
Click to collapse
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
xstefen said:
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
Click to expand...
Click to collapse
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
fullofhell said:
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
Click to expand...
Click to collapse
I typically run Arch or a derivative but its all the same, I'd help with whatever I could.
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
Click to expand...
Click to collapse
Just to be sure, that engineer mode can be accessed from *#808# and SIM lock section is when swiping to the right, in "Others column"? It is like that on my 5T (see screenshot) but I don't know if it's same on a converted 6T
Here's the Android 8 Oreo image for the Mi A2 Lite:
bigota.d.miui.com/V9.6.11.0.ODLMIFF/daisy_global_images_V9.6.11.0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
And here's the Android 9 Pie image:
bigota.d.miui.com/V10.0.13.0.PDLMIXM/daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz
Currently I am running the Oreo image. Not sure if that's important, but "anti" is blank and "rollback_ver" is "1".
As far as I understand, if I were to flash the Android 9 image, I would not be able to go back to Android 8, correct?
I know that xiaomi.eu images have ARB removed, but I don't think they have the Android One images.
Can I remove ARB from the above image myself?
Is it simpler to write a question than search and read answers?
I am sure that "fastboot getvar anti" returns "1" in MiA2 stock AndroidOne Oreo, Pie and Q.
ARB is initiated > 1 for MiA2 when someone flashes MIUI ports without substituting corresponding fiiles in ROM image.
Aerobatic said:
Is it simpler to write a question than search and read answers?
Click to expand...
Click to collapse
In fact it is not. I did a quite extensive search before I asked the question. Unfortunately I found no post that answers my questions. I read something about removing the "firmware-update" directory, but my images don't have that to begin with. Most guides I found refer to MIUI images (and usually start with the Mi Unlock Tool) and don't seem to apply to Android One images (where the bootloader can simply be unlocked with fastboot) either.
Aerobatic said:
I am sure that "fastboot getvar anti" returns "1" in MiA2 stock AndroidOne Oreo, Pie and Q.
Click to expand...
Click to collapse
It's a Mi A2 lite running the Oreo image from above and I have attached a screenshot of its fastboot answers.
Aerobatic said:
ARB is initiated > 1 for MiA2 when someone flashes MIUI ports without substituting corresponding fiiles in ROM image.
Click to expand...
Click to collapse
That's my question: Which files I have to substitute in the images?
AndreKR said:
In fact it is not. I did a quite extensive search before I asked the question. Unfortunately I found no post that answers my questions. I read something about removing the "firmware-update" directory, but my images don't have that to begin with. Most guides I found refer to MIUI images (and usually start with the Mi Unlock Tool) and don't seem to apply to Android One images (where the bootloader can simply be unlocked with fastboot) either.
It's a Mi A2 lite running the Oreo image from above and I have attached a screenshot of its fastboot answers.
That's my question: Which files I have to substitute in the images?
Click to expand...
Click to collapse
If you did a quite extensive search before you asked the question, you would know that only miui have arb, not android one, so no need to delete anything if you want to go back to older versions.
mariosenta said:
If you did a quite extensive search before you asked the question, you would know that only miui have arb, not android one, so no need to delete anything if you want to go back to older versions.
Click to expand...
Click to collapse
Ah, that's great. I found some confusing information, that's why I asked.
For example this guy tries to flash an Android One image after he was using a different one (he doesn't say which one) and gets bitten by ARB:
xiaomi.eu/community/threads/how-can-i-recovery-the-bricked-xiaomi-mi-a2.53447/
Also as I read, with Android 9 ARB is mandatory while the bootloader is locked, so it wasn't clear to me if Xiaomi uses the same ARB mechanism for that.
Hello, while debloating the MIUI I accidentally removed com.xiaomi.finddevice that resulted in MIUI spamming toasts "Find device was destroyed". I learned later that I would had got a bootloop if I rebooted then. After this, I reinstalled finddevice with pm install-existing, got a single "Find device stopped unexpectedly" toast and that was all. MIUI looks like working normally now, I even got a push notification prompting to enable Find Device. I'd like to know if the system is fixed now and I can reboot safely or not? I don't have the bootloader unlocked yet so it would be difficult to recover after that bootloop, or Xiaomi device lock, or whatever could happen.
Now I have these packages that look like crucial enabled:
Code:
galahad:/ $ pm list packages -e | grep -E "security|find|account"
package:com.xiaomi.account
package:com.miui.securityadd
package:com.miui.securitycenter
package:com.miui.securitycore
package:com.xiaomi.finddevice
package:com.lbe.security.miui
Are there any other packages that I need to install? Thanks.
Try to flash the MIUI again
VD171 said:
Try to flash the MIUI again
Click to expand...
Click to collapse
Thanks for reply. How should I do it, with Mi Flash?
Also I'm waiting for the bootloader unlock timer, Mi Unlock says that I shouldn't log out of my Mi Account as the timer will reset. Would reflashing reset that timer too? Or maybe I should first wait for unlock timer to timeout without rebooting and then try to perform any actions?
cyanog33n said:
Thanks for reply. How should I do it, with Mi Flash?
Also I'm waiting for the bootloader unlock timer, Mi Unlock says that I shouldn't log out of my Mi Account as the timer will reset. Would reflashing reset that timer too? Or maybe I should first wait for unlock timer to timeout without rebooting and then try to perform any actions?
Click to expand...
Click to collapse
I suggest you to wait for the time and then unlock bootloader first.
With unlocked bootloader, you can do anything you want to the device.
If you want to backup the state of the unlocked bootloader, just follow my guide:
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
It works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G - Probably some others Xiaomi devices How to backup: Step 1: Unlock your bootloader. Step 2: Backup partition: seccfg You can backup it using the SP FLASH TOOL, TWRP or copy it with...
forum.xda-developers.com
VD171 said:
I suggest you to wait for the time and then unlock bootloader first.
Click to expand...
Click to collapse
Got it, I'll wait. I'm not sure if the unlock would work though, maybe the Mi Account on the phone was corrupted somehow (com.xiaomi.finddevice was probably the only crucial package that I removed, com.xiaomi.account wasn't affected, Mi Account section in Settings looks like working correctly, but I don't know what to expect) and Mi Unlock will possibly refuse to unlock bootloader, however, to check it I need to boot into Fastboot.
cyanog33n said:
Got it, I'll wait. I'm not sure if the unlock would work though, maybe the Mi Account on the phone was corrupted somehow (com.xiaomi.finddevice was probably the only crucial package that I removed, com.xiaomi.account wasn't affected, Mi Account section in Settings looks like working correctly, but I don't know what to expect) and Mi Unlock will possibly refuse to unlock bootloader, however, to check it I need to boot into Fastboot.
Click to expand...
Click to collapse
If you can see the timer, probably everything is okay for unlocking the bootloader.
Your best chance is try.
If you can't unlock bootloader, probably you need to flash the whole MIUI rom again and re-start the process of unlocking again.
Once the timer finish, just attach the screenshots, and I will try to help you
Update: I unlocked bootloader without any problems. Mi Unlock factory resetted my phone and after reboot factory reset protection was triggered, so I entered my google account credentials and got no further problems. Now I've switched to a GSI ROM.
So, if you're willing to debloat your MIUI, I strongly recommend you to do it only with XiaomiADBFastbootTools's Debloater. It doesn't delete packages essential for system and you can reinstall them if something goes wrong. DO NOT REMOVE APPS MANUALLY WITH ADB UNINSTALL OR PM UNINSTALL UNLESS YOU FULLY UNDERSTAND WHAT YOU'RE DOING! If it happened, do not reboot, log into adb shell and use:
pm install-existing <package_name> or
pm enable --user 0 <package_name>