Somewhere along the lines of flashing Lollipop on my device, I must of clicked on something that I wasn't suppose and botched the install. Now its pretty much a 300$ paperweight. I can plug it in and it comes up with unknown device (device scripto failed) code 43. Already not a good sign. Take the battery out and plug it in and it comes as SEMC flash device. Doesn't help cause there's no tool out to deal with that for the Z3. Not that I'm aware of anyway. I'v been researching for about 3 days now and I'm about to buy a new one off amazon. I'm pretty sure its bricked permanently. But I figured it would hurt to get some input before I Buy a new one. It shows deviced connect, USB debugging off which doesn't help as that is not adb or fast boot, flashmode etc.
Correction: I must of clicked on exclude partition and that's probably why its all jacked up.
Its' pretty much a paperweight now lol
Soft brick
Have you tried reflashing it with a older version of flashtool or even a kitkat ftf.
I believe I saw a thread here somewhere the guided you though almost any kind of brick, I'm going to take a look if I can find it
Related
can somebody help me update my t-Mobile XDA? i messed up my phone once already and know i keep getting error 112 during first step in update. CE Erase fails according to the log. Something is clearly locked, but I don't know what i am doing wrong or forgetting. I don't think t-mobile will restore my phone a second time. please help. I have tried diamondv1.2, wm2005, wm2003se, nothing seems to work.
UPDATE: sorry wrong categorie
not sure if that last big is a signature or a real confusement if so then
you cant use rom from one device on another so i would make pretty damm sure which device i had before trying to flash in worst case you can ruin the device 100%
i checked the requirements, so that should be ok. i just keep getting that same error 112, like something is locked. i haven't been able to find out what the error means. any tips?
and the update software i used checks if the device is right...
perhaps some more details:
if i connect it to my charger it will say serial, unless i pull the plug out a bit, then it will say usb.
if i connect to my pc via usb it will say usb v1.00, but after a while this will disappear and the RED light will go on
I have tried flashing it, but since activesync does not see it as a pocketpc anymore, i can't flash.
i have read a 100 posts by now, but i have not found any solutions.
I have (er, HAD) a rooted stock droid 2 global. I read copious amounts of info to guarantee that my move from a blur-laden rom to a considerably-blur-LESS rom (Hexen) would go as pain free as possible. I printed out all the rsdlite info I could find, located all the appropriate files and drivers, found a good, md5 verified stock sbf, and prepared to make my phone better.
Step-by-step I re-read the instructions until I thought I had it right. I started, and waited for the final step "phone[0000]: phone is being rebooted."
It never came. I did everything right and it ended with rsdlite's status on the phone reading :"failed flashing process. phone [0000]: error switching phone to bp pass through mode (0x70bE); phone disconnected," and my pc giving me a "found new hardware: flash mdm6600" message. I am not able to find a driver for the mysterious new device that crops up as my phone is trying to reboot.
My phone sits unperturbed, still reading "SW Update in progress..." If I try to shut it off, it doesn't respond. And when I battery-pull and put the battery back in, it starts up immediately with a "Bootloader D0.11 Code corrupt..." message.
I cannot make it go into bootloader mode. All it does it what I've told you.
So, you tell me, please, am I screwed? Am I the proud owner of a 3-month old brick?
Dan
resolution
My phone is back.
Half the reason (okay 9/10ths) I posted was because I thought my phone was finished. I had searched thru here and the web many times during each SBF re-attempt, and I seriously think there were at least a dozens tries minimum.
No documentation was found for my issue: Bootloader D0.11
On my last search I found a set of Motorola USB drivers that were a newer version than what I had found every other time. They made the difference. The drivers that *worked* were V4.7.2.0. The previous drivers were 4.6.5.
I hope this helps...
Dan
What did you do to get out of the bootloader D0.11 screen?
Well, like I've said, all I did was use a different set of Motorola USB drivers. The drivers made the phone be recognized by the PC during the RSDlite process.
These are the drivers I used: Motorola_Driver_Installer_v4.7.2.0.msi.zip
All I did was RSD *again* exactly as I had been doing.
The only differences are that the whole process begins with the bootloader error message being displayed on the phone. RSDlite will recognize the phone when it gets to that part of the process. And when you get to the "switching the phone into BP mode" message and the simultaneous PC message "found new hardware: flash mdm6600" the pc message appears *very briefly* (presumably because *now* it has MDM6600 drivers) and the RSD process continues, exactly as it was supposed to.
I hope I've answered your question clearly. And I hope this helps you with your D0.11 error.
Just so that you know, I am *no* expert by any means when it comes to this stuff. I'm just like you: looking for answers.
Good luck,
Dan
Thanks for the help. After two hours last of searching and downloading last night, I finally got my wife's droid restored.
Hi there.
Yesterday, for no apparent reason de device stopped syncing my Gapps data. OEM 2.1 ROM. I did a backup and reset the device to factory defaults. Even if battery went to 100% and the USB cable were connected, the phone did not finished the process and now I have a non turning on mini pro. Mac does not feel it, neither Windoze or Linux with dmesg. PC Companion won´t see it neither. Neither FlashTool. I tried to flash it with the original ftf but the phone do not turn on and of course FlashTool won't see it. Tried pressing home and on/off but nothing. I searched like a dork for "bricked xperia x10 mini pro" but there´s a lot of crowd calling a semi-bricked, bricked. Which is not, because a semi-bricked can be repaired with SEUS or even FlashTool.
I know is a whole different animal, but once I bricked a Nokia and with some trickery the device came to life.
Guys, you`re my only hope. I really like this phone for texting and everything.
Thank you for reading. Best regards.
Bump!
Please help me out! At least tell me anything.
Thanks.
same issue
hi,
I am facing the same problem. If u find any solution plz help me.
Guys, i have exactly same problem. I tried connect my U20i using usb cable, but it wont detect my phone. It only charge the phone and wont sync it. Its happen when i restore to factory setting. So if somebody can help me, i really appreciate it. Anyway sorry for my broken english.
Sent from my MT11i using xda app-developers app
PC Companion dont need to see device for repair as u can see at here
bad quality but i think its no hard to see how to do it, hope it will help u
DemoSK said:
PC Companion dont need to see device for repair as u can see at here
bad quality but i think its no hard to see how to do it, hope it will help u
Click to expand...
Click to collapse
What do you mean?
When PC Campanion says "hold back key and connect phone to USB" then It detects the device.
I have bricked SE Xperia X10 mini pro, same simptoms phone doesn't react to anything it's absolutely silent, no image, no text.
And yes I tried SEUS, PC Companion, Flashtool (with ggsetup) and Omnius. Nothing hepled.
May be a battery is down but I can't check it as well.
Same here. The phone doesn't react to "off" button, No LEDs, no display, no sound, won't get recognized by Flashtool when USB plugged in with "back" held, a total, real brick, dark and dead and invisible to all software.
The battery was full - it was full when the phone got bricked by installing a kernel for ICS.
helllppp
sharp_fang said:
Same here. The phone doesn't react to "off" button, No LEDs, no display, no sound, won't get recognized by Flashtool when USB plugged in with "back" held, a total, real brick, dark and dead and invisible to all software.
The battery was full - it was full when the phone got bricked by installing a kernel for ICS.
Click to expand...
Click to collapse
I have the same problem please help:crying:
When you put the tick called "preloader" in Flashtools - then the phone is dead... now only jtag method may can help you(in some phone service)
I remember that one morning I found my Xperia Arc S with stock GB 2.3.4 rom like dead although it was fine when I plugged the charger in before I slept. In the morning I couldn't turn it on, removing and replacing battery did nothing. No light when I charged it. It was really looking like it was forever dead. After a few days, in despair, I tried every reset method I could find about Xperia phones, except the one that finally worked:
I holded the back or menu button (I forgot which one) then plugged in the USB cordon to the computer. I got a green or blue light! I learned later that it was Fastboot mode or Flash mode. Then I unplugged the device, and it started like if nothing happened. I only had this problem once again. Since I rooted it and installed a custom rom, I never had this issue again.
If you didn't try this yet, that is worth trying
Bricked Sony Xperia X10 Mini Pro (U20)
Hi, I really need your help.
I have bricked my Xperia x10 Mini Pro (u20)
I had CM7 Custom Mod running on my phone,
I update CWM 2.0 to 5. something and suddenly it stop working.
It hangs at the Sony Ericsson Boot Logo.
It won't enter into Recovery Mode.
I tried the PC Companion Repair, but it won't go past the "press and hold the back Key"
Because my PC won't recognize my Phone. (I had the SEMC USB drivers installed already)
Please help!!! Thank you
nihilon said:
Hi there.
Yesterday, for no apparent reason de device stopped syncing my Gapps data. OEM 2.1 ROM. I did a backup and reset the device to factory defaults. Even if battery went to 100% and the USB cable were connected, the phone did not finished the process and now I have a non turning on mini pro. Mac does not feel it, neither Windoze or Linux with dmesg. PC Companion won´t see it neither. Neither FlashTool. I tried to flash it with the original ftf but the phone do not turn on and of course FlashTool won't see it. Tried pressing home and on/off but nothing. I searched like a dork for "bricked xperia x10 mini pro" but there´s a lot of crowd calling a semi-bricked, bricked. Which is not, because a semi-bricked can be repaired with SEUS or even FlashTool.
I know is a whole different animal, but once I bricked a Nokia and with some trickery the device came to life.
Guys, you`re my only hope. I really like this phone for texting and everything.
Thank you for reading. Best regards.
Click to expand...
Click to collapse
best solution is to find a person who can jtag
I have the Xperia Z3V. Model D6708, firmware version 23.0.E.1.44. I have recently tried rooting my device (as per the steps found here: http://forum.xda-developers.com/z3/xperia-z3v-general/guide-sony-xperia-z3v-t3100402). I have run into numerous issues with this, as well as an unrelated issue.
As far as the rooting process, I have gotten flashtool and the ftf file downloaded and setup. I have successfully sent my phone into flash mode. Where I run into issues is as soon as I choose the firmware version to flash (located in the .flashtool/firmwares/Downloads directory) it will prepare the files for flashing, but as soon as it starts it errors out and tells me I need drivers for my phone.
So I go to get the drivers, I download them directly from here: http://developer.sonymobile.com/downloads/drivers/xperia-z3-driver/ . They don't work when installed manually through Windows device manager, I Google the issue and see that I should just use the PC companion. I get that all downloaded and setup, and a new issue arises. Initially my phone doesn't get detected in MTP, MSC, or debug mode so I mess with it a bit and have it auto detect. Finally it detects my device and starts attempting to get drivers, but on the last step it says PC companion needs to update, even though it already had, and is the latest version from Sony's website. Eventually it gets to a point where it goes through attempting to install my drivers but at the end, a new issue; "Sorry, the phone/tablet does not work with PC Companion.".
So what the hell am I supposed to do? Even Sony apparently doesn't know what to do with my phone. I have tried everything I can reasonably imagine. Reboots, factory resets, different modes of reboots. I cannot for the life of my get anything to work with this blasted phone.
To add to this frustration (and the whole reason for me trying this in the first place) is the phone has been doing the sleep of death recently. I have only had this phone for a little over a month and it has gone into the SOD 4 separate times. I have not dropped it, I have not water tested it, and I have not altered the software (since it appears to be f**** impossible anyways).
Any and all help is greatly appreciated. I really wanted to love this phone, but it has been a complete nightmare so far. Not aided by the fact of course that it's through Verizon so I'm sure their special brand of f*** you is tossed in here.
Hello everyone! Recently, My phone is Xperia XA with a model F3115 running Nougat, I unlocked the bootloader and tried to follow this guide so that I could obtain root. Here's the link:
Click here to check the guide!
Suddenly, after I followed the step 6 which is to flash a boot_delivery.xml from a Marshmallow Firmware, It was successful according to flashtool, it said remove the usb but when I tried to connect the usb again, for fastboot mode, my computer doesn't recognize my phone anymore and I can't turn my phone into fastboot or flashboot mode, I can't turn on my device. I've searched guides on how to fix. I found a guide where you need to disassemble your phone and do like Box or something and I also found a guide by using this SP Flash Tool (I can't do it as my phone is unrecognizable by the pc thus, showing Unknown Device when connected). I'm kinda scared to open my phone and wished if I can just fix without doing hardware changes. Anyone knows how to fix? Like should I do the assembly or there are other ways? I'm looking forward for your answers everybody. Thanks!
this isnt an answer
The same thing happened to my Xperia XA1 Ultra like 2 weeks ago and I am so screwed lol. I'm not allowed to buy a new phone so now I have to use my J3 2016. I was trying to flash a rom using flashtool but it came up with an error....blah blah blah...Long story short is my phone shows the charging LED when plugged in but doesn't boot into the ROM or fastboot and the other mode...HELP ME!!!!!:crying::crying:
Actually quite bummed about the whole thing cause my mum bought it as a birthday present and had to work really hard for it and now shes upset
Well... yours phone is dead. Change motherboard or buy new one.