I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.
I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.
Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.
Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.
I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.
Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?
Thank you.
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
No, I haven't found a solution to this yet. And you are the only person here that has replied.
I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.
If and when I figure this out, I'll post it here to help you out.
johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
Hi JohnG75,
Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.
In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.
If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.
Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.
There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
hi
clearly this wasn't as simple as the unrevoked method for my last phone,
I ran the script 'root many phone' and it cracked on whilst moaning about permissions and by the time it had finished the phone restarted a bit broken.
It had not play store, none of the previous apps on, wasn't actually rooted at all.
I managed to get play back on there but installing via adb.exe from the command line, and its almost like when I install something, that was on there before, it still has all the settings, so not quite sure what has gone on.
can anyone offer some advice, is it simplest to somehow get myself back to stock and start agin.
maybe I didnt run the root script from the right place. - phone was on and plugged in , usb debugging enabled.
any help much appreicated
I don't know of starting fresh is the 'best' option, but if you haven't done anything that you can't miss our can't do again it's never a wrong try.
Some people also reported that you need allow test locations on. And allow installation of external apps must also be set.
You can always try re rooting without reinstalling.
If you want to reinstall you're best of using Sony update service. Googling is fastest way to find it (not Sony pc companion)
Good luck,
And don't forget to mark your thread solved if it is solved
Did this help? Don't forget to press the thanks button
Sent from my LT30p using xda premium
http://forum.xda-developers.com/showthread.php?t=1914673
have you tried this method? I used it no problem last night.
welshkid said:
http://forum.xda-developers.com/showthread.php?t=1914673
have you tried this method? I used it no problem last night.
Click to expand...
Click to collapse
That's the root many android script he already used according to his post
Did I help? Then please don't forget to press the thanks button.
it's your question solved? Then mark your question solved in your title.
Sent from my Xperia T using XDA Premium.
hi
yes that was what I tried
do I need anything more than that script? (eg those ftf files i keep reading about?)
does the phone need to be on, or in the volume down on boot state
it appears I need 'test locations' and 'external apps' set
anything else I need?
i will try again today at some point
thanks
sure I am being a spanner, but I cant even find the test locations or external apps setting anywhere?
where might that be?
unless test locations is 'mock locations' (guess so)
stilll not finding the external apps option, thought it would be in apps setting somewhere..?
ok found that too in security > unknown sources.
ignore me
That root script didn't work for me either; it kept asking me to connect my device with USB-debugging enabled even though I had already done that.
I would suggest getting back to stock and trying again, BUT use FlashTool instead. It worked perfectly for me in mere seconds.
yesyesimanoob said:
That root script didn't work for me either; it kept asking me to connect my device with USB-debugging enabled even though I had already done that.
I would suggest getting back to stock and trying again, BUT use FlashTool instead. It worked perfectly for me in mere seconds.
Click to expand...
Click to collapse
I downloaded version 0.9.0.0 version, but no XperiaT in the list when I plug it in..
which phone did you pick?
presume the steps are
1. download flashtool
2. Install it on your PC
3. Run the Flashtool and connect your phone (enable USB debugging first)
4. Hit the Root button (second in row)
5. When you see "waiting for restore to finish" open your phone and run Backup&Restore app and restore RootMe.tar file.
6. Wait until Flashtool do the rest of work
thanks
xda-nat said:
I downloaded version 0.9.0.0 version, but no XperiaT in the list when I plug it in..
which phone did you pick?
presume the steps are
1. download flashtool
2. Install it on your PC
3. Run the Flashtool and connect your phone (enable USB debugging first)
4. Hit the Root button (second in row)
5. When you see "waiting for restore to finish" open your phone and run Backup&Restore app and restore RootMe.tar file.
6. Wait until Flashtool do the rest of work
thanks
Click to expand...
Click to collapse
If you mean in the adb drivers list, select Xperia TX. That was the only time I had to select a device.
OK finally success
although using the initial method.
maybe the problem was created by reading the 'root many phones' thread and where it says there is a special case for Xperia T/S etc I took that to mean when running the tool, to pick option '2) special case Xperia S tablet etc' - which didn't work
ran it again picked option '1) Normal' which did work
thanks for all your help
nat
Not necessarily relevant to the OP's problem but I thought I'd share in case it helps anyone else out...
When I tried rooting using Bin4ry's method I kept getting a adb server out of date error and the root failed.
I eventually traced this to having DROID explorer installed which was forcing an old version of adb to be running and stopped the newer version from starting up.
Once I uninstalled the old version I was able to runMe and root the phone.
Ok Guys, I started this thread because last weekend I had an interesting issue with my O2X. From one day to another, whenever I connected my phone to the computer it only charged, I had no USB connection. I’m not yet quite sure why it happened, the last thing I did to my phone was install CM10 nightly of 31 October 2012, and then I changed the default baseband I had (725) to the one GetRil was telling me to install (LGP990AT-00-V20l-EUR-XX-OCT-20-2011 0_CP) (this baseband didn’t fixed the strange noises of in call) two days after that I got the no USB bug, at first I thought it was software related, then after lots of reading and trying different cables and computers I thought it was hardware related, but then I saw an interesting chance of fixing it, and it did in my case
Credit goes to Kohos, I manage to have USB fixed temporary thanks to his post on modaco.com
I’M NOT TELLING THAT CM10 CAUSE THIS BUG, IT JUST HAPPENED TO ME WHILE USING THIS ROM
Specs
Phone: Optimus 2x (p990H made in south Korea)
Rom: CM10 Oct 31 2012 (when got the bug) now CM7 nightly 15 July 2012
Kernel: Symbiosis 2.6.32.59 v1.2
Carrier: Telcel
Country: México
Ril: 0725 (V10d, Europe)
BB: 1035.21_20110725
CWM: 5.0.2.0 (no touch version)
To solve this issue you need to have a stock ROM that can be flashed by CWM. Can be the rom, or a backup of the stock rom (If you don’t have one send me a PM), I didn’t tried stock-based ROM so those may or may not work; I’m not sure but rather use an original stock ROM. You also need to be able to enter CWM recovery, and have LGE drivers up to date.
For this method I used a stock nandroid backup.
I’ll describe step by step all I did to solve this issue so you can give it a shot:
1. If you have a flashable stock rom you may skip this step and go to step 3, if what you have is a nand backup you need to make your partitions back from EXT4 to EXT3 (this is the format that stock rom uses) so need to download the tool R2 found on the first post here:
http://forum.xda-developers.com/showthread.php?t=1021549
put it on your external SD card along with the backup of the stock rom
2. Reboot to enter CWM recovery and install the tool R2 (NOTE: this will erase all information of the internal memory)
3. Install or flash your stock rom or backup (In case you're using my backup, keep in mind, my file IS NOT a flashable rom, it is a backup, so trying to use the option "flash zip from external sd card" WON'T work, what you need to do is unzip the file and put it on sdcard/clockworkmod/bakcup, then on the recovery, you have to use the option "restore from external sd card", that way it should work, keep in mind that if you change the name of the file it will give md5 error for the name won't match the backup's md5)
4. Reboot and start the phone, once it is all loaded, on the phone app dial: 1809#*990# this will take you to the service (hidden) menu (If it doesn’t take you automatically to the service menu (without clicking dial) you’ll need another ROM or backup)
5. In this menu you’ll need to scroll to the option: Module Test > USB Mode Selection, in there make sure the option LG Android USB is selected
6. Then go back to the root of the hidden menu, and go to Port settings, there you’ll see several options, the ones we’re interested in are: AP USB, CP USB, AP UART, CP UART, the default should be AP USB, you can start playing with those options. (While doing this, you might want to play with your computer device manager scanning for hardware changes, that might help detecting the USB)
The recommendation is to select CP UART, wait, if your problem is not hardware related, it should popup a message of new unknown device, or LGE Platfrom Android USB device. If your USB show some life signal, then you’re almost done, if not, keep playing with the four options until you see some life signal.
What I did was select CP UART, click Ok, wait, AP UART, click OK, wait, CP USB, click OK, wait, AP USB, click OK, I waited here about 1 min, and then on the computer device manager I scanned for hardware changes, and suddenly my computer started installing all drivers again, this last option is the one that must keep selected even with reboot of the phone.
7. Once you get all done, reboot the phone and connect it to USB to see if it is recognized again, if not, repeat steps 4 to 6
8. Ok, If everything went fine, you should now have USB connection, now I would recommend you flash your Stock Rom, so everything that might cause this bug gets fixed (if you don’t do this, you might get the bug back eventually). To do so you might need to turn off your phone and plug it to your computer while clicking PWR and VOl- at the same time, if your computer doesn’t recognize your phone, use the device manager and scan for hardware changes, this should reinstall the driver needed to make this happen.
9. Finally I restored my last nandroid backup through cwm
I did this on Monday, and two days later I had no USB connection again, I repeated this steps and I had USB detection once more, today it happended again, and repeated the steps so I’m pretty sure this fix should work every time.
NOTE: This is a temporary fix, I've been trying to identify why the bug keeps comming back
Hope this help you all get over this serious bug :laugh:
Updates
This is my last froyo teclel stock backup
http://www.4shared.com/zip/AEVLSE34/2007-02-01000516.html
http://dl.dropbox.com/u/7867872/2007-02-01.00.05.16.zip
Disclaimer: Even though I'm sure it will work, try it at you own risk, I'm not responsable for any bad behavior or damage that could happen to your phone
UPDATE:
Ok, guys I told you I would make some test to make sure the bug won't come back or identify the problem, what I've found so far is that the problem might be caused by the wall charger (but might not the the only reason), If I'm not wrong, the LG stock charger has output of 5.2V - 650mA DC and I've been using a motorola charger (5.1V - 850mA DC output).
Four days ago I started charging my phone only with my computer (usb port has output of 5V - 500mA) and I've had no trouble at all, the bug hadn't come back, today I charged my phone with the wall charger and the bug immediately came back, so for now that's my theory, the wall charger, stock or not, might fail and deliver more current that the O2X need so it mess the phone, I'm going to make fix on my charger to prove my theory, (I have no money for a new charger xD, but I'm studying electronics) if it fix it, I'll let you know, but you can try and charge your O2X with your computer for a day or two to help me prove my theory or prove me wrong
UPDATE:
It's been some time since I last posted here, I've been busy with my finals, but have had some time to make some tests to my phone. On my last update I told you that I had a theory about the bug, well, so far I can tell you that the wall charger indeed have something to do with the bug, but its not the cause of it, I've been using my wall charger letting my phone connected all-night long and the bug seems to happen again, but letting my phone connected to the PC for a while allows the USB sync and debugging again, so I'm not sure why it happens, I'm about to finish my finals so I'll try to make some tests once I'm done, hope this giude help you
UPDATE:
Well, as I was testing my theory, I go back to zero, this is because, my phone, doesn't have the bug anymore, so I have no chance to keep testing solutions for it, the conclusion I got with this is that the wall charger doesn't create the bug, maybe it triggers it, but not always nor on every device because, I haven't sopped using the same wall charger and the bug haven't returned, the last thing I did was, use my computer to charge my phone for three days, always letting it charge to 100% (unless I have to move from the computer) and the bug didn't happened, then, on a rush I had to use the wall charger, the bug appeared instantly, and then keep charging it with the same charger, two days after that, the bug dissappeared, I made no rom change, nor baseband, nor ril, nor anything, just like that it disappeared, so, I have no way to keep testing, if it ever comes back, I'll make some tests again, but for now, I have nothing to work with, hope this thread help you to get over this bug, at least, for a while, I'll be reading this thread in case you have some trouble with the instructions or so, cheers
UPDATE:
Ok, so I deleted long ago the last backup you told me was not working, and since I went to CM10 from Pengus I haven't had the no USB bug, so, one person asked me for the backup, I just made a new one, (this one is 204 MB on zip, read step 3) and uploaded it to 4Shared and Dropbox, so, remember to read and follow the instructions as they are, hope this time you can restore this backup, and one more thing, this backup was made just after installing it on the phone, so it doesn't have even a gmail account, you have to put yours and update market if you need something from there, ps. dont mind the date of the name of the file, it is innacurate, cheers
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
kohos said:
when dialing the above mentioned 1809#*990# in the Port menu, switching from default AP USB to AP/CP UART gave me life signs.
After switching to AP UART I linked the Unknown device driver to lgusbdiag.inf located in C:/ProgramFiles(x86)/LG United Mobile Driver.
Suddenly it started installing it and is now recognized as: LGE Platform Android USB Device.
Once disconnected I lose USB again, I'm able to recreate the first steps though even in default AP USB mode by now.
Click to expand...
Click to collapse
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
kohos said:
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
Click to expand...
Click to collapse
I'm extremely sorry, there's one think I missed, give you credit (fixing that right away), I actually found your post on modaco.com, and tried to access to the hidden menu from CM7 with no success, fortunately, I do have an early froyo backup that can be flashed through CWM, the only thing is that is the Telcel stock rom (I don't know if this can work with other O2X devices, I think there should not be problem at all)
About ADB, it work in full with the latest drivers installed and scanning for hardware changes on the computer device manager, It even work entering the S/W update service on the phone (to install a stock rom)
I know that many people have had this issue, I spent a lot of time reading forums and stuff about it, the only post that actually helped me, was yours, so, credit is yours, I did this post to show people what I excactly did (that's why is a lot to read, but I wanted to make it as easy as possible to follow up)
To identify the problem is a long and slow task, so, I'll be making some tests and let you know what I found, right now I have no much time, 'cuz I'm about to start my final exams, so I'll be busy, but as soon as I finish I'll be more dedicated to it, I'll be making hardware and software tests but can't promise anything yet
vanmarek said:
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
I tried to use that ROM, but couldn't manage to download it (I think it was removed, if you want to give it a shot try to find another flashable stock rom or backup, if not, give me some hours to clean my bakcup and upload it somewhere to let you use it, (it is mexico's telcel stock rom, but it should work)
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
vladutz9 said:
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
Click to expand...
Click to collapse
It all depends on what you install, if you manage to install stock rom through CWM or another recovery, yes you will loose root, but will have usb connection so you can root again, later today I'll upload my own froyo stock backup (it's mexican stock for telcel carrier, i think it should work out of méxico, maybe could cause network trouble on other countries, but its just a posibility, the important thing is that you be able to access the hidden menu), this backup I'll upload can be installed through cwm and its already rooted, so its like installing any custom rom, you'll keep your recovery and root
Remember, this is a temporary fix yet 'cuz I still get the bug comming back, maybe its because I am restoring my last working cwm backup, the only thing I haven't tried is clean all, install stock, root, install custom rom, and download again everything, maybe the bug is caused by something on that last cwm backup
I'll let you know as soon as I upload my bakcup
cheers
Well thank you! How i have this issue from one year i learned to live with her, but i could not live without root. So if i will instal a stock rom without root i will be unable to correct the usb connection i will get stuck with stock rom and no root. Will be the end of my phone. In am interesed to gain the usb connection for change the bb, i supose i can be something wrong with my bb 1035.21_20110725 and gingerbread. You can check to change the bb to see if you get again losing usb connection. Cheers and thank you 4 all.
got this after CM10 install
I've only had my phone for 1 day from new and already got this problem.
Rooted with superoneclick
Installed CWM v5.x
Installed CM10 Nightly Nov 13th
Now no USB mode, only charging.
baseband: v10e
RIL: CM10 1106
EDIT UPDATE: Well its working for me again now, I think in my case it was because I was using Linux and CM10.
By going to Settings/Storage then pressing menu button and selecting 'USB computer connection' I was able to change the 'Connect as' option from MTP to Mass storage and it now works.
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
vladutz9 said:
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
Click to expand...
Click to collapse
Actually yes, I've managed to identify what's triggering the bug at least in my phone, so might be the same for others as well, see the second post
BTW, did you tried already the fix? did you used my stock froyo backup?, if it didn't work, I can make another and upload it
Hi. Looks like I have the same problem with USB as you. Your theory about the wall charger might be correct. Here's my situation:
So, I've got my phone two days ago, bought used, came with a general Sony Ericsson USB charger. It says it outs 850mA at 5.0V (confirmed with a multimeter). The phone is on stock Android 2.2.2, isn't rooted yet. The guy from who I got the phone says that he suffered too with this kind of problem, however he got it working after 2 weeks without the use of the hidden menu. This means, that in those 2 weeks, he might have used a PC or a laptop to charge the phone. I tried the hidden menu port settings, however the only "working" mode is AP UART, but it is not recognizable by the PC, even if I try to link the LG drivers manually. Cycling through the modes did not help. I'll try to charge the phone with my PC, and see if that dose anything.
Details of the phone:
Firmware version: 2.2.2
Baseband: 1035.21_20110218
Kernel: 2.6.32.9-dirty
Build: FRG83G
LGE Version: LGEP990-V10b
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
mondc1088 said:
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Click to expand...
Click to collapse
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
No luck...
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Doctor0710 said:
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Click to expand...
Click to collapse
Hello, I'm sorry it took me a while to answer, I've been busy with my finals, did you tired the tutorial I posted? the hidden menu modification? I know that you let your phone charging for a while with your pc, actually, it should've worked but, maybe the problem on your phone actually is something else, 'cuz I haven't had that issue that the phone says it is charging but its not connected to the charger, my brother told me that he have had that same issue but with other phone, he changed the wall charger and that "fixed" it, but I think if you haven't tried the tutorial, give it a shot, try changing to CP UART if your phone's usb is working as it should, your computer should detect a new unknown device, if not, myabe your phone is hardware damaged, hope you can fix your phone soon
cheers
monkeyass said:
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What I did on my phone is exactly what I posted, if your computer haven't detected your phone on CP UART I doubt rebooting will make a change, anyways the most important thing to see if your usb is damaged or not is to try on the hidden menu the option CP UART it almost instantly detect the device, but, not everytime, I once waited there 20 min, so, give it a shot if you want, the stock rom I posted (on second post) is Mexico's Telcel stock rom, rooted, it doesn't delete your cwm recovery nor root, you can give it a try if you want, but read the instructions 'cuz you have to restore the ext3 format of your phone's partition to make it work (it stays on boot loop if you don't restore ext3 format), if the backup doesn't work, let me know to upload a new backup, hope you can fix it
cheers
vladutz9 said:
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
Click to expand...
Click to collapse
Hey did you managed to fix the problem yet? did you tried the bakcup I uploaded? it's Mexico's telcel stock rom, rooted, its made by cwm so it doens't delete your cwm recovery, give it a try if the backup doesn't work, let me know to make a new one and upload it ok?
cheers
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one