Database Users

[How-to] Repair Damaged Bootloader + Trim Area [Red Led][Unknown Device]

Hello again
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
THIS PROCESS IS FREE
anyway if you want me to buy a Dr. Pepper just

Sometimes even after fix the bootloader the phone doesn't want to boot. In most cases this is by a damaged TRIM AREA (TA).
The trim area is a part of softwere stored in eeprom so it can be read and write with the proper software like SETool.
Read and Write trim area is very easy but you should know that some sectors of the TA are unique for you phone, lets call it Security Units.
The process for repair trim area is indeed very easy.
For sure we need Testpoint like in unlocking or bootloader repair process.
1. Backup Security Units with this script:
Code:
taread:00020851
taread:000207D3
taread:000207Da
2. Write a Working TA backup from another phone (same model)
3. Restore Security Units.
Thats all, now your phone should boot well but is 90% possible that you dont get Signal so for fix that we need to unlocking.
If this last thing is needed you can refer to this thread:
http://forum.xda-developers.com/showthread.php?t=1232033

Wow..Making a tutorial would be nice

This us why i love this forum! There is an awnser for everything. Good work
Sent from my MT15i using XDA Premium App

Alejandrissimo said:
Hello again
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
THIS PROCESS IS FREE
anyway if you want me to buy a Dr. Peper just
Click to expand...
Click to collapse
Appreciated .

rizenreincarna said:
Wow..Making a tutorial would be nice
Click to expand...
Click to collapse
there is no sense in a tutorial if you dont have setool dongle, but i can explain all you need if you want to unbrick you phone
anyway I will do a tutorial with pics for testpoint

i do you mean free?no charge at all to fix the phone?

orly1001 said:
i do you mean free?no charge at all to fix the phone?
Click to expand...
Click to collapse
yes, totally free

Ive PM'd you, I'd like to try your approach to resetting the device..
Cheers
Tony

I've sent you a PM

I sended you a pm too..

waiting for the tutorial

jatt101 said:
waiting for the tutorial
Click to expand...
Click to collapse
There is no tutorial as it's totally remote

Trim area repair process is now tested and working for NEO PLAY and ARC

So it's work for 0% issues?

uyo_kun said:
So it's work for 0% issues?
Click to expand...
Click to collapse
No bro this is for bootloader and trim area repair.
0% issue is about a charging sensor so it can be fixed with this

Alejandrissimo said:
No bro this is for bootloader and trim area repair.
0% issue is about a charging sensor so it can be fixed with this
Click to expand...
Click to collapse
So is this a yes or no? Does the repair of the Trim Area get rid of the 0% battery issue?
What state does this leave the phone in? Will future OTA's screw the phone up again or is it back to factory build?

tonyb15re said:
So is this a yes or no? Does the repair of the Trim Area get rid of the 0% battery issue?
What state does this leave the phone in? Will future OTA's screw the phone up again or is it back to factory build?
Click to expand...
Click to collapse
Trim Area repair does not fix the 0% battery issue. As for your other questions, I have no idea.

sent a pm to you..
//edit:
whole process took about 5 minutes, didn't need to flash new software, just write new semcboot.
thanks a lot, phone is working again!
i can totally recommend this for people having a broken bootloader

its late already guys ! i sent my phone to Store to repair my ARC becaus of waranty .. i hope they can't repair i want misty blue<of ARC s

milestone 2 a953 DEAD after DOWNGRADE

Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help

jakkokko said:
Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help
Click to expand...
Click to collapse
You can't downgrade, search for the SBF here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
Then, read this: http://forum.xda-developers.com/showthread.php?t=1497263

lean946 said:
you can't downgrade, search for the sbf here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
then, read this: http://forum.xda-developers.com/showthread.php?t=1497263
Click to expand...
Click to collapse
i know that i did a big mistake there is any solution pleased

jakkokko said:
i know that i did a big mistake there is any solution pleased
Click to expand...
Click to collapse
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.

Lean946 said:
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.
Click to expand...
Click to collapse
sorry but i sad that i can no more get my milstone boot to flash it with rsd or with memory card i sad it is completely dad and i have exactly the rom witch i was in it and the other one witch i flash the phone with it then it become dead
pleased try to understand me an my problem and help that i think my phone need a jtag to be flashed and unbricked

Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck

Lean946 said:
Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck
Click to expand...
Click to collapse
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung

If your phone shows a black screen right after turning it on, then it means you're on bootloader mode...
Next time pay more attention to the warnings...
Sent from my A953 using xda app-developers app

jakkokko said:
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung
Click to expand...
Click to collapse
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!

rabinhood said:
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!
Click to expand...
Click to collapse
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased

thank you every body i finally resolve the problem by downing this http://forum.xda-developers.com/showthread.php?p=10163846
then put the phone in bootloader mod with black screen and the RSD Lite detect it and i flash it with the good sbf and every think is ok

jakkokko said:
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased
Click to expand...
Click to collapse
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?

alexpsad said:
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?
Click to expand...
Click to collapse
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.

Lean946 said:
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.
Click to expand...
Click to collapse
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!

alexpsad said:
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!
Click to expand...
Click to collapse
They use JTAGs, but even if you get your hands in a JTAG box, I don't think we have any way to flash anything with it.

Amazon Blu R1 HD [Firmware] [Restore] [Unbrick] [Unroot]

How to Firmware Restore the Amazon Blu R1 HD
With the Help of many of you at XDA we have put together a working scatter file and I have pulled the Firmware from the device so that we can now restore this phone.
View attachment 3826922
STEPS TO RESTORE DEVICE AND BE ABLE TO HAVE ADS AND OTA UPDATES WORKING AGAIN
1. Download SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip
2. Extract the SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_HD_Amazon.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete you can unplug the device and reboot it with the power button. Congrats you have fully restored your Amazon Blu R1 HD. Bonus you have also enabled bootloader unlocking if you want it.
Tutorial Video with all the steps need to restore.
NOTE: This has been fully tested on the Amazon R1 HD 16GB model but should work on the 8gb also.

You're the man!

Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.

Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
EDIT - DO NOT USE THE DOWNLOAD+FORMAT MODE EVER ON THE R1, IT WILL RESULT IN A BRICK, IT MAY WORK ON OTHER MTK MODELS, BUT EXPERIENCE HAS SHOWN IT WILL BRICK THE R1 HD!!!! DOWNLOAD ONLY IS THE ONLY SAFE METHOD!!
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....

kal250 said:
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....
Click to expand...
Click to collapse
I rooted my phone via this method: http://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Keep in mind, only "recovery" was checked and nothing else.

yujiba said:
Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.
Click to expand...
Click to collapse
Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Format your phone, but not the bootloader, and then try reflashing

We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs

ColtonDRG said:
We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Click to expand...
Click to collapse
The format method, i stumbled upon, i just added as a last ditch effort, I'm not sure whats causing the errors to begin with. The scatter addresses all still match the block addresses mapped in the new OTA, so that theory is shot, im not sure what else could be going on.

If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:

burnanator said:
If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:
Click to expand...
Click to collapse
Never occurred to try that, curse this trend of non removable batteries anyways -_-

kal250 said:
Never occurred to try that, curse this trend of non removable batteries anyways -_-
Click to expand...
Click to collapse
Yup. That's why i tried it. This is the first phone i have had with a non-removable battery.

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
I just saw your other thread you started
http://forum.xda-developers.com/r1-hd/how-to/question-restoring-to-factory-default-t3440059
And now I see why you had this error. You have the 8gb version not the 16gb. So this method uses the wrong scatter file for you phone. Please update the forum if you still have the phone and need assistance. There are some commands that you can run in adb to see the partition sizes and then with that the scatter file can be adjusted for your phone

sorry for being off topic here but i really need to know if its possible to unlock more 4g bands , in my contry they don't release the infomation of what bands the providers work so its a guessing game, since i got this phone i purchased the 4g sim card , even with the band 12 update still stuck at 3g , even with proper 4g apn still stuck at 3g wich i came to a conclusion that the 4g bands from the Blu R1 HD are not the same as my providers...in conclusion can it be done ( open up more bands to see wich band will get me the 4g) and if so please explain to me how i can do so please.

This worked for me, but I had to factory reset after because OTA was still detecting root.

Help me!
hello, I do all the steps but remains in the logo and reboots

THIS DOES NOT WORK WITH 8GB/1GB version :'(

Hello,
I just want to unroot my Blu R1, what should I do?

DOA Bricked
Any hope for an R1 which will now not even power up?

This will not work on any of the latest versions. My model is a 2GB/16GB - I was on Coltons root and tried this to go back to stock with my phone now stuck in boot loop.
Do not use this method.

SM-950F Hard bricked, JTAG?

Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?

S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me

Thanks, I'll give it a shot

ok let me know then

Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/

Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30

A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??

Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?

Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.

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