Database Users

Update Failed and Phone Cannot Start. Only Flash Blinks When Charging, NO START/Boot?

I got an update notification. And clicked to update.
When restarted the phone, the phone went to die. I could not start my phone.
I tried these:
1) Kept my fingers on VOL Down and POWER buttons for 2 minutes (even more), but NO USE.
2) Tried to open screws but my screwdrivers could not fit for them.
I bought it 3 months back, but in Flipkat and no service center near me. Any solution for it?

What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?

echo92 said:
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
Click to expand...
Click to collapse
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.

TrueUniue said:
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
Click to expand...
Click to collapse
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?

echo92 said:
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
Click to expand...
Click to collapse
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.

TrueUniue said:
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
Click to expand...
Click to collapse
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.

echo92 said:
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
Click to expand...
Click to collapse
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.

TrueUniue said:
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
Click to expand...
Click to collapse
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?

echo92 said:
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
Click to expand...
Click to collapse
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.

TrueUniue said:
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
Click to expand...
Click to collapse
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21

echo92 said:
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
Click to expand...
Click to collapse
I got this when I clicked blankflash:
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>.\qboot.
exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.009] Check qboot_log.txt for more details
[ 4.010] Total time: 4.010s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>pause
Press any key to continue . . .

I think, if any one can find new blankflash, I can fix my phone. I think those blankflases are old. I'm on April update, and failed when I tried for June update.

Hard bricked

Hello members,
(This is my last try to save my device)
What happened?
I wanted to flash stock rom and by error I double clicked on Flash_factory in the the fastboot folder.
The device booted into fastboot and never came back. It went to edl mode (coz led was blinking) I flashed the fastboot rom but I guess in the 2nd half the Mi flash tool showed the error as TIME OUT.
In device manager, phone is detected as Qualcomm 900E so tried to install drivers (9008) after disabling signature enforcing but it showed that windows can't verify the driver.
Went to Mi service center they said it's a water damage (3 month ago it happened but the device was working fine until now) so the service center didn't do any real efforts to fix it.
What are my options! Any help will be appreciated.
P.s no edl or Fastboot.

iamshivendu said:
Hello members,
(This is my last try to save my device)
What happened?
I wanted to flash stock rom and by error I double clicked on Flash_factory in the the fastboot folder.
The device booted into fastboot and never came back. It went to edl mode (coz led was blinking) I flashed the fastboot rom but I guess in the 2nd half the Mi flash tool showed the error as TIME OUT.
In device manager, phone is detected as Qualcomm 900E so tried to install drivers (9008) after disabling signature enforcing but it showed that windows can't verify the driver.
Went to Mi service center they said it's a water damage (3 month ago it happened but the device was working fine until now) so the service center didn't do any real efforts to fix it.
What are my options! Any help will be appreciated.
P.s no edl/Fastboot now.
Click to expand...
Click to collapse
Fastboot flashing is the safest method to flash your device. Download stock rom files from official website and flash each file separately via fastboot.
Sent from my [device_name] using XDA-Developers Legacy app

nikhel said:
Fastboot flashing is the safest method to flash your device. Download stock rom files from official website and flash each file separately via fastboot.
Click to expand...
Click to collapse
I mean to say i have no access to flastboot nor edl mode.

iamshivendu said:
I mean to say i have no access to flastboot nor edl mode.
Click to expand...
Click to collapse
Search about Deep Flashing.
Sent from my [device_name] using XDA-Developers Legacy app

nikhel said:
Search about Deep Flashing.
Click to expand...
Click to collapse
Okay

Power cycle the phone by pressing power button for 10-15 sec after that phone will become 9008
But since your phone is completely wiped out by factory command your imei is destroyed

emprazol said:
Power cycle the phone by pressing power button for 10-15 sec after that phone will becom 9008
But since your phone is completly wiped out but factory command your imei is destroyd
Click to expand...
Click to collapse
Can i restore my imei?

iamshivendu said:
Can i restore my imei?
Click to expand...
Click to collapse
yes you can but you must active diag port first then find a qcn and edit it with your imei and restore with qpst
its complicated i think its better to visit a technician

Lenovo Tab 3 8 (TB3-850M) - Hard Bricked

Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.

wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.

AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course

wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.

AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...

wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:

I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.

i have the same issue.
one day stop working

AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&amp_ct=1551037935701&referrer=https://www.google.com&amp_tf=From %1$s&ampshare=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down

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.

Need help with a bricked Realme 2 Pro

Yesterday I tried to install a different ROM for my Realme 2 Pro (RMX1801)
I tried to flash TWRP but it does not boot into TWRP recovery instead reboot to normal booting, I tried other version of TWRP for RMX1801 but all of them didn't work at all.
After that I accidentally flash TWRP to boot instead of recovery. It ended up soft bricked my phone, goes to bootloop and things. I tried to flash the original ColorOS recovery and boot but I think I got the wrong one and ended up bootlooping so I was stuck
After that, I've made a terrible mistake. I ran the command fastboot flashing lock and the bootloader is now locked. I made the the brick even harder now.
Now my phone can only goes Download mode I guess. I can't get it into fastboot to flash it with different image. It only vibrate and, show the Realme logo and show "boot/recovery has been destroyed, please flash the correct image..."
I can see Qualcomm HS_USB QDLoader 9008 (COM-3) in my device manager, tried to install driver, but using the flash tool it shows "No Device is connected through this port"
I tried to use QFil, but I have trouble finding the right flash file, stock rom can't do the job because it's mising essentials files for QFil to Download
I am truly stuck now, I don't want to go to customer service as my last option. Please help me

no help ?

thuanc177 said:
no help ?
Click to expand...
Click to collapse
Any update?

PrateekPanwar64X said:
Any update?
Click to expand...
Click to collapse
sadly, no

I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.

PrateekPanwar64X said:
I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.
Click to expand...
Click to collapse
Vivo driver

PrateekPanwar64X said:
I got it fixed, I connected phone to PC, Pressed all 3: Power btn, vol up & vol down and heard a sound in pc.
My phone was detectable in Device Manager > Enable hidden items and has Q_BULK in Communication Ports. Installed Vivo drivers & contacted a telegram group who fixed it by flashing stock ROM using MSM tool for $10 via teamviewer (You need oopo's username & password authorization so you cannot do it).
You can already see in COM-3 port, All you need is to flash using MSM tool (I tried finding passwords online they didn't worked so ended up paying). So try that (Beware, First check if they're legit guys & do not use personal chat with anyone / Send full payment before your phone is fixed).
& Remember never lock your bootloader.
Click to expand...
Click to collapse
hi can you tell me the telegram group cause i'm in the same problem like you had.

Retr0_680 said:
hi can you tell me the telegram group cause i'm in the same problem like you had.
Click to expand...
Click to collapse
I had found in xda form like this, I’ll find and message.

i have same issue flashed
NusantaraROM - RMX1801 which requires magisk did install rom. then since banking apps were not working so i uninstalled magisk and my device bricked. now no matter which os i install none is able to pass the rom logo. i check my hardware for emmc issue that guy said hardware is all good. i flashed through edl mode using msm download tool agent charged me 800 and the device still stuck in realme logo.​

i request u guys please help me