Hey guys,
This one really has me stumped and I need some help. I have 5 Xiaomi Redmi Note 3 Pros - we're starting to use these at work. I bought two first to trial with, and they worked awesome on CM, and it was easy to unofficially unlock. I used this method. The next batch simply won't work with exactly the same process. I flash the device with 7.1.8.0 Global and the modified bootloader and whilst the flashing process goes OK, the device does not boot into MIUI afterwards. It flashes the MI logo twice, then shuts off. Plugging in the PC results in a blinking red light. Fastboot works, and I have been using that to reboot to EDL mode to try and fix it, but that's about it. Soft bricked.
So far I've tried both the original unofficial bootloader and the updated one from here and they both result in exactly the same behavior, both on Global ROM 7.1.8.0 and 7.3.6.0. Omitting this modified bootloader will result in the system being bootable on stock MIUI, but that's not what I want.
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Has Xiaomi blocked unofficial unlocking or modified bootloaders via a hardware update? It's the only thing I can think of since I have two Xiaomi Redmi Note 3 Pros that worked flawlessly with this method (although I suspect they were slightly older stock). Is there any way around this? I have another 13 phones on the way and I don't really want to make 15 Mi accounts to unlock officially.
Why can't you unlock different phones on the same account?
razr96 said:
Why can't you unlock different phones on the same account?
Click to expand...
Click to collapse
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
stephendt0 said:
Last time I checked it was one phone per month per account. Also, it takes ages, and doesn't always work (but neither does the unofficial unlock as I'm now discovering).
Click to expand...
Click to collapse
Well i can unlock an unlimited number of times on my account.
This is news to me... I'll try that then. Last time I tried official unlock it got to 50% and froze, so that's why I was trying to do the unofficial unlock. It also takes ages to get the code.
I'd still like to be able to unlock unofficially though.
stephendt0 said:
Hey guys,
If I boot into fastboot and try to unlock the bootloader I get the following error: "FAILED (remote: oem unlock is not allowed)".
Click to expand...
Click to collapse
I'm having the exact same issue!
I also tried to switch between stable MiFlash and XiaoMi Flash beta.
Yeah its really frustrating. I love these phones, but the bootloader unlock process is pure hell.
I found the solution:
Boot into a working ROM (e.g. 7.1.8 global)
1) Enabled Developer options
2) enable USB debugging
3) enable OEM unlocking (how could I miss this!?!)
After that you can flash the modified fastboot rom and unlock the bootloader.
Voila
I'll test this later and report back. I have a sneaky feeling it might not work...
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
{
"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"
}
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
stephendt0 said:
Alright, an update.
Just before I went to do the unofficial unlock, I got a confirmation code saying that I am able to unlock officially. I tried this on one of my phones (China Dev ROM) and it worked great. I went to do the second one, and I got presented with this error:
Damn.
I then tried what you mentioned. Flashed stock 7.1.8.0, enable OEM unlock (it was enabled when I enabled dev options anyway...) and then rebooted to fastboot. I then tried to flash the emmc_appsboot.mbn file from fastboot... no luck. I get "FAILED (remote: device is locked. Cannot flash images)", which is no surprise since the device still has a locked bootlaoder. I then thought alright, well I have the ROM installed with OEM unlock enabled, lets try booting to EDL mode and flashing the ROM with the modified bootloader but without wiping data. I did that, and no luck - just flashes the Mi Logo twice and shuts off. Gah! There's something special about these phones. They must be running a new hardware revision that prevents modified bootloaders from being installed. The only way I can think of unlocking a bunch of phones is to create a heap of different Xiaomi accounts and use the official unlock method, but that is a major hassle!! Really frustrated about this situation. Anyone able to offer some insight?
Click to expand...
Click to collapse
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
cetchmoh said:
Hey, after you enabled OEM unlock in the options reboot to edl and flash the ROM with the modified emmc_appsboot.mbn. After its done reboot to fastboot (Power & Vol Down) and perform "fastboot oem unlock-go". Sorry that my instructions were not clear enough.
Click to expand...
Click to collapse
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
stephendt0 said:
I don't see why that would work. I'll give it a try tomorrow anyway... have you had this exact issue before? I haven't seen it mentioned before, I did a lot of Googling before I made this thread.
Click to expand...
Click to collapse
The setting to "enable OEM unlock" is stored somewhere where MiFlash doesn't write during flashing.
If it is not enabled you get the error described in your first post (FAILED remote: unlock is not allowed).
You still need to edl flash the modified bootloader to unlock. Good luck
IT WORKED.
Oh my gosh. I could have sworn the "enable OEM unlock" option was active the entire time I was trying to unlock the bootloader, but nope. I must have forgot the first time around. The guide doesn't mention that this is necessary, although the screenshot indicates that it was enabled for them. It must have been turned on by default on some phones and turned off on some other phones. That must have been it. For some reason I also thought the system would be able to boot up with the modified locked bootloader, so I thought there was a problem there when it turned itself off.
In the end it was really simple:
Boot into stock ROM, enable "Enable OEM Unlock"
Reboot to EDL mode.
Flash ROM with modified bootloader
Reboot to fastboot
Unlock bootloader
Alright, consider it solved. And I feel like a massive idiot. Thanks! At least if someone else has issues with this they can at least know now that it was something silly :silly:
Hey,
What was causing the problem? Im trying to unlock bootloader from couple of days and I have no idea what to do now. I checked dev settings and enable OEM unlock every time when im trying to flash ROM with modified bootloader and every time: (FAILED remote: unlock is not allowed).
Do all in 64 bit windows then go to advance option n select raw and patch then it will work
Not works on marshmallow works on lollipop
Related
{
"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"
}
The LG G6 H870 for the European market and the USA carrier-free US997 can now be officially unlocked through LG's developer unlock program.
Your H870 is from outside Europe? You have a H871/2/3/etc or H870K/DS/etc? That's not a European H870, won't work. Your US997 tied to a carrier? Won't work.
Please read the FAQ and use the thread search feature before asking questions.
This thread is a work in progress and actively being updated.
LG Developer Unlock Site Here
Prerequisites:
European LG G6 H870 or USA carrier-free US997
Computer w/ADB & Fastboot. ADB/Fastboot for Windows here. ADB/Fastboot for Linux/OS X here.
Basic knowledge of ADB, Fastboot and Windows command prompt or Linux/OS X terminal.
Device IMEI. This 15-digit code can be found on your box, the settings menu or by dialing *#06#
LG developer account -- sign up for free by clicking the "Start Unlocking the Bootloader" button at the bottom of the LG site HERE.
Directions:
LG's official bootloader unlock directions can be found here but I've still rewritten the steps out below while revising some things and also adding steps for TWRP and root.
1. Enable USB-Debugging on your phone. USB-Debugging is required for the adb commands to work. To enable USB-Debugging, go to Settings >> About phone >> Software info and tap Build number until it says you are now a developer. Return to the previous screen, select Developer Options and enable USB-Debugging (this option may be greyed out if you have your USB cable plugged into your phone).
2. Enable OEM unlock on your phone. To enable OEM unlock, go to Settings >> Developer options and toggle/turn on Enable OEM Unlock.
3. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP. If using Windows please make sure you've installed LG's USB drivers. You can download them HERE.
Alternatively, you may be able to boot into fastboot without ADB by powering off the phone then power the phone on while holding Volume UP (USB cable will need to be removed otherwise it may boot into LG Download Mode)
4. Once in the bootloader, use the following fastboot command to obtain Device ID:
Code:
fastboot oem device-id
Fastboot command will return a string. This is the Device ID which is needed to generate your unique unlock key.
Example :
Code:
$ fastboot oem device-id
(bootloader)-----------------------------------------------------------------
(bootloader) Device-ID
(bootloader) CD58B679A38D6B613ED518F37A05E013
(bootloader) F93190BD558261DBBC5584E8EF8789B1
(bootloader)-----------------------------------------------------------------
To generate your unlock key, you will need to paste together the 2 lines of output into one continuous string without "(bootloader)" or spaces. In the example above, the Device ID would be:
CD58B679A38D6B613ED518F37A05E013F93190BD558261DBBC5584E8EF8789B1
5. Copy Device ID and IMEI into the LG Developers Bootloader Unlock site and hit the confirm button. In a few moments the unlock.bin will be emailed to you. Download unlock.bin to computer.
6. While the phone is still in fastboot enter the following command to unlock the bootloader:
This will unlock your bootloader AND factory reset your device wiping all data!
You can use the LG Backup app or LG Bridge to backup and restore your data before unlocking the bootloader.
Code:
fastboot flash unlock unlock.bin
7. You can now reboot the phone and boot into your bootloader unlocked device! Enter:
Code:
fastboot reboot
8. Want TWRP or root?
For TWRP you will need to download the TWRP H870 image. Current unofficial TWRP build is available HERE. (thanks to @Rashed97)
For root you will need to download either SuperSU or Magisk and then flash either of the zips using TWRP.
Reboot back into the bootloader
Code:
adb reboot bootloader
(you'll have to first re-enable USB debugging since data was wiped after the bootloader unlock)
or power off again.. unplug the USB cable then power on the phone while holding Volume UP.
9. Flash TWRP:
Code:
fastboot flash recovery twrp.img
After flashing TWRP unplug the USB cable and power off the phone (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice until it boots into TWRP. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed TWRP. If stock recovery is installed it WILL wipe data.
For TWRP to "stick" you must 1st boot into TWRP and not boot back into Android until after doing one of the following...
flashing SuperSU/Magisk
deleting the recovery-from-boot.p file from the /system directory
flashing the no-verity-opt-encrypt-4.1 or android-boot-repack zips
10. Now you can flash your root zip of choice.
Feel free to back up first.. but otherwise.. time to install SuperSU/Magisk. Reboot into system when finished.
Have fun and be careful.
FAQ:
Q: I have an H870 but it is not a European H870... can I unlock the bootloader?
A: No, this official unlock program is ONLY for the H870 model for countries in Europe just like LG did for the LG G4 and G5.
But... for about a 10 day span G4 devices from SE Asia worked with the official site and users received unlock.bin files.. despite that variant never showing up on the supported list. So you never know what can happen until you try and submit your device-id/IMEI into the LG Developer Bootloader Unlock site. :good:
Q: Will more devices be added?
A: Impossible to say what will happen in the future.. we must wait and see. The LG G5 bootloader unlock program was originally only open to the European H850 but months later the H840 G5SE and the USA RS988 G5 were added to the program.
Q: I can't get my phone to show up with ADB or Fastboot, watdo?
A: Make sure ADB/Fastboot is properly setup for your OS... udev rules setup in Linux.. LG USB drivers installed for Windows... OS X/MacOS just works. Also, confirm USB debugging is enabled.
ADB still not working?... try changing the phones USB modes.. from maybe charging to MTP.. or MTP to PTP.
Q: What happens to warranty if I unlock or root?
A: YMMV I suppose. The official LG site claims that warranty is void if damage is caused by the unlock. On the T-Mobile G6 there is now a bootloader unlock counter. I will assume this counter is also on the H870/US997, so it will be hard to hide the fact that you unlocked the bootloader. Please share any unlocked bootloader LG G6 warranty replacement stories in this thread.
Q: Can I re-lock the bootloader?
It IS possible to re-lock the bootloader with the the command: fastboot oem lock
You'll have to boot back into the bootloader (adb reboot bootloader) to issue the fastboot command.
Re-locking the bootloader WILL wipe data just like the unlock process. Use LG Backup app/LG Bridge or another backup method first if you want your data.
Flashing a KDZ in LGUP or LG Bridge will NOT relock the bootloader.
DO NOT re-lock the bootloader if you have a modified boot/system img... restore them to stock first or you will not be able to boot into android after the lock and need to flash a KDZ in download mode.
Q: So many words... yudodat?
A: Here is a video on how to unlock the G4... up until the 6minute mark it is step-by-step 100% the same as G6. Only slight difference is when you get to the TWRP/root steps. https://www.youtube.com/watch?v=O64GfQORCaE
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Consider donating to me.
Thanks autoprime, keeping an eye out for us G6 owners in the rootless wasteland ☺
(As a VS988 owner I know I'm really stuck in purgatory, but can always hope ? It was time to finally upgrade from my G3 - you did awesome work on that phone, hugely appreciated by many.)
Donated.
Oh yeah. Real theming can start...
Sent from my LG-H870 using Tapatalk
Great news ! I was really missing adblock and Xposed DPI tweaks (with such a big screen)
Did someone already flash TWRP ?
Will try it out on a H870DS eventually and see if it works. Thank you very much!!!
Don't think there is TWRP at present, its coming though.
unlock.bin sitting in my Inbox...
Looks like TWRP will be available in a few days...
Big up to all !
So my guess is that the unlock.bin would be device specific?
I've got the H870, but from ZAF...
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
zEar said:
You guess right. The file is obtained from the LG Bootloader Unlock Site, and is based on your device-id.
What is the exact model you have in System Settings -> About -> Hardware info ?
Mine is just LG-H870.
Maybe you get the Euro version in ZA ?
Click to expand...
Click to collapse
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Awesome!
thanks a lot, is time to mod
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Finally , I have an H870, how can I know if it's the European model?
tried it with the (h870s) and it said that the device is not supported, will it ever be supported?
What about root is it working?
Well this is brilliant news, just upgraded to the G6 and it'll arrive later today so looking forward to future roms for this device.
isaakmg said:
Without twrp we haven't make nothing.......
Enviado desde mi LG-H870 mediante Tapatalk
Click to expand...
Click to collapse
this is gonna be easy
scabs said:
Mine also just says LG-H870
The IMEI is hardware bound right?
Edit: Reason i'm asking is that i've tried the site and says "Unfortunately, your device(South Africa, (SOUTH AFRICA) )does not support unlocking the bootloader."
I wonder if installing the EU firmware will work?
Click to expand...
Click to collapse
Yes the IMEI is flashed somewhere in the hardware, and IMEI ranges are allocated by regions.
An EU firmware could work, but wouldn't change you IMEI.
Sorry for you, you'll have to wait for an unofficial way to unlock the bootloader if it is ever found...
Well, we EU LG G6 users may not get Quad-DAC, 64Gb of storage or wireless charging but we at least get this (which is better than anything).
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
{
"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"
}
alvesluscas said:
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
Click to expand...
Click to collapse
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
how do I check the bootloader status?
alvesluscas said:
how do I check the bootloader status?
Click to expand...
Click to collapse
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
onliner said:
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
Click to expand...
Click to collapse
I just check here it is not unlocked
device unlocked: false
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Androbots said:
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Click to expand...
Click to collapse
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
onliner said:
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
Click to expand...
Click to collapse
I see that now...
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
mohsiin4u said:
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
Click to expand...
Click to collapse
but the device is connected to the internet
alvesluscas said:
but the device is connected to the internet
Click to expand...
Click to collapse
Your computer Must be connected to internet, and not the device
mohsiin4u said:
Your computer Must be connected to internet, and not the device
Click to expand...
Click to collapse
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Your PC connected to ur device hotspot internet connection? If yes then connect another hotspot to ur pc it need when u connect ur Device to PC in fastboot mode
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
NewBee3 said:
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
Click to expand...
Click to collapse
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Have you try to flash fastboot global or developer with clean flash?
alvesluscas said:
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Click to expand...
Click to collapse
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
SH3H1 said:
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
Click to expand...
Click to collapse
try flash stable china rom..
dinoredfield said:
try flash stable china rom..
Click to expand...
Click to collapse
I was told to do this, but mine is Kate (Special Edition) there is no Chinese rom for him
rainsmile said:
Have you try to flash fastboot global or developer with clean flash?
Click to expand...
Click to collapse
I tried both with developer and stable global
Is there any way to bypass Xiaomi's account system and wait time? It isn't only the pain in the ass, but I would trust an XDA developer a lot more than a Chinese corporation like Xiaomi with any possible privacy issues related to their bootloader unlock process.
I've seen a thread for the Mi 4c which seems to be similar to what I'm looking for.
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Has anything similar been done for the Mi 8 Lite?
Thanks!
No
Good luck. Just be patient and read all you can about Mi8 Lite while waiting. That is what I did. Made the time pass more quickly. NOTE: Do not change sim cards mid-way through. It will reset your 15 days. Almost got burned by doing that myself.
I had the same issue. Try to use Miflash unlock version 2.3.803.10. MAYBE it can work.
u need to wait, no other way
MiFlash Unlock Tool Version 3.3.827.31
Have your SIM in phone.
Login to your MI account on the phone and on PC.
Set your SIM phone number in MI account settings (PC).
Find Mi Unlock Status item in Developer settings in phone settings and
Add account and Device
Turn off phone. Connect it to PC. Start MiFlash Unlock.
When it asks for phone, boot it in Fastboot (hold vol+ and power button)
Proceed...
On my friends Redmi 4x it showed 72 hrs to unlock.
On a fresh Mi account...
dakok said:
MiFlash Unlock Tool Version 3.3.827.31
Have your SIM in phone.
Login to your MI account on the phone and on PC.
Set your SIM phone number in MI account settings (PC).
Find Mi Unlock Status item in Developer settings in phone settings and
Add account and Device
Turn off phone. Connect it to PC. Start MiFlash Unlock.
When it asks for phone, boot it in Fastboot (hold vol+ and power button)
Proceed...
On my friends Redmi 4x it showed 72 hrs to unlock.
On a fresh Mi account...
Click to expand...
Click to collapse
My 3 redmi note 4x's were unlocked same day. Newer devices have the longer wait time. So far nothing you can do but wait.
The solution is in files
I know how to flash without Unlock Bootloader.
kevinramir said:
I know how to flash without Unlock Bootloader.
Click to expand...
Click to collapse
Well good for you and so do I. It is very limited what you can do though.
The solution is in files
No, is just modify files
cidxtc said:
Well good for you and so do I. It is very limited what you can do though.
Click to expand...
Click to collapse
I've tried some versions of this program, but none worked, and I've seen and heard reports that the miunlock program does not really work properly. So I gave up unlocking and I want to undo it.
Please give me a name of a good device so that I can change it on my MI8 Lite? preference Motorola and Samsung.
kevinramir said:
I know how to flash without Unlock Bootloader.
Click to expand...
Click to collapse
Can you please help me with this? Do you have any guide or advice for this?
matheusfdelgado said:
I had the same issue. Try to use Miflash unlock version 2.3.803.10. MAYBE it can work.
Click to expand...
Click to collapse
HOLY **** THIS VERSION ACTUALLY WORKED FOR ME
Thank you so! much dude!!!
Marlonese said:
HOLY **** THIS VERSION ACTUALLY WORKED FOR ME
Thank you so! much dude!!!
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"
}
Not working anymore
Got mine to work with the newest version now too, tho
Still sad that Xiaomi tries to make it so hard to unlock bootloader
I've just done unoff unlocking process without paying. If it is interesting, i can describe.
And for Mi8 also, but it need to edl-autorization flash (some money).
domestik said:
I've just done unoff unlocking process without paying. If it is interesting, i can describe.
And for Mi8 also, but it need to edl-autorization flash (some money).
Click to expand...
Click to collapse
? You don't have to pay to unlock your bootloader officially?
MartonDev said:
? You don't have to pay to unlock your bootloader officially?
Click to expand...
Click to collapse
unofficial unlock
So here is instruction to get unofficial unlocked Mi8 Lite device ("platina").
Must say "bla-bla" about risk of damaging. My phone was "baseband unknown" problem, so no way to unlock officially.
You must have some skills.
All you need files except FW's are in attachment.
1. I have MI8Lite CN version 9.6.6.0. I dont know how about other versions.
2. Remove back cover and antenna cover to reach TP.
3. Extract attach, run miflash, select extracted directory, connect phone in 9008 mode and flash.
In \images only few files and corrected loader, so you dont need auth-account to flash.
4. At end of flashing (not during process!!!!) I got an error. It is normal.
5. Reconnect battery, press Vol-down, connect to PC. You must have fastboot mode and NO info on screen (it is normal, bcz your phone now "wayne" not "platina").
6. Run mi_unlock_en_sod, press left key in it then press right key. You must see green text in this program and your phone reboots. Still garbage on screen! But now unlocked!
7. Go to FW-directory of your phone (same as in your phone), edit flash_all.bat. Remove First and second line (checking phone model), save file.
8. Execute command "fastboot flash antirbpass dummy.img". Result must be OK.
9. Run flash_all.bat.
10. That's all. Your phone must turns on, unlocked and "platina".
11. Corrected firehose loader from \images can be used to flash any MI8Lite FW without edl auth.
On Mi8 process much easy but expensive. You need to flash 9.5.11.0 version via edl auth, run mi_unlock_en_sod, press left, press right. I have been done huge amount.
On Redmi Note 7 process must be same as on Mi8Lite bcz it is one phone in two different cases.
https://yadi.sk/d/SF1Uh7D7yrYqnQ
domestik said:
So here is instruction to get unofficial unlocked Mi8 Lite device ("platina").
Must say "bla-bla" about risk of damaging. My phone was "baseband unknown" problem, so no way to unlock officially.
You must have some skills.
All you need files except FW's are in attachment.
1. I have MI8Lite CN version 9.6.6.0. I dont know how about other versions.
2. Remove back cover and antenna cover to reach TP.
3. Extract attach, run miflash, select extracted directory, connect phone in 9008 mode and flash.
In \images only few files and corrected loader, so you dont need auth-account to flash.
4. At end of flashing (not during process!!!!) I got an error. It is normal.
5. Reconnect battery, press Vol-down, connect to PC. You must have fastboot mode and NO info on screen (it is normal, bcz your phone now "wayne" not "platina").
6. Run mi_unlock_en_sod, press left key in it then press right key. You must see green text in this program and your phone reboots. Still garbage on screen! But now unlocked!
7. Go to FW-directory of your phone (same as in your phone), edit flash_all.bat. Remove First and second line (checking phone model), save file.
8. Execute command "fastboot flash antirbpass dummy.img". Result must be OK.
9. Run flash_all.bat.
10. That's all. Your phone must turns on, unlocked and "platina".
11. Corrected firehose loader from \images can be used to flash any MI8Lite FW without edl auth.
On Mi8 process much easy but expensive. You need to flash 9.5.11.0 version via edl auth, run mi_unlock_en_sod, press left, press right. I have been done huge amount.
On Redmi Note 7 process must be same as on Mi8Lite bcz it is one phone in two different cases.
]
I have a Redmi Note 7. I have "NV data is corrupted" on my device and locked bootloader. Need to unlock it in order to replace the QCN file and fix baseband, IMEI, modems, etc. Can you explain to me how did you unlock your bootloader? Pls
Click to expand...
Click to collapse
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Press and hold the volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"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"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant
I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"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"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com