Hi Everyone,
My tablet is Lenovo B8080-F model, 16GB with Wifi. I got it rooted and installed TWRP on it. I was so over excited about this and wanted to flash custom ROMs on it. I searched and could not get the proper ROM for the B8080-F, in my eagerness, I decided to flash the ROM for Lenovo A3000. Since then my tablet could not boot up again. It got stuck at the Lenovo logo. My windows system can still detect the tablet when plugged to the PC, but ADB DEVICES command shows nothing.
I need help. I need step-by-step guides on how to revive the tablet. I appreciate.
Muyiwa.
Update:
My PC can detect the device. It is shown as Android ADB Interface under Windows Device Manager. There is no COM Port.
If I type: adb devices
Response: ? Unauthorized.
Please help!
Thanks.
Muyiwa.
Ouch
Me too, i need help
I actually have such an tablet lying around. Haven't been used in five years. Never got custom ROMs, right? I don't think Lenovo ever bothered to upgrade from Kitkat.
@[email protected]
@Mirage20000C
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.
My One Plus 6t was facing minor errors in the new update. I tried to roll back anf it ended up getting hw and sw error. I read on many forums and got a way to install a custom ROM by using MSM Tool. I mistakenly installed One Plus 6 ROM. Now the device boots up with no response to the screen. The MSM tool is not working. It says "Image Error". The phone is also not recognized by My PC as the usb debugging is off. The device status is displaying "Locked". I have ran out of options and cannot take it to any professional due to Corona Lockdown.
Thanks for your Time.
Hi guys, I've been following the forum trying to solve my problem but nothing worked. I was trying to rollback from android and oxygen 10 to android pie 9, I did it sometimes (trying to fix the cts fail, another story, I gave up and I was happy to return for the last time to Pie) and everything went ok, but the last time I did it, installed the rollback, rebooted and the yellow message appears. I don't really know what to do, I can't get access to fastboot, cache, hard factory reset, anything. I tried the msm methods, always getting "images do not match the phone" (and I tried different versions for different OSs, also for Tmobile, not the case tho).
Do you have any last options for me or I have to ask for technical support and send it to OP? the phone is brand new (bought it 2 weeks ago), never rooted or anything like this.
Thank you very much.
Power off the phone hold the vol up and down button at the same time while holding then plug in your cord msm should recognize your phone
@matZOOOOO
Check youtube for some videos on how to use msm tool. I have seen a few videos there for 6t restore to stock, unbrick... The XDA thread here for msm tool is extremely detailed.
Any time I've ever delt with windows os it's always always always a driver issue. I hadn't even seen windows in like seven years until I had to install it dual boot on my laptop to use msm tool. But I had similar experience as you are. What worked for me was uninstalling the qualcomm usb drivers and reinstalling them, then of course reboot and after that the tool ran all the way through and I had my phone again.
Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com