Database Users

[Q] Nexus 7 doesn't boot

Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!

Nexus Tool Kit

rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?

swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.

swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.

ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.

swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?

ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.

Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.

Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.

Unable to unlock bootloader after 327 firmware update

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.

Unable to hack Asus Zenfone Laser 2 [ZE550KL - Z00L - Z00LD]

Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.

Uhm... no replies till now?

i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help

When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere

I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.

Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse

hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.

BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.

These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.

Cannot unlock bootloader, phone not recognized in fastboot (RN7)

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.

Essential Phone Half-Bricked?

Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!

McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.

I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable

DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!