Question Moto X40 CN flashed to EU Problem - Motorola Edge 30 Ultra / Motorola Moto X30 Pro

Hey there,
i flashed my X40 CN to EU without problems and locked the bootloader after. After that i realised that certain features seem to not work properly for me. The peek display doesn't show me any notifications nor is the Edge Lighting working either. I now want to flash back to CN but can't unlock the OEM since it's greyed out for me.
I'd be glad about any help.

Unlocking the bootloader after locking it won't work, so far I understand it's not possible to unlock the bootloader again at the moment.
The only method that would be working is tricking the phone into EDL mode and flashing back to other rom.
This is yet not possible, the only thing we can do is wait for someone to find out how to get the phone into EDL mode.
I'm having a simelar issue (check my thread).

Sheldor_95 said:
Hey there,
i flashed my X40 CN to EU without problems and locked the bootloader after. After that i realised that certain features seem to not work properly for me. The peek display doesn't show me any notifications nor is the Edge Lighting working either. I now want to flash back to CN but can't unlock the OEM since it's greyed out for me.
I'd be glad about any help.
Click to expand...
Click to collapse
Are you still able to install OTA updates? Maybe it will eventually get fixed once a new update comes in OR if Peek Display is updated via PlayStore.

No OTA updates so far. Peek display is working now. After a factory reset and new setup it worked again. Bootloader is still locked and OEM unlock is still greyed out. Hopefully there will be a fix soon. Lenovo rescue is not working , the model XT2301-5 is not supported.

Related

[OTA] Huawei Mate S Firmware C432B321/C900B321 [MM] [Beta] - FRP Unlock enabled!

A few days ago some users enrolled in MM beta program started receiving new B321 OTA, so I flashed it on top of my B303 MM and so far all good.
Apart from feeling really butter smooth and including WPS Office, Developer Options now again include OEM Unlock option(FRP unlock), solving the no bootloader unlock on MM issue.
Be sure to be on B303 MM stock recovery, extract the \dload folder from zip and place it on root of external SD card;
Get into Advanced Project Menu by dialing *#*#2846579159#*#*
Go to the bottom and select "HOTA Update"
Wait for reboot, EMUI will verify, install and optimize -took about 15 minutes, so be patient.
What I noticed is that on B321 Advanced Project Menu is gone, only standard(*#*#2846579#*#*) is available.
B321 OTA Update: https://mega.nz/#!t5EhnBQK!ewPCJtBvSd3kWOc2DBmL83poB8Lo1oXzHSguE2TIWbo
B303 stock recovery: https://mega.nz/#!Q0dhEZ7Q!stOQ_0oHPfXnMVfBZqBDkq1fEyxUJ8Jrt5z2mUcdYMo
hi, in dload folder, we have two files. which one should we use?
put the hole zip into dload and start the hota-update
Hi.
So i updated to this firmware and got the unlock OEM option, and i unlocked it, got into fastboot mode (well the FRP lock screen that showed b4 when i didn't have the oem unlock option). I did the fastboot unlock process with the oem unlock key i got from Huawei website and it said it unlocked sucessfully, but i have no changes, everytime i try to go into bootloader it says that it is FRP locked :/
Any ideas?
johnwickz said:
Hi.
So i updated to this firmware and got the unlock OEM option, and i unlocked it, got into fastboot mode (well the FRP lock screen that showed b4 when i didn't have the oem unlock option). I did the fastboot unlock process with the oem unlock key i got from Huawei website and it said it unlocked sucessfully, but i have no changes, everytime i try to go into bootloader it says that it is FRP locked :/
Any ideas?
Click to expand...
Click to collapse
Isn't FRP unlock different to bootloader Unlock?
Well basicly i get the same screen as if my phone was still FRP locked :s even tho i enabled oem unlock in dev settings..
johnwickz said:
Well basicly i get the same screen as if my phone was still FRP locked :s even tho i enabled oem unlock in dev settings..
Click to expand...
Click to collapse
You must activate the "Unlock OEM" option, reboot into fastboot and make sure you have "FRP: Unlocked" in red text. Once you confirm this use the bootloader unlock key provided by Huawei.
Well for me it says FRP locked :/ even tho i enabled oem unblock.
johnwickz said:
Well for me it says FRP locked :/ even tho i enabled oem unblock.
Click to expand...
Click to collapse
And from that screen have your run the appropriate command in fastboot using CMD in windows and the key you received from Huaweiupdateextractor?
---------- Post added at 04:42 PM ---------- Previous post was at 04:15 PM ----------
Battery consumption seems a little higher on B321...will need to keep an eye on it over the next few days
If you mean bootload unlock key yeah i have done it. Still only screen i get is FRP locked
johnwickz said:
If you mean bootload unlock key yeah i have done it. Still only screen i get is FRP locked
Click to expand...
Click to collapse
If in fastboot screen(picture, maybe?) you have BL unlocked/FRP locked I understand you have previously unlocked BL while on Lollipop and then somehow FRP re-locked again, maybe wrong TWRP restore...
No thats the thing i didnt have BL unlocked when in lollipop
I have managed to update to b321 from b303 version with little / no issue. Everything seems OK apart from a small annoyance - the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
nobbysheep said:
I have managed to update to b321 from b303 version with little / no issue. Everything seems OK apart from a small annoyance - the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
Click to expand...
Click to collapse
I'm not sure if it's a bug but I prefer it without the vibration....I was of the understanding that the bug was that it couldn't be turned off in lollipop so I think if anything it's fix.
Battery drain is my biggest concern... On mobile data it's appalling...can't wait to go back to lollipop
brumgav said:
I'm not sure if it's a bug but I prefer it without the vibration....I was of the understanding that the bug was that it couldn't be turned off in lollipop so I think if anything it's fix.
Battery drain is my biggest concern... On mobile data it's appalling...can't wait to go back to lollipop
Click to expand...
Click to collapse
I've checked this on my honor 7 and seems to work ok (e.g. haptic feedback for navigation buttons works) so I'm pretty sure it's not correct on mate s. I'll try factor reset and see if that cures the problem. - unless anyone else has any better ideas
So I am still on 303. will it be possible to flash the 321, then unlock the bootloader, flash custom recovery and thereafter restore an update of someone that provided a clean lollipop build via twrp?
As long as there isn't official 6.0 I would really like to get back to 5.1.1 xD
But my guess is we I still have to wait for a rollback firmware...
Sent from my OnePlus using XDA Labs
Cris7ianO said:
So I am still on 303. will it be possible to flash the 321, then unlock the bootloader, flash custom recovery and thereafter restore an update of someone that provided a clean lollipop build via twrp?
As long as there isn't official 6.0 I would really like to get back to 5.1.1 xD
But my guess is we I still have to wait for a rollback firmware...
Sent from my OnePlus using XDA Labs
Click to expand...
Click to collapse
Still no rollback works..you need to wait for official rollback update from huawei
Sent from my HUAWEI CRR-L09 using Tapatalk
Is anyone able to make an TWRP Flashable file? =/ i got an bootloop und cant flash over the Stock recovery without dialing the key =/
I need the complete Rom or i´m f**** =/
nobbysheep said:
the haptic feedback for navigation buttons has stopped working. I've checked all settings and all seems OK. This was working fine on b303 so maybe it's a bug? Anyone else experiencing this?
Click to expand...
Click to collapse
This error was also in lollipop version. try to switch it off in settings reboot and the switch on again and reboot and it should work like you want.
bgx said:
This error was also in lollipop version. try to switch it off in settings reboot and the switch on again and reboot and it should work like you want.
Click to expand...
Click to collapse
@bgx thanks for suggestion. Tried that and still no joy. I suspect it's a bug tbh. I'll try a factory reset tomorrow and see if that cures the problem. Not a massive problem but annoying as hell.

Bootloop after recent Android OTA Update

Hello Community,
i have a Problem after the installation of the newest android Update (OTA).
The A2 just Boot till the white AndroidOne Logo and it hangs there after a time it seems it shut down itself.
My Device:
-USB Debugging is disabled, its a new testing device.
-I cant boot in recovery mode (vol-UP+Power) just boots to the white androidOne Screen and there it hangs
- I can enter fastboot(VOL-Down+power) mode and the device is listed when i type fastboot devices in my terminal on pc
- when i fire up MiFlash tool it list my device after clicking refresh, if i want flash the latest FW (http://en.miui.com/download-353.html) i get the error:
error:"Flash bluetooth_a error"
- My bootloader is locked.
Question:
How can I flash a offical Android with a locked bootloader?
is it a good idea? or better send it back for a warranty solution (i dont want wait)
is there another way to solve my problem? i really dont know whats the problem is. i did not rooted the device or anything.
would be lovely if someone could help me. with an instruction what i can try.
Thank you very much and have a nice day
Regards
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
wow really? that are bad news...
thank you anyway :crying:
maybe someone other got a idea?
regards
Lot of users faced this after today's update including myself. Since my bootloader is locked, only option left is EDL flashing by connecting motherboard test points.
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Abrilabr said:
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Click to expand...
Click to collapse
Yea, but if you want use it as enterprise Device the open Bootloader is a problem.
ilyas111 said:
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Click to expand...
Click to collapse
that seems not possible with a locked Bootloader (very new phone)
or can you provide a working solution with a locked bootloader? i wont use this EDL thing because its just new and i dont want open it.
Thank you all anyways
Try with this tool : https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
(edl included)
Same trouble here, we are fu...ed!
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
xotob said:
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
Click to expand...
Click to collapse
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Reptant said:
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
Click to expand...
Click to collapse
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
boonc said:
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
Click to expand...
Click to collapse
Same problem here, does anyone have a solution?
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
ilyas111 said:
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
Click to expand...
Click to collapse
yes, but i cant use more of fastboot comands, cause bootloader is locked, cant use "flashing unlock/unlock_critical"
Cizzle4 said:
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Click to expand...
Click to collapse
I'm in your same situation
Exactly the same situation here... Waiting for a solution without losing warranty.
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
UnlimitedBB said:
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
Click to expand...
Click to collapse
I can understand that. I will claim warranty because its new and i dont want do that test point thing.
on private i would buy and recommend xiaomi anyways but if you want these hardware for some enterprise things then better not.
Iam out of this Thread now but if you want talk here some more feel free.. maybe somebody can bring a solution for all you guys who face this problem but i think its not possible without a open BL or the TestPoint Method.
Regards and have a nice day
Hi. I'm with locked bootloader. I received new January update. No change - stock variant updated to Pie. So it's safe to update or waiting for new one? Mi A2 4/64 micron ram

ReUnlocking converted A2 (6X)

I have a converted A2 (+ARB 4), with UNLOCKED bootloader.
I read somewhere if you relock the BL , you will not able to UNLOCK it again ever after! (is it true?)
and other thing: If it try the MIUI BL Unlocker Official Application to unlock my device (even when it is still unlocked) what could be happen? (I've just followed the steps till the warning msg: "Unlocking Bootloader will erase user Data" ). (I read somewhere else that for unlocking miui devices you need to submit the request and you need to wait for a long time to get the code, and I was going to get the code for a case of necessity in future.)
I need to know how far I can play with these stuffs on my devices and left a practical way to recover a Bricked phone. ( I consider even TEST POINT as a practical option [tried once and it is damn easy and fun ] )
Im sorry bro but the actual model and serial code of your phone is a A2.And that means you probably wont unlock it it will give a hardware error.But pls try it and report.Dont worry there will be a fix!!
Tech_jetoncesaj said:
Im sorry bro but the actual model and serial code of your phone is a A2.And that means you probably wont unlock it it will give a hardware error.But pls try it and report.Dont worry there will be a fix!!
Click to expand...
Click to collapse
If it locked again my BL, what would be the solution? I didn't find any.
the mi unlock app requires a mi account with unlock permissions (account! not phone)
if you try to unlock an unlocked a2 you should either get unsuported - it's meant for miui devices - or already unlocked.
The app first checks the account and passes to further steps, then recognizes my phone, and warns me about wiping Data. ( At this step I declined and closed the app)
Your hypothesis seems correct, but if in any circumstances I would be left with relocked converted A2 , ist there any chance to reunlock it again?
that's why the test point method exists, for locked that you try to fastboot flash
I tried, and it just says: Device Unlocked, no need to reunlock again!
So now is it safe to lock my bootloader and try the app again?
if you lock the bootloader via fastboot commands it wont boot any more.
only way to safely lock is with miflash and you cannot miflash a wayne miui on a converted a2. it will see that it's the jasmine.
if you miflash the a2 fastboot rom it will relock ok - if the flashing works...might not cuz of the arb - but you wont be on miui any more.
what are you trying to do anyway?
i think what you dont understand is the unlock on miui and android one are the same end result but different steps. for miui you godda use the mi unlock, for and1 its just the dev options switch
laviniu_c said:
if you lock the bootloader via fastboot commands it wont boot any more.
Click to expand...
Click to collapse
So if I run the command and re-lock it by Fastboot, how can I re-unlock it again?
laviniu_c said:
only way to safely lock is with miflash and you cannot miflash a wayne miui on a converted a2. it will see that it's the jasmine.
if you miflash the a2 fastboot rom it will relock ok - if the flashing works...might not cuz of the arb - but you wont be on miui any more.
Click to expand...
Click to collapse
So do you mean there is no safety way to re-lock a converted A2 which runs MIUI ?
(and If I had a Banking app which needs a Locked BL to work, there will be no chance to run it at all?)
laviniu_c said:
what are you trying to do anyway?
Click to expand...
Click to collapse
As I said I want to know all the aspects of practical ways to deal with my phone, right now I am totally happy with it, but actually the opportunity of dealing with all these technical stuffs convinced me to buy this phone.
laviniu_c said:
i think what you dont understand is the unlock on miui and android one are the same end result but different steps. for miui you godda use the mi unlock, for and1 its just the dev options switch
Click to expand...
Click to collapse
I've heard that some ROMs may re-lock the phone, since then I would like to know if in any circumstances I would be stuck on that situation how can I re-unlock my phone.
any official miui rom that has the firmware folder in it might do it for example, so will bad ports....
try to use the magisk hide options to fix the banking app, add it to the list of apps for which it specifically hides root. add also the google services and make sure you pass the safetynet tests and your device shows as certified in the playstore settings. i think there were some modules to fix the bl check
laviniu_c said:
any official miui rom that has the firmware folder in it might do it for example, so will bad ports....
Click to expand...
Click to collapse
So lets assume it has been happened, what would be the procedure to rescue my phone? since as you said if the BL locked again it will not boot to OS.
laviniu_c said:
try to use the magisk hide options to fix the banking app, add it to the list of apps for which it specifically hides root. add also the google services and make sure you pass the safetynet tests and your device shows as certified in the playstore settings. i think there were some modules to fix the bl check
Click to expand...
Click to collapse
I would'nt like to root the phone, isn't there any other option?
if you lock the bootloader with any kind of non official rom for your phone (i.e. jasmine_sprout) which in your case is android one it wont boot. the end. only way out of that is the edl mode and miflash. that's the basic difference between locked and unlocked, it checks what os it loads and it makes sure the loaded os is the official rom for the phone. converting the a2 means it needs to be unlocked and you load a rom that's a ported miui10 from wayne to jasmine_sprout. if you flash the full rom, that has the locked bootloader from wayne which will fail to start since:
1 - the phone still isnt wayne
2- the rom isnt quite the official one (since it's renamed to work on jasmine)
3 - even if the phone was fully wayne, you dont really want the official mi 6x rom since that's china only. i.e. no google services
the only unknown in all this is the ARB, but edl should ignore that.
somehow i was under the impression you already have magisk (root/hide) up and running on the converted miui 10. yes, there are good miui 10 ports (for example xiaomi.eu) that give you the miui experience on a2 except they will never have the full ota support that the official rom has.
my advice? stick to the stock a2 rom. locked and full stock. the moment you need to start experimenting is when the android one support stops OR if you really want root.
if you wanted miui and you're outside china, mi 6x is still NOT the way to go. cuz it doesnt have an official global rom anyway. i dont get why everyone is jumping through hoops to get unofficial roms installed with stock support available.
laviniu_c said:
if you lock the bootloader with any kind of non official rom for your phone (i.e. jasmine_sprout) which in your case is android one it wont boot. the end. only way out of that is the edl mode and miflash.
Click to expand...
Click to collapse
So please consider these situations:
The phone is A2 converted to 6X &
The BL has been re-locked &
ARB 4 has been triggered
how can I use EDL mode to unlock it?
(I think miflash would not help because the LOCKED BL and the phone is actually A2)
(I think also Fastboot wont be able to unlock it since it is A2 Converted to 6X)
laviniu_c said:
yes, there are good miui 10 ports (for example xiaomi.eu) that give you the miui experience on a2 except they will never have the full ota support that the official rom has.
Click to expand...
Click to collapse
I'm afraid but I didt't get the point, now every week I receive Pie beta updates (besides there are stable versions too) which actually stable enough, almost Bug & Lag Free (it differs Rom to Rom, but believe me it is COOL ) , and by PitchBlack you can use direct update. (I prefer to install it by myself since I LOVE TWRP & its child PB). so what exactly we miss of original OTA service of XIAOMI?
laviniu_c said:
my advice? stick to the stock a2 rom. locked and full stock. the moment you need to start experimenting is when the android one support stops OR if you really want root..
Click to expand...
Click to collapse
But I think it wouldn't be an option for who has triggered ARB4! isn't it? (I read when you got ARB4 you must forget AndroidOne! even TestPoint won't help)
laviniu_c said:
if you wanted miui and you're outside china, mi 6x is still NOT the way to go. cuz it doesnt have an official global rom anyway. i dont get why everyone is jumping through hoops to get unofficial roms installed with stock support available.
Click to expand...
Click to collapse
Again I didn't get what do you mean, could you please explain it a bit more? (since my current MIUI 10.4 has almost everything)
http://bigota.d.miui.com/V10.0.2.0....0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tgz this should work with the testpoint/edl method and miflash. (unless arb does something to stop it)
there's a few problems with your approach.
1) not official. any time the guys maintaining the custom rom can decide to stop producing it.
2) all work into these custom roms is voluntary. are they sometime better? sure, never said they werent but again, xiaomi/google/android have far far more resources at their disposal and while the phone is under the official period it will be maintained.
3) did you bother to read the first lines in any custom rom? they take 0 responsibility for whatever happens to your phone. they do not intend to break it, but they dont have to support you if you're in trouble either. if you dont have a valid warranty, that's understandable, you don't lose anything. but guess what? there are official vendors for xiaomi all over the world, offering official warranty. that holds as long as you're on STOCK.
4) though most custom roms are well intended, there is nothing assuring you there's nothing inside there that you dont want installed. you move your trust from xiaomi/google/android (which you can hold accountable) to whoever made that rom (who just carpet say, it's your phone you're doing the flashing, anything happens you're on your own). in most cases those devs don't mean harm, but they could and there's nothing to stop them (and they would never put in the hours of work if there was accountability for their action - i perfectly understand them. it's sortof like, i can try to do this, but because my work is not paid for by the end user they do not have any hold over me. it's correct and yet at the same time it's very very dangerous.). ever seen a custom miui built by a shop? i have, it's packed full of junk, bugs and malware. another thing here is testing. the official rom goes through a bunch of tests/beta versions. not saying it's perfect but it's better then the "known bugs: you tell me". custom rom devs cannot do it any other way, they dont have the time to test or the team to test.
5) the official devs don't have this option, they have a job and do it. it's a completely different approach.
this is not a rant against custom rom devs, i understand them 100%, they're trying to help. what i'm saying is there's always 2 sides to each story. there's no right or wrong, there's just what's best for each user. some of us will want the safe and easy way of the stock roms. some will want custom roms. in the end everyone is doing what they choose with their phone.
laviniu_c said:
http://bigota.d.miui.com/V10.0.2.0....0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tgz this should work with the testpoint/edl method and miflash. (unless arb does something to stop it)
Click to expand...
Click to collapse
I think it will not work, the Actual duty of ARB4 is to preventing you to use these things! as much as I know after ARB4 you have two options: MIUI 10 or custom ROMs such as Havoc or so, for AndroidONE we need to wait a version of AndroidONE which be compatible with ARB4! otherwise flashing STOCK AndroidONE will simply brick your phone! THE whole IDEA of this THREAT is this!
And BTW as much as I know XIAOMI.EU is cooperating now with the XIAOMI ! besides we do not keep a phone for a whole life time, 2-3 years of supports would be far enough. and they do offer it right now!
and I would like to lock the BL for further security reasons but it seems to be impossible so far otherwise someone suggests a practical way for it.
I guess you need to contact me.
sz.hatef said:
If it locked again my BL, what would be the solution? I didn't find any.
Click to expand...
Click to collapse
Hey its not very good to talk here in xda.We can try some methods!
Chat with me in telegram.
 @blackgryphon1
Dont worry about brick,bcz im the only one who can unbrick,downgrade a xiaomi phone even if its arb4.
Feel free to contact me.
Also join my group i will be there too.
Since i cant post links,search this on telegram <<its my group>><<iT HAS A BLACK PHONE WALLPAPER AND IT HAS 86 MEMBERS!
Mi A2 & Mi 6X
Tech_jetoncesaj said:
Hey its not very good to talk here in xda.We can try some methods!
Chat with me in telegram.
@blackgryphon1
Dont worry about brick,bcz im the only one who can unbrick,downgrade a xiaomi phone even if its arb4.
Feel free to contact me.
Also join my group i will be there too.
Since i cant post links,search this on telegram <<its my group>><<iT HAS A BLACK PHONE WALLPAPER AND IT HAS 86 MEMBERS!
Mi A2 & Mi 6X
Click to expand...
Click to collapse
Just as I said, I would like to know the possible ways, currently I haven't any problem, could you explain it a bit , how could it possible to reunlock my BL if it get locked on MIUI?
ahem.
There is NO way to unlock an A2 device that has been converted to an 6X with ARB anti 4.
Your bootloaders are important in this case (xbl.elf and abl.elf). ARB and bootloader status is also managed here.
If you are using A2, with 6X system without ARB anti 4, that phone uses A2 bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will still accept any flashes without authentication. You may or may not be able to unlock it again through fastboot.
If you are using A2, with 6X system and firmware with ARB anti 4, that phone uses 6X bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will not accept any flashes without authentication*. You cannot unlock the phone through fastboot**.
*There is a workaround to this but you need to open your phone's back.
**Because MIUI devices need Mi Unlock to be unlocked, and Mi Unlock wants you to log in, and the system is not accessible, your phone will stay bricked.
You can still unbrick the phone with the above workaround, but you will be stuck with China MIUI and won't be able to unlock your phone's bootloader even if you logged in because your phone is not registered on Mi Unlock database (since Android One devices do not need/use Mi Unlock because of Google's enforcements).
Too long, didn't read?
Do not attempt to lock your phone. Even if you are on fully stock with your phone's own firmware. Locking is extremely risky due to the fact that even unlocking the bootloader corrupts the system integrity in some way.
Letzen said:
ahem.
There is NO way to unlock an A2 device that has been converted to an 6X with ARB anti 4.
Your bootloaders are important in this case (xbl.elf and abl.elf). ARB and bootloader status is also managed here.
If you are using A2, with 6X system without ARB anti 4, that phone uses A2 bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will still accept any flashes without authentication. You may or may not be able to unlock it again through fastboot.
If you are using A2, with 6X system and firmware with ARB anti 4, that phone uses 6X bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will not accept any flashes without authentication*. You cannot unlock the phone through fastboot**.
*There is a workaround to this but you need to open your phone's back.
**Because MIUI devices need Mi Unlock to be unlocked, and Mi Unlock wants you to log in, and the system is not accessible, your phone will stay bricked.
You can still unbrick the phone with the above workaround, but you will be stuck with China MIUI and won't be able to unlock your phone's bootloader even if you logged in because your phone is not registered on Mi Unlock database (since Android One devices do not need/use Mi Unlock because of Google's enforcements).
Too long, didn't read?
Do not attempt to lock your phone. Even if you are on fully stock with your phone's own firmware. Locking is extremely risky due to the fact that even unlocking the bootloader corrupts the system integrity in some way.
Click to expand...
Click to collapse
Thanks a lot, it explains everything and totally sounds right to me,
Just couple questions:
so in any circumstances it could be again usable just with a Chinese ROM, and so there will be no way to install Google Play on it, since there will be no custom recovery , no root accessibility , ... , It will be for ever with a Pure Chinese ROM (which practically would be unusable for us). Am I right?
Considering above situation, sending the device to a Xiaomi Center could help us to get back to any kind of global ROM (AndroidONE / MIUI) or not?
Right now I am totally happy with Xiaomi.eu MIUI BETA roms, no need to switch to other projects, I need to know is there any chance to stuck with a locked BL while attempting the new Beta ROMs? I use PitchBlack to flash new ROMs every week. Or if I want to ask it in short: How to prevent to get a Locked BL?
Thanks a lot again.
sz.hatef said:
Thanks a lot, it explains everything and totally sounds right to me,
Just couple questions:
so in any circumstances it could be again usable just with a Chinese ROM, and so there will be no way to install Google Play on it, since there will be no custom recovery , no root accessibility , ... , It will be for ever with a Pure Chinese ROM (which practically would be unusable for us). Am I right?
Considering above situation, sending the device to a Xiaomi Center could help us to get back to any kind of global ROM (AndroidONE / MIUI) or not?
Right now I am totally happy with Xiaomi.eu MIUI BETA roms, no need to switch to other projects, I need to know is there any chance to stuck with a locked BL while attempting the new Beta ROMs? I use PitchBlack to flash new ROMs every week. Or if I want to ask it in short: How to prevent to get a Locked BL?
Thanks a lot again.
Click to expand...
Click to collapse
does flashing a MIUI.eu beta ROM without deleting the firmware folder lock the bootloader ?
what's the benefit from not deleting the firmware folder?
i'm using a converted MI A2
thanks

Question: If I Downgrade Amazon Ali G6 XT1925-6 to 8 would I be able to unlock the bootloader?

So, I have been doing a lot of reading and I think this would work. As we know Amazon is not allowing Moto Ali G6 XT1925-6 to be unlocked. One person said he was able to unlock his phone that had Oreo on it. If I use the oldest 8 stock ROM from https://mirrors.lolinet.com/firmware/moto/ali/official/AMZ/ I think I should be able to unlock the bootloader. Then I can install any custom ROM.
As I understand it since both factory ROM would have the same manufacture signature. Or did anyone have a better solution?
​
johnl12 said:
So, I have been doing a lot of reading and I think this would work. As we know Amazon is not allowing Moto Ali G6 XT1925-6 to be unlocked. One person said he was able to unlock his phone that had Oreo on it. If I use the oldest 8 stock ROM from https://mirrors.lolinet.com/firmware/moto/ali/official/AMZ/ I think I should be able to unlock the bootloader. Then I can install any custom ROM.
As I understand it since both factory ROM would have the same manufacture signature. Or did anyone have a better solution?
​
Click to expand...
Click to collapse
No, if you downgrade firmware with a lock bootloader, you will not be able to toggle the "OEM Unlocking"
because the device will not boot.
OK, now that it is brick shouldn't I now be able to install any ROM I want via rescue? Sorry, but I like to think outside the box.
Oh., I think I should state why I want to go to 11. It Dark Mode.
I am having problems looking at my phone. Gmail on 9 doesn't have Dark Mode. Websites are white. Even "Setting" can't be changed which when I set the theme to Dark you would had thought it would. I am using Chrome Beta so that helps, I've tried those blue light apps.
I was hoping that switching to 11 would give me more Dark mode options. I can't buy a new phone right now.
If anyone has a suggestion I would appreciate it. Thanks

Question Unlock bootloader security concerns

Hello to everyone,
I wanted to unlock the bootloader of my device so I can modify it and I tried to follow the steps given by Xiaomi.
1] enable OEM unlock in developer settings,
2] connected my device to PC
3] signed in xiaomi unlocking tool
then a warning about security changes appeared before finalise the unlocking stating that i will lose fingerprint unlocking service of my phone.
The question is if someday I decide to return my phone to full stock state will fingerprint and the other security services return as functioning?
Thank you in advance.
Yeah you'll be fine. You will have to downalod rom image form xiaomi website, downalod xiaomi flashing tool, connect phone in fastboot mode and flash original os. Phone will be like brand new
And i don't remember that my fingerprint scanner had any problmes, now i have custom rom installed and its perfectly fine
Wociej said:
And i don't remember that my fingerprint scanner had any problmes, now i have custom rom installed and its perfectly fine
Click to expand...
Click to collapse
Thank you for the info. It's just what Xiaomi Unlock Tool reports I couldn't know.
The reason I am asking is because I need fingerprint services and NFC for my work.
Thanks again.
alexakispantazo said:
Thank you for the info. It's just what Xiaomi Unlock Tool reports I couldn't know.
The reason I am asking is because I need fingerprint services and NFC for my work.
Thanks again.
Click to expand...
Click to collapse
it will work... no issues with biometric sensor...
alexakispantazo said:
Thank you for the info. It's just what Xiaomi Unlock Tool reports I couldn't know.
The reason I am asking is because I need fingerprint services and NFC for my work.
Thanks again.
Click to expand...
Click to collapse
Will you install custom rom?
Wociej said:
Will you install custom rom?
Click to expand...
Click to collapse
I will try some custom roms and if they won't have the features I want I'll try the Indonesian region rom for mi apps. Also, I know I shouldn't relock the bootloader with custom roms, but can I relock it with different regions official roms?
alexakispantazo said:
I will try some custom roms and if they won't have the features I want I'll try the Indonesian region rom for mi apps. Also, I know I shouldn't relock the bootloader with custom roms, but can I relock it with different regions official roms?
Click to expand...
Click to collapse
Don't, bad idea.
alexakispantazo said:
Hello to everyone,
I wanted to unlock the bootloader of my device so I can modify it and I tried to follow the steps given by Xiaomi.
1] enable OEM unlock in developer settings,
2] connected my device to PC
3] signed in xiaomi unlocking tool
then a warning about security changes appeared before finalise the unlocking stating that i will lose fingerprint unlocking service of my phone.
The question is if someday I decide to return my phone to full stock state will fingerprint and the other security services return as functioning?
Thank you in advance.
Click to expand...
Click to collapse
Yes, everything works fine. If you want a close to stock experience flash xiaomi.eu, and everything will work. Fingerprint, facial recognition, nfc and banking apps will work perfectly fine, nothing to be worried about

Categories

Resources