Problem with BIOS Tablet Onda v820w - Windows 10, 8, 7, XP etc.

I updated days ago with bad rom the Tablet Onda v820w with windows 10.
I found the correct Bios and now I have the correct file.
But now, I can´t access to windows to update the flash.
How to unbrick this tablet.
Some method to flash the bios outside windows?
The tablet power ON but screen is black, but microusb works It turns on the light of the hub that I have put
The BIOS brand is "Insyde".
If need moore details please ask me.
Very Thanks four your help.
Regards

can you access command prompt (CMD)?
or
can you access the bios and flash from there instead?
only ever flashed bios a few times (on desktop) but ive always done via the bios screens rather than in windows itself.
.

Hi
I can´t access to CMD, because the screen don´t turn on.
Only can put pendrive and Keyboard with MicroUsb hub. (This turn on the light when push the power button)
But I don´t know if tablet have some method to rescue the bios from Bad update.
Thanks

I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?

locoslaw said:
I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?
Click to expand...
Click to collapse
Hi I have the same tablet, when it works it is perfect, but the screen scrambles and the console become Un usable and freezes, i thought that it might just be windows 8.1 so I managed to put windows 10 on it last night but today it is doing the same thing. Could some one offer some advice.

Well...
Hi, I was able to fix a v975i tablet that was completly dead, because of wrong bios update, in my case i use a programmer unit and pro skills to weld. Basically you will flash the bios and download the correct bios , but i had to desolder the chip from the motherboard.

Related

Chuwi VI8 Bricked (Blackscreen)

I have a problem, I flashed bios and now my screen is black, I can't see anything and I can't do anything... Can you help me?
Everx89 said:
I have a problem, I flashed bios and now my screen is black, I can't see anything and I can't do anything... Can you help me?
Click to expand...
Click to collapse
You may have flashed the wrong bios.
I had a black screen to, the back-light was on, but the screen was displaying nothing.
Do yo know if windows boots?
You can see that if the power led flashes green a few seconds after booting the device for windows boot, for android boot you have a sound notification from the mailbox.
If you are in that situation, you can try the following process, tell me and I will try to provide you the right links.
I had flashed the wrong bios (single OS without hdmi instead of the super vi8 bios) and had no display anymore, I had to flash again the right bios without display, only by memory.
You need a USB hub with a USB keyboard. (and another pc to get the files needed to reflash)
- I got the bios for the right version of the vi8 (look a the model number on the back of the device) on official chuwi website (in chinese but I used google chome translation)
- I put the bios on a usb key root with the Onda flash tool executable and changed the extension of the bios file from img to fd.
- I plugged the usb key in the usb hub
- I booted windows and logged in 'blindly'
- I pressed Windows key + R to execute a command and typed 'e:update.exe' to launch the flash tool on the USB key, then I heard a sound warning from the flash tool, pressed enter and let the software do its work for 5 minutes.
- I then shutted down and rebooted the tablet by long pressing the power switch.
- I had the display working back with the chuwi logo and estimated myself lucky.
Conclusion : Check the destination model of the firmware twice before flashing!
reply
hi ;
I am in the same situation could you please share with me the flash tool link.
Ok go to this post and download the joined zip : Then replace the bios with yours (file with the fd extension) change .img or .bin to .fd, if I remember well.
http://forum.xda-developers.com/showpost.php?p=59869681&postcount=3
kuroz91 said:
Ok go to this post and download the joined zip : Then replace the bios with yours (file with the fd extension) change .img or .bin to .fd, if I remember well.
http://forum.xda-developers.com/showpost.php?p=59869681&postcount=3
Click to expand...
Click to collapse
Many thankks.
it was difficult for me work under black screen but when I connect tablet to HDMI TV it can display screen
now I just need windows installation package to finish reinstallation, I found this page but it requires for baidu account to can download it
many thanks for your help.
HI, I am about the same way. (ended up bricked this way trying to clear cmos without opening it)
I have checked and my tablet is running windows for good (checked with nano HDMI cable).
backlight is on, touchscreen works, LCD is off.
I can log onto Android and windows. I have contacted Banggood ( I ordered it there) and they gave me a link to download "good" bios. I have flashed it but still the same problem.
My tablet is number q32g221509018**
The bios I tried now is CHUWI.D86JLBNR03.ROM
stripes on screen chuwi vi8 dual boot
hi i have problem i flased bios and now i have only stripes on screen how can i make it work?? thx
Chuwi vi8 stripe on black screen
Can you help me how to fix a stripe in my black screen I flash a wrong bios... Pls help me
Anonymous.Developer said:
Can you help me how to fix a stripe in my black screen I flash a wrong bios... Pls help me
Click to expand...
Click to collapse
Check out this post https://forum.xda-developers.com/android/help/unbricking-teclast-x89-kindow-t3412968/ and this outside link https://techtablets.com/forum/topic/unbrick-x98-pro-bios-usb-flash/
for information on solving a hardbrick on a tablet.
I'm currently in the process myself with my Teclast X16 Plus
Did any of you fix the hard brick?
Hey. Link is dead.
And i have problem too like you chuwi vi8 .. blackscreen..

cm 12.1 rom is fine but "System UI has crashed" ;-;

My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
wifiwitch987 said:
My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
Click to expand...
Click to collapse
I think first I'd replace the PC. If that's not practical, try to boot it to this .iso once you've burned it to CD:
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Download the recovery.img to root's home, connect to the MOJO and turn it on, open a terminal and issue:
# fastboot -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
Should boot the MOJO into the recovery. If you can't get your PC to boot properly I think you're OOL. You might look into getting a used PC, one that's out-of-date or simply has a bad (or no) HDD, that you can pick up cheap, and use this simple Linux distro (Puppy Linux it is, with fastboot and adb binaries installed by me) for an OS. But be careful, Linux is addictive, and you may find yourself in the same predicament as I am: losing patience with the bloated domineering Windows OS.
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
wifiwitch987 said:
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
Click to expand...
Click to collapse
You can flash this (or most other linux live-CD .iso files) to a USB drive with a utility called Unetbootin. IIRC it's available for Windows, Mac, or Linux. I have no idea whether your Alpha is capable of booting to it, though. Any chance of borrowing another PC, maybe one a bit more traditional? Your little brother's old slow laptop maybe? FWIW I just finally managed to get fastboot and adb working on a Chromebook with an ARMv7 processor, but I doubt you want to go through that much work. Does the Alpha have an Intel processor?

[Firmware] for the SWM8802

Hi,
Finally there is a complete working firmware (for sp flash tools) for the bricked or in bootloop hanging SWM8802.
If you're device is working wel, then is my advice have fun with it and do not flash it!!
If there is an update from the manufacturer i will update the post with it.
For the bricked or in bootloop hanging SWM8802 follow these steps:
Code:
1) Download Firmware, sp flash tools and mt8127 vcom usb drivers from the link bellow.
2) Extract the folders.
3) Disconnect the device completely from the power!! (I use a 12v adapter to connect the device at home).
4) Open sp flash tools and choose scatter-loading File (search the one located in the swm8802 firmware folder).
5) Press download button in sp flash tools.
[B][COLOR="Magenta"][COLOR="Red"]"Keep in mind that after connecting the power (in my case adapter),
you only have 2 - 3 seconds to connect the usb cable between the device and computer.
That is why you should already connect the USB cable to the computer or the device before starting to flash"
[/COLOR][/COLOR][/B]
6) Power on you're device.
7) Connect the unit to the computer with a usb cable on the front usb port of you're device.
8) If you have done all the steps right, sp flash tool will start flashing your device.
<br>
Firmware, sp flash tools and mt8127 vcom usb drivers (all in one zip file):
https://yadi.sk/d/gZvmllBw3WeoLz
Tutorial on how to install Windows 10 mtk vcom usb drivers:
https://tehnotone.com/windows-10-mtk...tion-tutorial/
With great thanks to 4PDA for the hard work!
sandr2010
SOTSKY_A
Giabursu
AS WITH ANY UNSUPPORTED SYSTEM MODIFICATIONS, USING THIS MAY LEAD TO A BRICK.
PLEASE BE AWARE THAT NO ONE ON THE INTERNET IS RESPONSIBLE FOR ANY DAMAGE TO YOUR UNIT!!
reserved for possible possible updates ........
Working?
Since using this firmware update on the SWM8802, has it gotten bricked or stuck in a bootloop at all again? Or is it working 100% perfectly fine? Any issues you're aware of? Thanks!
The-Ace said:
Since using this firmware update on the SWM8802, has it gotten bricked or stuck in a bootloop at all again? Or is it working 100% perfectly fine? Any issues you're aware of? Thanks!
Click to expand...
Click to collapse
I have the idea that my stereo is working beter, i used the option format in SP flash tools. The only thing is that i needed to find a navigation software because the IGO wasnt there anymore.
No issues or something that i have seen or feel in this rom. The only problem is, i dont like that i can not turn off the beep from the touchscreen in the settings.
my device does not work now does not turn on, Please help with another firmware for my swm8802
thank you
Hi, I have a similar problem with my SWM 8806 unit. I follow all the steps published in this thread but the SP Flash Tool can´t download the firmware (MT8127). It seems like a problem with the Drivers. I have installed the PreLoader USB VCOM, DA USB VCOM, USB PORT and USB VCOM in a Windows 7 laptop.
This is the log:
MainWindow::CreateDLSetting(): Download sceneDOWNLOAD_ONLY).(..\..\flashtool\UI\src\MainWindow.cpp,472)
ISetting::set_stop_flag(): dummpy stop_flag(0x04D81180) set.(d:\home\mtk14060\autoscript\project\wcp2_cleanroom\da\download_agent_main\flashtool\setting\ISetting.h,45)
APCore::Connection::ConnectBROM(): Connecting to BROM...(..\..\flashtool\Conn\Connection.cpp,72)
APCore::ConnMediaUSB:reConnect(): Scanning USB port...(..\..\flashtool\Conn\ConnMedia.cpp,55)
APCore::ConnMediaUSB::Search(): Search usb, timeout set as 120000 ms(..\..\flashtool\Conn\ConnMedia.cpp,21)
USBSetting::SearchUSBPortPool(): SearchUSBPortPool failed!(..\..\flashtool\Conn\USBSetting.cpp,165)
USBSetting::Search(): Scaning USB port failed!(..\..\flashtool\Conn\USBSetting.cpp,139)
APCore::ConnMediaUSB:reConnect(): Failed to find USB port(..\..\flashtool\Conn\ConnMedia.cpp,74)
APCore::Connection::ConnectBROM(): Connect BROM failed: S_TIMEOUT(..\..\flashtool\Conn\Connection.cpp,99)
APCore::Connection:isconnect(): Disconnect!(..\..\flashtool\Conn\Connection.cpp,155)
BackgroundWorker::run(): BROM Exception! ( ERROR : S_TIMEOUT (1042)
Somebody know what I´m doing wrong ?
tks
Can anyone make video of this instruction?
I had bootloop but after Im trying this solution my device is dead after I was put usb A-A to front panel.
can you tell me me some infos about this unit before i buy ?
1] i Want to know the Antutu score of this unit
2] I want to know what GPU chip has. should be Mali400 or 450 i guess,
3] if it supports OTG
thx
samm000 said:
I have the idea that my stereo is working beter, i used the option format in SP flash tools. The only thing is that i needed to find a navigation software because the IGO wasnt there anymore.
No issues or something that i have seen or feel in this rom. The only problem is, i dont like that i can not turn off the beep from the touchscreen in the settings.
Click to expand...
Click to collapse
Hi
can you tell us how you flash the new firmware.
i have the igo backup if you want it
thank you
mihaiwasile said:
my device does not work now does not turn on, Please help with another firmware for my swm8802
thank you
Click to expand...
Click to collapse
my unit is now in the same condition....All i get now are DRAM errors...
Upgade the firmware
Hi guys
i finaly found out how to flash our cheap android 8702 player.
first of all download this https://yadi.sk/d/gZvmllBw3WeoLz
then unzip it to desktop
then go to device manager and add a divice manual choozing the one from the file you unzip Windows_10_MTK_VCOM_USB_Preloader_Drivers_tehnotone.com
instal drivers media tek da usb vcom port
and mediatek preloader usb vcom port
you will not see any new device in device manager just add the drivers
now oper the flash tool and select the scater file ftom the swm8802 firmware folder
then choose format all +download
you are ready now just klick on the green download arrow
after you do that conect the male to male usb cable to pc and to the front usb port at the player and after conect the power cable
now it start to flash the new firmware.
what i found after instaling is that the player is 4.4.4 and its faster
it is rooted
and it needs igo to be installed so copy your igo to sd before upgrade
there is also https://yadi.sk/d/nPuSTzgB3U65b2 update.zip to download if you like this is very easy to flash
just copy the update.zip to sd and go to settings / about device / locale update and click update
everything work grate to me.
good luck
sorry for my bad english
make video
can u make video to see how is working and the interface and i want to know if u can change the radio fm backround
LudaNick10 said:
can u make video to see how is working and the interface and i want to know if u can change the radio fm backround
Click to expand...
Click to collapse
It is exactly the same with the original but faster.
And it is rooted it has super user su.
You can change the background of the radio if you change the backgroud of the default launcer the same background goes to radio.
I will try to make a video just give me time
socioan said:
It is exactly the same with the original but faster.
And it is rooted it has super user su.
You can change the background of the radio if you change the backgroud of the default launcer the same background goes to radio.
I will try to make a video just give me time
Click to expand...
Click to collapse
Does this work on the swm 8802? just run the update?
Anyone tested this with 8802?
Thanks for this info, your english is not that bad!
If have been struggling to flash my swm8802, been following all the steps/downloaded the drivers/scatter files and flash tool.
Still unable to get the flash tool to run, could it be because my unit is still in the vehicle connected to power cord? Could it be that the drivers isnt installed correctly?(code 10 error with yellow sign on driver) or is it as simple perhaps the usb cable is faulty? When plugging in laptop(windows10) I dont see or hear any sign that a unit is plugged in, should I see something?
Sorry for lengthy Questions
Barnard27 said:
Thanks for this info, your english is not that bad!
If have been struggling to flash my swm8802, been following all the steps/downloaded the drivers/scatter files and flash tool.
Still unable to get the flash tool to run, could it be because my unit is still in the vehicle connected to power cord? Could it be that the drivers isnt installed correctly?(code 10 error with yellow sign on driver) or is it as simple perhaps the usb cable is faulty? When plugging in laptop(windows10) I dont see or hear any sign that a unit is plugged in, should I see something?
Sorry for lengthy Questions
Click to expand...
Click to collapse
To make flash tool to work you must first take out the unit from the car. Then have ready an external power and a usb cable plugged to the pc. Start the flash tool press download and then plug the power to the unit and immediately the usd. Flash tool must start downloading
thanks for reply on taking the unit totally out of power, I managed to get it flashed...and now the unit is dead, no button lights no screen, as if the power is totally gone. Please tel me this is the norm and i just need to keep something in for couple of seconds?
Barnard27 said:
thanks for reply on taking the unit totally out of power, I managed to get it flashed...and now the unit is dead, no button lights no screen, as if the power is totally gone. Please tel me this is the norm and i just need to keep something in for couple of seconds?
Click to expand...
Click to collapse
I just tell you what i have done.
i don't know what was the external power that you give to your unit it should be 12V and it has positive and negative
you must know what you do and do it at your risk sorry for your unit but i am writing what i have done
Barnard27 said:
thanks for reply on taking the unit totally out of power, I managed to get it flashed...and now the unit is dead, no button lights no screen, as if the power is totally gone. Please tel me this is the norm and i just need to keep something in for couple of seconds?
Click to expand...
Click to collapse
Even my unit died after the procedure that seemed to have been successful. I can't even run the procedure again as it gives me a "DRAM" error (4032). Barnard27 managed to solve the problem? Who could help me? 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

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.

Categories

Resources