Can't unlock bootloader after flashing stock ROM - Moto Z2 Play Questions & Answers

Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices

motorbass said:
Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices
Click to expand...
Click to collapse
Your original issue was because you upgraded from stock Oreo, which if you would have spent the 5 minutes reading you would have known that A11 roms all require stock Pie modem.
As for your current situation, i don't think you can get out of this one; you might try your hand with Lenovo Moto Smart Assistant or try putting the pie update into the phone to force the updater to upgrade you but you really have put yourself in a weird situation. Your phone is now
1. Locked
2. On the stock rom
3. Without the original recovery
So the bootloader is ****ing confused as to what to do

Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.

motorbass said:
Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know nowadays a short attention span is rewarded, but reading all the way through to the end is usually worth it. If LMSA can't save you then you have officially bricked your phone (unless you find some exploit) OEM Unlock remains unavailable because the image you flashed isn't signed, and as such the phone has gone into FLASHING_LOCKED instead of OEM_LOCKED; i'm pretty sure you can guess the difference between those two.
One last hail mary would be the updater and P; since OTA's are signed you may be able to unlock your phone again (and this time custom roms WILL work! How about that)

Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.

motorbass said:
Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.
Click to expand...
Click to collapse
That is probably because your particular region did not get Pie; search through this forum, there's a way to force the updater to recognize the OTA

Related

MiFlash - Trying to Unlock Bootloader

I'm starting to lose all hope in this device...
I bought my phone from, what I thought, was an official Xiaomi online store, my mistake, buyer beware, lesson learned. However. I have the phone, I like the form factor and all that, and the thought of trying to get a return from a Chinese company sounds like the kind of hassle I don't want to deal with. I'm well experienced in rooting/flashing devices (Nexus 5, OnePlus 2, OnePlus X, Xperia Z5c). I've done it a thousand times on these devices.
My new Mi5S came with "MIUI Global 8.6 | Stable 8.6.10.0(RM1100)" preinstalled.
I only found out after I bought it that the reseller installed this version. They apparently did this so they can make it a global rom. They installed Google play services, Play Store, removed chinese apps and made English the default language. That's great and all, but they also have the Locale setting locked in as China. It's unchangeable. And installing Google Launcher from the Play Store doesn't work (yet Pixel Launcher, downloaded from the web, works fine). Not a huge deal I guess.
Anyway, long story longer, I'm trying to unlock the bootloader.
I got permission, downloaded the Unlocker, VolDown+Power into Fastboot and ran the MiFlash unlocker.
It goes to 50% and then says "Couldn't verify device". That's where I'm stuck.
I've tried everything I can think of, and I just can't unlock the Bootloader.
Is anyone else having this same issue? Has anyone found a way to get TWRP on here?
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
MoonBuggy said:
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
Click to expand...
Click to collapse
I have verified that I'm using the proper account and that Mi Cloud sees my device as online.
Could you clarify which driver you ended up using?
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
lummujaj said:
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
Click to expand...
Click to collapse
I already have permission. Still doesn't work.
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
dgrasley said:
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
Click to expand...
Click to collapse
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
I am still waiting patiently for my Mi5s to get here...
If "fastboot devices" shows your mi5s in fastboot mode right before unlocking - then you have the right driver and the 50% problem should be solved.
CL0SeY said:
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
You can unlock in vendor rom..
Without unlocking you should be able to flash official rom using miflash/fastboot
Vendor rom updater/recovery may not word (did not work for me) to update to official chinese rom..
Click to expand...
Click to collapse
MoonBuggy said:
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Click to expand...
Click to collapse
any funky method you have to install the driver? i am struggling here. adb is fine, but fastboot shows no devices. have tried every driver i can find including above!
edit - for the record i disabled driver signature verification in win10 and installed the above drivers, and still no luck. here is my cmd output
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when it reboot into fastboot a new driver installed on windows and i can see the android bootloader interface in device manager but still no fastboot. weird? also miflash is showing the device when the phone is in fastboot.
---------- Post added 28th October 2016 at 00:33 ---------- Previous post was 27th October 2016 at 23:37 ----------
ok fixed the driver problem. for anyone else stumbling across this:
reboot to fastboot mode, then in device manager update the bootloader interface driver with the google driver that comes inside the C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver folder. (you need to have miflash installed obviously)
note that windows10 you may have to disable driver signature verification for this.
:good:
I got my phone today and had the same problem but i solved it at last, i installed the chinese dev rom and then it worked to unlock the bootloader and i have installed xiaomi.eu rom and works great.
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
marcel112 said:
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
Click to expand...
Click to collapse
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
dgrasley said:
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
Click to expand...
Click to collapse
I was using a windows 10 machine, but i didnt succeed severall times.
The thing i did was trying to unlock, 50% error, then boot the phone, turned off find Mi phone, rebooted, tried again still no go, rebooted again, tunred on find Mi phone again, then tried unlocking again...: Eureka!!
That was the solution, so i tried that on a different machine with no drives installed at all!!

Possible Brick - Flashing Unlock Not Allowed

I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!
So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?
Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).
I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?
ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk
ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.
ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.
Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk
I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:
0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk
Aiit.tnx
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.

Redmi Note 5 blocked

Hi, i'm a user from France.
After installing the last Android version proposed by Mi on the 7th of June 2019 my phone is now stucked on the black screen with the red mention " this miui version can't be installed on this device " - I made the choice to wipe all the data - after restarting nothing changed and I'm stucked to the same black screen.
First big loss. I didn't do any thing solo, I've just being installing the official update proposed by the company like I always do when notification comes. I don't do extra stuff that I have no knowledge about, I'm a regular user.
Now I'm trying to wipe the data through my computer using XiaomiFlash, however I'm getting this error alert : Flash antirbpass error.
What does it mean ? I have read about Google protection briefly on the internet but now it's getting really complicated for me to swim in these waters,
none of the solution worked for me, from the ADB thing to the CMD thing - I also downloaded a "dummy" file which I don't know how to use. After installing ADB I don't get any file of that name in my ":c" repertory and when typing the command "fastboot etc" in CMD it says that it's not recognized. I don't know what I'm doing and I don't know what to do, I don't have a car to get to the nearest phone repair shop and it's like i'm in an alien world with all the technical vocabulary in front of me when search the solution online.
All help would be really appreciated for an ignorant beginner like me.
1.Connect phone to PC, backup important data.
2.Reboot phone to bootloader(fastboot,Power+Volume Down).
Goto PC CMD
fastboot flash antirbpass dummy.img
fastboot flash recovery twrp-3.3.1-0-whyred.img
3.Reboot to TWRP (Power+Volume UP).
Wipe DalvikCache, Cache, Data, Internalstorage, System, Vendor.
Install miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0.zip.
Wipe Cache, Data and do Factory reset.
4.Reboot to system.
Just try abovementioned steps, good luck!
Thanks garyemail for your help.
I'm halfway done with this problem, but another thing came on the way which is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-0-whyred.img
target reported max download size of 536870912 bytes
sending 'recovery' (38924 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.942s
Apparently my phone is locked after being checked :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.014s
I know there is no way for unlocking it through "official" method by using whatever Xiaomi is throwing away, do you have a particular way to get that unlocked ?
I know Xiaomi and Google would scream out of hysteria by reading this post but I'm not trying to unlock my phone for the pure sake of adrenaline.
They putted out that Android Update, not me. It didn't work. Rather it blocked my phone.
Now that the only way to solve the problem is to unlock the phone, what do you know, they decide to put a lock on the phone that basically doesn't allow the user to officially and directly restore the phone.
What is wrong with these people ? Are we just supposed to throw the phone away and buy a new one whenever they are making an uncorrect move resulting in a broken phone ?
I learned now what I'm paying when adding a high price difference for an iPhone, I'm paying for avoiding all that torture which Google and Xiaomi together are dragging me into.
Buy a 1€ phone and spend 1000€ worth of time in searching the remedee in case of a problem. -> Android logic -> money saved at first look, whatever happen you are entirely on your own. A small rock hiding a mountain.
Buy a 1000€ phone and spend 1€ worth of time in searching for the remedee to the sickness. -> Apple logic -> expensive at first look, but client satisfaction guaranteed - time and energy saved.
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Wiguna77 said:
First of all, you bought a non official phone, that mean you bought your phone out of your region. May your phone is from china and it supposed using china rom. But your phone a china version and using global rom but that not wrong, when that happen unlocked bloatloader is needed. the only problem is, when the global version installed, you or the guy that sold the phone to you, lock the boatloader so it seems look like a global phone version but actually its the china one and that forbidden by xiaomi itself, and they have announced a year ago on the miui forum. The only one solution is to unlock the bloatloader ones again. I hope you understand what i wrote and sorry for bad english
Click to expand...
Click to collapse
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
RebornSAGA said:
Hey thanks Wiguna for your help, greatly appreciated. I'm facing now a new and big problem. The "unlock" button on the Mi Flash Unlock is greyed, apparently it's because my phone being locked, but the only way to unlock my phone is through Mi Unlock and they are blocking me the access to unlock my phone. Do you have any way to unlock the phone through a non-xiaomi way ?
I don't know why they would prevent their users for unlocking their phone, is it this illegal ?
Click to expand...
Click to collapse
There is no "non-xiaomi way" you have to flash the chinese official rom with miflash and then unlock your phone, thats the only way.
btw you can try the "EDL-Method".
Thanks Gerr1 and thanks anyone else who helped. Really appreciated.
[How To] Unlock Bootloader on Your Redmi Note 5 Pro
Try abovementioned link!...
First unlock your phone bootloader, then do the #2 setps again!...
Hi
Whenever, Irey to turn on the device, it freezes in the mi logo and can only access the FASTBOOOT. I tried to flash the device but ut says "Flashing is not allowed in Locking State" Also, I treid unnlocking the phone through the mi Unlock software but once it says "You've exceeded the number of verification attempts allowed within 24 hours" and I can login twice in a day to that aoftware it seems. Also, I tried to unblock the device through CMD but it says failed. Please Help. Its hard to work without a phone
Please help

Rollback EMUI from 10 to 9 to bypass FRP

Hi all,
Got a mobile that we dont know the previous Gmail account this was registered with. Therefore, I need to bypass the FRP to recover the mobile and use it for testing purposes. Accidentally, I upgraded it to EMUI 10 and after fixing several softbricks, I have no clue how to downgrade it to EMUI 9.
Goals:
Rollback EMUI 10 to 9 on Huawei 20x C185
Abuse flaws on EMUI 9 to bypass FRP
Do all via Linux tools (preferably console)
Firmware
EVR-L29 C185 EMUI 10
https://mega.nz/#F!zRUGFKyZ!je09cCOdJRPePDvykLwJCQ
http://www.mediafire.com/file/m7l6xlqe4se0u7s/dload.zip/file
Fail attempts
Enter upgrade mode and dload a previous C185 EMUI 9.0.x or EMUI 9.1.x (via OTG cable + microSD card). This always produces the same error: Software upgraded failed!
Try to change country to have chances to flash different firmware.
Logs:
Code:
> fastboot oem get-build-number
...
(bootloader) :EVR-L29 10.0.0.180(C185E6R3P3)
OKAY [ 0.011s]
finished. total time: 0.011s
> fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
Any idea?
Try Hisuite
sunrider07 said:
Try Hisuite
Click to expand...
Click to collapse
hey @sunrider07,
apparently you need to enable HDB options to use HiSuite, right? Tested HiSuite on Linux emulated via Wine. I was able to use the Huawei tool but I couldn't hook up the mobile to the app. Have you used HiSuite to downgrade the bootloader? If so, it is really needed to have adb connection? Remember my phone is protected via FRP.
This is the way to enable HDB (Huawei ADB dev options):
4. Go to device setting and enable USB Debugging. You can follow our guide on how to enable USB Debugging on Huawei phones.
5. Connect HiSuite to your mobile.
6. HiSuite will automatically shows a system update on your device.
Click to expand...
Click to collapse
Being blocked by FRP, HDB switch cannot be enabled so i am not sure if HiSuite can be used
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
sunrider07 said:
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, I do need to find another way to perform a downgrade on the bootloader and base image to EMU 9.0 where there are public and known vulnerabilities to overcome FRP. Otherwise, I will need to wait until a FRP bypass is public, or reverse engineering the HiSuite software to find some fastboot commands to see if I can leverage any of these. It seems I am stuck with it.
Apparently I found this video from 5 days ago: https://www.youtube.com/watch?v=USvi-1O2Y6o
Anyone knows well the mode USB upgrade?
--
mac231us said:
I saw that too. I too need to downgrade but cannot as usb is not connecting. I can connect to one of the Hisuite versions through wlan option but it cannot be used to change the system (only through usb). Cannot do system recovery (says take it to service center)
Yes video shows if you go into usb mode through recovery (which I can) you can use the MRT tool to flash the rom. I plan to look into it. Otherwise I might just take it to a service center in an upcoming overseas trip (still almost 2 months away)
Click to expand...
Click to collapse
Do you know where to download this MRT tool? It seems like super unprofessional tool without github repo.
mac231us said:
Separately in my case-The device is not recognized when connecting through usb to the computer (usb ports, cable, windows version, drivers etc all tried-the device type and name is not recognized. OTG usb works but that is only for backups, backup restore and dload method to upgrade-which cannot be used to downgrade to 9.1 or 9.0 from 10.0) Fastboot commands are severely limited in 10 as my device country vendor is unknown. The device works fine otherwise (calls, mms, apps, internet, themes) Device cannot be registered at Huawei as unknown device though I can register in themes. With dload I can switch back and forth between 10.0.0.180 and 183 or even a lower 10 but not to 9 series.
Click to expand...
Click to collapse
Dont own a Windows10 laptop to use HiSuite, looking for one to see if I can connect it via WiFi. Did you mention you can use all these calls, mms, apps, internet, themes? In this case, we have different issue.
Can you run this command?
Code:
$ fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
mac231us said:
Surprised there is no way to fastboot erase and install firmware-I heard you need a service rom to completely redo the phone.
Click to expand...
Click to collapse
The MRT tool must use a fastboot command too. We can always reverse this tool to extract the command. Do you have the tool?
In this video there are downloading links:
MRT sw
--
anyone able to bypass the frp?

Question RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU

Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^
THANK YOU SIR
To ask a dumb question, but is this only the 6 or for the pro as well?
Works for both
Thank you so much, it work after someone help me erase flash
Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out
Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Same issue for @CyberWolf92
Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.
Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.
Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot

Categories

Resources