Related
Hello Guys
I have a UK Sony Xperia Play which was rooted- using the rooted 2.3.3 kernel Originally and was updated by sony from 2.3.2 to 2.3.3 which worked ok before I rooted the device.
I then decided to use another members rooted firmware which worked - Please see here :- http://forum.xda-developers.com/showthread.php?t=1145729
I wanted to reflash to with 2.3.2 which worked then I did a sony update again over wifi and after that I could not boot the phone at all it just vibrates nothing happens - no boot logo- I have reset the phone by taking the battery out and it is fully charged and it does work in flash mode but when I try to reflash the rom again it using flash-tool and stock firmware the software says it has been done but does not boot. Any thoughts on why this is.The Bootloader has been unlocked previous to root
Thanks
Mark
You've unlocked your bootloader AND updated Over The Air?
Yea he has an unlocked bootloader... There are countless threads warning you not to update over wifi or 3g if you unlocked bootloader... =( try the development forum to see if you can get it unbricked
Sent from my R800i using XDA App
Hi there yes I have unlocked the bootloader the 1st time before I started do u think I should unlock the bootloader again well go through the motions but I cant fastboot blue its stuck in firmware updater green all the time I think its bricked thanks fir your comments I have tried most solutions in the forum without success
Sent from my GT-I9100 using XDA App
Hey guys just got the solution from the developers forum bin4ry freexperia unbrick solution I am happy now
Regards
Mark
Sent from my GT-I9100 using XDA App
Be careful what ever you do because you can destroy your radio if you use the wrong fix.
I have not had your problem but I believe there is a fix binary made as long as you have done nothing to the phone since you bricked it
Edit: /\ lol a little slow I guess /\
Sent from my R800i using XDA App
Glad it worked out for you, sorry I couldn't copy and paste the link for you to unbricked you phone since I'm using the xda app on my play
Sent from my XPlay using XDA App.
Hi
I had the same problem with my xperia play (R8000i), after upload over wifi, my xperia play doesn´t work. i can´t do the fastboot neather the battery charge.
I already made the FlashTool with: R800i_4.0.A.2.368_World.ftf and Xperia Play_Release_Generic UK.ftf
The FlashTool Works successfull but xperia play don´t boot.
Someone here already have the solution for that?
Thanks
I have the exact same issue, what's the fix?
EDIT: OK, rather than start a brand new thread I thought I'd just reply here.
Basically, I unlocked and bootloader of my phone and rooted it ages ago, and totally forgot the dire warnings about OTA updates. I spotted someone on here mention that they'd installed an OTA update on a rooted phone and decided to do it, as I've noticed that my Play is really buggy of late.
Of course, this has bricked my phone. When I press the power button the phone just vibrates, and if I hold it in, it vibrates every few seconds.
I've tried plugging the phone into the PC in recovery mode (holding down back, green light comes on) but my PC says I need an S1boot Download driver (which I swear to god I already have, I think I needed it to unlock the bootloader in the first place!). I've followed all instructions, downloaded the drivers and pointed the installer in the right location but I keep getting a message that says the hardware cannot be installed.
I'm running Windows XP, by the way. Can anyone help a foolish soul?
S1Boot Download issue solved: http://forum.xda-developers.com/showthread.php?p=17497338#post17497338
OK already have this driver installed and can use the FlashTool normally, but the Xperia play does not start, and I can not put them in the way fastboot mode.
When I press the power button the phone just vibrates, and if I hold it in, it vibrates every few seconds.
I have used the PC Companion and Update Service did not work
Does anyone have a solution?
You need to wait for the prompt to connect your phone in Flashtool. When prompted, you have to hold down the 'back' button when you plug in the USB cable. The power light should go green to indicate the phone is in fastboot mode.
Had already done this process.
I already made the FlashTool with: R800i_4.0.A.2.368_World.ftf and Xperia Play_Release_Generic UK.ftf
The FlashTool Works successfull but xperia play don´t boot.
You need to flash the special unbrick tft, it's on the forums somewhere
Fastboot = BLUE light (search button+usb). Used to flash/boot with fastboot commands from a cmd window on a pc/laptop and such.
Flash mode = GREEN light (back button+usb). Used when flashing with flashtool.
Regards Dousan...
Duddyroar thanks
But I did a search on forum and did not find the file tft unbrick.
You could put the link?
Mr_Taser said:
Duddyroar thanks
But I did a search on forum and did not find the file tft unbrick.
You could put the link?
Click to expand...
Click to collapse
I think he's talking about this one by Bin4ry:
http://forum.xda-developers.com/showthread.php?t=1126354
Regards Dousan...
Thanks to everyone who helped.
The phone back to start normally.
Thank very much
How do i rescue my bricked phone!
Click to expand...
Click to collapse
well the answer lies within this thread.
how do you brick a phone
well, there are many ways you can brick a phone.1. you install the wrong software
2.you install a 'broken' rom
3. you install a recovery that isnt supported for our phone
4.or you were messing with your bootloader
etc etc... you get the point
how to rescue a bricked x81st: If you have done a soft brick then you can boot into xrecovery and restore your latest backup. easy
2:if restoring doesn'twork or you have a hard brick then you should either launch:SEUS (sony ericsson update service) or pc companion. click update and follow the steps.
3:if none of that works then you will have to send it off to se. if you dont get some kind of phone company to fix it then its as useless as a real brick lol or a replica of a phone.
3:you can use a flashtool to fix it as well. if you open flashtool you usally get a number of options such as unlock bootloader etc. there should be an option where you can restore it. (lol i think)
Cheersi hope it helped. if it did then please do press the thanks button.
-wilbso
Soft Brick is the common brick we get.
Hard Brick is a brick you can only get with messing with the bootloader. There's no complete brick.
Say something about flashtool too.
Chris95X8 said:
Soft Brick is the common brick we get.
Hard Brick is a brick you can only get with messing with the bootloader. There's no complete brick.
Say something about flashtool too.
Click to expand...
Click to collapse
ok. besides the complete brick is what i call doomsday. thats just my own little thing lol. and yes i will metion 'bout' the flashtool too
how about hard brick??
X8
I bricked my phone while a opened bootloader.Phone was not recognized SIM and i havent data connection too.SE PC repair does not helped me,backup file as well.Only helpful tool was S1Tool with "restore" button.It fixes my phone and i opened bootloader again with success!
Thanks for developers!!!
X8;OPENED BOOTLOADER;nAa kernel;DUAL TOUCH;GINGERXPERIA V17 2.3.7
montekristo said:
I bricked my phone while a opened bootloader.Phone was not recognized SIM and i havent data connection too.SE PC repair does not helped me,backup file as well.Only helpful tool was S1Tool with "restore" button.It fixes my phone and i opened bootloader again with success!
Thanks for developers!!!
X8;OPENED BOOTLOADER;nAa kernel;DUAL TOUCH;GINGERXPERIA V17 2.3.7
Click to expand...
Click to collapse
Quite a few people repaired their phones with s1 tool. Iv never actually hard bricked my phone. IV done soft brick> bootloop but I fixed that be restoring a backed in xrecovery so these replies I
Getting are quite helpful. As long as your phone is repaired everything is alright.
sent from my x8 running gingerdx
Hello, can you please help me! I bricked my xperia neo, while trying to update se tweaked rom v 8.5. Now i'm facing the "sony ericsson" screen, totaly blocked. I've tried many times to flash it, whith wotan client, flash tool, but it's imposible to enter flash mode again, no green led, only bocked se screen, please help!!! how did you manage o get into flash mode?
benga_mircea said:
I bricked my xperia neo, while trying to update se tweaked rom v 8.5. Now i'm facing the "sony ericsson" screen, totaly blocked. I've tried many times to flash it, whith wotan client, flash tool, but it's imposible to enter flash mode again, no green led, only bocked se screen, please help!!! how did you manage o get into flash mode?
Click to expand...
Click to collapse
On the W/X8 and X10 mini/Pro you can get into FLASH MODE by keeping the back button pressed while connecting the TURNED OFF phone by USB.
That being said, you have a NEO which doesn't work that way.
Your phone has "fastboot" - to get there ... turn off the phone, keep the bottom right key pressed and connect the USB cable to the PC.
What you have to do from there on out is either best asked in the RIGHT subforum or through Google research.
B.Jay said:
On the W/X8 and X10 mini/Pro you can get into FLASH MODE by keeping the back button pressed while connecting the TURNED OFF phone by USB.
That being said, you have a NEO which doesn't work that way.
Your phone has "fastboot" - to get there ... turn off the phone, keep the bottom right key pressed and connect the USB cable to the PC.
What you have to do from there on out is either best asked in the RIGHT subforum or through Google research.
Click to expand...
Click to collapse
how did you get this thread back up?
Sent from my X8 using XDA App
wilbso said:
how did you get this thread back up?
Click to expand...
Click to collapse
Hummm...?
I only replied to benga_mircea's post from today.
Or ... did I miss something? *notsure*
Thank you for your help, but I can't acces flash mode or fastboot mode again, lika I use to, after I connect the batery, push the back button, insert the usb, a few seconds and the "sony ericsson" screen pops up again and stays blocked. I think I've killed my phone
Well, for as long as you see the SONY ERICSSON boot logo - and I'm assuming from the way the X8 works here - the boot loader and kernel are intact; there's just a problem boot-strapping the system ROM (shot system, bad flash).
The real problem is that Fastboot isn't comparable to the Flash Mode of our phones ... it's very different.
In your stead I would try to find out how you can perform a "disaster restore" (like we do with our W/X8 through Flash Mode and Flashtool) by flashing back to stock.
Anyway ... just to repeat it ...
1. You need to TURN OFF your phone and DISCONNECT it from the computer/charger.
2. You insert the USB connector into JUST your phone.
3. You press the bottom/right button (also "Back"?) and keep it pressed while you connect the USB to the computer.
Once the phone connected to the computer as a (wild guess!) "Flash Device" or "Fastboot Device" you need the apropriate tool(s) and Stock ROM image - in case PC Companion refuses to repair your phone.
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
Any chance this thread (in the Xperia Neo General section) could be of any help to you?
B.Jay said:
Hummm...?
I only replied to benga_mircea's post from today.
Or ... did I miss something? *notsure*
Click to expand...
Click to collapse
Where did you find it? I mean where did boy find the thread? My Sig? Looking through old posts?
Sent from my X8 using XDA App
B.Jay said:
Well, for as long as you see the SONY ERICSSON boot logo - and I'm assuming from the way the X8 works here - the boot loader and kernel are intact; there's just a problem boot-strapping the system ROM (shot system, bad flash).
The real problem is that Fastboot isn't comparable to the Flash Mode of our phones ... it's very different.
In your stead I would try to find out how you can perform a "disaster restore" (like we do with our W/X8 through Flash Mode and Flashtool) by flashing back to stock.
Anyway ... just to repeat it ...
1. You need to TURN OFF your phone and DISCONNECT it from the computer/charger.
2. You insert the USB connector into JUST your phone.
3. You press the bottom/right button (also "Back"?) and keep it pressed while you connect the USB to the computer.
Once the phone connected to the computer as a (wild guess!) "Flash Device" or "Fastboot Device" you need the apropriate tool(s) and Stock ROM image - in case PC Companion refuses to repair your phone.
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
Any chance this thread (in the Xperia Neo General section) could be of any help to you?
Click to expand...
Click to collapse
Thanks! I tried like 50 times, and nothing, the ennoing "sony ericsson" is booting (no sony ericsson logo as usualy, just the writing) I flashed 10 times in the past whith no problem. Now, even when I put it to charge ( wall charge) the phone is turning on showing that stupid "sony ericsson" writting, I cant shut it down from the on\off button. Before killling it, I've instales stock MT15i_4.0.A.2.368_GLOBAL ROM, then I upgraded to MT15i_4.0.2.A.0.42_Global, then rooted with DooMLoRD_v4_ROOT-zergRush-busybox-su, Installed CWM( wiped cache, updated SE tweaked v8.5 Rom) After the restart, the "se" writting started booting. I've pulled out the batery, and begined flashing it with flash tool(no green led).The flashing started and my little brother accidentaly pulled out the Usb cable; that's the whole story! I've tried like 100 times with wotan, flash tool and FlashTool_0.2.9.1_FOTAUnbrick, no result, even if pc companion tells me "phone conected" and gives me further instructions whith the phone being dead, and the flash tool showing me to connect de device... Thank you for all the help, hope there is a solution. sorry for the long post and my bad english...
---------- Post added at 11:43 PM ---------- Previous post was at 11:24 PM ----------
04/040/2012 23:40:02 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/040/2012 23:40:04 - INFO - Device disconnected
04/040/2012 23:40:06 - INFO - Device connected with USB debugging off
04/040/2012 23:40:06 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/040/2012 23:40:07 - INFO - Device disconnected
04/040/2012 23:40:10 - INFO - Device connected with USB debugging off
04/040/2012 23:40:10 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/040/2012 23:40:18 - INFO - Device disconnected
04/040/2012 23:40:35 - INFO - Device connected with USB debugging off
04/040/2012 23:40:35 - INFO - For 2011 devices line, be sure you are not in MTP mode
Flash tooll results when trying to connect (pulling batery-10 secs, back butoon, usb cable)
benga_mircea said:
The flashing started and my little brother accidentaly pulled out the Usb cable; that's the whole story!
Click to expand...
Click to collapse
Whoa... that's what I call a "security vulnerability".
If the flash process got interrupted because your lil bro pulled the USB cable I'm somewhat certain the NAND is messed up pretty good - no wonder you're stuck at the SE boot logo.
If there's no way by which you can get the device back to normal (read: even the guys over in the Neo sub-board are out of ideas/help) I think your best shot would be to send it in to SE for repair if you still got warranty. SE should have other means to resurrect the device and slap it back into shape.
I'm sorry I can't really help you here with this - the Neo is different from the X8 and also different from the way my tablets work.
Thank's for the advice! My waranty is lost, i've unlocked the bootloader. Only if I could enter in flash mode!
benga_mircea said:
Thank's for the advice! My waranty is lost, i've unlocked the bootloader. Only if I could enter in flash mode!
Click to expand...
Click to collapse
Well, on my Samsung, which has Fastboot, I first enter Fastboot and from there I put the device into download mode for flashing (in theory you can compare "Download mode" to the "Flash mode" - in Flash mode the W/X8 awaits a ROM image to be flashed into the NAND, pretty much the same as "Download mode" works).
Since your Neo isn't completely dead (you just have a shot system due to the flash interruption) you only need to find a way how you can re-write the system.
I lack the time to research how the Neo works, but I think there should be a way to get the device going as you can even "resurrect" a W/X8 where you formatted the system partition (by mistake in CWM, for example). However, that's not as bad as interrupting the USB connection but about the same "ooops" to blank the system.
Flash mode not working, fastboot not workingI Tried a lot of programs (wotan, flash tool, fota unbrick tool, octopus, omnius for se, pc companion, se update. Non of them manages to connect to my phone. If only I could connect for 1 sec. I have a backup of TA, but I can flash it. Thanks anyway!
is it safe to unlock BL, if we have x8 with manuf.code 11W28? pls help me
NarutoDroid said:
is it safe to unlock BL, if we have x8 with manuf.code 11W28? pls help me
Click to expand...
Click to collapse
yes 11W30 or below should unlock fine but for me 11W33 also no problem
Sent from my E15i using xda premium
well, i just flashed the DFHKT_U_4.5.2-109_DHT-22-23 over DEFYPLUS_U3_4.5.1-134_DFP-137, yes, i know, BIG MISTAKE, the DFP-137 was with other name when i flashed it for the first time, now the phone doesn't boot and charge, its practicably dead, what can i do?
Edit: sorry for the title, I tried to say, it does not load or boot.
Edit2:fixed, just had to turn it on like flash a new sbf, then connect to a pc and start flashing another one.
Uf...
Solution
Bleak3993 said:
well, i just flashed the DFHKT_U_4.5.2-109_DHT-22-23 over DEFYPLUS_U3_4.5.1-134_DFP-137, yes, i know, BIG MISTAKE, the DFP-137 was with other name when i flashed it for the first time, now the phone doesn't boot and charge, its practicably dead, what can i do?
Edit: sorry for the title, I tried to say, it does not load or boot.
Edit2:fixed, just had to turn it on like flash a new sbf, then connect to a pc and start flashing another one.
Uf...
Click to expand...
Click to collapse
Hello, I try to help, in this case you have to get a SFB / original Flash file your operator, hence try to turn the phone into bootloader mode (ON button while the volume button (Vol-+) to same time, hence the contectas to computer with RSD Lite and flash it so
WARNING
MUST BE WITH YOUR OPERATING SYSTEM OPERATOR MOBILE HOME AS PACKAGE CAME AS Failure to do so may become unusable PERMANENTLY (an example is putting on the SFB of another operator, or other model)
If you have questions contact me via Facebook, is in my profile page
If I helped you, give thanks
Please ask all questions in the Q&A section. Thread moved there.
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Same happend to me, can't even unbrick it.
Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
same here
Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this