Hi all! I have a Sony Xperia Z3 I recently acquired, it seems to be bricked, possibly hard bricked I'm not sure, but the phone refuses to boot into fastboot or flashmode. Here's what I've noticed so far:
EDIT: The bootloader on the device was never actually unlocked! After getting in contact with the previous owner, all he did was use KingRoot to gain root access on the phone, then installed SuperSU and Clockworkmod recovery respectively. After installing the custom recovery the previous owner had then attempted to flash a variant of Cyanogenmod but the flash failed, since the bootloader wasn't unlocked, resulting in the bricked state the phone is currently in.
The phone shows a red LED when left plugged in to charge overnight
If power button + volume up buttons are held, the red led turns off and the phone vibrates 3 times, but nothing else happens
When connected to the computer via USB, the red led will appear again for a couple seconds, then disappear, then appear, and repeats this process until unplugged. While this is happening you can hear the computer recognizing the phone being constantly plugged in and unplugged.
When plugged into the PC, flashtool recognizes the phone as "Device Connected with USB debugging OFF"
Booting into fastboot or flashmode doesn't work, no matter what button combinations I've tried none of them worked to put the phone in either of these modes.
Is there any way I can unbrick the phone? I don't think this is a driver issue as the computer is recognizing the device in device manager and flashtool sees it, however shows "Device Connected with USB debugging OFF". Is there anyway to somehow enable USB debugging in this state?
I've also tried using adb commands to reboot into fastboot, however this is pointless as the phone is not recognized as an ADB device, when you type "adb devices" there is no devices listed.
HUGE thanks to anyone who has any input on my situation, any help is gladly appreciated! Thank you everyone!
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
lavin40 said:
I'm not sure you can do anything about it being hard bricked but I did want to ask you a question how was you able to unlock the bootloader on your tmobile z3, that might be why it's acting up cause I heard tmobile z3 bootloader couldn't be unlocked
Click to expand...
Click to collapse
EDIT: I just got in contact with the previous owner, the bootloader was actually not unlocked, the phone was simply rooted via KingRoot, after that SuperSU was installed, then Clockworkmod recovery. After that the previous owner had attempted to flash a new custom rom from clockworkmod but it failed, resulting in the brick. So as it turns out the most probably reason for the brick was because the bootloader was never unlocked, causing the flash to fail, putting the phone in this bricked state. Does anyone have any suggestions on what I can do at this point to unbrick it, now knowing the bootloader was never unlocked? Thanks!
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Omario-242 said:
If there's no way for you to plug it into the PC without the constant unplugging by itself it's very difficult to do anything. If you try to get into flash mode/fastboot is the phone just not recognized or is it in the "red led" mode?
Usually if you flash a custom without the bootloader unlocked, the bootloader corrupts the system and shows an error while trying to boot. A full brick is very uncommon. You may just try to plug it in and see if EMMA or Flash Tool recognizes the device in any possible way.
I guess the last thing you could do is get in contact with a repair service and ask them if there's a chance that they unbrick it.
Click to expand...
Click to collapse
When I try to go into flash mode or fastboot, nothing happens except for the phone vibrating 3 times and getting the red LED. I've also tried plugging it in and running EMMA however it's not recognized at all by it.
Flash tool recognizes the phone, but throws this message everytime its connected
"Device Connected with USB debugging off"
Is there anything I can do with Flash Tool with the phone being recognized in this state?
I guess as a last option I could try to get in contact with a repair service and ask if they'd be able to unbrick it, however I do not know of any as I've never been to one, hopefully theres another way to unbrick it without having to go here.
Thank you everyone so far who has replied to my thread so far! Please let me know if anyone has the same issue or has an idea for helping unbrick my phone, I appreciate all the tips I've gotten so far.
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Omario-242 said:
I searched a little bit and most of the people which got the same problem said that they weren't able to unbrick it it just because the device wasn't recognized at all. Maybe try the Sony Update Service (program) and see if it recognizes it in any way.
If you start adb and type "adb devices" with plugged in phone is adb giving out anything?
Maybe try to hold down the volume down/up while plugging it in but don't release it at all.
Click to expand...
Click to collapse
Hi, thanks for the tips, I just tried downloading and installing the Sony Update Service program however it terminates immediately after opening and checking for updates as Sony has discontinued the program since Sony PC Companion replaces this program.
If I type "ADB devices", the phone does not appear on the list, as for some reason ADB is not finding the phone in the state that it's in. I've tried repeatedly typing in this command numerous times when its plugged with no luck.
I've also even tried holding down the volume down/up buttons with a rubber band as i plug the device into the computer however no change, I still get the same result.
Thanks for the tips though!
tz16 said:
Use this tool ( Pc companion by Sony). Install driver and repair phone.. It will fix hard brick d6616. You can find intrustion about this tool on google
Sr . Bad english
http://support.sonymobile.com/global-en/tools/pc-companion/
---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------
D6616 dont have any custom from now. Dont flash any rom or kernel custom, it will lose boot, and hard brick
Click to expand...
Click to collapse
I've already tried using Sony PC Companion however it does not detect my phone at all in the current state for some reason. I've tried everything the program told me to do, pressing and holding numerous button combinations however the program will not recognize the phone. Thanks for the tip though.
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
tz16 said:
when my d6616 get bricked.. I follow that way n it unbrick my phone. you should try again.
http://imgur.com/a/pyFcs
Click to expand...
Click to collapse
I've tried this exactly as you showed above, however this is the screen I get stuck on, since Sony PC Companion does not recognize my phone. Look at the picture below. Please let me know if you know how to get past this/get Sony PC Companion to recognize my phone, thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
Hi, thanks for the link and instructions, I just installed the drivers successfully, however Sony PC Companion still isn't recognizing my Xperia Z3.
Anything else I can try? Please let me know, thanks
Unplug your device
Hold Volume+ ....and plug in back till your pc load device " flashmod"
I remember this way, when i do it my pc reconized my device with other name
tz16 said:
Install this driver from Flashtool
https://drive.google.com/file/d/0ByttYFWdXh0kcW1VYVpiWE5iSEE/view?usp=sharing
Picture instruction
http://imgur.com/a/QvXpZ
Click to expand...
Click to collapse
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Omario-242 said:
I'd guess the problem isn't anything related to drivers on the PC.
The state the OP's device is in is the problem. You can only install/flash/update a device if it is in the correct state for the process (flash mode for updates/installations, fastboot for flash via adb etc.). I for myself never had a brick where the device wasn't recognized in any functioning way.
Usually if a custom rom is flashed onto locked device the bootloader can't process the system as it compares signature keys which aren't present in the custom ROM. The bootloader then exits the loading of the system and gives out an error message, but the device can still boot into flash mode and fastboot.
Since the OP's device doesn't boot into anything (even with various button combinations and/or hard reset) I'd say that it's now a quite nice looking paperweight.
Like I said before I think the only option is to contact the official Sony repair service.
EDIT: One last question, did you plug your device into a USB3.0 in your PC? Because I remember having problems with it while trying to flash something onto my Z3 once. Maybe try a different USB plug if you haven't already.
Click to expand...
Click to collapse
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
sebzter said:
Hi, my computer doesn't even have USB 3 ports, I've tried every single USB port on my computer all give the same result..
Do you know how to get in contact with the official sony repair service and would they be willing to unbrick it for free (or for a reasonable price that won't exceed the price the phone is worth) I've tried calling Sony already telling them my Z3 was bricked however they told me that since the phone ran out of warranty 4 months ago, they wouldn't repair it, even if they charged, since apparently Sony doesn't do out of warranty repairs.
If getting the phone repaired via the official sony repair service, I may have found a last option below, however this will require me to take apart the phone.
After doing much more research, I've heard with S1tool, if you take apart the phone and find the testpoint, you can then flash the phone from there in order to get fastboot and flashmode back, then after successful flashing from testpoint, the phone will boot into fastboot/flashmode and allow you to restore the phone normally. Is this possible with the Z3? A quick google search gives you a bunch of threads started for finding the testpoints and recovering those devices for the Xperia Z1, ultra, etc. but I haven't found a specific guide for the Z3. Is this still possible? I've attached pictures below of what I believe is the testpoint for the Xperia Z3, I found these looking them up on the internet.
Thank you everyone who's replied so far, please let me know what I should do at this point. Thanks
Click to expand...
Click to collapse
Ok I think I'm out on this point as I honestly have no idea about the whole test point procedure. About repair service though, I guess they don't repair it because they may have to give warranty on their repaired products. Maybe try a mobile repair service in your neighborhood if there's one, but like you said I don't know if the price for a repair exceeds the devices worth.
I guess if you can find this test point it would be a reasonable option for you and I really wish you good luck with that and your phone.
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
sebzter said:
Here's some more screenshots of where I'm at right now as far as the phone being recognized by the computer. The phone shows up as 2 devices, HID-compliant device, and USB input device. I've attached pictures of this in device manager below as well as the list of Connected Devices I see in flashtool when I go to Devices > Check Drivers
Click to expand...
Click to collapse
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
ndmuni said:
is your device recognize in fastboot....instead of 'adb devices' try 'fastboot devices' in cmd,
if it does try to use fastboot to reboot into recovery.
Click to expand...
Click to collapse
Hi, thanks for the tip, however the phone doesn't seem to be recognized in fastboot devices either. Heres a screenshot of what I get when I type in adb devices and fastboot devices. Thanks
Try installing Minimal adb with fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
If youconnect your device in fastboot mode....power off, hold vol up ..does your pc sees it?
Related
I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
hi everybody,
I left my phone charging in the night(it was on) and when i came to take it in the morning (it was off)... i tried to turn it on but it didn't turn on!
(IM USING ORIGINAL SONY CHARGER AND USB THAT CAME WITH IT)
when I plug it in to a charger the LED turns green (that means that the battery is at 90% or above)
i tried power and volume up (hard reset) but it didn't work!
when i connected to my computer it wasn't detected....(tried all USB ports)
Also, i tried to enter Flashmode and Fastboot mode.. and none of them worked!
Xperia companion didn't detect it....
I tried to turn it on several times but it didn't work!
i even tried all buttons combination (power, both volumes ) all together, and nothing worked!
PLEASE HELP ME!!!
please anyone have an idea or any suggestion that might help!
all your suggestions are so much appreciated!
THANK YOU VERY MUCH!
I used to be a bit similar to your situation, but its power indicator is not lit. Pressing other buttons did not respond. I also tried to connect it to the computer, but still didn't respond. I had no choice but to send it back to the after-sales service. The response I got was that the power IC was damaged.
Nidhal AKA the king said:
hi everybody,
I left my phone charging in the night(it was on) and when i came to take it in the morning (it was off)... i tried to turn it on but it didn't turn on!
(IM USING ORIGINAL SONY CHARGER AND USB THAT CAME WITH IT)
when I plug it in to a charger the LED turns green (that means that the battery is at 90% or above)
i tried power and volume up (hard reset) but it didn't work!
when i connected to my computer it wasn't detected....(tried all USB ports)
Also, i tried to enter Flashmode and Fastboot mode.. and none of them worked!
Xperia companion didn't detect it....
I tried to turn it on several times but it didn't work!
i even tried all buttons combination (power, both volumes ) all together, and nothing worked!
PLEASE HELP ME!!!
please anyone have an idea or any suggestion that might help!
all your suggestions are so much appreciated!
THANK YOU VERY MUCH!
Click to expand...
Click to collapse
doesnt seem like something that can be fixed on a software level, you need to send it to sony to fix it if youre under warranty.
Nidhal AKA the king said:
hi everybody,
I left my phone charging in the night(it was on) and when i came to take it in the morning (it was off)... i tried to turn it on but it didn't turn on!
(IM USING ORIGINAL SONY CHARGER AND USB THAT CAME WITH IT)
when I plug it in to a charger the LED turns green (that means that the battery is at 90% or above)
i tried power and volume up (hard reset) but it didn't work!
when i connected to my computer it wasn't detected....(tried all USB ports)
Also, i tried to enter Flashmode and Fastboot mode.. and none of them worked!
Xperia companion didn't detect it....
I tried to turn it on several times but it didn't work!
i even tried all buttons combination (power, both volumes ) all together, and nothing worked!
PLEASE HELP ME!!!
please anyone have an idea or any suggestion that might help!
all your suggestions are so much appreciated!
THANK YOU VERY MUCH!
Click to expand...
Click to collapse
Send it to sony service same thing happened for me and they gave me another phone.
Similar, but Sony do not want to know now
Blackghosthm said:
Send it to sony service same thing happened for me and they gave me another phone.
Click to expand...
Click to collapse
It's a long story, but bought an XZ from Toby Deals ( never ever use those rip off merchants ).
Decided not to want to turn on just before the year warranty ran out. Red flashing LED whilst charging, white Sony screen comes up, then goes off again, repeats ad infinitum. Obviously tried all the usual volume up/power button resets and this actually responds with the one buzz/three buzz response. Original charger and even a brand new battery - no change.
Didn't want to send back to Singapore, so tried Sony support who advised to send to Sony UK repair center.
I sent it in, came back as 'can't repair due to non UK model'.
Advised Sony on line support again, who promised me it would be looked at if sent in again.
Did that and they sent it back repaired and working ( no hardware ) - reflashed ?? Happy for three days.
Same thing happened after three days / same symptoms as before
Sent in again, sent back as 'non UK model' again. Started to cry
Informed Toby Deals who now don't want to know, as now a few moths past warranty expiry date.
Now I have a bricked expensive phone and have had since January. What a waste of money.
All I want to do, is whatever Sony UK repairers did in their factory.
No detection on PC and Companion either, which I feel is a big problem for any reflashing ideas.
Any ideas anybody please ?
Hammerheadz said:
It's a long story, but bought an XZ from Toby Deals ( never ever use those rip off merchants ).
Decided not to want to turn on just before the year warranty ran out. Red flashing LED whilst charging, white Sony screen comes up, then goes off again, repeats ad infinitum. Obviously tried all the usual volume up/power button resets and this actually responds with the one buzz/three buzz response. Original charger and even a brand new battery - no change.
Didn't want to send back to Singapore, so tried Sony support who advised to send to Sony UK repair center.
I sent it in, came back as 'can't repair due to non UK model'.
Advised Sony on line support again, who promised me it would be looked at if sent in again.
Did that and they sent it back repaired and working ( no hardware ) - reflashed ?? Happy for three days.
Same thing happened after three days / same symptoms as before
Sent in again, sent back as 'non UK model' again. Started to cry
Informed Toby Deals who now don't want to know, as now a few moths past warranty expiry date.
Now I have a bricked expensive phone and have had since January. What a waste of money.
All I want to do, is whatever Sony UK repairers did in their factory.
No detection on PC and Companion either, which I feel is a big problem for any reflashing ideas.
Any ideas anybody please ?
Click to expand...
Click to collapse
Your phone is still booting, so the boot partition is still ok.
Download newflasher.
Install the Sony ADB drivers, to do this you will need to boot your Windows10 into safe mode and use 'driver signing disabled'
Read up on Xperiafirm, download the latest firmware for your region.
Put a copy of the Newflasher into the firmware download folder.
Unplug your phone from the PC.
Turn your phone off completely Power and Vol up (+) until it vibrates three times.
Run the newflasher and when prompted, plug your phone back in while holding the Volume up (+). Once the process has started you can let go.
Good luck
If you see any led light , try to use pc companion ( if your phone is not unlocked ) and if you have unlocked bootloader try to use xperifix to download the latest software for your phone and then flash it using newflasher ( don't forget to have the Sony USB drivers on your computer ) pls tell us if it works to find another way to fix your smartphone.
Didgesteve said:
Your phone is still booting, so the boot partition is still ok.
Download newflasher.
Install the Sony ADB drivers, to do this you will need to boot your Windows10 into safe mode and use 'driver signing disabled'
Read up on Xperiafirm, download the latest firmware for your region.
Put a copy of the Newflasher into the firmware download folder.
Unplug your phone from the PC.
Turn your phone off completely Power and Vol up (+) until it vibrates three times.
Run the newflasher and when prompted, plug your phone back in while holding the Volume up (+). Once the process has started you can let go.
Good luck
Click to expand...
Click to collapse
Thanks for the info Didgesteve.
I am running through this now, but the firmware within Xperiafirm is a little light on the F8332 version ( dual sim ).
The single sim F8331 has lots more options including one for UK Virgin Mobile, which could be mine. The only other option for the 8332 is the Central Europe 1 CE1 option, which I don't think it is. Any advice please ? I am trying to find it on the Sony site, as @IgorEisberg states "XZ F8331 and F8332 are on the sony server now"
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Didgesteve said:
Your phone is still booting, so the boot partition is still ok.
Download newflasher.
Install the Sony ADB drivers, to do this you will need to boot your Windows10 into safe mode and use 'driver signing disabled'
Read up on Xperiafirm, download the latest firmware for your region.
Put a copy of the Newflasher into the firmware download folder.
Unplug your phone from the PC.
Turn your phone off completely Power and Vol up (+) until it vibrates three times.
Run the newflasher and when prompted, plug your phone back in while holding the Volume up (+). Once the process has started you can let go.
Good luck
Click to expand...
Click to collapse
Thanks for the info Didgesteve.
I am running through this now, but the firmware within Xperiafirm is a little light on the F8332 version ( dual sim ).
The single sim F8331 has lots more options including one for UK Virgin Mobile, which could be mine. The only other option for the 8332 is the Central Europe 1 CE1 option, which I don't think it is. Any advice please ? I am trying to find it on the Sony site, as @IgorEisberg states "XZ F8331 and F8332 are on the sony server now"
Hammerheadz said:
The only other option for the 8332 is the Central Europe 1 CE1 option,
Click to expand...
Click to collapse
It doesn't matter which region you have as long as the model number is the same, it's not locked to any language. The language can be chosen on start up, from a fresh install.
Central Europe 1 CE1 will be just fine.
Didgesteve said:
It doesn't matter which region you have as long as the model number is the same, it's not locked to any language. The language can be chosen on start up, from a fresh install.
Central Europe 1 CE1 will be just fine.
Click to expand...
Click to collapse
Thanks. I did think that, so went ahead anyway.
I think I have a connectivity problem. Nothing is showing in device manager, so cant add the drivers any other way can I?
Newflasher shows 'no USB device with vid:0x0fce pid 0xb00b !'
Hammerheadz said:
Thanks. I did think that, so went ahead anyway.
I think I have a connectivity problem. Nothing is showing in device manager, so cant add the drivers any other way can I?
Newflasher shows 'no USB device with vid:0x0fce pid 0xb00b !'
Click to expand...
Click to collapse
Did you install the drivers in 'safe mode'?
Hi. Yes I did. Still no joy, but I haven't tried since last time. I'll have another go this week, unless you can think of anything else it could be, or that I can try?
my xz premium reboots when I plug in charger. I will sell it and buy samsung ( i dont like it) before it dies completely lol
oh it was water in charging port, now all works perfectly
Didgesteve said:
Did you install the drivers in 'safe mode'?
Click to expand...
Click to collapse
Still no joy.
I am using Windows 10 and when I requested recovery reboot, it does give me a safe boot option ( option 5 I think ), but it also gives me a 'disable driver signing' option too and you can't opt for both.
I have actually tried to boot in both modes and the newflasher does the same thing - see attached screenshot
Not sure what more I can do, to get these drivers on. I have also run in developer mode and set USB device discovery to on, to no avail.
If device manager never sees the phone, how will I ever be able to install the drivers.
The newflasher, asks to install Gordongate and it doesn't matter if I select yes or no, it still says no usb device.
I am running newflasher from here :
C:\Xperia firmware\F8332_Customized CE1_1315-4550_41.3.A.2.171_R1E
...........but I have tried to run it from the driver folder too.
I am stuck. If I can send it to you, please PM me !
:fingers-crossed:
Hammerheadz said:
Still no joy.
I am using Windows 10 and when I requested recovery reboot, it does give me a safe boot option ( option 5 I think ), but it also gives me a 'disable driver signing' option too and you can't opt for both.
I have actually tried to boot in both modes and the newflasher does the same thing - see attached screenshot
Not sure what more I can do, to get these drivers on. I have also run in developer mode and set USB device discovery to on, to no avail.
If device manager never sees the phone, how will I ever be able to install the drivers.
The newflasher, asks to install Gordongate and it doesn't matter if I select yes or no, it still says no usb device.
I am running newflasher from here :
C:\Xperia firmware\F8332_Customized CE1_1315-4550_41.3.A.2.171_R1E
...........but I have tried to run it from the driver folder too.
I am stuck. If I can send it to you, please PM me !
:fingers-crossed:
Click to expand...
Click to collapse
Windows10, boot into safe mode, choose 'disable driver signing' in the advanced menu, start the computer and install the Sony drivers. If that doesn't work, answering yes to the first question in Newflasher creates a new drivers zip folder within the Newfalsher folder. Install these drivers, again with driver signing disabled.
When you put the phone into flash mode and plug it in to your PC, what does it say in the device manager?
Didgesteve said:
Windows10, boot into safe mode, choose 'disable driver signing' in the advanced menu, start the computer and install the Sony drivers. If that doesn't work, answering yes to the first question in Newflasher creates a new drivers zip folder within the Newfalsher folder. Install these drivers, again with driver signing disabled.
When you put the phone into flash mode and plug it in to your PC, what does it say in the device manager?
Click to expand...
Click to collapse
Thanks for your reply Didgesteve.
I installed the drivers by installing the sa0115adb.inf successfully, but as the phone is continuously cycling through a 'Sony' white screen and blank screen ( frequency 3secs of each ), device manager does not seem to 'see' anything at all.
I also installed the ggsommc.inf driver, when prompted and answered as a 'ye's for the GordonGate option. It didn't give me a failure message, but also didn't state 'installed successfully' as the sa0115adb one did.
I also tried another generic driver called android_winusb.inf to no avail.
Hammerheadz said:
Thanks for your reply Didgesteve.
I installed the drivers by installing the sa0115adb.inf successfully, but as the phone is continuously cycling through a 'Sony' white screen and blank screen ( frequency 3secs of each ), device manager does not seem to 'see' anything at all.
I also installed the ggsommc.inf driver, when prompted and answered as a 'ye's for the GordonGate option. It didn't give me a failure message, but also didn't state 'installed successfully' as the sa0115adb one did.
I also tried another generic driver called android_winusb.inf to no avail.
Click to expand...
Click to collapse
Try to use pccompanion sorry if I'm late
PC companion is no good, as the device can't been seen by windows or that app. I was wondering what the Sony uk repair centre used the last time they repaired it. Wish they would again !!
Hammerheadz said:
PC companion is no good, as the device can't been seen by windows or that app. I was wondering what the Sony uk repair centre used the last time they repaired it. Wish they would again !!
Click to expand...
Click to collapse
Not at all it's like newflasher
Hi, I need help with my XZ Premium. After updating an OTA the phone went into bootloop mode. I have tried to repair from Companion and Flashtools with several Firmwares and nothing has worked. When it turns on, it enters the Sony logo and it restarts the blue led ignition and then green led. Any help please? Thanks in advance and sorry for my English
Have you tried flashing a new firmware?
RickyGrizu said:
Any help please? Thanks in advance and sorry for my English
Click to expand...
Click to collapse
Download Xperiafirm, find the latest 'custom' build for your region and download that.
Download Newflasher and put a copy of all the files into the same folder as your firmware.
Delete userdataxxx.sin. This keeps your data partition.
Unplug phone from PC.
Turn phone off completely. Volume up (+) and power until the phone vibrates three times.
Start Newflasher.exe
Hold volume up(+) on phone while plugging in USB lead.
Let Newflasher do its thing, takes 5 minutes mimum, don't unplug until you're told to.
You might need the Sony drivers if you haven't done this before.
Edit: I don't understand how you can go wrong with Xperia companion, it tells you what to do. The fact that your phone fires up means that the boot sector is working fine, along with flashboot. I'm guessing that you're not turning the phone off properly before you try any of the flashboot procedures.
Didgesteve said:
Download Xperiafirm, find the latest 'custom' build for your region and download that.
Download Newflasher and put a copy of all the files into the same folder as your firmware.
Delete userdataxxx.sin. This keeps your data partition.
Unplug phone from PC.
Turn phone off completely. Volume up (+) and power until the phone vibrates three times.
Start Newflasher.exe
Hold volume up(+) on phone while plugging in USB lead.
Let Newflasher do its thing, takes 5 minutes mimum, don't unplug until you're told to.
You might need the Sony drivers if you haven't done this before.
Edit: I don't understand how you can go wrong with Xperia companion, it tells you what to do. The fact that your phone fires up means that the boot sector is working fine, along with flashboot. I'm guessing that you're not turning the phone off properly before you try any of the flashboot procedures.
Click to expand...
Click to collapse
Thanks for answering so quickly. I tell you the following. I try to do what you say but I get an error. I looked for information about it and it tells me that I have to have the "Activated Debugging" which I do not have active and I can not start the S.O to activate it. I do not have the Bootloader unlocked either. I await answers, thanks!
RickyGrizu said:
Thanks for answering so quickly. I tell you the following. I try to do what you say but I get an error. I looked for information about it and it tells me that I have to have the "Activated Debugging" which I do not have active and I can not start the S.O to activate it. I do not have the Bootloader unlocked either. I await answers, thanks!
Click to expand...
Click to collapse
Don't forget to install the drivers
raven213 said:
Don't forget to install the drivers
Click to expand...
Click to collapse
Yes, I have everything installed correctly
raven213 said:
Have you tried flashing a new firmware?
Click to expand...
Click to collapse
What do you mean with a new firmware?
RickyGrizu said:
Thanks for answering so quickly. I tell you the following. I try to do what you say but I get an error. I looked for information about it and it tells me that I have to have the "Activated Debugging" which I do not have active and I can not start the S.O to activate it. I do not have the Bootloader unlocked either. I await answers, thanks!
Click to expand...
Click to collapse
You shouldn't nneed debugging enabled, you would get that error if you were plugging the phone in with the volume down(-). But you're not going into recovery, you want volume up(+) into flash. You don't need USB debug enabled for flash.
RickyGrizu said:
Hi, I need help with my XZ Premium. After updating an OTA the phone went into bootloop mode. I have tried to repair from Companion and Flashtools with several Firmwares and nothing has worked. When it turns on, it enters the Sony logo and it restarts the blue led ignition and then green led. Any help please? Thanks in advance and sorry for my English
Click to expand...
Click to collapse
all of the methods listed so far are tedious, but everyone is ignoring the easiest and best one: download the Xperia Flash Tool from Sony Developer World, plug in your phone (I forgot the key combination), and it will automatically find the right and most recent, Sony-approved firmware, and all that you have to do is press okay. I get my XZP into bootloops about every month, and every time all that I have to do is plug it in and press okay.
b.rad42 said:
all of the methods listed so far are tedious, but everyone is ignoring the easiest and best one: download the Xperia Flash Tool from Sony Developer World, plug in your phone (I forgot the key combination), and it will automatically find the right and most recent, Sony-approved firmware, and all that you have to do is press okay. I get my XZP into bootloops about every month, and every time all that I have to do is plug it in and press okay.
Click to expand...
Click to collapse
But to use the Xperia Flash should not have the bootloader unlocked? because if so, I do not have it unlocked or I can unlock it. Thank you!
RickyGrizu said:
But to use the Xperia Flash should not have the bootloader unlocked? because if so, I do not have it unlocked or I can unlock it. Thank you!
Click to expand...
Click to collapse
ah. that makes more sense. in that case, you can't use newflasher or flashtool as they require an unlocked bootloader. personally, i'd contact sony, as your warranty should still be valid. if they won't help, you can always go to sony developer world and get a bootloader unlock code. then use fastboot to unlock your bootloader in fastboot mode (works even while it's in a bootloop) (if you need the commands lmk). after that you can use sony's flash tool, flashtool, or newflasher.
b.rad42 said:
ah. that makes more sense. in that case, you can't use newflasher or flashtool as they require an unlocked bootloader. personally, i'd contact sony, as your warranty should still be valid. if they won't help, you can always go to sony developer world and get a bootloader unlock code. then use fastboot to unlock your bootloader in fastboot mode (works even while it's in a bootloop) (if you need the commands lmk). after that you can use sony's flash tool, flashtool, or newflasher.
Click to expand...
Click to collapse
I think there's some confsion between Sony's Emma and Xperia companion.
One is used to repair and back up your phone and the other is for flashing firmware builds. Niether of them require the bootloader to be unlocked.
Flashtool and Newflasher can also be used without unlocking the bootloader.
The difficult thing seems to be turning the phone off properly before trying to connect it to Xperia companion for repair. But there are instuctions in this thread and the linked thrreads above. At some point you've got to decide if flashing this is within your skillset, if not then send it back for repair. Make sure you've registered your phone, then call the helpline.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Didgesteve said:
I think there's some confsion between Sony's Emma and Xperia companion.
One is used to repair and back up your phone and the other is for flashing firmware builds. Niether of them require the bootloader to be unlocked.
Flashtool and Newflasher can also be used without unlocking the bootloader.
The difficult thing seems to be turning the phone off properly before trying to connect it to Xperia companion for repair. But there are instuctions in this thread and the linked thrreads above. At some point you've got to decide if flashing this is within your skillset, if not then send it back for repair. Make sure you've registered your phone, then call the helpline.
Click to expand...
Click to collapse
This is what appears to me in Emma ...
RickyGrizu said:
This is what appears to me in Emma ...
Click to expand...
Click to collapse
What are you trying to do with Emma? that's a developers tool. I recomend Xperia companion to get your phone up and running again.
Didgesteve said:
What are you trying to do with Emma? that's a developers tool. I recomend Xperia companion to get your phone up and running again.
Click to expand...
Click to collapse
It does not work!
Didgesteve said:
What are you trying to do with Emma? that's a developers tool. I recomend Xperia companion to get your phone up and running again.
Click to expand...
Click to collapse
RickyGrizu said:
It does not work!
Click to expand...
Click to collapse
i have the same pb and i need bootloader unlock code for g8142
imei 357008081440044
Hi Everyone! Actually ive also the same issues with my Sony Xperia XZ Premium , i tried to reflash it many times, but it didnt helped. I used the repair process also via PC Companion, after the end, nothing went changed. The Phone is already broken since two years, i tried so many ways to fix it, but nothing helps. Im just wanna to make a backup or something, but i cant achieve the storage of the phone.
---------- Post added at 08:16 PM ---------- Previous post was at 07:55 PM ----------
clubshop said:
i have the same pb and i need bootloader unlock code for g8142
imei 357008081440044
Click to expand...
Click to collapse
Hi! There is your unlock code: 595EEC6F3A360C86 But anyway on this site you can generate at everytime a new one. on the sony developer site you can find many more informations about the Emma Software, and so on. What is happend with your Phone? In my case, it was on the charger, and the cable got little bit burned or melted, and since that the phone is in the bootloop, its restarting repeatedly without end. It shows a Sony Logo, and thats all.... Sad story, it happend already two years earlier, but it was only 6 months old...
Ok, it seems this thread is a bit older but i have the same Problem, search the Web and try to fix it X Times with flashing by using all the WWW is giving me to use. Nothing off all that works but then i found out the Solution.
My exact Problem was when i start the XZP, it boot up, i can see the Sony Logo for a few seconds (5-10) then led flashes very Quick greenblue and green then it resatarts and the Bootloop begins.
I Unplug all the Flex wires inside and after that i plug in only Battery and Power/Volume Buttons. after that, the XZP starts Normal. after that i plugged in one Flex after another and finally find out, the System stucks with the Main (rear) Camera plugged in on the Board.
I think it depends on a Shortcut on the Camera or the Phone is fall to the Ground.
I change the Camera to a new one and the Problem is fixed.
Maybe this can also be a Solutin for other series XZ Phones with the same problem.
I hope this is also helpfull for others.
Sorry for my bad english, i can wrirte it also in german if wished and maybey someone can Translate it correctly.
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.
In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting
viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem
whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.
whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port