Related
Hello,
I managed to brick my new Feiteng H7100 phone, i flashed wrong rom to it and got a greenish screen when trying to start the phone.
So i formatted the phone in SPFT tool "Format whole flash" and from then it stopped responding, i cant start the phone anymore, and the charging indicator wont light up when charging.
When connecting the phone to try and reflash it the computer recognizes that i have connected the phone to the computer, but flashing doesnt work.
It is the S7180 with 1GB ram.
I hope there is a solution to it and it can be fixed, iam not sure if this can be called had brick or soft brick.
Was very close to throw it out of the window yesterday, but then thought i can give it a chance
Thanks
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Mine is dead also
jemmars said:
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Click to expand...
Click to collapse
Same mine is completely dead after I flash it - Its not recognized by the originally drivers in windows 7. Showing up as an Unknown Device.
if it is showing up as an device, it isn`t bricked. you need to get the right firmware and flash it again. force install the drivers for the unknown device or take the drivers for Rom you flashed. (e.g. flashed wrong preloader from ZTE to a Star device, need to install ZTE drivers)
While I don't know the specifics of the Feiteng H7100, I've "bricked" many an android phone and tablet. Fortunately it's usually easy to fix.
1) Reboot the device into CWM Recovery Mode (usually by holding power and volume buttons at the same time)
2) Plug it into your computer & run "adb devices" - if you device comes up as a Recovery device, then you're probably home free
3) Run an "adb push newly_downloaded_cyanogenmod_rom.zip /sdcard/" - the data location (/sdcard/ in this example) might vary depending on your device
4) Wipe Cache
5) Install Zip from sdcard and choose your new_rom.zip
Hello everyone. I bought MK8099iii with Rtl8723bs. I wanted to changed the rom because i need rooted device for my appradio. I did that in Rkandroid tool and information in the end was:Run ok , but now i have ony blank screen when i connect my device to tv:/ I did everything correctly. I think i found the problem but i cant fix that. Still i can connect device to PC in flash mode and i can flash again but If i am trying to put new rom again to device and i press erase idb its evrythings ok but is just 6 files and after that device is disconnected. I think thats the problem. When i open android tool 2.1 and i connect my device and i press the read IDB i have a lot of numbers. if I test device is succes. . I think i cant erase IDB. Should be more files like 6. I hope somebody can help me. Thanks for your answers
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks to @yuweng
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Reserved
Nice Guide, Can you please list MTK devices ????
421rahman said:
Nice Guide, Can you please list MTK devices ????
Click to expand...
Click to collapse
OK, Will be adding attachments later, Thanks
Salman
--
Thanks @Salman Al-Badgail for this use full info.
Deena Khanam said:
Thanks @Salman Al-Badgail for this use full info.
Click to expand...
Click to collapse
welcome & Thanks
@jamsubzero check this guide
@jamsubzero I saw your post and thread regarding Dead Bricked
Hey guys.
I own a lenovo A328. For the past couple of months my phone, gets poping up "com.google.etc.etc has stopped".
I tried doing a factory reset, but no luck. Then I learn that I can flash it using SPflash tool with the stock firmware.
And luckily, I did it, my phone back to normal. But then, a few couple of weeks, it started to pop up the same error messages again until I can't do anything on my phone, and unitl it boot loops. So, I reflash again with the same firmware (stock).. and it works again. And same thing keeps repeating and repeating;
until I thought I can try to change the options in sp flash tool..
Instead of "Download only", I choose, "Firmware upgrade".... the flashing finished successfully.
BUT when I press the power button to turn it on, nothing happens, and when I charge it, I cant see the charging screen (or it's not actually charging). I'm sure that it is charging before the flashing, and the power button is working.
When I connect it to the computer, i hear a "connected" sound, then "disconnected", and repeating.
i also tried to reflash it, both the "DL only" and "Firmware upgrade", even the "Format all + ...."
and it flashed successfully (meaning, computer still recognized it), but still not turning on.
Please help me. please.
Click to expand...
Click to collapse
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
What you did is you flashed wrong firmware to your device and the result you in Dead Brick, However there is still solution for your problem. Please Please Please do a proper search first and download correct firmware and other necessary files for your device. Please check firmware number ok.
You can Flash it again but you need to open phone and try, Check here for better understanding.
GUIDE : HERE. Or else please go to any mobile shop and ask them to flash. Dont tell the original reason that you tried to flash or etc. Tell them that it stop suddenly and for now I am unable to access it. They charge you about 5-15 USD based on your country, for me they had charged 10U$D me for lenovo A3500-HV dead flashing. Hope this help you.
i got no scatter file in stock rom pls help!
Aller retour si flash tool
Hard bricked Lenovo a7000
**Hi I got problem on yesterday I was install ing new Rom but suddenly my Lenovo a7000 hard brick
It is not responding any point .even charging .and charging light also .it's dead
But it when I connet to my pc it's connecting sound conning from pc ....My phone is dead plaease help
Salman Al-Badgail said:
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks [email protected]
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Click to expand...
Click to collapse
S
Sir please help me out
I have Micromax a120 device. Few days back it got bricked it stuck on bootloop and not working even after factory reset moreover my pc is not recognizing mobile and display message as device descriptor request failed. I have installed all drivers
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
Salman Al-Badgail said:
Reserved
Click to expand...
Click to collapse
Sir please help me out
I have Micromax a120 device. Few days back it got bricked it stuck on bootloop and not working even after factory reset moreover my pc is not recognizing mobile and display message as device descriptor request failed. I have installed all drivers
im having mt8127 mtk device it is not flashing iam having corrupted preloader i tried to flash the preloader it is not flashing , can any body knows to fix it??
How can a phone that's bricked be switched off? Am a bit confused.
Salman Al-Badgail said:
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc)
THIS IS FOR INFORMATION ONLY.
Q. How Phone gets Bricked?
Ans : Basically, phone get bricked during the installation of Android OS (flashing).
Reason/why it happens
- If flashing is interrupted by low battery or loose cable connection during flashing.
- Using wrong firmware or a custom ROM (unstable) to flash your phone.
Result:
* Phone will not boot even after holding the power key and it will not accept charging. (Hard Brick / Dead Brick)
* Boot-Loop
* Restart loop
* No Recovery (In this situation, Hard Reset will not work)
Q. - Why Phone becomes dead (MTK Android Phone) ?
Ans : While installing Custom ROM or Stock firmware (unstable), Preloader (.bin) file becomes corrupted.
PRELOADER - It is the file in MTK android phone which helps to boot the phone.
Tools & Software Required:
SP Flash tool
Android Stock ROM
MTK USB Driver
PC / Laptop
Dead MTK Phone
USB cable.
NOTE: SP Flash tool has 3 Dropdown, Its meaning & How to use:
MOTA SIU : while choosing this function before clicking on Download, only boot, recovery and Android will be updated.
Format All + Download : while choosing this function before clicking on Download, it first erases the old Firmware then install new firmware. (Recommended when MTK phone stuck at logo & hard reset fails)
Firmware Upgrade: while choosing this function before clicking on Download, its update the Android version. (Recommended when installing a higher or lower version of Android manually)
Steps to Fix/Unbrick Dead Android (MTK) Phone
1- Install MTK driver.
2- Download the tool.
3- Unzip it and double click on Flash_tool.exe.
4- It will launch the tool.
5- Download Android stock ROM, unzip it.
6- Click on Scatter-Loading and assign the path of file (Select Firmware i.e. {.txt extension}).
7- Click on Download.
8- Switch off Mobile and connect it to PC using USB cable by pressing Volume down as boot key.
9- Flashing starts and when completed, Download OK will appear.
Also check Here for more Understanding, Special Thanks to @yuweng
Please let me know if anything is wrong here, so that I can make correction and help other member for better understanding.
Also hit THANKS button if you find this as useful info.
If you found this post helpful then don’t forget to share this post with other Android users so that they could get their dead phones working in few easy steps without paying few dollars on it.
Click to expand...
Click to collapse
i am trying to flash vivo s7 and the cable shake and since then the phone is dead, have flashed it several time, it complete but it refuse to on
I need help please
Basically I was flashing updates for my CUBOT Nova and everything was going fine and I tried out this custom recovery which wouldn't mount any partition so it didn't really suit me. And I did this a dozen of times with other recoveries and if anything happened I had the firmware in SP tools ready to be flashed and if I could save going to it I just used the fastboot to flash it, and so I decided to completly stop and just put my phone back to normal and because I done it before I formatted the whole flash, (and FYI every 2 times I plugged in the phone powered off my computer always searched for drivers in the windows update but it failed and so everything still worked) but after I formatted it and plugged it out and in to download the firmware, my computer successfully installed the drivers and at this moment I was like shoot so I tried to download and it didnt recognise my phone and so I uninstalled the driver my computer installed and see if it worked and it kept installing it again, so I decided to uninstall every mtk driver I had and rebooted, when I installed every single driver again it tried to download drivers from the windows update but it failed and on the sp flash tools it goes to 100% on the Downloading DA (so the red bar) and stays like that for a while and I get notifications that I have a unrecognisable usb device and after a while it gives me randomly 2 errors 0xC0050005 and 0XC0060001 and I know someone is going to tell me I dont have the right firmware or that it's not the right ones but it isn't I got from the official Cubot website and I got an early versions from firmwarefiles I think and none of them work, now I just have a phone without anything on it and I cant flash anything on it until I just hope someone would walk me through what to do I would appreciate so much I'm sorry I wrote so much as I had to explain in max detail as I could what happened!
netcrafy said:
How can a phone that's bricked be switched off? Am a bit confused.
Click to expand...
Click to collapse
i wanted to say the same thing, also i tried enter EDL for 2 days DD (helio G80) LMFAO
Hi there
I would like to know if you can help me in repairing my device.
So i wanted to do an upgrade on the tablet and i messed it up.
I was on CMW recovery at first and then i did a format on cache system and data. but when i wanted to flash the rom CM14.1 it fail and the devices restarted.
the screen goes on but i can see faint lines on the screen.
I did make a back up of the rom and tried to flash it back but it didnt work.
I used all the roms and it still didnt work. I tried many SP flash tool and formating and still not working. every single rom has been flash and all are green but the phone does not want to boot. i have youtube and followed the instructions and every single step i can think of but u have a gut feeling i am mssing something.
I cannot write SN on the fone as it will not work. i have uninstalled all the drivers re-install all the drivers did all the instruction that you have provided but still it will work.
the tablet does still detect on the PC and it does work. so basically it is in a bootloop but its not powering up. Some suggested using MRT TOOLS or MIRACLES but i have a problem with that as it always have a virus attached it to and when i download it the pc removes it. so i dont know where i can get a good crack tool.
i really need your help if you can.
Hello Guys
i closed SP tool while flashing
my phone : infinix hot 10s
i cant power on it and cant join fastboot and cant join bootloader
When i connect phone by orginial usb
computer said (USB not recoginzed)
i installed all drivers but now phone is dead and he was rooted so i cant going to warranty
how i fix it?
Kindly Help me,
I was Flashing my Z3 by Flash Tool , i accidently select D6646 ftf file instead *of D6616 ftf , during flashing Flash Tool gives error at Kernal.sin and Phone goes Down,
No Soft or Hard Reset Work,
NO Flashmood / Fastboot Mood work ,
Flash Tool only Show
'Device connected with USB debugging off
19/021/2017 07:21:01 - INFO *- For 2011 devices line, be sure you are not in MTP mode
and Device Manager Shows SOMC Flash Drive,
When Connect By press Vol Down button and Attach USB Cable, USB not Recognized Error Shows*on Windows 7
I have TA backup from Flash Tool ( ie T1 and T2 ) before flashing in case of Partition break, where as
I realize its kernel brokeup
Kindly Plese Guide me what can I do to live my phone back
are you sure fastboot mode doesnt work? just power off and press vol+ and power if led is blue then you are is fastboot mode. then try to flash kernel.sin in adb command with pc . cheers
Yes sir sureonly red led show just for 2 3 sec n then goes off flash tool shows debugging mode off .. i disconnect battery to completly shut off phone after that i connect n same probelm
https://forum.xda-developers.com/showthread.php?t=2646405
xkeita said:
https://forum.xda-developers.com/showthread.php?t=2646405
Click to expand...
Click to collapse
ihad used that trick after whole day research , I can conclude S1tools does not support 2012 upgrade model, I received error as ID HASH IS NOT SUPPORTED,
however my bootloder is unlocked, and I hav unlocked code also, and also phone is rooted ,
Yes this could work for us as we still doesn't have the preloader dump.
AFAIK there is not unbricking way for now.
Somewhere I read that pc companion could work with Q9008. Also worth to try with emma.
I want working on this to finalize the unbricking guide but will not be soon as I need my device for the rom port. When done I will work on this unbricking.
Also it is not a kernel problem. Your flash replaced s1 bootloader with a wrong one.
Good luck a be patient
What about this: https://forum.xda-developers.com/showthread.php?t=1849170 ?
nailyk said:
Yes this could work for us as we still doesn't have the preloader dump.
AFAIK there is not unbricking way for now.
Somewhere I read that pc companion could work with Q9008. Also worth to try with emma.
I want working on this to finalize the unbricking guide but will not be soon as I need my device for the rom port. When done I will work on this unbricking.
Also it is not a kernel problem. Your flash replaced s1 bootloader with a wrong one.
Good luck a be patient
What about this: https://forum.xda-developers.com/showthread.php?t=1849170 ?
Click to expand...
Click to collapse
Thankq sir, for your reply so if its s1 bootloader then is it possible to bring my phone again live will u guide me what the next thing should i do
talharais said:
Thankq sir, for your reply so if its s1 bootloader then is it possible to bring my phone again live will u guide me what the next thing should i do
Click to expand...
Click to collapse
Sorry for confusing :s
I think, today, there is no way.
You can try with the official emma flash tool or pc companion but I really doubt.
nailyk said:
Sorry for confusing :s
I think, today, there is no way.
You can try with the official emma flash tool or pc companion but I really doubt.
Click to expand...
Click to collapse
Ohhh , sir i have TA backup still cant do anything and also charging also doesnot solve problem as mention in one of the xda thread
https://forum.xda-developers.com/showthread.php?t=1849170&page=1
talharais said:
Ohhh , sir i have TA backup still cant do anything and also charging also doesnot solve problem as mention in one of the xda thread
https://forum.xda-developers.com/showthread.php?t=1849170&page=1
Click to expand...
Click to collapse
Not related with TA backup for now. You change your bootloader with a wrong one.
It is almost like if you flash the wrong bios on your mother board. You can't flash it again until someone find an 'electronic' way.
Give a try with pc companion or emma.
nailyk said:
Not related with TA backup for now. You change your bootloader with a wrong one.
It is almost like if you flash the wrong bios on your mother board. You can't flash it again until someone find an 'electronic' way.
Give a try with pc companion or emma.
Click to expand...
Click to collapse
Pc companion is not reconize the fevice actually i explain what i idid,
I was flashing d6616 by flash tool
Firstly i unlock bootloder by sony , through unlock code they email then i rooted the device by kingo root n then flash accidently i chosse d6646 rom instead of d6616 rom then during flashing flashtool gives error at kernal.sin and after that device goesoff
When i plug into the pc it reconize my device as SOMC Flash device andflash tool gives dubugging off
Thats was the whole senrio by which my device brick so after whole story i really disappointed to know that my device is just use for paper weight... :crying:
I downloaded the emma after install it desnot show any usb device
You own a d6616? It have unlockable bootloader :s
Send it to repair center. No other choice.
And yes it is confusing, it say bootloader unlock after the fastboot command but it is not true.
@blackhawk_LA made some posts about D6616. Maybe he could help you.
I just post here to announce you the bad new your device is hardly softbricked.
nailyk said:
You own a d6616? It have unlockable bootloader :s
Send it to repair center. No other choice.
And yes it is confusing, it say bootloader unlock after the fastboot command but it is not true.
@blackhawk_LA made some posts about D6616. Maybe he could help you.
I just post here to announce you the bad new your device is hardly softbricked.
Click to expand...
Click to collapse
Service status shows unlock bootloader to yes.. well very thankful for you reply means there is no way to unbrick my phone
talharais said:
Service status shows unlock bootloader to yes.. well very thankful for you reply means there is no way to unbrick my phone
Click to expand...
Click to collapse
Keep an eye on https://forum.xda-developers.com/z3/devs-only/unbricking-d6603-t3365262
I just brick my device too so will try to make some progress on it
nailyk said:
Keep an eye on https://forum.xda-developers.com/z3/devs-only/unbricking-d6603-t3365262
I just brick my device too so will try to make some progress on it
Click to expand...
Click to collapse
Tanks buddy I am watching your thread, and also let me know when done,
Hi, I decided to post it here because it seems that anything I post on Xperia Ion forum is not read, it is inactive.
I already searched everywhere and I'm loosing my hopes. I'm trying to revive an Xperia Ion and this is what I get:
When I plug the phone in the wall charger the red led turns on for some minutes and then turns off.
The same happens when I plug on PC, when the led turns off it is detected as "Somc flash device" in windows device manager and this shows in flashtool:
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
Nothing changes if I plug in pc with volume + or - pressed, it don't goes into fastboot or flashmode.
I hope you could help me. Thanks
dude i have the same problem as yours i have a z3 d6643 and i made a mistake when downloading the kernal the device loads normal flash mode and flashtools working! power button + volume down runs twrp but it no longer starts at sony black screen someone please help!
evilhedrox said:
Hi, I decided to post it here because it seems that anything I post on Xperia Ion forum is not read, it is inactive.
I already searched everywhere and I'm loosing my hopes. I'm trying to revive an Xperia Ion and this is what I get:
When I plug the phone in the wall charger the red led turns on for some minutes and then turns off.
The same happens when I plug on PC, when the led turns off it is detected as "Somc flash device" in windows device manager and this shows in flashtool:
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
Nothing changes if I plug in pc with volume + or - pressed, it don't goes into fastboot or flashmode.
I hope you could help me. Thanks
Click to expand...
Click to collapse
Same problem with an XZ, someone has a solution?
sometime Win recognize the device as QUSB_BULK
Looks like I killed my Z5. The model is 6683 (Z5 dual), and I flashed with E6533 (Z3+ dual).
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device", in detail VID_0000&PID_0000.
But if I disconnect the battery, it recognized as "SOMC Flash device", VID_0FCE&PID_DDDE
Is it possible to resurrect it?
I hope if I can flash with correct bootloader in this state, it will enought to boot up and able to flash with the right firmware.
Macs1209 said:
Looks like I killed my Z5. The model is 6683 (Z5 dual), and I flashed with E6533 (Z3+ dual).
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device", in detail VID_0000&PID_0000.
But if I disconnect the battery, it recognized as "SOMC Flash device", VID_0FCE&PID_DDDE
Is it possible to resurrect it?
I hope if I can flash with correct bootloader in this state, it will enought to boot up and able to flash with the right firmware.
Click to expand...
Click to collapse
Are you able to connect it in flashmode and fastboot ?
With battery, no.
Without battery, my laptop recognize as "SOMC Flash device", but no tool can connect to it (like FlashTool).
(I think then different PID is the reason)
Macs1209 said:
With battery, no.
Without battery, my laptop recognize as "SOMC Flash device", but no tool can connect to it (like FlashTool).
(I think then different PID is the reason)
Click to expand...
Click to collapse
it seems to me that you are an advanced person in playing with your mobile, this kind of issues is beyond of my knowledge but I was replying to your thread hopefully someone here can help, I'm fearing that you have messed up with your mobile
Well, you could try to flash it from Ubuntu (NOT inside Windows 10 !) via FlashTool,
under windows there are limitations with different device IDs that separate drivers would be needed (and if only "wrong" ID is detected under Linux it doesn't really matter, since it's detected anyway),
perhaps under Linux operating systems you have more luck
Thank you for idea, but not working.
Finally I found an old SETool3 box , and successfully flashed with it without battery
Somehow it can fixed it.
Macs1209 said:
Thank you for idea, but not working.
Finally I found an old SETool3 box , and successfully flashed with it without battery
Somehow it can fixed it.
Click to expand...
Click to collapse
I am facing a similar situation, can you help me by telling me what exactly did you do to solve the issue step by step?
Same Problem With Me PLZ HELP
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
[email protected] said:
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
Click to expand...
Click to collapse
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Flashtool Doesn't Recognise This Device. U can use Setool/ Setool Fusion Box to Repai
bma1973 said:
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Click to expand...
Click to collapse
Bro
In this Condition Flashtool Not Recognised Ur Device. There is only a best solution U Can Use SETOOL/SETOOL FUSION BOX To Repair/ Flash Ur Device.
[email protected] said:
Dear Bro Ive same problem with my Xperia e6683 Total Dead After Wrong Flash with Xperia Z3+ File... SO Plz help me how to fit step by step guide plz....
As on 20 Jan 2017
I've Flash Successfully It With Setool fusion Box Without Battery Use Test Pin Method. Now My My Phone Again Alive..
Click to expand...
Click to collapse
bma1973 said:
Dear Bro Ive same problem with my Xperia x Total Dead After Wrong Flash
The phone is completely dead, cannot turn on, not vibrating on power button etc.
When I connect to my laptop, it says "unable to recognize USB device"
using test pin method it is recognized as "SOMC Flash device"
i have backup ta partition and ftf firmware of my xperia i can't find any tool to flash
can you guide me please
Click to expand...
Click to collapse
wrong flash means wrong kernel!
you might be stuck on black screen when you frist switchon device! the device is running! but since its stuck on bootloops no interface is open!
press power and volume up button for 15+ seconds and let it JERK 3 times , this if force shutdown. the device should get connected now in flashmode