Related
I just noticed the new update when I opened the Kies in the PC and happily updated in my XP machine hoping that my long pending FW update which I was unable to do can now be done.
But you will not believe, my xp still struggles to detect my device even in this new update, I wonder what kind of update Samsung makes and if you see the version number there is a huge jump between .10071 to .10074 but for what.
Now I am trying to update my Windows 7 machine and let me see if I can succeed atleast there.
i had good device detection in previous version of kies
but in the new version it sucks
also the download said 123mb but went to almost 200mb
in both versions samsung apps store doesnt work, maybe its just for bada os.
UPDATE: yes finally I succeeded with the update from Kies. The upgrade worked fine like a breeze on my Windows 7.
People try the new update, as far as I can see the new update is not available in the samsung websites. When you open your Kies on your PCs it automatically notifies of an update. Goodwork Samsung atlast, Kies works and now I am ready for the froyo release.
sany said:
People try the new update, as far as I can see the new update is not available in the samsung websites. When you open your Kies on your PCs it automatically notifies of an update. Goodwork Samsung atlast, Kies works and now I am ready for the froyo release.
Click to expand...
Click to collapse
I would try, if I could download it some day in the near future. Now I have got 266 MB of 123 MB and sit several hours to watch those little pieces to flow from internet to my hard disk. It is senseless waste to update it for downloading a file at a time. Doesn't Samsung anymore can make an installation package?
Installed the Android SDK and now after the update on KIES, it won't go past 'detecting phone'.
My phone won't connect completely via Kies mode anymore. Oh my.
_
Sent using my Samsung Galaxy S i9000 using the XDA App
Same lost my connection but not sure it was an application installed previously or Kies.
Uninstalled Kies and installed the previous version but still no go same problem.
Has to be something on my Galaxy causing the issue.
I read someone said to format the internal SD and external SD to ensure no files are on it then sync.
That would mean re-installing or backup restore all my applications again.
This is just nuts.
can't find the URL to download this
Some people are sleeping over at Samsung. What a crappy software!!
I hope there will be some good Kies alternatives soon..
Hi All, I've been trying to get this phone working since Monday. I have installed and uninstalled the different versions of KIES a number of times. Still no joy. Once, today, it recognized the connection, but wouldn't sync to outlook, for me to be able to transfer my contact details across. Great phone (I think!), but awful software. I hope there's a 'breakthrough' soon!
Kies works fine if you proceed like this:
Check: Galaxy > Settings > About Phone > USB > Kies (ask for BlaBla will not work)
WakeUp the phone from sleep mode
Plug the bloody thing...
... and wait
... and wait
... and wait
... and wait UNTIL you can see the device in Windowz (about 2 minutes)
Start Kies
e volià
hanzi54 said:
Kies works fine if you proceed like this:
Check: Galaxy > Settings > About Phone > USB > Kies (ask for BlaBla will not work)
WakeUp the phone from sleep mode
Plug the bloody thing...
... and wait
... and wait
... and wait
... and wait UNTIL you can see the device in Windowz (about 2 minutes)
Start Kies
e volià
Click to expand...
Click to collapse
Not necessarily. Kies is one of the WORST applications I EVER USED! Terrible from the word go, NEVER been able to sync from phone to Outlook. Also, Outlook to Phone might happen once in a 100 times you try. Else it will give errors like "value does not fall within expected range". What the hell does that mean, hopefully Samsung knows and better improve the product.
Prankey said:
Not necessarily. Kies is one of the WORST applications I EVER USED!
Click to expand...
Click to collapse
I can't resist asking... have you used Nokia PC Suite or - even better, a lot better - the latest, freshly compiled Ovi Suite?
Tears flood my eyes just thinking about using it once again. And I know I'll have to. Kinda like that nasty job you hate but keep having to shuffle yourself to since you depend on it due to lack of skills, education or any fu"#$ing alternative ideas/options....
Yes. You hate it. But you'll use it again. And again. You all will.
Beowulf_pt said:
I can't resist asking... have you used Nokia PC Suite or - even better, a lot better - the latest, freshly compiled Ovi Suite?
Tears flood my eyes just thinking about using it once again. And I know I'll have to. Kinda like that nasty job you hate but keep having to shuffle yourself to since you depend on it due to lack of skills, education or any fu"#$ing alternative ideas/options....
Yes. You hate it. But you'll use it again. And again. You all will.
Click to expand...
Click to collapse
Nokia PC Suite is/was horrible and slow but at least it connected, can't say the same about KIES... personally I've only had little trouble with it but there's a whole lot of people who haven't been as lucky. Thank god we can use mass memory without starting up KIES
I have encountered the connection issue as well but that was after i installed Launcher Pro. into my i9000. Once i remove it, the connection run smoothly without any problem.
Hope this help.
when i updated kies i couldnt connect either , my phones said it was connected but kies begged to differ.
i uninstalled kies and all reg keys and downloaded the full kies and voila it worked again.
to the above poster get homeswitcher from market and you wont have to uninstall launcher pro , just switch when you want to connect to kies
regards
I think it's software conflict which are causing the issues.
I had a fully working Kies with the exception of the Calendar sync but after several application installations I can now not connect to my computer by USB.
I'm thinking of noting down all my software installations and resetting my phone as well as formating my internal memory. See if Kies comes back up.
Then I will install my software bit by bit testing each time to see which software might be causing the conflict.
chtan said:
I have encountered the connection issue as well but that was after i installed Launcher Pro. into my i9000. Once i remove it, the connection run smoothly without any problem.
Hope this help.
Click to expand...
Click to collapse
I installed home switcher so i can use the default launcher when i need to use kies.
Yesterday i updated kies and it took over 3hrs to download using the update function.
I wish Samsung would learn the magic of OTA.
(and remove all kinds of bloatware like touchwiz)
I wish i still had my old N1.
akselic said:
Nokia PC Suite is/was horrible and slow but at least it connected, can't say the same about KIES... personally I've only had little trouble with it but there's a whole lot of people who haven't been as lucky. Thank god we can use mass memory without starting up KIES
Click to expand...
Click to collapse
Yes mine did connect last week. I'm glad I installed the latest suggested upgrade build with the "Several Stability Enhancements" on the change log. It did connect fine this time.
And after the nicely animated Synch I'm now busy deleting the several randomly-added duplicated entries to both my calendar, notes and contacts on both the device (E72) and Outlook 2007.
That was useful, because it connected. And plus, sorting out all the mess manually will be a great past-time and distraction while I await for Samsung and Broadcom to figure out why gps tracks look like something your 3 year old drew on the living room wallet when you left that CD pen forgotten on the table.
Its been like 2 hours now downloading kies from the update popup while trying to run previous kies. Says its 100% dowloaded but still keeps downloading files like 980mb/123mb and to make it worse i keep having this popup from kies saying "The Internet is not connected. Do you want to check the connection and try again?" theres a Retry button i press in order to continue the download. I have windows 7 x64 and internet speed of 16mb so i dont get it. I thought of going to sleep and let it download all night, but its impossible since i need to press the retry button every minute when i get the pop up.
TheCarl said:
I installed home switcher so i can use the default launcher when i need to use kies.
Yesterday i updated kies and it took over 3hrs to download using the update function.
I wish Samsung would learn the magic of OTA.
(and remove all kinds of bloatware like touchwiz)
I wish i still had my old N1.
Click to expand...
Click to collapse
Thanks for the home switcher suggestion, for whatever reason i don't actually have to switch out of launcher pro when i use KIES.
Also, someone i correspond with here in PMs since we are both English speakers in Korea, hasn't installed KIES because he's on a mac. Yesterday we were talking about Swype and since i had asked him about his fw he brought up that he received an OTA update. I was shocked to say the least, and his firmware is as current as mine, however he didn't get the first three updates that i did through KIES.
Anyone having issues with Kies updating itself? I can start updating the program, but it constantly says "check your internet connection" (which is fine tyvm..). Basically the 70mb it has to download is taking several hours on a 60/60 cable line
To add insult to injury, when i try to firmware upgrade it tells me it can't find the Informationserver for the device. I wonder if Kies and HP printerdrivers are made by the same people
The wife has a SGS and to be honest kies is always a nightmare to use.
It seems to take forever to connect every single time, its the most un-user friendly program I think I have ever come across.
To be honest I had been looking at getting an SGS (having sold my nexus 1) but this coupled with the GPS issues is really making me think twice.
I had the same Kies update problem.
In the end I just uninstalled it and installed the updated version directly from the Samsung website. It seems to work OK
Amazing that Samsung has produces such a pos software for the phone. I just done use it at all.
Format your internal SD memory and your problem should be resolved.
They were for me.
Remember to backup your data and apk's first.
I have to say, the SGS forum seems full of people experiencing problems, usually of a bricking nature...
Is there something inherently unstable about the SGS or is the process of flashing it just really dangerous? I used to have a HTC Touch HD and I didn't remember the forums being this full of problems...
it's Windows and its horrible way of controlling the USB ports
i always have problems with USB in Windows, with any USB device on any version of windows.
on Linux it's simply it either works, or it doesn't work, no grey areas
Windows have lots of grey areas, like USB works but is not detected properly, or detects properly but the speed is crippled because something else is also on the same bus, or is detected and working, but the port is very slow operating at USB 1.0 when it should be at USB 2.0 speed, etc, etc, etc
all kinds of random problems with USB in windows
that's why some people flash fine no problem one day, then next day try again and it fails
Well I had problems with KIES for a while, and just as I got that working and tried flashing my phone (was running JM1 tried JPM Froyo) and its not worked since, just sent it back to Phones4U today hoping they can re-flash it. I've been flashing phones for years now having previously owned 2 HTC WinMo phones and NEVER had a glitch like this.
I think there are a few serious issues with this phone that Samsung need to address or seriously risk alienating customers. I won't have another Samsung handset if this keeps happening to mine
Thats a pretty weird selection on that poll, lol.
Yes IMO the SGS is quite unstable at times, especially with early firmwares and stock - JF3 was absolutely appalling beyond belief IMO - nearly sold it in my first week!
With the later firmwares and with the voodoo fix, it is a LOT better, but still far from perfect, and the GPS never worked properly for me.
As for flashing being "dangerous", I couldn't disagree more. These phones are hard to brick. I bricked my N1 today but I still got it back, it just took an hour!
SGS is pretty hard to brick, as long as you have the 3 buttons operational, you would have no problem recovering from a bad flash
tameracingdriver said:
Thats a pretty weird selection on that poll, lol.
Yes IMO the SGS is quite unstable at times, especially with early firmwares and stock - JF3 was absolutely appalling beyond belief IMO - nearly sold it in my first week!
With the later firmwares and with the voodoo fix, it is a LOT better, but still far from perfect, and the GPS never worked properly for me.
As for flashing being "dangerous", I couldn't disagree more. These phones are hard to brick. I bricked my N1 today but I still got it back, it just took an hour!
Click to expand...
Click to collapse
I think most of the problems with flashing through kies or odin is just that the new installation can't boot because of some conflict with previously installed software or setting. Since a factory reset seems to usually fix the problem. It just sucks that so many phones don't have 3br mode.
Why only 2 options? 3rd option should have been: No biggie as long as you have 3br-mode
My bet is = get a good cable (yes, this Samsung one IS crap -> I prefer Nokia's),
get a good motherboard (not top of the line, why would you?, not budget either)
make sure ur system/USB port is stable (u might want to undo overclock for the process... still I got mine fsb OC'd from 1066 to 1642 and still no prob)
make sure you have good drivers, and no viruses! (important! and underestimated)
And yes, 3button download mode is A MUST.
Plug in/flash/sit back and relax...
Flashed mine like 30-50 times already, not a single problem (besides the missclicks ;p)
My SGS and KIES work together happily. Never have any problem flashing via KIES. The 3-button combo (either download or recovery mode) is a must. Waiting for Froyo to be distributed in my country (Indonesia) now.
Never had issues with flashing with kies nor Odin3
A lot of the people who "bricked" it though soon managed to unbrick it.. Many of us freaked out and posted one of those threads at SOME point of time.
Most of the real bricks seem to be:
1) People flashing wrong ROM's
2) The IMEI thing
It's less riskier these days anyway probably, because of the existence of the Riff Box.
Hello guys, I am having some problems with the official Update froyo for samsung vibrant. I can't answer any call and the status bar doesn't work. Anyone else is having the same problem. I am going to downgrade my phone with odin to android 2.1 and then instal the rom axura or Nero.
dont have this problem
Mine has been stock ROM since I bought it last fall, upgraded to the official 2.2 KA6 and experienced huge lag issues, status bar would sometimes take up to 5 seconds to open after a swipe, apps would lag, etc. GPS was never fixed for me. No problems with calls though. I went back to JFD and then flashed Axura. No lag, GPS works (<10s lock, excellent accuracy), etc. Just do it, I should have done it long ago.
Upgrade
I am having a problem as well, have search not just this one but many. I can hookup mini kies and it starts the download gets about 1/3 of the way through and stops, says " cannot upgrade, try to pull the battery and reinstall and try again" have tried that four times? Suggestions anyone, I have not even heard anyone have this problem, have tried T-mobile, XDA, Android Community forums and nothing.
Anyone?
Have you tried resetting the phone?
Sent from my Sprint Galaxy Tab
No have been trying to avoid that, I will try it though. Did not want to redo everything I have on the phone. Oh well, I will give it a try.
Thanks,
try to do this.
First check if you have checked on usb debugging. Samsung mini kies has to detect you phone now. Upgrade your phone
No I didnt, I will try that first. I have to charge the phone now, I did not realize that was not checked.
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...
BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists
When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta
Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.
tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post