Related
I bricked my Xiaomi Mi 8 phone by performing steps to re-lock it. It only boots into MI-Recovery 3.0 or Fastboot mode but I cannot do anything with it. MI Unlock and MI PC Suite does not recognize the phone, Flashing it does not work and MI PC Suite does not detect the phone. .
Here is what happened:
1) Xiaomi Mi 8 came with MIUI 9.5 Global Stable ROM installed that was unlocked from the Factory.
2) I used OTA upgrade to upgrade to MIUI 9.6.1 Global Stable ROM right after turning on the phone for the first time. 3) A few days later the phone allowed me to upgrade to MIUI 10 on my device also via OTA upgrade and everything worked fine until this point.
I have not been able to install a few of my applications from Google Play store – Netflix being one of the examples. In Xiaomi forums I got the information that this is because the device has been unlocked. To change that I followed an article to re-lock the device in an Xiaomi forum “[Tutorial] How to Re-lock Bootloader of Any Xiaomi Devices without Flashing” .
Unfortunately this is where I got into trouble. Here are the exact steps I performed:
-> fastboot devices
2dbe209b fastboot
-> fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.021s]
finished. total time: 0.022s
-> fastboot oem lock
...
OKAY [ 0.050s]
finished. total time: 0.052s
After entering this command the phone rebooted into MI-Recovery 3.0 with 3 Menu Options:
1. Reboot
2. Wipe-Data
3. Connect with MIAssistant
There is an error message on the bottom of the screen saying "This MIUI version can't be installed on this device". Rebooting brings me to the exact same screen.
Here are the resolution actions that I have tried so far:
1. Connecting to MI Assistant is not working. The phone shows that the USB is connected but MI PC Suite 3.2.1.311 does not detect the device.
2. Trying to undo the locking and unlocking the phone again does not work either. Here is the commands I have tried
-> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.030s]
finished. total time: 0.042s
->fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.008s
3. Following the official Unlock procedure with MI Unlock Tool Version 3.3.827.31 does not work either because the program does not recognize my phone and stays at the “Not Connected to Phone” screen.
Any ideas how I get out of this? I would appreciate any help.
-----------------------------------------------------------------------
I fear after reading more posts from this forum I know what happened. It seems the merchant sold me a Chinese version of the MI 8 with Global ROM without telling me. Packaging of the phone was original sealed and everything brand new and not tampered with so I fell for it. Appreciate any suggestions how to resolve nevertheless otherwise I bought an expensive paperweight ...
You have brick the phone,you need authorized account to install a China rom and lock bootloader and unlock with your mi account. If you install China rom you need to unlock bootloader waiting 720 hours then unlock and install global rom only with unlock bootloader!
Last week I bricked my mi 8 due to ARB protection, maybe I can help you. In your case you should try to unlock the phone with the official mi unlock tool, if it doesn't work or you don't want to wait too much, things are gonna be a little harder.
You have to open the phone and put it in EDL mode: http://en.miui.com/forum.php?mod=viewthread&tid=3459005&extra=page=1&mobile=2
After that you have to check s-unlock and someone with "EDL authorized account" will help you to restore your rom.
Ok, it's not free, but it's the only thing saved my mi 8 without sending it back to China or waiting months for an EDL authorized account
Thanks
Thank you for the fast answer - I will try it.
mi 8 locked
lucaci.ed said:
Last week I bricked my mi 8 due to ARB protection, maybe I can help you. In your case you should try to unlock the phone with the official mi unlock tool, if it doesn't work or you don't want to wait too much, things are gonna be a little harder.
You have to open the phone and put it in EDL mode: http://en.miui.com/forum.php?mod=viewthread&tid=3459005&extra=page=1&mobile=2
After that you have to check s-unlock and someone with "EDL authorized account" will help you to restore your rom.
Ok, it's not free, but it's the only thing saved my mi 8 without sending it back to China or waiting months for an EDL authorized account
Click to expand...
Click to collapse
hi lucaci.ed can you explain to me how you fix your mi 8.,? thanks before
sherwinprambudi said:
hi lucaci.ed can you explain to me how you fix your mi 8.,? thanks before
Click to expand...
Click to collapse
https:// s-unlock. com /productsandservices/server#g15
You have to buy one of these services.. it depends by what you need, but I think the cheaper option would be fine. I suggest you to contact them on Facebook before you buy and explain your problem, so they can tell you what's the best option for you.
I specify I don't work for them, but they just saved my phone from sending back to China. It's not my responsibility if it doesn't work or if you lose your money
I tried Android 10 and I decide to downgrade my Mi 9T Pro to Android 9. After downgrade, so many things broken because of persist.img
So, I reflash the persist.img (from V10.3.17.0.PFKCNXM) file and problems solved. I am using xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9 now.
Netflix Widevine is turned from L1 to L3, so I cant play HD or HDR contents. How can I fix that?
once you have modified the vendor/persist partition (flashing the vendor/persist.img through twrp) there is no way to recover widevine L1 except for having to change the equipment for a new one or with a change of pcba
And if you try to flash using EDL? and then tell us if it is possible to recover the widevine L1
pixel_mx said:
once you have modified the vendor/persist partition (flashing the vendor/persist.img through twrp) there is no way to recover widevine L1 except for having to change the equipment for a new one or with a change of pcba
And if you try to flash using EDL? and then tell us if it is possible to recover the widevine L1
Click to expand...
Click to collapse
EDL doesn't help. What is pcba?
you could try format data with twrp, then you install xiaomi.eu
Gonz19 said:
you could try format data with twrp, then you install xiaomi.eu
Click to expand...
Click to collapse
This is the normal procedure to install xiaomi.eu and I already did like that.
You should backup your stock persist. L1 is gone forever now so far I know.
Kollachi said:
You should backup your stock persist. L1 is gone forever now so far I know.
Click to expand...
Click to collapse
:crying:
I have a Global device. Unlocked BL and flashed the Indian version using fastboot. Haven't rooted but I have formatted all the partitions from twrp before fastbooting the indian rom.
Problem is now I cannot download Netflix app from the Playstore and figured also the playstore "Device is not certified" there in settings.
I want to know this is common and there's no way to get Widewine L1 when BL is unlocked? Or is there a possibility if I go back to the official Global rom and lock it?
fernoct said:
I have a Global device. Unlocked BL and flashed the Indian version using fastboot. Haven't rooted but I have formatted all the partitions from twrp before fastbooting the indian rom.
Problem is now I cannot download Netflix app from the Playstore and figured also the playstore "Device is not certified" there in settings.
I want to know this is common and there's no way to get Widewine L1 when BL is unlocked? Or is there a possibility if I go back to the official Global rom and lock it?
Click to expand...
Click to collapse
Just flash magisk and safetynet patch module, then delete play store data. You can install Netflix now.
Just wondering, what are other disadvantages aside from loosing L1 ? I also flashed my persist image on A3 due to downgrade and sensor problems. Will service center be able to flash to restore it? Cause the phone is running fine on anything else
Same Issue with me. Any progress on your situation OP?
Maybe you should have done some research before doing something that stupid. Flashing persist.img is guaranteed to make you lose l1 permanently.
Hi,
anyone know how to change widevine cdm L3 to L1?
my phone status:
- ROM WW1910.44
- FINGERPRINT WW1910.44
Edited: already can unlock bootloader. Tried this already:
1. unlock (UBL)
2. flash
3. root
4. unroot
5. locked BL again
but still in L3 ~_~
Thank you.
v3ll said:
Hi,
anyone know how to change widevine cdm L3 to L1?
my phone status:
- LOCKED BOOTLOADER (because i tried to Relock the bootloader and run "fastboot oem asus-csc_lk" and it said it already locked)
- ROM WW1910.44
- FINGERPRINT WW1910.44
- Cannot unlock bootloader via unlock device tool apk anymore (it said "An unknown eerror occurs, which may b a network connection issue. please wait and try again later") ->already tried to factory reset, still no effect. internet connection via mobile or wifi same thing cannot.
- Cannot unlock bootloader via EDL (https://forum.xda-developers.com/rog-phone-2/how-to/how-to-unlock-rog2-phone-via-edl-mode-t4008267), on step 3:.Double click to open “1.update_image_EDL.bat”, it said:
"{ERROR: WritePort:5164 Could not write to '\\.\COM10', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times. " Tried to change the usb port but same thing happened.
Thank you.
Click to expand...
Click to collapse
After entering 9008 mode, you can flash the file through Xiaomi miflashtool or QPST tool, and then open one click to unlockbootloader.If you use Xiaomi tools, you need to rename prog_firehose_ddr.elf to prog_ufs_firehose_sdm855_ddr.elf. Use QPST tool, need to change EMMC to UFS !!!
johnny886 said:
After entering 9008 mode, you can flash the file through Xiaomi miflashtool or QPST tool, and then open one click to unlockbootloader.If you use Xiaomi tools, you need to rename prog_firehose_ddr.elf to prog_ufs_firehose_sdm855_ddr.elf. Use QPST tool, need to change EMMC to UFS !!!
Click to expand...
Click to collapse
i managed to unlock bootloader via EDL using your method (https://forum.xda-developers.com/rog...-mode-t4008267), but after flashing rom and relock it, still same widevine L3. it drives me crazy!
v3ll said:
i managed to unlock bootloader via EDL using your method (https://forum.xda-developers.com/rog...-mode-t4008267), but after flashing rom and relock it, still same widevine L3. it drives me crazy!
Click to expand...
Click to collapse
In EDL mode, after flashing the file, enter fastboot mode and run the command to try it. It can clear the unlock information of the phone and let you return to L1 is no longer L3.
(bootloader) Reset count info (the device need to be authorized) :
(bootloader)
(bootloader) >>> fastboot oem reset-boot_count
(bootloader) >>> fastboot oem reset-lock_count
(bootloader) >>> fastboot oem reset-a_retry_count
(bootloader) >>> fastboot oem reset-a_unbootable_count
(bootloader) >>> fastboot oem reset-b_retry_count
(bootloader) >>> fastboot oem reset-b_unbootable_count
(bootloader) Lock device authorized :
(bootloader)
(bootloader) >>> fastboot oem reset-dev_info
johnny886 said:
In EDL mode, after flashing the file, enter fastboot mode and run the command to try it. It can clear the unlock information of the phone and let you return to L1 is no longer L3.
(bootloader) Reset count info (the device need to be authorized) :
(bootloader)
(bootloader) >>> fastboot oem reset-boot_count
(bootloader) >>> fastboot oem reset-lock_count
(bootloader) >>> fastboot oem reset-a_retry_count
(bootloader) >>> fastboot oem reset-a_unbootable_count
(bootloader) >>> fastboot oem reset-b_retry_count
(bootloader) >>> fastboot oem reset-b_unbootable_count
(bootloader) Lock device authorized :
(bootloader)
(bootloader) >>> fastboot oem reset-dev_info
Click to expand...
Click to collapse
Thank you and done it. Also locked the bootloader after it. But it still L3..
https://photos.app.goo.gl/DpQCBBw24kCDQcu58
v3ll said:
Thank you and done it. Also locked the bootloader after it. But it still L3..
https://photos.app.goo.gl/DpQCBBw24kCDQcu58
Click to expand...
Click to collapse
Hi
Please could you update if you managed to fix it and get L1.
Thanks
RedLeader00 said:
Hi
Please could you update if you managed to fix it and get L1.
Thanks
Click to expand...
Click to collapse
nope, did many things but cant change it back to L1, now i gave up and just root my device instead. if you do have the working method pls inform me.
v3ll said:
nope, did many things but cant change it back to L1, now i gave up and just root my device instead. if you do have the working method pls inform me.
Click to expand...
Click to collapse
Hi. No I was not be able to fix it neither. I will wait for next update and finger crossed I guess...
Any update so far? That drive me crazy too. After unlock bootloader by using EDL method, i have accidentally get the wrong persist.img (wrong size) then when flash back i've lost the serial number (but i find other way to get back the serial number). If you understand what happened to bootloader and L3 security please help. Now i can not unlock bootloader by Asus apk anymore.
Have anyone been able to relock the bootloader and get back Windevine L1?
Did anyone reached out to Asus on this? Eventhough warranty is lost, the phone should report properly SafetyNet and all the needed security properties to Widevine.
Still no update regarding L1?
I kind of regretting unlocking bootloader using EDL method
After re-locking the bootloader, have you tried the below command once and checked what it returns? Safe to use!
Code:
fastboot oem check-fuse
The below command might also be available and may help with something. I DON'T KNOW ANYTHING ABOUT THE BELOW COMMAND AT ALL SO USE IT AT YOUR RISK THOUGH after doing some research
Code:
fastboot oem set-fuse
Mayank7795 said:
After re-locking the bootloader, have you tried the below command once and checked what it returns? Safe to use!
Code:
fastboot oem check-fuse
The below command might also be available and may help with something. I DON'T KNOW ANYTHING ABOUT THE BELOW COMMAND AT ALL SO USE IT AT YOUR RISK THOUGH after doing some research
Code:
fastboot oem set-fuse
Click to expand...
Click to collapse
It said unknown and failed the command "fastboot oem set-fuse"
Full steps to relock bootloader and get Widevine L1 were posted here: https://zentalk.asus.com/en/discussion/18495/bootloader-relock-does-not-restore-widevine-l1.
After having a chat with a couple of other members of the ROG II Telegram discussion group, the above info was shared and posted in ZenTalk.
Happy usage of Custom ROMs!!
anthonws said:
Full steps to relock bootloader and get Widevine L1 were posted here: https://zentalk.asus.com/en/discussion/18495/bootloader-relock-does-not-restore-widevine-l1.
After having a chat with a couple of other members of the ROG II Telegram discussion group, the above info was shared and posted in ZenTalk.
Happy usage of Custom ROMs!!
Click to expand...
Click to collapse
Hey, sorry for necroing this topic, but... This telegram group is open for everyone? And if yes, can you please send me a link? It would be very useful.
I didn't tinker with my ROG 2 yet just because don't wanna lose L1.
Thanks in advance!
Enviado de meu ASUS_I001DD usando o Tapatalk
ClowReed said:
Hey, sorry for necroing this topic, but... This telegram group is open for everyone? And if yes, can you please send me a link? It would be very useful.
I didn't tinker with my ROG 2 yet just because don't wanna lose L1.
Thanks in advance!
Enviado de meu ASUS_I001DD usando o Tapatalk
Click to expand...
Click to collapse
If you search telegram for rog 2 you'll find it. Sorry, telegram links aren't allowed at xda
I ordered a "Global ROM Xiaomi Redmi K20 Pro 12GB 512GB Exclusive Edition Smartphone Snapdragon 855 plus 4000mAh 48MP Triple Cameras 6.39'' on AliExpress (yes I know now it was mistake to get "Global ROM"...). Everything actually looked really good, Google Play store worked, device model showed up as "Mi 9T Pro", only thing I needed to do was lock bootloader for banking apps etc and everything has been working great.
At some point I was offered OTA update to MIUI 11, and I decided to install it last night. The install went until 65% and then the screen went black and the phone rebooted into the dreaded "The system has been destroyed" error. Now since my bootloader is locked I don't know how to recover from this - Mi Unlock Tool and fastboot both won't unlock, Mi tool wants me to add my account in developer options which of course isn't possible. I tried the "fastboot continue" method too with no effect. All I want is stock MIUI with locked bootloader and working OTA updates.
fastboot vars:
product: raphael
secure:yes
anti:1
board_version:4.9.2
hw-revision:20002
unlocked:no
Is EDL mode the only way to recover from this?
So you locked your bootloader and installed the OTA?
Unfortunately yes, bootloader was locked when OTA was installed.
A1a2Z7 said:
I ordered a "Global ROM Xiaomi Redmi K20 Pro 12GB 512GB Exclusive Edition Smartphone Snapdragon 855 plus 4000mAh 48MP Triple Cameras 6.39'' on AliExpress (yes I know now it was mistake to get "Global ROM"...). Everything actually looked really good, Google Play store worked, device model showed up as "Mi 9T Pro", only thing I needed to do was lock bootloader for banking apps etc and everything has been working great.
At some point I was offered OTA update to MIUI 11, and I decided to install it last night. The install went until 65% and then the screen went black and the phone rebooted into the dreaded "The system has been destroyed" error. Now since my bootloader is locked I don't know how to recover from this - Mi Unlock Tool and fastboot both won't unlock, Mi tool wants me to add my account in developer options which of course isn't possible. I tried the "fastboot continue" method too with no effect. All I want is stock MIUI with locked bootloader and working OTA updates.
fastboot vars:
product: raphael
secure:yes
anti:1
board_version:4.9.2
hw-revision:20002
unlocked:no
Is EDL mode the only way to recover from this?
Click to expand...
Click to collapse
Flash correct regional ROM through QPST/QFIL
You'll get a locked bootloader with OTA updates
Thanks for the response. It looks like QPST/QFIL only work if the device is already in EDL mode. Is there a way to boot to EDL without special cable / using motherboard test points? I tried fastboot oem edl and got "FAILED (remote: 'Oem edl command is not allowed Lock State')".
Following this Thread. Let me know If you get any Answer please mine stuck too and cant do aything and dont want to open my brand new device.
2VJ5 said:
Flash correct regional ROM through QPST/QFIL
You'll get a locked bootloader with OTA updates
Click to expand...
Click to collapse
It doesn't work with Raphael.
So an update for those wondering. To fix this I had to use EDL mode and flash the original China ROM. It seems EDL cables do not work on this phone, so I had to open it up and use the test point method to boot into EDL mode. Even in EDL mode and using QFIL, there is still an authentication process on the phone itself, which requires an authorized Xiaomi account in order to load firmware. Obviously my own account does not have that authorization, so I paid $30 to one of those shady looking "unbrick" services. They remoted into my PC with UltraViewer (TeamViewer ripoff) and logged into their account and the flash succeeded.
Lesson learned... never lock the bootloader on this phone!
So a few days ago I picked up my X4 on Amazon to replace my dying old Samsung, (XT1900-7, 4/64) for 125€ which is a steal for the specs you get. After playing with it for a while I decided to unlock the Bootloader so I can root it. When I tried the fastboot oem get_unlock_data in fastboot mode It only says "Invalid Command" then I realised I have the Amazon Prime version (which had Alexa installed), which allegedly cannot be unlocked, and was stuck in Android 8. So after a lot of googling I tried Sideloading Pie in fastboot, which didn´t work. Applying update from SD Card also didn´t work (couldn´t mount /sdcard). So I followed this method here: https://forum.xda-developers.com/moto-x4/how-to/rom-upgrade-directly-to-pie-8-0-locked-t3876127 (thanks to TeamRainless). I downloaded the factory signed Image from the MEGA Link: https://mega.nz/#!QQ1mgKpS!ce2kysojSUv9pzA-V4YE4kv5jg0S7X5X1lNrIWn6su0. I put the zip file (DO NOT RENAME THE FILE!) in the root folder of my internal storage, then checked the update manually in the Settings, and voila! It applies the Pie update in the 30 Minutes and now I have the retail version of the ROM without Amazon apps on it.
I applied all patches until September 2019 (PPWS29.69-37-5). I rebooted into fastboot mode and ran the fastboot oem get_unlock_data as usual and now I get the 5 lines of code I could use to unlock the device. I logged into Motorola website and pasted the code, accepted all the T&Cs, got the unlock code in my Email and now my phone is unlockable. I ran this in fastboot fastboot oem unlock *code given in email* and the phone was unlocked. When I rebooted the phone all my data was deleted so if you want to do this back up your data first! I hope this gives hope to all of you who bought the Amazon version without knowing. Good luck trying and stay healthy guys!
https://postimg.cc/gallery/XXVR3H3
wow thnx for information
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
gatesps said:
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
Click to expand...
Click to collapse
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Or is there any other way how to install mentioned image?
maks_kyiv said:
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
Click to expand...
Click to collapse
Device Model #, Codename, and Software Channel.
maks_kyiv said:
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Click to expand...
Click to collapse
Only if the bootloader is already unlocked
maks_kyiv said:
Or is there any other way how to install mentioned image?
Click to expand...
Click to collapse
sd_shadow said:
Device Model #, Codename, and Software Channel.
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
sd_shadow said:
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
Bad, I will wait for any working bootloader unlocking method for Amazon phones.
maks_kyiv said:
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Tried on another PC. Got all fastboot variables successfully.
So my phone is from US.
I also have an XT1900-1 already upgraded to Pie with a locked bootloader. I had a thought - would it be possible to trick the update service into thinking that this image is an upgrade? How does the update service know that the image is a newer version anyway?