Related
So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Xluk3 said:
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Click to expand...
Click to collapse
Not that I know,do you have the stock recovery or twrp?
I have the exact problem with my new zuk z1. Any idea is appreciated. The nice phone seems lost now.
Seems like you'll have to restore your zuk to the zui version again. Do you have qrst and zui version downloaded??
The service port never pops up
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Setup.zuk said:
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Click to expand...
Click to collapse
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Tarsa said:
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Click to expand...
Click to collapse
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
mikarbach said:
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
Click to expand...
Click to collapse
PLease do update me if you manage to fix it. This is getting very frustrating
I have the same problem, caused after a cyanogenmod update... Did someone fix this??
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I've tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
CarlosAir said:
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
If tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
Click to expand...
Click to collapse
No idea, my device is actually dead.
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
CarlosAir said:
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
Click to expand...
Click to collapse
Try another cable, another USB slot, another pc/laptop
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
t.h.i said:
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course I have tried this, with two different computers and two different USB cable, both actually working on my N5X. But the point is, that I do not reach the point, that qfil recognizes the phone. Also not with the trick of starting with power-button/USB-cable. It constantly tries to reboot and with adb I get a message 'not authorized' .
---------- Post added at 11:17 AM ---------- Previous post was at 11:05 AM ----------
carlese said:
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
Click to expand...
Click to collapse
I think in my case the after the first successful CM13-snapshot-installation was two fold:
1. I have not enabled USB-debugging and do not have had connected it to my computer after the first CM13-installation.
2. Due to some unknown reason the automatically update via CM itself has boot looped.
The second point is not a real problem, I think. I have had a bootloop many times before with other phones, as well as with the Zuk, but I was always able to resolve the problem with adb. I think the first point was the problem, so adb wasn't possible, due to authorization problems. The reason why qfil does not work, I really do not know exactly, but qfil in fact was not able to recognize the phone.
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
alexisdance said:
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
Click to expand...
Click to collapse
Sry, no I do not have
Hello!
I have dealt with this sort of problem before and have successfully un-bricked my friend's device. I will be posting a guide to solve this problem soon.
Hang-on!
My ZTE Blade AF3 (T221) can't boot into fastboot nor normal mode (so I could use adb). I can only use recovery mode. I tried to flash the stock firmware through apply update option, but the latest available firmware online is 1.0.4 and the recovery is on 1.0.5 (DIS_RU_QB18D_P731A20V1.0.5). That wouldn't be a problem if the update-script didn't check for the version of the current firmware and abort the installation because it's newer. I tried to delete the checking code from the script, but then the file verification check fails. I didn't find an option to turn that check off and I can't flash a custom recovery due to the lack of fastboot mode.
There is also another mode to which it can go into if I just let it boot without pressing any buttons. The ZTE logo appears, then disappears and the white screen remains. In Device Manager it's identified as "Gadget Serial". I don't know if I could use it somehow.
Is there anything I could do to flash the stock ROM or another recovery to the device?
Thanks for help!
Edit: If someone knows a method to boot into fastboot other than holding down the volume - key and plugging in the USB cable the advice is more than welcome, I just think I tried every kind of button combinations (although I wouldn't have guessed myself the process to go into recovery mode, so there's always the chance).
You already solved it? Maybe i can help you!
codeblvnc said:
You already solved it? Maybe i can help you!
Click to expand...
Click to collapse
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
geiszla said:
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
Click to expand...
Click to collapse
I had this phone, i need to check but have some firmwares in my personal computer. I will try make a easy-understanding tutorial to you
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
I can abd sideload and update from SD card, but everything I have fails signature verification.
edit: so frustrating trying to find that 1 zip
Dizzee said:
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
Click to expand...
Click to collapse
Just use MiFlash, that one's guaranteed to work. Read my DFU unbrick guide to know how to use it. Just skip the part where you have to disassemble the phone, since you can get to EDL mode by (with the phone off and the USB cable connected to the PC) holding both volume buttons and inserting the USB-C cable to the phone.
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Dizzee said:
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Click to expand...
Click to collapse
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Choose an username... said:
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Click to expand...
Click to collapse
I got it from here: http://www.ztedevice.com/support
selected:- United Kingdom > Mobile Phone > Axon 7
it offers a file "AXON 7(ZTE A2017G) SD card software package(328540B2634ZTE A2017GV1.0.0B11)"
which hints at being compatible with A2017G... but is A2017V and is chinese, although you can change the language in settings there is still plenty here and there, plus chinese bloatware
and No, I didn't get cell signal.
I've gone back to Marshmellow, I will try again, didn't think it would be so different/difficult... Although wow at MiFlash.
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Dizzee said:
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Click to expand...
Click to collapse
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Choose an username... said:
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Click to expand...
Click to collapse
... after I finally got it working again (thanks for the assist), I thought relocking it was just making it secure again. I been rooting/unrooting and swapping out roms since the galaxy s2, who'd think you can't unlock and relock... I do think there should be warnings as it is too easy a mistake to make... lmao stop doing dumb stuff you start first
My phone is insured so I'm not overly fussed, but others will be less fortunate.
hello everywone...i have a troble to...my phone is A2017GV1.2.0B04 like this in post.
I bay this phone whit broken screen, i change the screen and try sim card but the phone is locked Whit google account... When I try my sim to test microphone, the phone it's work OK, but I unlock google account whit add tools and after that my phone don't have a service.
Phone tells no service or turned off airplane mode...what is not true... I can change the 4g/3g/2g connection to only 3g or something else... Wi-Fi and everything else work great but no service... The phone see what operator is on sim but no service... Somebody to help me please and tell me some tutorials how to fix?
I by this phone from Denmark and now I'm in Serbia... Eny help please
Thanks anyway Dragan
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Mistake,whit adb tools...
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&_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&_ct=1551037935701&referrer=https://www.google.com&_tf=From %1$s&share=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