Database Users

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.

I have totally bricked my zte axon 7 a2017g and i seriously need help!!

So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx

Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...

Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.

Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears

Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much

Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09

Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude

Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back

Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"

Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.

RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that

Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//

@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool

Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)

https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly

IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.

Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?

choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this

I'm trying to unbrick my x720 by QFIL but my pc won't recognize Qualcomm 9008 port

My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.

Bad cable or need to reinstall drivers...

marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.

Say sth more about your phone state and history...

marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.

I've no idea how to help you... Sorry.

gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c

tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.

Is yours 722?
Sent from my SM-A730F using xda premium

mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.

gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium

mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.

gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.

So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium

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

Phone doesn't boot even in edl mode

Hello, I flashed a firmware update through a modified recovery and now phone doesn't boot. It doesn't even show the logo, seems completely dead.
I've tried all combinations of keys, none work; if I push vol+ & vol- and connect it to pc nothing happens, it's not detected by windows or MSM Tool
Could anybody help me?

Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using international tool or India while using indian tool or EU when using european tool.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
If this does not work, plugin your device and hold vol-,vol+ and power for a long time.
Make sure that you have qualcomm drivers etc installed.
Win11 can cause problems.

I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.

Hammerhand.17 said:
I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.
Click to expand...
Click to collapse
You did explain yourself correctly. I had the same problem and by pressing buttons i somehow entered edl mode and it was working.
I think it worked that way for me:
I started MSM tool, changed to eu and pressed start. Than i connected my phone and held down power, vol+ and vol-. But it could be that i hold the buttons before i connected the phone.
It will work somehow im sure. Its nearly impossible to brick a a/b device with a simple rom flash.

As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.

Hammerhand.17 said:
As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.
Click to expand...
Click to collapse
English is not my native language, too.
I had no windows sound, no nothing. My pc didnt know there was something connected.
Did you use the MSM tool before? Because you have to make sure that all drivers are installed.

Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.

Hammerhand.17 said:
Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.
Click to expand...
Click to collapse
My phone was dead too. But it did something if i hold all 3 keys together for a very long time but i dont remember completly. But i guess you know how a/b devices work, you never flash both slots at the same time so a hard brick by flashing is nearly impossible.
So the drivers wont help until your pc recognice the phone. ANd if you used msm before, the drivers should be installed.
Are you using the original 1+ cable? if yes try a third party cable.
Try switching the usb ports too.

Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.

Hammerhand.17 said:
Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.
Click to expand...
Click to collapse
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint

jroki said:
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint
Click to expand...
Click to collapse
No, I didn't. I didn't even know that you could achieve edl mode this way. If you make some progress, please share it.

i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here

jroki said:
i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here
Click to expand...
Click to collapse
Have you tried to use deep flash cable?

If you have a voltmeter that can help you in your search.
You're looking for a pair of points, conspicuously by themselves.
They could be blocked by a connector for something like a camera.
One point should measure 1.8V That is the internal power supply.
One point should measure 0V That is the sensing input pin.
If you have any resistors of say 200-3000 ohm that is a safer thing to jump test points that you're not sure of.
When you jumper the points the 1.8V stays the same and the 0V goes to 1.8V
If all else fails you can try to disable the flash by using a 100-200 ohm resistor to ground on testpoints near the flash memory.
If the ROM bootloader finds it can't even access the flash it will also go to EDL mode.
I believe (but don't know) that the "deep flash" cable support is part of the SBL/XBL (and not the boot ROM) and so it may not work on all models.
I've never got one to work, but that may be my fault.
In any case, if someone has authoritative info on it, I'd love to know.