Database Users

[CLOSED]Yoga Tab 2 (830, 1050, 1380) - get back to KitKat

@MikeChannon removed OP. please close
what? lol

Yeeha! You are the magic man....

workdowg said:
Yeeha! You are the magic man....
Click to expand...
Click to collapse
He truly IS the man. Helped me out BIG style.

ionioni said:
READ CAREFULLY AND BE WARNED BEFORE ANYTHING:
THIS CAN HARD-BRICK YOUR DEVICE AND I TAKE NO RESPONSIBILITY FOR THAT!
use it only if you must or not at all
you can read this for some details about what bricks are so you understand what you can get into
this is for all Yoga Tab 2 models 830, 1050, 1380 (regardless of the submodel F,L,LC)
it restores(downgrades) your bios firmware from whatever Lollipop version to the original/genuine one from the latest KitKat stock rom released by Lenovo (and all the latest KitKat stock rom's have 150422 in the rom filename, ie April 15, 2015 and nothing not even minor OTA's were released after this date for KitKat, next ones upgraded KitKat to Lollipop)
useful to:
1. those who want to return back to the KitKat stock rom from Lollipop (if you simply flash back the KitKat stock rom files and you are still on Lollipop bios firmware you will softbrick as the Lollipop bios is a x64 version while the KitKat loader/kernel are ia32 so you will get stuck at efi shells, bios screen etc)
2. those who took the Lollipop OTA, succeded, but had in time problems (bricked their device) and cannot flash a Lollipop stock rom as they don't have one (not being released by Lenovo/available yet and at least some 830 and 1380 models are in this situation), so they must flash back KitKat stock rom and after take the OTA to Lollipop (and the KitKat flashing part put's them in the same situation as those from p1.)
3. those who tried to take the Lollipop OTA and had problems and they tried to flash KitKat stock rom and yet they are failing (this could be due to problems in the updating while OTA was applied, yet could be that their bios firmware was updated to Lollipop version)
4. those who want to test stuff (going down/up between versions) ... you name it...
how to use it:
1. first download and extract the corresponding tool for your device (830 and 1050 models share the same bios firmware so they have a common tool), while at this you can watch the little attached recording i made with the tool restoring the bios for my 1380F tab so you know what to expect when you run it. USE THE TOOL THAT MATCHES/CORRESPONDS TO YOUR MODEL, you can hard-brick if for eg you use the 1380 one on a 1050 model (didn't even tried but nothing good can happen)
2. place your tab in the DnX mode: power off (by force if you have to), press and hold both VolUp and VolDown butons, keep them pressed, now press Pwr to start and release Pwr when it turns on/buzz (but keep holding pressed Vol buttons), in a few seconds your screen will display "Fastboot starting..." and it will hold on that, now you can release the Vols (you are in DnX mode). you must get that message, try again the whole sequence until you succed, don't move on until you have that "Fastboot starting..." on your screen.
3. run the tool (you must have the intel drivers installed, if you flashed to your tab at some point you should have them already), follow the messages i think it's quite easy and straightforward, in a few minutes you will be done and having a brand new kKitKat bios firmware on your tab
(3) if while running it hangs on the "Preparing to push files..." message, and your tab starts to the whatever error message you had before it means that you already have a KitKat bios (the tool works only with the Lollipop bios firmware) so you don't need to restore the bios, you can flash stock KitKat rom directly (in this scenario the tool doesn't modify anything on your tab)
4. when it finishes the tool will automatically reboot your tablet, leave it for a few seconds to start (it will most likely go ninto some efi shell, or bios screen whatever your old files were) afterwards turn it off (long press Pwr) and that's it
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
i must warn you again, while i tested this tool (i think i moved from KitKat to Lollipop and back at least 20 times and never had any issue with it) you are the only responsible if something bad could happen, this is playing with bios (and any mistake will hard-brick your tab so you will have to send it to a service for fixing). make sure you have enough battery (while i used the tool even when i was with 5% on my battery i would not recommend, i say at least a 30-40%, the process runs only for 2-3 minutes so that should not be an issue). and of course once it started the flashing DO NOT EVEN THINK OF INTERRUPTING! (you could close other software on your PC that maybe can hang your computer while flashing.. you got the point)
Good Luck!
edit: i already have messages about successful bios restoring (as expected no? ) but failing on completing the OTA to Lollipop update after flashing anew the KitKat stock rom. to them and to all of you people who are going to Lollipop from your newly flashed stock KitKat: SET YOUR COUNTRY CODE!!! after you flash back stock kitkaton the first boot input ####6020# in your contacts and a dialog will pop from which you MUST choose a country (no matter which one, preferably yours or a close one), then after the tab reboots for updating the region and comes back to Android check that you have a country code set by entering #### 59930# and it should show the code you chosed. if you take the OTA without a country set you will FAIL! if you failed on your OTA to Lollipop flash anew the stock KitKat rom and set the country code
also do not take an OTA if your device is rooted, always UNROOT first then take the update, and you can root back after or just don't root until you finished the whole Android installing and OTA updates
Click to expand...
Click to collapse
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.

Works perfect! Thanks!

daWyrd1 said:
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Click to expand...
Click to collapse
yeah... the guys at Lenovo deserve a break, they have such a beautiful daadeedaadoo sound on the boot animation (that one cannot even disable it )
bisti2004 said:
Works perfect! Thanks!
Click to expand...
Click to collapse
Pentru putin

Mersi Dorin!

My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?

aerofisher said:
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
Click to expand...
Click to collapse
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting

Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
ionioni said:
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Click to expand...
Click to collapse

aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.

aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
http://bfy.tw/2gNc (just having fun) it is the one that says phone support.
ionioni said:
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
Click to expand...
Click to collapse
Yes, once i talked to them (about 5 minutes) they emailed me all i needed and i just had to find a local fedex dropoff center. They boxed it and i got it back in 6 days.... this seems to be a common thing for them....
Sent from my YOGA Tablet 2-1050F using Tapatalk

Yoga Tab 2 (830, 1050, 1380) - get back to KitKat
You are my lifesaver and I just can not thank you enough @ionioni
how can you make a file like restore-kitkat-bios-1380.zip ??!! you are such a genius !! :good:
We will never be able to flash it back to KitKat Bios without this zip file !! :crying:
But why don't we need to flash it back to Kitkat Bios on my Samsung Note 3, S5, Note 10.1 (2014 version) and Nexus 9 ?!!
thank you very much for your hard work again and keep up the good work pls

this was on my inbox and it should continue publicly maybe others can benefit
KainXSS said:
I'm wondering what your flashing to the tablet with your tool, I have a Lenovo S8-50F and lollipop is pretty abysmal on it, so I'm wondering what your flashing to downgrade the bios so I can try it on the S8, since its very very similar to the 830.
Click to expand...
Click to collapse
you should NOT use the tool unless it is made exactly for your model, or you most likely will hard-brick. moreover Lenovo uses an in-cpu module for digitally checking the authenticity of the firmware you have on your board at pwr on time and even if you have a bios that would work on your model if it is signed with another key it will cause a hard-brick (the measured boot module will refuse to load the IBB in the new bios).
for eg if one writes the 1051 windows variant of bios on the 1050 android one (they are identical in hardware) it hard-bricks (tested).
send me a link to the latest KK stock rom for your device and i will check on it.

That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.

bombolota1 said:
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
Click to expand...
Click to collapse
not so much you can do, the hardware is fine, it just got the wrong firmware in it... somehow you must rewrite the bios but you cannot do that from the outside (ie by software means) without being able to boot at least in DnX mode. you can check quickly ... if after you PwrOn (well.. after you long press Pwr button as at this moment Powered On of Off are werid concepts ) you don't get NOTHING on your display (ye not even the Lenovo -> Powered by Android white/black logo) than that's it (try maybe to see if somehow DnX didn't got hooked by entering a fastboot devices and see if by some miraccle you don't see your device there)
your device must be opened by a repairing service tech (especially if he is on warranty), you could do it yourself (i did) but you need the appropiate tools and know/how otherwise from a hard-bricked yet recoverable (the hardware is ok) you will transform it into just a paper holder

updated kitkat bios restore tool to version 2 (foolproof version). read the main thread post at the beginning.

Good morning.
Please let me introduce my situation. I use Lenovo Yoga tablet 2 Pro. On 9-th of november I updated Android to 5.0.1. Unfortunately, one of my commercial aps now can not make a connection with external device (no appropriate information about USB connection is appeared).
I am affraid the problem lies on the Android 5.0.1 system. Before that everything had worked perfect.
That is way I decided to downgrade to the Androix 4.x.
I found above treads, but have some doubts.
Is above tool downgrade my system to Android 4.x or do I need to do some additional operations, to get back to the Android 4.x?
In the section - how to use it (point 5) we can read:
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
Click to expand...
Click to collapse
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.

pawlikp100 said:
In the section - how to use it (point 5) we can read:
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
Click to expand...
Click to collapse
you must:
1. Downgrade the bios using the restoring tool (you mention "Yoga Tab 2 Pro" so you must use the 1380 version), and you must do that so you can flash KitKat stock rom on your tablet (if you try to flash directly, without the bios downgrade it will fail and you will soft-brick your tablet)
2. After restoring the bios, download from here your stock KitKat rom and extract
3. Flash using Intel Phone Flash Tool (open with it the "flash.xml" from the target_bin directory of the extracted archive). the Intel Tool can be found in the tools directory of the same extracted archive.
4. After you finished sotck KitKat flashing, remember to set your contry code (####6020# in Contacts), also it's not necessary to make your settings wifi etc before you set your country code as they will anyway going to be deleted (a factory reset is performed on country code setting operation). if you don't set a country code you will fail when upgrading to Lollipop.
5. Update using the Lollipop OTA or stay on KitKat

Thank you for explanation.
I download system, installed Phone Flash Tool, open it and chose flash.xml, but after connecting my YT2Pro I can not see device specific with "Start to flash" button in the Device list area of the program.
see below screen. Is this screen looks as it should? (ups, unfortunately I can not post images, because I am new user).
One more thing, tablet should be turned off during flashing?
Right now my tablet is connected to the laptop by USB. It is not switched off and charging is in progress (laptop does not see my tablet as an additional disc/device).
Is above status correct?

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

Unbrick a SM-J510MN using a working SM-J510MN

How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks

Gianlucas94 said:
How to unbrinck an SM-J510MN using another one that is working to get the files needed for odin.
Does having a working device help me?
When I try to use odin I get the message "Volume Size is Too big"
Thanks
Click to expand...
Click to collapse
Wrong firmware.

I had my original SM-J510MN bricked last night because I tried to install a corrupt or incompatible TWRP image on it, so, in the way all through the hell I did the following:
1. There is no information on Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally, I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock ROMs which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1 and then the phone booted normally.
While I was looking for a custom ROM then I didn't realize the WiFi stopped working so I am looking for a solution.
2020-06-06
To bring the Wi-Fi back to my device I had to flash LineageOS 14.1, and then you will be able to flash any custom ROM you may find.
I hope this helps, greetings from Colombia.

akira_yuki said:
I had my original SM-J510MN bricked last night because I tried to install an incompatible TWRP on it (wrong device with similar name), so, in the way all through the hell I did the following:
1. There is no information in Google about this exact machine (MSM8960).
2. I messed up with SmartSwitch PC Software piece of junk by reinstalling the driver which never worked, provided by its own SmartSwitch option menu.
3. That driver installed before was never going to work because you have to boot Windows 7 in a way to avoid signed drivers checking (Pressing F8 at boot).
4. After a research I found out that I had to downgrade the SmartSwitch version to a one with the enabled tab "Device initialization".
5. Finally I had the driver and a correct SmartSwitch version just to realize I had to type the Model name of my device in UPPERCASE because those Samsung engineers didn't realize a normal user may be would type in lowercase ().
6. I typed the S/N (serial number) located on the backside of the phone and I got the message "Please check the model name and S/N, and enter them again". I triple checked the inserted values, to this point I was feeling I'm totally lost.
7. I downloaded at least 10 Gibibytes (Gigabytes but in the right terms) in stock roms which none of them worked for multiple and different reasons.
So this beautiful COVID-19 lockdown morning I woke up inspired thanks Jehovah God and I just tried the old way to inspect this whole site by using Google like this: "site:xda-developers.com j510mn" and I found a compatible fully working TWRP that I flashed using Odin v3.14.1
I hope this helps, greetings from Colombia.
Click to expand...
Click to collapse
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.

NecromancerViper said:
When you open your device hold power button + Down volume + home button and flash the stock ROM, its a soft brick, not hard brick. J510MN is fully compatible with every version of TWRP.
Click to expand...
Click to collapse
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?

akira_yuki said:
OK, sorry for not having been that explicit, but I'm going to be right now:
Last night I had a useless phone...
satisfied?
does your correction help in any way? does that help with the initial post at all? is there any difference between hard and soft bricked that could help on that?
Click to expand...
Click to collapse
I mean, 3.2 and 3.3 versions of TWRP support MN

Samsung S10 + bootloop ERASE FAIL: READ ONLY

Samsung S10 + SM-F975F/DS IMEI stating Taiwan (Update: Very contradicting information if the phone is Snapdragon OR Exynos) if it even matters to solve the issue I dont know
Owner of the above since 2019 without issues; USB debugging mode activated in 2019 and never changed since then.
Samsung always updated which I assume the UI 3 Android got updated in January of my vague memory/recollection (honestly never paid attention of what is being updated, only that the phone needs to be on charge while doing ANY update)
Issue: phone in constant bootloop every 4 minutes with top message in red color "ERASE FAIL: READ ONLY" see photo attached
Cause: happened 4 days ago: Watched video stream on chrome browser; phone froze and applied a 10sec. power shut off (never had to do that before, 1st time)
Investigation:
I tried (found out by doing so) to interrupt the bootloop with pressing Power button and same time Volume Down Button in order to restart it and follow the following commands found on the internet as per UI 3 update:
Recovery Mode as followed does nothing:
Hold the Power button of your device till the power menu pops up and select Power Off. = does not apply as in bootloop
Wait for your device to turn off completely. = it does never turn off completely UNLESS I press Power button and same time Volume Down Button und plug into USB C Data cable of which the charging circle with the lightening strike appears without any percentage % of which photo is attached (phone charge can keep up with its bootloop in order to avoid battery drainage as there is no % indication)
Plug-in a USB-C data cable connected to your PC or USB-C earphones in your device. = I start from here whenever the phone restarts every 4 minutes or whenever I do it manually by pressing the buttons as I described in point 2.
Now, check if your device has a Bixby Button (Such as Galaxy S10/Note10):
Without Bixby Button: Press Volume Up + Power Button for a few seconds.
With Bixby Button: Press Volume Up + Bixby Button + Power Button for a few seconds
After the above steps, you will boot into Recovery mode.
Download Mode as followed does nothing: IT DOES WORK NOW you need to be very fast before the phone starts (recovery mode does not work)
Make sure you have a USB cable connected to the computer
Then press and hold the Volume Down and Bixby buttons at the same time
Continue holding these two buttons down while you insert the USB cable that is connected to the PC
Recovery Mode before update instructions as followed does nothing:
Step 1: Start by turning off your Galaxy S10.
Step 2: After it’s powered down, press and hold Volume Up button and Bixby button (this is the button underneath the volume buttons in case you didn’t know).
Step 3: Without letting go of the Volume Up and Bixby buttons, press and hold the Power button.
Step 4: As soon as your device turns on, let go of the Power button.
Step 5: After you see a blue screen, let go of the remaining two buttons. Now you are in Recovery mode.
Download Mode before update instructions as followed does nothing:
Step 1: Turn off your Galaxy S10.
Step 2: When it’s turned off, press and hold the Volume Down button and Bixby button.
Step 3: Without letting go of the two buttons, press and hold the Power button.
Step 4: You will get into Download Mode.
Have tried all the above methods several times the past 4 days.
Have drained the battery in terms of keeping the phone in bootloop resulting in no power.
Unhooked the battery by means of removing the rear panel and unhooking the battery cable for more then 15minutes and repeat the 4 different methods
Unhooked the mainboard from various connections and put together and repeat the 4 different methods
No indications in Windows 10 Device manager
Questions, doubts and thoughts:
Is it possible in this state to access with ADB of a professional in order to perhaps clear the cache, resolve the issue without having access to recovery mode?
Should I simply try to purchase a new battery even though I never had any battery issues?
I am aware that a motherboard change will resolve it to the cheapest way possible but as I like to save the data such as different accounts this is not an option besides the phone is physically in good condition (never went under water or dropped). maybe to unsolder the flash memory onto a new mainboard as recovery mode might be part of the processor where the RAM is saved.
Any way to drain the entire phone further which may resolve the issue without loosing data. Similar in removing a CMOS battery on a PC mainboard and using a jumper.
Willing to pay and currently living in Europe.
UPDATE: Odin firmware performed by skilled professional member of xda forum, but still not working. EMMC issue which needs to be addressed with ISP in order to fix the issue. unfortunately I was told by local professionals that they do not have the tools for it. Therefor I wonder if someone knows someone who knows someone who can be of help. Location is Spain but Europe would also work.
UPDATE2: Got the phone back from technician who has experience with ISP but still same Error remains as to his conclusion that this is not an Exynos phone of which he has not the hardware tool to fix it and probably no one in Europe will have it.
Thank you very much in advance

Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?

Vuska said:
Sorry... my english not so good...
so the point is whether you can enter recovery or download mode or not ?
Click to expand...
Click to collapse
I am able now to enter download mode.

snakebite3 said:
I am able now to enter download mode.
Click to expand...
Click to collapse
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...

Vuska said:
and do you able to flash stock again ? (newest one, because we cant downgrade the bootloader)...
Click to expand...
Click to collapse
Thank you for following up.
these ones were tried out:
Samfw.com_SM-G975F_DBT_G975FXXS9DTI8_fac
Samfw.com_SM-G975F_DBT_G975FXXU9FUCD_fac
Samfw.com_SM-G975F_XSG_G975FXXU9FUBD_fac
I am not sure but that person who helped me remotely may explain better

According to technician its Qualcomm Snapdragon which can only be fixed with the right tools. Not in europe.
I been getting different information and do require some expertise if someone can please help me

any further advice, input or suggestion?

I also Own Samsung S10+.
its showing the same thing.
tried Flashing Via Odin it failed.
Tried to enter Recovery Mode but also failed to enter recovery mode.

OMG. I thought I was the only one in the world. I sent it yesterday to a data recovery technician to see what they will do since according to some insider in order to recover the data they would have to access the phone and fix the boot of which the problem get solved itself since they can not remove the memory chip itself as it would get ruined. They will diagnose the problem first before they do anything. Obviously a mainboard change would be the easiest but thats not an option.
Was your phone also updated to UI Android 3.0?
How did it happen if I may ask?
I wont give up since my phone is physically totally fine.

Update from a data recovery company its communication:
What we tried to do in order to recover your device's data was to load through the phone's bootloader (in Download Mode) a software agent that allows us (in some cases) to transfer the data stored in the data partition. This software agent has been developed by us together with some of our partners and as we are sure you will understand we cannot give you more details about what this particular software does or how it does it, since this information is covered by professional and business secrecy.
In this case the phone's firmware was damaged to a degree that made it impossible for the information to be accessed with this software.
At this moment, we doubt the data could be recovered by any software available now in the market. That's our opinion, but you can of course send it to other companies to see if they can recover it.
Since I am not the only one anymore with the same issue I recommend for people to come forward in order to get help

So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge

snakebite3 said:
So far there is a tool needed to reprogram EMMC but I dont know which tool neither do I know where to find that person with this knowledge
Click to expand...
Click to collapse
Your device is powered by Snapdragon or Exynos?

LinhBT said:
Your device is powered by Snapdragon or Exynos?
Click to expand...
Click to collapse
I honestly dont know anymore since numerous people said contradicting things.
I am under the impression it is Exynos as of the research of the model SM-G975F/DS

Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).

According to the seller: "The phone is Taiwanese version and CPU should be Exynos 9820"
Maybe someone can help me please.. still

If its Exynos powered, then I have no solution for it. Sorry bro!!!

LinhBT said:
If its Exynos powered, then I have no solution for it. Sorry bro!!!
Click to expand...
Click to collapse
Thank you for your reply.
Can you please explain me why and who I should be looking for.

Anyone has knowledge how to fix this issue, please? USA based

LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
Hi mate, My phone is Snapdragon powered..
My problem is almost similar.. But not exactly.. After almost 2 months I am not able to find a solution.. But after this period of researching and googling about things related to my problem.. I feel now, either any one of the following is the cause of problem:
1. Emmc is stuck or locked in read-only mode `(Can move files from pc , delete already present files anywhere in any directory, but all changes vanish after reboot... all file and directory structure remain intact- moved files from pc gets deleted.. and deleted files which were already present come back after reboot )
2. Corrupted /data and /cache partition, as e2fsck in twrp terminal results shows "filesystem still has errors" and "e2fsck: unable to set superblock flags on /dev/block/mmcblk0p** ) in both these file system (I think they are preventing flashing procedures- Odin stock firmware flashes and twrp custom ROM flashes both are successful, but after reboot no changes can be seen... - Even Recovery.img and boot.img flashes don't seem to work even both are shown successfully flashed in twrp) After reboot current version twrp boots again instead of newly flashed different version recovery.img ... same with boot.img even after running magisk uninstaller zip files.. running uninstall.zip 2nd or 3rd time also shows magisk patched image detected in log which should be removed in 1st iteration itself..
3. Might be magisk is preventing these changes to be made.. or It might be the /System_root creation as mountpoint for system partition which used to be previously /system normally. This might be the superblock creation which not used to be there
My Samsung's twrp and Download Mode seems to be working but no changes made by them even after successful operations by both.
Can you suggest anything? You can look my thread as to get even more detailed overview of what's happening and whatever I'have tried here - https://forum.xda-developers.com/t/...t-not-changing-anything-after-reboot.4462639/
You can see my attachments in my above thread to see my directory structure of system_root and my download mode pictures and odin system ROM flash pictures.

LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
any tips here?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com

Lenovo Tab M10 FHD Plus (X606f) won't power on after flashing older ROM

I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again ?

I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.

ldeveraux said:
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
Click to expand...
Click to collapse
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.

python_rocks said:
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
Click to expand...
Click to collapse
assuming windows, check that your drivers are detecting the recovery module

ldeveraux said:
assuming windows, check that your drivers are detecting the recovery module
Click to expand...
Click to collapse
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch)...
Click to expand...
Click to collapse
Cool. Are you doing a Halium port for this device?

Yahoo Mike said:
Cool. Are you doing a Halium port for this device?
Click to expand...
Click to collapse
I'm not a Halium dev but I'm trying to flash the device. Me and another member of the community have our tablets dead after flushing it with supposedly Android 9 ROM. Not even Lenovo's Rescue Tool is helping now.

python_rocks said:
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
Click to expand...
Click to collapse
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.

ldeveraux said:
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
Click to expand...
Click to collapse
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.

python_rocks said:
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
Click to expand...
Click to collapse
Oh i misunderstood completely! That is worse, i have no clue how to fix it...

python_rocks said:
The tablet won't power on at all.
Click to expand...
Click to collapse
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.

Yahoo Mike said:
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Click to expand...
Click to collapse
Yeah, I've ordered opening kit. I'm going in. Quite a few people got their devices working by disconnecting the battery and connecting it back. I've noticed that no matter how long the
tablet is on charger the LED stays red, it doesn't change to orange or green.
This same problem has happen to two more members of the community. Same tablet.
We had to flag that ROM as it bricks the tablet.

python_rocks said:
We had to flag that ROM as it bricks the tablet.
Click to expand...
Click to collapse
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.

Yahoo Mike said:
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Click to expand...
Click to collapse
Thank you for trying to help.
The flash tool doesn't do anything when I click Download and plugging in the tablet while holding the volume down button. Dropdown option was set to "firmware upgrade" as advised.
The guide suggests that it's for people who can at least power on the device. It says "switch off the phone ..." which I don't need to do since I can't even switch it on

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again
Click to expand...
Click to collapse
Did you mange to fix it?

A. Alaska said:
Did you mange to fix it?
Click to expand...
Click to collapse
You need to use a rework station heat gun or maybe a hair blow dryer might work to heat the sides of the screen to remove it.
I recommend cutting a water bottle in a square or rectangle shape then using the corner to slowly pry the screen off. After that remove the battery ribbon and hold the power bottom for 20-60 seconds to fully drain the charge.
Then recconect it and turn it on 100 percent works.
Just remember you must have the flash tool app and firmware ready in upgrade or download mode while holding down vol. It will reflash the tablet and bam will unbrick.

Just to note down my experiences here as well. I now also got into the same trouble. I tried
TB-X606F_S100015_191127_BMP.zip and also TB-X606F_S300091_201215_BMP.zip
It turns out that with these two you cannot start up the device anymore. Just as the thread-creator described. In my case pluging out and in again seems to give the SP FalshTool the chance to flash again (put it in "Download"-Mode before). So the latest firmware by today - TB-X606F_S300429_21110_BMP.zip - helped me to revive it again.
For me this is nice, but I also wanted to put Ubuntu touch on it just as described here: https://gitlab.com/ubports/community-ports/android9/lenovo-tab-m10-fhd-plus/lenovo-x606 ... unfortunately I am blocked now due to not being able to bring Android 9 on it. btw: There is no proposal on the site which firmware-version is even Android 9. I just guessed from the date.