Hi guys,
yesterday I received my Note 3 Pro Kenzo (SD) from Gearbest.
There was an old MIUI-version installed that wasn't really localized to German (maybe a shop-ROM), so I decided to install an up-to-date version of MIUI.
I downloaded the "Redmi Note 3 Qualcomm Latest Global Stable Version Fastboot File Download" from here, which seems to be V8.0.1.0.LHOMIDG (MIUI8), put my phone in fastboot mode (in EDL-mode it didn't work, MiFlash didn't find my phone) and installed the ROM with MiFlash. Everything is working now, localization is perfect and the phone runs smooth.
The only strange thing is, that I haven't been able to unlock the bootloader officially yet, wether with the "old" ROM-version nor with the latest Global Stable MIUI8.
On MIUI7 the unlock-tool said, I don't need an unlock(?), on MIUI8 it says my phone is not permitted (or something similiar), even if I have the confirmation-SMS from Xiaomi (that was on August 19th) and I'm logged in into my Mi-account on the phone and in the unlock-tool.
Am I doing something wrong? Here it's said that it should be possible to unlock using the offical way with my new ROM.
Or do I have to be on another ROM to unlock my bootloader?
Background is that I want to try out different ROMs, so I need to install TWRP first - and I absolutely need root-access!
Can I flash TWRP over adb without unlocking?
Any help from you is really much appreciated.
Thanks a lot and best regards
Mischa
You need unlocked bootloader to flash TWRP to the device
Did you follow the steps here?
http://en.miui.com/thread-280561-1-1.html
Thanks for the link, this looks really useful!
Is it right that I can stay on my Global Stable (Fastboot) ROM? Or do I have to flash the Global Beta Recovery ROM?
Guys, I need some help!
My phone is only found from MiFlash when it's in Fastboot-mode. When I put it in EDL-mode MiFlash can't find it.
EDIT: BTW, I just found this in my MiFlash-log:
Code:
[23:16:02]:install driver C:\Program Files (x86)\MiFlash\Source\ThirdParty\Google\Driver\android_winusb.inf to ,result False,GetLastWin32Error Unknown error (0xe000024b)
What does it mean? My phone is found with "adb devices" and the adb-drivers seems to be okay
The "Qualcomm HS-USB QDLoader 9008"-driver is installed and shown in the device manager when I executed "adb reboot edl".
My phone seems to be in EDL-mode with black screen and blinking red LED.
Right now I'm running Global Stable (Fastboot) V8.0.1.0.
I had to install this ROM also when I was in Fastboot-mode, cause only then MiFlash found my phone (same problem), not in EDL-mode.
Do you have any idea what went wrong?
Worst thing is that I can't flash any ROM using this way anymore, cause MiFlash now says "phone is locked" when I try to flash anything in fastboot mode. Also recovery ROMs are not usable with updater-app (maybe because my bootloader is still locked).
So, seems like I'm caught: I can't unlock my bootloader, I can't flash any other ROM, I can't root and can't install TWRP - I'm stuck on Global Stable V8.0.1.0
I really appreciate any help from you!
Best regards and thanks a lot
Mischa
EDIT: SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It finally worked
What I did? I used MiFlash V2016.04.01 (instead of the lastest version from August 30th), which I got from here: http://xiaomitips.com/download-in-progress/?dlm-dp-dl=1474 (I hope it's allowed to post links here, otherwise PM me for downloading it from my Google Drive).
After I installed it, it re-installed the Qualcomm-drivers - and with this version I was finally able to see my phone in EDL-mode.
I also found out that only with this version you could set the advanced settings in MiFlash, cause in the newest version this option is not available anymore.
BTW, after every attemp to unlock the bootloader officially failed, I now unlocked it successfully using the unofficial way.
Best regards
Mischa
Hi everyone,
This is starting to really do my head in, considering I unlocked, flashed and rooted Redmi 3S on first try and in a few minutes.
I managed to unlock bootloader of Redmi Note 4 SD after finally installing correctly usb fastboot drivers (using MiFlash). I flashed TWRP 3.2.2.0, flashed OPT patch and SuperSU, and got a TWRP bootloop (phone always booted into TWRP).
Using MiFlash, I flashed Global Dev Rom and then phone updated by ota to latest 7.6.29. HOWEVER, stupid of me, I flashed rom with option checked of Clean All and Lock, accidentally locking bootloader again.
I try to unlock phone again with Mi Unlock Tool, log into my account succesfully and Tool doesn´t detect phone. Drivers are installed but Tool says Phone Not Detected. I unplug and plug usb cable to all ports and nothing.
However if I use older version of Mi Unlock Tool 1. 1, it detects phone but when I unlock ,it stops at 50% saying Couldn´t Verify Device. Account is bound to phone and I´m logging in with correct details.
Does one need to apply to Xiaomi again for a second unlock?? Driver problem? Account problem?
Anyone have any ideas? I would like to flash TWRP and root phone to be able to fix once and for all that FRIGGIN audio mic noise cancellation when recording videos, seeing as Devs don´t develop a rom with that huge bug patched.
Any help would be very much appreciated.
Cheers!!
Did you try it? https://forum.xda-developers.com/redmi-note-4/how-to/bootloader-unlock-variants-to-read-t3565459 Read also second post, you should turn on oem unlock, and one apply for one phone.
Thanks buddy, tried all that, but I have posted in that specific bootloader thread to see if someone has an answer.
Cheers friend!
Hello guys,it's been 3 days since I applied for unlocking my RN4 and even after getting permission I wasn't able to unlock it
Last night I got frustrated and started looking for any unofficial trick like RN3 has.... What they do is put their device in edl mode and flash a moded apps boot.mbn file and then on fastboot they execute the unlock boatloader command like fastboot OEM unlock and get a working unlocked bootloader for their device.....
I used to work as a professional DRS -digital repair specialist in reliance Jio so there we. Had a water 2 named mobile which can't be fixed after soft brick as it had the edl mode via any cable or any other process so when I opened the handset I saw those dot pinouts and tried to short them one by one and finally I got it to boot in edl mode and then flash it with qfil.....
Same as that phone... This RN4 also had those pin outs, so I opened the back and started shorting pin outs while battery was unplugged and hey yehh that let my phone in edl mode huhu ... I was happy and to test if it works or not... I got a global fastboot ROM and I wasn't able to flash it before edl via fastboot but now.... When I fired up mi flash... Set directory I was able to get it in working state (yes soft brick RN4 got life)
Than I got a twrp recovery and renamed it to recovery. IMG and put it inside of mido(RN4) flashing folder and flashed it .... But sadly even after it got flashed via mi flash I saw stock recovery...
So here I am asking for a file to get our bootloader unlocked which is emmc_appsboot.mbn
I'll upload the original file and it will be glad if some one will help me to modify that mbm file to make it unlock via fastboot.........
Let's see if people dev. Will help me or not..
Or even if some one will give me a already unlocked bootloader IMG or mbn file I'll proceed further... So plz do help me... We're soon close to get an unofficial bootloader for our beloved RN4..
You will be able to unlock 100% within 7 days... If you have a Current account is not bound to this device error
Kevin Saiza said:
You will be able to unlock 100% within 7 days... If you have a Current account is not bound to this device error
Click to expand...
Click to collapse
Hi Kevin!
7 days from when? Receiving the bootloader unlock permission, since our last try or what?
droidiser said:
Hi Kevin!
7 days from when? Receiving the bootloader unlock permission, since our last try or what?
Click to expand...
Click to collapse
Knock knock.. 50-50.. It's sometimes from the day you had permissions from Xiaomi, sometimes it's from last try. BlameXiaomi
Unlocking bootloader is nightmare on Mi phones. I was trying to upgrade to MIUI 9 Developer ROM from my current stable and I have to unlock the bootloader to do so. It's crazy ! I didn't have to do that on Redmi Note 3. It was easy to switch between stable and developer roms from updater app.
Anyone has any idea how can I flash the latest developer build on my Redmi Note 4 with out unlocking bootloader?
devil2016 said:
Unlocking bootloader is nightmare on Mi phones. I was trying to upgrade to MIUI 9 Developer ROM from my current stable and I have to unlock the bootloader to do so. It's crazy ! I didn't have to do that on Redmi Note 3. It was easy to switch between stable and developer roms from updater app.
Anyone has any idea how can I flash the latest developer build on my Redmi Note 4 with out unlocking bootloader?
Click to expand...
Click to collapse
Developer Build can be installed without unlocking bootloader from updater on Redmi Note 4 also.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hey folks,
I've tried my best so far, but I am stuck.
I wanted to change the ROM on my wife's Redmi 3 pro. It was running on a rather old RR version and I wanted to go back to MIUI to have a better camera.
After an unsuccesful attempt to flash this, I was stuck in a bootloop.
This - in general - was no problem: I've decieded to flash an official firmware via MiFlash, but this apparently didn't work as well.
So, now MiFlash has locked the phone again but not properly installed anything.
I can access Fastboot and the pre-installed recovery, but nothing more.
The unlock tool tells me that I can't unlock it because it is apparentyl not bound to my MI account (and I have no clue with which account I've unlocked it the last time).
Desperately appreciation any kind of help!
Thanks in advance.
UPDATE: I was apparently not patient enough. After quite a while it finally booted. Now I can access the system again, but still can't unlock the phone.
UPDATE 2: I also found out with which account I've unlocked it and thus everything worked after all. Now sporting Lineage 14 with camera mod.
Please, feel free to explain how can it finally booted. Your experience might be help somebody sometime.
?