Bricked Lenovo Tab M10 fhd plus while trying to downgrade, any advice? - Thinkpad Tablet General

Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60

Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.

Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.

did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .

Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.

Related

Bricked gift :D

I got bricked Pop C7 7041D Dual Sim as "gift", and I'd like to fix it. Phone has installed TWRP Recovery by hanuma50 v.2.4.1.0 - pretty much this is all I can do with it. It's unable to wipe system, I dont have any custom ROMs to try.
Reguar boot just loops from boot logo to white screen.
I tried SP flash tool, but it gives all sorts of errors, Mobile Upgrade S fails (cant connect to phone).
Computer sees it as Mediatek USB Device, but it keeps on connecting and disconnecting round and round?
Is there any way to make this phone usable?
Also, I can't do adb via recovery, as the computer does not see the phone.
voolandis said:
I got bricked Pop C7 7041D Dual Sim as "gift", and I'd like to fix it. Phone has installed TWRP Recovery by hanuma50 v.2.4.1.0 - pretty much this is all I can do with it. It's unable to wipe system, I dont have any custom ROMs to try.
Reguar boot just loops from boot logo to white screen.
I tried SP flash tool, but it gives all sorts of errors, Mobile Upgrade S fails (cant connect to phone).
Computer sees it as Mediatek USB Device, but it keeps on connecting and disconnecting round and round?
Is there any way to make this phone usable?
Also, I can't do adb via recovery, as the computer does not see the phone.
Click to expand...
Click to collapse
I've got a solution if you wanted to try it, search on google MTXXXX preloader drivers, replace the X with your processor number, if you are not too sure of your processor number search up the Alcatel pop C7 specs on gsmarena, then once you downloaded the preloader drivers type in devmgmt.msc on the run command, this will launch device manager, then click on the top where it says username-PC, go to action > add legacy hardware, then click next, advanced, show all devices and then have disk then click on the folder that you extracted with the preloader drivers, then wait for the drivers to install, you will get a code 10 error, that's normal just ignore it, then go to SP flash tool and flash the firmware and you no longer got a bricked "gift", sorry if its a little confusing just read through carefully and you will be fine

Black screen, no DL mode, no boot, just a brick - device without root

Hello guys!
Unfortunately I have managed to full brick my phone which has worked without any issues for more then 3 years.
My story:
1. Phone started to have random restarts, basicaly, when phone lagged little bit - it restarted phone.
2. When I did manual restart, I got into bootloop and could not get out
3. With a heavy heart I did a factory reset. - Problem with random restarts ontinued together with random bootloops.
4. Did maybe 5 more factory resets, nothing happened.
5. Found a tutorial to flash new firmware.I was on 5.0.2 D802 30d so I used same. (PC suite could not find my phone and LG support tool always freezed on SW install)
6. I used LG Flash tool with normal flash. - used *.kdz which I have downloaded via LG support tool - checked size with dl from source from xda and they were same so i used it.)
7. All success, but device keep restarting - i think no bootloop anymore.
8. I did full flash again with LG flash tool so have a clean install and hopefully fix everything.
9. Suddenly mid-install my phone auto-disconnected from laptop and even with Retry attemps I wasnt able to get it running again. Then my phone restarted itself and that was it.
Now I cannot go to recovery mode, I cannot go to Download mode, all I see is black screen (turns some light on little bit underneath but no data visible).
Also when connect to my Windows 10 laptop multiple discs trying to load and trying to format disk. (one of them contains folder image with some files inside).
I dont have root, I dont have any other tools installed on my phone, just a normal user.
I tried to download adb but i dont understand it much, and also it cannot find my device.
Is there any way how to still fix my phone or is it completely lost
If so, I please you for a dummies step-by-step list .
Thank you so much in advance. :crying:
So good news,
I managed to load img back with dd application.
My Download mode together with factory reset is working.
I have tried to flash it with LGUP and even with some accused usb disconnections I probably managed to flash new lollipop to my phone.
Now it is optimalizing apps to load android correctly. Only issue I have is low battery, it always drains it too quickly so it cannot load properly.
Any idea how to charge the battery? Every time I connect phone with usb cable it starts up into boot, possible bootloop (cannot say if it is because of low battery or real bootloop)
Thanks
Dude try to install crdroid 7.1.2 nougat rom of d802 this will fix your battery problem
root it and install TWRP with srktools 2.0
this is best way to root G2 5.0.1 lolipop
you can also use LG One Click Root to obtain root then don't update su binary and install Autorec of you model to get twrp
nudget said:
Hello guys!
Unfortunately I have managed to full brick my phone which has worked without any issues for more then 3 years.
My story:
1. Phone started to have random restarts, basicaly, when phone lagged little bit - it restarted phone.
2. When I did manual restart, I got into bootloop and could not get out
3. With a heavy heart I did a factory reset. - Problem with random restarts ontinued together with random bootloops.
4. Did maybe 5 more factory resets, nothing happened.
5. Found a tutorial to flash new firmware.I was on 5.0.2 D802 30d so I used same. (PC suite could not find my phone and LG support tool always freezed on SW install)
6. I used LG Flash tool with normal flash. - used *.kdz which I have downloaded via LG support tool - checked size with dl from source from xda and they were same so i used it.)
7. All success, but device keep restarting - i think no bootloop anymore.
8. I did full flash again with LG flash tool so have a clean install and hopefully fix everything.
9. Suddenly mid-install my phone auto-disconnected from laptop and even with Retry attemps I wasnt able to get it running again. Then my phone restarted itself and that was it.
Now I cannot go to recovery mode, I cannot go to Download mode, all I see is black screen (turns some light on little bit underneath but no data visible).
Also when connect to my Windows 10 laptop multiple discs trying to load and trying to format disk. (one of them contains folder image with some files inside).
I dont have root, I dont have any other tools installed on my phone, just a normal user.
I tried to download adb but i dont understand it much, and also it cannot find my device.
Is there any way how to still fix my phone or is it completely lost
If so, I please you for a dummies step-by-step list .
Thank you so much in advance. :crying:
Click to expand...
Click to collapse
You can fix using qhslb 2.0
You can find video on YouTube.

PC doesn't recognize my LG (download mode)

Hey guys!!!
Can you please help me with this?
Yesterday i tried to install a new ROM on my LG Android phone (My LG phone is not working properly, it has a reboot loop). I tried to do a factory reset without success -> the dead Android logo appeared :/
I put my phone in Download Mode and connected to the pc but Windows does not recognize my phone.. it says: "USB device not recognized.. the last USB device you connected to this computer malfunctioned and Windows does not recognize it"
I do not know what to do now.. when i try to flash a ROM with the LG Flash Tool it fails because LG program does not recognize my device..
PS: LG Support Tool recognizes my phone (it shows the model) but i cannot flash a ROM
Thanks!!:fingers-crossed:
android_simply said:
Hey guys!!!
Can you please help me with this?
Yesterday i tried to install a new ROM on my LG Android phone (My LG phone is not working properly, it has a reboot loop). I tried to do a factory reset without success -> the dead Android logo appeared :/
I put my phone in Download Mode and connected to the pc but Windows does not recognize my phone.. it says: "USB device not recognized.. the last USB device you connected to this computer malfunctioned and Windows does not recognize it"
I do not know what to do now.. when i try to flash a ROM with the LG Flash Tool it fails because LG program does not recognize my device..
PS: LG Support Tool recognizes my phone (it shows the model) but i cannot flash a ROM
Thanks!!:fingers-crossed:
Click to expand...
Click to collapse
Were you using a custom recovery? (i.e. TWRP)? If so, are you able to boot into recovery? It was a few years ago but whenever that happened to me I would have to use the hard reset option. If I remember correctly, on my LGG2, I would hold down the power button and the volume down button at the same time until the LG logo appears, then right when it appears, release and re-press both buttons again holding them down again until the hard reset option showed. Then when it asked me if I was sure I wanted to reset my phone, select yes (it made nervous the first ten times or so). Eventually I began to trust it would, in fact, do what I was informed it would do which was boot into TWRP without actually resetting anything. From there I was always able to flash a new ROM etc. Anyway, if you knew all that sorry, just trying to help. If not, please get second opinions since I will not be held responsible for your device and since it's been years since I tinkered with mine. Having a Samsung now, I don't mess with it cause rooting a Samsung Note trips Knox and then Samsung Pay is disabled.
Anyway, happy flashing and best of luck to you. It was an awesome hobby while I was involved with it.
Cheers!
Sent from my [device_name] using XDA-Developers Legacy app

Zte axon 7 mini edl backup needed - lost stock recovery!

Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.
This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version
A18xcn said:
Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.
Click to expand...
Click to collapse
If you have white screen or ZTE logo then I know how to solve it.
Funny enough, hook the phone to the pc, open adb command and type adb devices.
You will see you pc recognises the phone in adb as recovery.
If this happens let me know and I'll show you how to push the entire bootstack to data/media, then write all these files to each partition. After that your twrp will work and you are done.
These happened to me about 10 times now and I even created a bat file which I double click and it does all the operations at once then reboots straight into twrp. Quite cool actually.
Nevertheless I'm also interested in an edl ROM to umbrick another axon 7 mini I have which is totally, utterly bricked.
I have opened the phone (still opened) and I managed once to get the test point to work and connect to qcn configurator but since then I never got it to be recognised again.
Good luck
Cheers
bius88 said:
This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version
Click to expand...
Click to collapse
Mate, you don't know how helpful this post was.
I have bricked this [nasty] phone about 10 times.
but yesterday I learn yet another lesson, after trying to flash a new splash screen, the phone went totally dead, connecting directly in DFU mode.
I sort of panicked because I didn't have a fresh data backup and there aren't full EDL ROM for this phone easily found on the web.
After focusing in making sure my laptop had the correct drivers (loader/bulk/adb) and after I got confident to use the deepflash cable to move from DFU to EDL, bulk device recognised, right click on it and update the driver to show the loader (901D) then I though what would be the next step.
I did not understand the MIflash tool and the version I had didn't seem to work at all I scratched my had for a while.
I then used the EDL tool, placed your files into the FULL folder and ran through the steps...….mate.....that was beautiful.
I ended up flashing the full B13 on top of the B09 and the system works perfect without any loss of data.
Having learnt all this, I went brave and confident I could rescue my other axon 7 min, which had been dead for over 2 months. Although I had to open it to access the test point, after about 50 or more attempts, I had tried lots of combinations, test point again etc.
It turned out I have left the phone plugged in to the PC with every plug disconnected except the usb board and went to do the washing up. 2-3min later my pc gave a sound, loader 901D was already ready and I repeated the exact process.
You basically saved both of my phones!!!! THANK YOU

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

Categories

Resources