Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
racker16 said:
Click to expand...
Click to collapse
Which commands you using for bootloader unlock?
strongst said:
Which commands you using for bootloader unlock?
Click to expand...
Click to collapse
fastboot -i 0x2b4c oem unlock- go
I was using right command
racker16 said:
fastboot -i 0x2b4c oem unlock- go
I was using right command
Click to expand...
Click to collapse
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
strongst said:
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Yeah I have used this also but same ,
Waiting for device
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
in developer options (in settings) make sure both oem and usb debug are ON
CoreKido said:
in developer options (in settings) make sure both oem and usb debug are ON
Click to expand...
Click to collapse
Its already on that time
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
Buddy try this tool
http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
Related
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
EDL (Emergency Download) Mode has been removed/ disable from MIUI 8.1 onwards and Redmi 4A later Xiaomi devices. So you can flash MIUI Fastboot ROMs on your device by using Fastboot mode only, if your bootloader is unlocked. And, we can't use Qualcomm Jig Cable(s) also now.
So, we have only one way to know Qualcomm HS-USB QDLoader 9008 port from PC. It's Test Point Method. This method will work with every MIUI ROMs (Upgrade/ Downgrade) , Locked Bootloader/ Unlocked Bootloader and also work to recover from a Dead boot device (Bricked).
While touching these two points with a metal tweezers plugin the usb cable to the phone and PC will make the phone enter edl mode. You can then release the tweezers.
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
TioCareca said:
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
Click to expand...
Click to collapse
In any case, the bootloader muz be unlocked to initiate EDL using ADB fastboot..
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
adrenochrome25 said:
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
Click to expand...
Click to collapse
What makes you think I'm so lame as well. I have used this command and flashed my mi max 2 with fastboot rom. Tho I don't remember if bootloader was locked or unlocked. Probably it was unlocked. But still no issues as anyone can unlock thier bootloader officially.
i wasnt intended at you. it seems they forgot some ways when they first deployed the edl blocking access but with the most recent "roms" they have blocked every access way to edl when bootloader is locked : adb, fastboot & cable
the only way left is from internal pins, but we can expect they will hide them even better on new phones.
Today it's much worth to wait 72h (+30days if you just already unlocked another one today) than opening the models that have "non removable" batteries and risking to leave traces/damages
it's really a shame that xiaomi lock their phone this way, it's a very bad message at the users (fastboot is so much restricted that you cant even switch between stable&dev anymore with locked bootloader) but we still have the chance that they allow unlocking and that this unlocking is a real one allowing full control
Fastboot rom isn't needed untill we brick our device and we can't brick the device untill we have unlocked bootloader. So basically edl mode will work when it's really needed.
It doesn't work for my MM2. Got it since 4/12/17. Didn't know i need to login to mi acc to register my device, set usb debugging, developer's mode, unlock status...I had the phone for less than 2 hrs after updating to MIUI 9 from ver 8 (using the updater app) before it suddenly froze up, crashed and went into bootloop. I tried contacting xiaomi svc ctr but those clowns refused to help saying my device is china export.
I cldn't even get them to help me register my device on my mi acc using the imei & s/n info. So if anyone could offer some suggestions as to how I could ressurrect my phone, I wld be most grateful. Failing which the only avenue is to bring it to a svc ctr in China to get them fix it.
Rgds
My test points don't seem to work
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Nike Lee said:
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Click to expand...
Click to collapse
I managed to short the test points and got the Qualcomm HSB device on the device mgr, flashed the mi max2 with the latest global stable (V9.2.1) rom. But the phone is still stuck at the Android logo with 3 dots...
I wld have thought EDL flashing wld have wiped out everything on the phone and start afresh?
I am now thinking of formatting the entire phone and reflashing it again. How wld I do that?
Thanks for any inputs.
Hi, Does EDL with test point flashing refresh the boot partitions?
I have shorted the test points and successfully reflash the phone with the latest stable global ROMs (even back to MIUI 8.5.6) but just couldn't get the phone past the MI/Android logo after restarting it
If the boot partition files have been messed up and EDL flashing is not refreshing these files, no matter how many times I try to EDL flash the device, it's not going to help. Pls correct me if I am wrong.
Any other options I can try?
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
bro thank u so muchhhhhhhhhhhhhhhhhhhhhhhh. it worked im so happy now...........was trying since hours....but u helped me mannn
Hi.. may i asking u guys that u guys have try to unlock bootloader at ver.318 firmware? cause i unable to unlock my phone bootloader at this latest firmware..does anyone has same issue with me?
What issues are you facing? Unlock method works perfectly.
arvinchugh said:
What issues are you facing? Unlock method works perfectly.
Click to expand...
Click to collapse
i have follow the instruction that to unlock my phone but when i want to unlock my phone bootloader it sometimes show tat code 0kb and wont move anymore...sometimes it until stuck at waiting devices and the phone only show click power to shutdown.. .and sometimes already process all the process in cmd but the phone still at bootloader mode and wont restart..
i have try uninstall and reinstall my driver in my pc still the same.. my operating system is using windows 8.1 and windows 7
Hey guys i just updated to firmware 327 from 326.. I am using fully stock rom with locked bootloader.. I wanted to unlock bootloader but was unable to do so.. Whenever I try to run the unlock.bat file the black cmd screen remains stuck and nothing happens.. Plz help me i wanna try few roms so help me to unlock bootloader (6gb variant)
Is this because of the latest firmware??
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
andriyhar said:
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
Click to expand...
Click to collapse
Bro official unlocking method will void warranty even after i relock my bootloader later right? So i wanna do it the unofficial way so i can relock bootloader and go back to stock if I wish and would get ota updates
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
Yes it's detected.. Bt the black cmd screen gets stuck while unlocking
Any solution guys plz need help
try using cmd prompt in administrator mode....
ujilraj said:
try using cmd prompt in administrator mode....
Click to expand...
Click to collapse
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Well, I am not an expert in this. It should just work. And the Windows 10 thing is absurd. I am using Windows 10. Plus, development mode is not enabled in my laptop.
Credits to the following -
@Sudeep Duhoon for this guide - [UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
ASUS for phone, drivers, rom, this and that
Mod edit. Link removed. Reference: https://forum.xda-developers.com/one...rward-t3765018
@Saktis_STi for raw factory rom
@Shivam Kumar Jha for fixing the script
@Sujeet Ranipa for drivers link
@esashwin for testing
Use unlock.sh instead of unlock.cmd
If the phone is indeed detected in fastboot mode using
Code:
fastboot devices
, try running the script from unlock.sh instead of unlock.cmd.
I have not been unable to flash fastboot stock ROM from this laptop using the .bat file but for some reason, .sh file works fine.
Just install Git on windows. It will give you a wrapper to run shell scripts on your windows machine (Git BASH).
Again, I am not an expert. This might not work but at least it won't corrupt anything.
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
_uchihaitachi_ said:
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Click to expand...
Click to collapse
Try anyother pc
Many users solved unlock problems by changing pc
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
Ok bro thanks for help.. Will try on another pc coz my pc has only 3.0 and 3.1 ports ?
iamfarhanansari said:
Try anyother pc
Many users solved unlock problems by changing pc
Click to expand...
Click to collapse
Ok bro thanks for help
Phone is not detected.
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
I have this same issue my phone is not detected.
Please help.
I too have same problem
C:\>cd unlock
C:\unlock>fastboot devices
J7AAGF02D693CWW fastboot
C:\unlock>unlock
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
Solution to unlocking bootloader where screen blacks out on flashing
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
I had the same issue, after reading to many webpages, stumbled on this official unlock tool apk. Once the bootloader is unlocked using the app, the phone reboots into ASUS UNLOCK MODE with device status as unlocked and message to restart the phone. Heres the catch this is already the fastboot mode so flash TWRP at this stage. If you restart the phone in fastboot before flashing twrp, on running the flash cmd the screen of your phone would black out with a message "press any key to shutdown". Hope this helps.
unlock tool apk
then how do I install that official unlock tool in fastboot mode. since I can only access CSC FASTBOOT MODE.
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Same here
connect it through a USB hub, it worked for me
Cicciocap94 said:
connect it through a USB hub, it worked for me
Click to expand...
Click to collapse
A usb 2.0 hub did the trick for me, using a usb 3.0 only laptop. It did not work with my usual usb3 hub.
N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.
Maybe it's helpfull to install a VPN, in my case flexvpn from playstore, before starting unlock- process...
I solve with an old PC...but I wait for 270h to unlock...
thank you all for your comments, I don't know exactly what happened but Mi unlock recognized the device and asked me to wait for 33 hours to finish the unlocking process.
arunbiju969 said:
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.
Click to expand...
Click to collapse
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim
N7Witcher said:
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim
Click to expand...
Click to collapse
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?
arunbiju969 said:
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?
Click to expand...
Click to collapse
Thank you very much for taking the time to answer all of my questions! You've been very helpful.
I've been thinking about what you wrote but I think I wanna install the official global ROM via Mi Flash. If I select the "clear all and lock" do I risk bricking my device? That's my main concern.
I didn't mention it earlier, but the only reason I want to unlock the Bootloader is so I can flash the official global Rom, (my carrier takes ages to update the rom they install, and it's also full of bloatware) this is my main phone (less than a month old), and while I understand that keeping the bootloader open and using custom ROMS could enhance my user experience, for the time being I want to keep things simple and safe. Maybe in the near future I'll start tinkering with custom rom and recoveries.
Thank you everyone for your suggestions! I don't know exactly what did the trick, but I was able to unlock the bootloader and flash a global ROM. I've encountered some issues with it but that's another topic.
Once again, thank you all!
N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection
Anirban Kopty said:
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection
Click to expand...
Click to collapse
Can you give detailed instructions on how to "update that driver with the ADB Drivers"? After installing the 15 secs ADB drivers and Xiaomi drivers, my Note 7 is still being recognized as an "Android" device with the yellow caution sign.