Problem with M HORSE S80 and SP Flash Tool - Upgrading, Modifying and Unlocking

Hello, I have a big with SP Flash Tool and my chinese phone M HORSE S80 :
ROM for M HORSE S80 (as known with Mpie N9700 name too, it's a generic phone) :
I a new user, so I can't post links but you can type in Google, M horse s80 rom, and go to needrom link
-In June 2016 (dates are important), I tried to flash my M HORSE S80 on my MacBook on Windows 7 32 Bit, it flashs ok the first time, I tried this a second time, but flash stops, and my phone won't power on . I tired several times, but I can't finish the flash, even if I format the NAND Flash.
-During few months, I keep the phone on shelve, and in January 2017, I retry this, with the same method, the same rom, etc ... and, it's strange but it's works the first time, when phones power on, there is a button for wipe cache partition and data partition, I click on this button and it's boots perfectly.
-This Sunday, I tired to flash the phone, but it's dosen't works. I will explain this :
+I tried differents OS and computers, Windows XP, 7, 10 on my Dell computer; 7 on my Mac, and it's dosen't works, I reinstalled clean Windows 7 10-15 times on my PC/Mac
+I can say something : When Preloader VCOM drivers was freshly install, SP Flash Tools recognize this driver as VCOM Drivers for 3-4 times, and after it changes automatically (only VCOM)
+Another thing : When SP Flash Tool is very speedy to flash the phone, phone is automatically disconnected and I have 4008 error (like in June 2016) . But When the program flash very slowly, flash goes to 100 percents, and say green tick. There is more chance to have a working phone in this situation.
+I know this is the good rom, because I flash this in January and it's works perfectly before
+I don't know if it this a hard brick or soft brick phone, because, When I try to power on with good battery, nothing happen in the screen, but when I connect to computer, phone is reconigzed .
+But when I put good battery and I turn on, Flashlight is activated for milliseconds. And when I tried to do another reflash, now flashlight is not activated, but phones vibrates for milliseconds.
+I tried to dissasemble the phone, to disconnect all cables ( screen, wifi, etc ...), and put another battery of another m horse phone, and it's dosen't work
+At the begin, when I flash for the second time, I can see the boot screen, phones tries to boot (I can see the animation and the boot sound for milliseconds, and there is a bootloop, and when I wait 10 minutes after, screen goes black)
+I tried to follow the instructions exactly, but it dosen't work (for example you need to press volume - button when it's flashing)
+I tried every combinaison for go in recovery mode, but there is no access to recovery mode (but there is a recovery mode when I go in mediatek update program, when I'm in Android)
+I tried new, old, etc ... of SP Flash Tool
+I tried differents USB cables
So, I don't know what SP Flash Tool and my phone do, i don't know why it's works in January and not in April or June, maybe i think that i need to wait few months for try to repair the phone, but I want to repair this phone, and I indicate all what I do, so help me please .
Thank you for reading.
PS : I'm French, so it's difficult to me for talking in English.

Resolved problem
Hello, today, I can say I finally resolve my phone problem : I think this is the solution :
-You need to dissasemble the phone
-Place a fan on the motherboard of the phone (The NAND Flash is very hot, so this is why the phone disconnects automatically when you flash the phone)
-After this the flash should go at 100 percents
-Then try to download ZOPO 6560 ROM (the KitKat version)
-Extract userdata and cache file from the ROM
-Put this in SP Flash Tools, and then flash only these 2 files
-When it's done, power on the phone, and try to wait few bigs minutes, normally it's should work, but if it's didn't work, try to do something with cache and userdata files, I don't know
So this is my solution that I want to share if there is some bricked-china phones

Related

Solution for Hard Bricked LG G4 (9008)

Hi guys,
Some people including me faced Hard brick issue with LG G4, which has now two solutions. the first is temporary, i discovered it and it involves using an SD card flashed with Original EMMC dump ( i tested it with H815 ands H811) , the second needs advanced hardware, equipment and soldering skills ( JTAG) .
The solution that i want to explore is trying to revive the phone with the SD card.
http://forum.xda-developers.com/g4/development/unbrick-lg-g4-h811-9008-qualcomm-t3456417
http://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853
The H811 dump that i made has TWRP recovery and unlocked bootlloader, so if someone know how to help that would be awesome.
How ???, its very simple. I dont have very good UNIX architecture skills , but if the SoC successfully booted from the SD card. We could see if it detects the EMMC memory ( with parted or with LS command). I personally Tried to brow /dev/block directory from TWRP i hoped to find MMCBLK1 or something but that was unsuccessful , im pretty sure the TWRP or the Soc Does not mount it automatically .
I really dont know How , but i'm very Sure that there is a Solution headed that way , So if some one is Good with Unix architecture and can find a way to soft Flash the EMMC from TWRP ( installed in the SD card ) it would be very Nice
hi,i tried the sd card method...it boots but immediately gives me secure boot error (1006).
i have an h815 bl locked
Hello
I have LG H815 and have bricked. I have installed wrong firmware so it is brick now.
I try new tot file with QPST . but it says fail what s wrong with me?
My computer is win 10 64 bit
You can fix fastboot mode with this way.
1. First you need to download stock rom that your phone supported. extract laf.img file from rom and copy it into fastboot directory
2. download LG Flash Tool and make it ready
3. open flash tool and load firmware and dll that support your model.
open command prompt and make sure you in fastboot directory where the fastboot and related files are stored.
Run following commands.
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
Click to expand...
Click to collapse
Hurry up, now you need to start flash with lg flash tool, if device does not start into download mode. remove battery and insert again, press and hold Vol Up btn and plug USB cable it will boot into download mode. and your device com port should be 41, if not change it in device manager. and start LG Flash tool to load stock rom. once it finish loading rom your device will start and will show you factory test 1, 2, or 3. if it stuck there more than 3-5 minutes. reboot your phone. now you will have welcome screen.
I hope this will work with supported models.
Hit Thanks button if this work for you to help others for this useful reply.
ayuda
sylentears said:
You can fix fastboot mode with this way.
1. First you need to download stock rom that your phone supported. extract laf.img file from rom and copy it into fastboot directory
2. download LG Flash Tool and make it ready
3. open flash tool and load firmware and dll that support your model.
open command prompt and make sure you in fastboot directory where the fastboot and related files are stored.
Run following commands.
Hurry up, now you need to start flash with lg flash tool, if device does not start into download mode. remove battery and insert again, press and hold Vol Up btn and plug USB cable it will boot into download mode. and your device com port should be 41, if not change it in device manager. and start LG Flash tool to load stock rom. once it finish loading rom your device will start and will show you factory test 1, 2, or 3. if it stuck there more than 3-5 minutes. reboot your phone. now you will have welcome screen.
I hope this will work with supported models.
Hit Thanks button if this work for you to help others for this useful reply.
Click to expand...
Click to collapse
hi , am sorry for my inglish is bad
my lg h815 don't have recovery mode , no fastboot mode , no logo,
without connection to the computer when before if it was
only when press power button the phone make a 1 vibration, but nothing more
i need help¡¡ the phone woking with normality , i make downgrade to mm, bootloader unlocked unofficial, install twrp and flash firmware to android n, flash rom v30 h-rom, and magistic, after swipe for reboot birck no more display
one more thing, when press power button the phone make a vibration but no image in the display , wait a 30 seconds and again press power button and appears a imagen with 0% and a connection cable but I connect it and nothing, the screen turns off, another thing when I remove the battery with the phone connected to the PC the non-battery icon appears but when I put it back it turns off I want to think that it is not hardware
the phone worked very well until I gave it a restart, I hope it is not the plate regarts from arequipa, PERU sorry for my inglish
MichaelCV said:
hi , am sorry for my inglish is bad
my lg h815 don't have recovery mode , no fastboot mode , no logo,
without connection to the computer when before if it was
only when press power button the phone make a 1 vibration, but nothing more
i need help¡¡ the phone woking with normality , i make downgrade to mm, bootloader unlocked unofficial, install twrp and flash firmware to android n, flash rom v30 h-rom, and magistic, after swipe for reboot birck no more display
one more thing, when press power button the phone make a vibration but no image in the display , wait a 30 seconds and again press power button and appears a imagen with 0% and a connection cable but I connect it and nothing, the screen turns off, another thing when I remove the battery with the phone connected to the PC the non-battery icon appears but when I put it back it turns off I want to think that it is not hardware
the phone worked very well until I gave it a restart, I hope it is not the plate regarts from arequipa, PERU sorry for my inglish
Click to expand...
Click to collapse
lol, when you see a screen with 0% and a usb connected image, that mean your battery dead
why not just try to charge your phone? or replace a battery?
ling751am said:
lol, when you see a screen with 0% and a usb connected image, that mean your battery dead
why not just try to charge your phone? or replace a battery?
Click to expand...
Click to collapse
Hello, well after what happened I thought the same and went to buy another battery and when they tried it did not work, I repeat, not fastboot, no logo, no recovery, only a small vibration without screen, it is not detected by the PC in any of its modes as dead, the detail is that this happened after restarting when I had flashed bootloader N, rom V30, magiistic, I gave it restart and it did not turn on again, so I discard that it is hardware .
I think the problem was that I flashed the bootloader with full aboot, that gave me hardbrick I was told in a forum in Spanish I leave the link I hope you help me thanks
https://www.htcmania.com/showthread.php?t=1397519 use this method to unlock the bootloader
Hey MichaelCV
I have exactly the same problem with my LG G4 H815p. I was running [ROM][H815] H-ROM G4 NOUGAT [v29a] _ LG G4. The phone was up and running and last night I flashed the "LG-H815_29a_Modem_and_Bootloader.zip" to try resolve an issue I was having with the mobile data indicator not showing. I flashed the zip in TWRP, rebooted the phone and now it is bricked. I have exactly the same symptoms as you. Windows and FWUL does not see the phone, no matter what combination of keypressed etc that I try.
Lets hope we find a solution here for it.
Chris

[help] ZE551ML crashes, TWRP freezes, no connection in xfstk downloader

Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help
j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware
Thanks for your quick anwer. Will try to get through it haha :good:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help
@j4y_ha
Goodluck
timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw
Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse

bricked zenfone 2 ZE551ML

Hi,
long story short:
- worked for few hours, then refused to start, black screen, just vibrating
- bought it from my mom, by the time I got to see her, too late to retrun the phone. Seems like was a chinese import (I'm in France) so no ASUS support and too late to return it to seller...
- so tried to unbrick it following https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785.
- Got the first steps ok (xfstk done)
- time to unzipthe stuff etc, phone turned off and PC rebooted for whatever reason
Where I'm at right now:
- nothing happens, not a vibration, not a detection in device manager, nothing... (I charged it)
-When plugged into computer, after a while, gets hot (more than battery charging, means CPU working like hell?)
Seems like dead for good? any hope to "reanimate it" at least to the fastboot to resume the precedure?
Thx much for your help, buying another one would be ... super sad and difficult
Cheers!
Try to flash using asus flash tool.
1. Download the lollipop raw firmware.
2. Asus flash tool
3. Drivers .
Now start the flashtool then select your device model from list then browse for the raw file that downloaded.
Now connect phone in boot loader mode.
Then click start it will take some time to flash. During flashing phone restarts at that time again boot it to bootloader mode.
You will loose total internal storage data.
R.sahane1 said:
Now connect phone in boot loader mode.
Click to expand...
Click to collapse
that's the issue, can't enter bootloader mode (phone remains completely dead even if charged, no vibration, screen remains black etc)
thx anyway

Recovered a bricked Zenphone 2 Z008 after 2 years...

Backstory
2 years ago, I installed nougat into my marshmallow zenphone. A few days later there was a problem with 3g and wifi, so after some searching, I found out I needed to flash modem.zip, after doing so, the phone no longer boot, bootloader is good, recovery is gone and fastboot is gone. Spent about 20+ hours trying to recover... but to no success. The main problem was using the XFSTK method, it did boot to fastboot, but the damn phone product code becomes a Z00A, so flashing a z008 rom led to fastboot refusing to flash. Flashing a z00a rom led to bootloop...
Since I wasted too much damn time trying to recover, and I needed a phone quickly, I bought a 32GB mi max for $120 and never looked back.... until today 03 March 2018.
Recovering the hardbricked Asus phone easily
1) Install the intel usb soc http://drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
2) Disable driver verification in Windows 8/10 by rebooting into advanced menu
3) Install intel usb soc above
4) Download and install Download xFSTK Downloader v1.7 https://drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view
5) Download the files for xFSTK and unzip
ZE550ML http://drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
ZE551ML http://drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
6) Open xFSTK,
go settings, tick enable GP flag override and use the number 0x800000807
link the dnx fwr, ifwi and droidboot from step 5 as follows: https://i.imgur.com/mKZoUdi.png
7) Make sure your phone is off, click begin download then plug in phone, it will start flashing
Sometimes it fails while flashing firmware, sometimes it fails while flashing OS. Doesn't matter keep retrying. Pressing volume button while plugging in phone MAY help.
8) Once successful, you will see 4 color background, then usb cable image, then fastboot mode. If you fail halfway in flashing you will stop at either one of the images. Keep retrying until you reach fastboot.
9) At fastboot, you are safe. Go charge your phone for 1 hour. If your screen dies, do not press power button, press volume button it will remain in fastboot mode.
10) While your phone is charging, install asus flash tool https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download the raw file https://drive.google.com/drive/folders/13In6163G8S9BbjiNlEOF-fOXhVIC0z9r?usp=sharing
11) With phone charged, plug in your phone and open the flash tool. Your phone should appear. If not replug usb cable/change usb cable/port, restart the flash tool and leave it plugged in and wait UNTIL the flash tool recognizes it. It will recognize... eventually.
12) select correct model, tick erase data, and locate the firmware. Once recognized, highlight it and click START
13) After 20 minutes, it will be stuck because of the change in serial number. plug out usb cable, restart program, plug back in.
14) Wait for the program to recognize the NEW serial number, then reflash the phone, this time IT WILL BE SUCCESSFUL and will boot into Android marshmallow.
Miscellaneous steps after unbricking
Unlock bootloader, flash recovery, flash custom firmware, root, gapps
Good of you to share. Thanks.
Bricked my own yesterday got it up and running after 6 hrs of looking at guides nice phone good spec but probably be selling on as it not getting any security updates any more I could live with marshmallow but bit wary of no security updates

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

Categories

Resources