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.
Related
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.
aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.
could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.
Did you get this problem resolved? I have the exact problem with the exact phone!!!
thank you very much
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.
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!
Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.
I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck
Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?
Hello and thanks for clicking in!
I am broadcasting an SOS to anyone who may be able to help.
I am also aware that because of the recent stock OTA which I have already installed (build 35b), this may be game over, but if anyone has any ideas, I am ready to try anything.
A brief history: I was jumping between SkyDragon and Jasmine and at one point, my phone was acting funny so I wanted to go back to stock.
I flashed stock using kdz to 24b and everything was going fine for a bit until I updated to 35b OTA (big mistake).
Now my phone is completely unusable - for awhile I could get it to work for an hour or so by factory resetting, but any time I installed any apps, system processes would constantly fail, display would become unresponsive, and at one point, all audio just stopped working (headphones, speaker and ringtones, notification sounds, alarm, even bluetooth). I tried to flash stock again and now my computer won't recognize Android MTP device. I have tried all the LG drivers I could find, Koush's adb drivers, Verizon LG drivers, and no matter how I try to get my computer to recognize my phone I always get this error:
'Device driver software was not successfully installed:
MTP USB DEVICE FAILED'
I have tried TOT and KDZ methods to downgrade to stock and nothing will work because my computer won't recognize my phone.
Does anybody have any advice?
Thanks in advance.
a9u1tar1st said:
Hello and thanks for clicking in!
I am broadcasting an SOS to anyone who may be able to help.
I am also aware that because of the recent stock OTA which I have already installed (build 35b), this may be game over, but if anyone has any ideas, I am ready to try anything.
A brief history: I was jumping between SkyDragon and Jasmine and at one point, my phone was acting funny so I wanted to go back to stock.
I flashed stock using kdz to 24b and everything was going fine for a bit until I updated to 35b OTA (big mistake).
Now my phone is completely unusable - for awhile I could get it to work for an hour or so by factory resetting, but any time I installed any apps, system processes would constantly fail, display would become unresponsive, and at one point, all audio just stopped working (headphones, speaker and ringtones, notification sounds, alarm, even bluetooth). I tried to flash stock again and now my computer won't recognize Android MTP device. I have tried all the LG drivers I could find, Koush's adb drivers, Verizon LG drivers, and no matter how I try to get my computer to recognize my phone I always get this error:
'Device driver software was not successfully installed:
MTP USB DEVICE FAILED'
I have tried TOT and KDZ methods to downgrade to stock and nothing will work because my computer won't recognize my phone.
Does anybody have any advice?
Thanks in advance.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Try seeing this guide it will help you restore your stock ROM as it should correctly.
Good luck!
nilac said:
Hi and thank you for using XDA Assist
Try seeing this guide it will help you restore your stock ROM as it should correctly.
Good luck!
Click to expand...
Click to collapse
I have been through and tried both methods thoroughly, including going through it with a friend. It seems that the root of my problem seems to be that I can't get my phone to connect MTP to any computer. It just won't get recognized by any computers. I tried on my desktop and laptop and my friend tried on his and his roommates machines. We put our heads together and still couldn't figure out how to get it work.
He suggested that it is a kernel/baseband error as I had installed a custom ROM with its own kernel and when flashing back to stock, it was conflicting with the custom kernel that was on the phone and this is what is causing my phone to malfunction so miserably.
a9u1tar1st said:
I have been through and tried both methods thoroughly, including going through it with a friend. It seems that the root of my problem seems to be that I can't get my phone to connect MTP to any computer. It just won't get recognized by any computers. I tried on my desktop and laptop and my friend tried on his and his roommates machines. We put our heads together and still couldn't figure out how to get it work.
He suggested that it is a kernel/baseband error as I had installed a custom ROM with its own kernel and when flashing back to stock, it was conflicting with the custom kernel that was on the phone and this is what is causing my phone to malfunction so miserably.
Click to expand...
Click to collapse
Hi again, well try then to ask over the Q&A thread. Right here:
Good luck!