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.
Related
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
Hello Friends, (The topic could be added with "USB device not recognized" as well.)
I have rooted the Optimax v1.1 Rom months ago on my Xperia Ray. I cannot ask these at the Optimax thread because I dont have any posts up to now. Yesterday I wanted to change my rom but before doing the procedures, I erased all the data both in phone root and sd card by settings section on phone. Then my phone didn't worked again. There is a boot-loop problem. I have been searching for 7 hours and did every possible ways that people talked and still couldn't solve the problem. First and very important problem is that when I plug the phone in flashmode or fastmode windows gives an error of "USB device not recognized". I removed all the sony stuff and flashtool and pda.net drivers. I also removed all the staff which includes "Xperia" at regedit. Then I tried the steps at http://forum.xda-developers.com/showthread.php?t=1492805 for so many times. However it still doesnt recognize therefore I cannot flash the boot-loop problem solver. The only way that boot-loop doesnt occur is when I plug the phone to computer and turn it on with normal way. I cannot use application menu since there isnt any launcher application is installed also there isnt any keyboard application. Therefore I cannot do anything about this. I wrote a long paragraph to explain my problem because I have a midterm two days later which means I can't explain the issue to people by one by. I hope you can help me.
After a sleep break, with a refreshed brain, I tried the hard brick solution steps with another computer and lastly I solved the issue.
I'm glad it worked for you.
I was in a similar situation (well, not as bad, I had all my data on sd) but that method in the post didn't work for me as SEUS kept telling me I already had the last version.
I manage to fix it by flashing a Stock ROM in ftf file format with Flashtool.
I'm just mentioning for others in the similar situation so they know there is an alternative.
Thanks.
Hello,
I'm trying to get this tablet fixed for my brother in law. It got stuck like this just hours after his daughter started using it.
They can't return it because they ordered it several weeks before Christmas, so by the time she even opened it, the 30 return policy had expired.
None of the steps I have found here or on other forums for booting into recovery are working. I've tried over and over again.
I've tried several of the various steps on here and a few other places to plug USB into my computer to see if I could get it into recovery that way, but, the computer will not load drivers. Windows simply tries to load a driver, then settles on a MTP Device, and when I try to Update Driver, it says no better driver was found, even when I point it to the folder where the driver is "supposed" to be. (Ones that others say they have been able to get working).
I'd love to get this working for my niece, so any help would be greatly appreciated.
Thanks in advance.
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Go to a repair shop is the only solution
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Pay1 said:
My tablet got stuck on the boot screen (a 'bootloop') and so I downloaded the Swedish instructions, tools and firmware image files from the manufacturer's website. I installed the driver on my laptop, connected the tablet, flashed the latest firmware and got it working. Annoyingly, the Chrome browser would not work whatever I did, and eventually I tried to flash an older firmware image onto the tablet. This killed it completely. The screen shows nothing at all; you can just about tell that the backlight has come on due to a dim glow, but the screen is still blank.
The worst thing is that the laptop no longer detects that the tablet is connected to it. It does not even report it as an unknown device. This is what really worries me.
I've read other threads on this forum where Flashtools is advised for bricked phones, but will this work with a tablet where the computer cannot even detect the device is attached?
Any help will be much appreciated many thanks.
Click to expand...
Click to collapse
Yes, as @droid_god said the only way is a repair shop because they use those jtag devices to fix your phone.
I'm at a point where i need enough help that im starting a thread about it.
How it started:
It all started when i restarted my G5 with Quick Reboot [ROOT] (AntaresOne Studio ) because it was lagging/slow.
After restarting the phone would not boot. It would always go to the Optimizing XXX of XXX apps, finish, restart and optimize again.
What ive tried:
I factory reset my G5 by using TWRP and formatting the data partition.
That allows me to use the stock? G5 ROM, but one huge issue, is that if i turn on Wifi, the phone reboots within 2 seconds to the tmobile screen and gets stuck.
It fails to reboot after that.
My phone has retained root. I was able to verify that by downloading Root Checker and it confirmed that i have root.
SuperSU also worked properly and SnapChat fails to login because it is detecting that i still have root.
I have been rooted for several weeks without any problems fyi. I have not updated my phone at all.
I was hoping i could unroot and flash the stock unmodified? tmobile ROM,
but in download mode, LGUP detects the device as "unknown device"
and if the phone is booted, LGUP does not detect it, instead it gives me a drivers need to be installed warning.
(The drivers are already installed, because i installed then when originally rooting, i also reinstalled everything the root guide suggested anyways)
At this point i am clueless as to what else i can do.
Currently i can use the phone more or less fine but i can only run on data.
Play store has trouble installing apps via data so i tend to download and install APKs directly via file manager.
Thank you for any help and insights in advance.
Well, I would suggest flashing the 10D kdz to get back to stock. However you need LGUP working to do that...
It sounds like a driver issue... I would uninstall the driver, reboot, reinstall, and try again.
As for uninstalling the drivers, that is easier said than done sometimes. You may need to manually remove the driver files if the uninstaller does not.
You may want to use something like Revo Uninstaller to monitor the install and then do an uninstall again.
If you have another computer, doing it on that computer could be an easier route, heh.
http://imgur.com/a/HIy8z
SO i tried it on my mom's windows 7 desktop, and it look slike all the drivers installed properly, however when i run LGUP, same thing happens.
It shows up as "unknown device". The other LG software also doesn't detect it. I can factory reset the phone and it stays rooted, but the broken wifi is a huge issue.
I'll keep try thou. Your driver issue idea seems valid but idk what is happening at this point :/ I used to love this phone and LG (coming from the S4) but no so much anymore...
The chinese brands will take over at this rate lol. Axon 7 is compelling. Again, Thanks for the advice
EDIT:
I fixed it. Issue was due to build.prop. because the file was modified it caused the software to not detect the phone properly apparently, so putting back a clean stock build.prop allowed LGUP to recognize the device.