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
Related
Hello, I recently decided to root my phone and place Cyanogenmod on it. When I did that I realized my radio was no longer working. In an attempt to just get back to a working phone for the time being I flashed a rom that I believe was just for the Nexus S and not Nexus S 4G. Due to my stupidity I am unable to communicate from the device to my computer using USB. When I attach the device to the computer nothing happens. The device does not even appear in the device manager. I have tried on multiple computers as well. On top of that the rom seems to have put me back into the stock recovery. If anyone could help me figure out just how to get USB working again I would be very appreciative.
I should note that I can still transfer files to the phone using the sd card or via ftp.
Thank you for your time and help.
Change the USB cable?
Yes, forgot to mention that. I have tried 2 cables both of which work on other devices.
What if you hold in the middle of the volume buttons (i.e. both up and down at the same time) and keep holding, then plug in to your usb port? It should come up as download mode. If it will do that you might try using Odin.
Or try a different machine perhaps?
are the drivers the same for the S as the 4g?
do you have clockwork on the phone or have you tried to run recover by holding volume up and power?
just throwing things out.
Hello, I appreciate any and all suggestions and help.
I have Odin downloaded and installed, but the computer can not find the device so Odin can not do what it needs to do. This is even the case in download mode.
In terms of recovery I am on the stock recovery. I was on clockwork but made a small mistake and now am back to stock.
I know if I can just get the computer to see the phone exists I can fix it.
If you can find the full OTA package for NS4G, you can try putting it on the SD card and flash it via stock recovery.
Also another thing worth trying is connecting the phone to an Ubuntu machine and see if it's detected or not.
I have tried looking for the original full OS. I will continue looking, but the different OS thing is a good idea I did not think of. I will attempt that now. Thank you.
I installed Ubuntu and the Android SDK and Ubuntu was unable to see the phone as well. I am going to keep searching for the original firmware to see if that will fix it. Thank you for your help so far, it is greatly appreciated.
I have found the only rom my phone will accept now is
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Which is for the M200 variant. This apparently the Korean version.
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.
Hi all,
I've got a Nexus S 4G CDMA Sprint phone running Stock ICS 4.0.4 IMM76D.
My bootloader is unlocked from previous roots and whatnot.
My problem is that my phone is not being recognized by my computer at all. We're talking complete nonrecognition. No yellow triangle in device manager, no pop-ups, nothing. This phone will just not be read by my computer! I've tried different cords, different computers, re-installation of drivers after resetting my computer, installed PDA net, did a factory reset on the phone, I've literally been on Google for hours upon hours upon hours trying to figure this out and can't figure out why the computer is not recognizing the phone and why the phone is not allowing me to put it into usb mounting. It is however, charging via the computer and wall plug. I can get into stock 3e android recovery, fastboot using V-Up and Power and I can get it into download mode. It is NOT recognized in any modes by the computer nor other computers including my Linux box. The phone states that the usb control initializes but then ends a moment later. I am thinking this is a hardware issue but that leaves me with two issues:
If I was to go to Sprint to have it fixed they would realize my bootloader was unlocked thus voiding the warranty and I'd feel like quite an idiot at the store
If it is hardware related why is the charge working on the device.
I have also tried to bend up the usb plate to make it touch the pins better but that did not help at all. I am at my wits end and really need some help here, I've done everything I could find on Google and here plus more. I want to just return it but with the bootloader unlocked this is really not a possibility. I am looking for help to either become able to lock the bootloader without it having to be connected via the computer so I can then get it fixed if it is hardware related or if I can get the darn thing to be read by the computer once more. so yea, this is where I am at and I would appreciate it so much if someone could help me out, thanks guys!!!
Wireless adb in playstore should help.
Sent from my Nexus S 4G using XDA
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Ebicoustic said:
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Click to expand...
Click to collapse
You might be able to download your rom of choice and rename it update.zip. I'm not sure if it will flash though....someone else chime in if I'm wrong. You can use wireless file transfer if needed.
Sent from my Nexus S 4G using XDA
Yea I've tried that, everything gets shot down by the recovery with a E:Signature Verification Failed. Thank you for your help so far but I don't think this is something that is going to be helped. I've put in a ticket to Samsung for a repair under it's warranty. In the past I've sent in a rooted phone and they've fixed it so I think I'm going to give that a shot. Just don't want to be without a phone for 2+ weeks.
Well good luck...you are running stock unrooted so it shouldn't matter. It is a dev phone for damn sake. Sorry couldn't help.
Sent from my Nexus S 4G using XDA
Well if you want to download a custom rom... Since you are on this forum. Download any rom (preferably CM9 since its quite good from my experience). Flash the stable version and wait till everything is completed. Now when you flash make sure you download a recovery...eg ClockWorkMod Recovery from google market. You should now have a custom rom installed and download wireless adb as chappy said. See if that works
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
joao.m.neto said:
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
Click to expand...
Click to collapse
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Mr.Ak said:
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Click to expand...
Click to collapse
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
joao.m.neto said:
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes,as I said, could be a battery issue but we are still not sure yet.I can give you the link for winxp or win7 if you need and then you can dual-boot it alongside windows10.You should install drivers from cm11s restore toolkit thread(executable drivers),maybe then your device will show up in device manager though it is highly advised to do this on Xp or 7 since 8,8.1 and 10 has driver signing issues.