Related
FIXED.
Go to my post to see what I did!
http://forum.xda-developers.com/showthread.php?p=14498494#post14498494
Ok... The amount of problems I have experienced going from SC Rom, SimpleClean or whatever it was, to Heinz57 is extremely ridiculous... I'm going to skip all that I've done and go straight to the problem. Heinz 57 requires me to have EC10 kernel and radio or whatever. Well being on SC I had EC01. The only thing I found was to go to stock to get EC10 kernel and radio. Well, the very first time I flashed a rom, I was a noob, and forgot to freaking backup my stock rom, so I lost my stock Cellular South rom. In trying to get CWM and all this crap fixed and working, I eventually got Heinz57 installed, but I didn't have Cell Data, you know, like the internet. I could make calls, text, blahblah, but no 3G or anything like that. Then it hit me, this happened when I installed some stock rom that was for U.S. Cellular or some bull, but when I read it, it was for my phone, which is Mesmerize, and it was EC10, and one of the posts in there said it would take everything, even the radio. Well apparently something went wrong, so I'm thinking, why not get the stock rom for US Cellular for 2.1 and then use Kies to upgrade to 2.2, well apparently that's all it did was upgrade it. Because my phone was still US Cellular. Basically I either need the stock rom for Cellular South (2.1 or 2.2). I GUESS? Will that fix my radio? Is there just a radio I can flash with Odin? I've tried some EC10 radio I found in the Facinate forum (For some reason everything in the Mesmerize forum points to the Facinate forum, whatever. Lol), but it didn't do anything. Maybe EC10 just won't work on my phone? Do I go back to EC01 then just say whatever and try installing Heinz on that? I don't know I'm so lost haha. Any help is appreciated. Thanks.
EDIT: Sorry, the radio I flashed was EC01, not EC10.
This one: http://forum.xda-developers.com/showthread.php?t=1029436
EDIT2: So with @davidbruington informing me that I have a Showcase, I tried installing the EB11 files and Radio. No change. Same thing.
CS Showcase should have originally came with DJ20 radio.. I too made the mistake of flashing a Fascinate radio trying to get my TXTs to work with Evil Fascinate rom "awesome ROM BTW". Well I got TXTs working and lost data. Afterwards I have flashed all the Showcase ROMS, even the one with EB11 which supposedly works with the Showcase and data is STILL broke. So something gets changed flashing to a fascinate/mesmarize radio and back. If I knew what to look for I'd open up CDMA workshop and change it back. Anyone have any ideas? I will also add that after flashing to EB11, *228 gives me a programming failure everytime I try.
Both of you are running radios not built for cell south. Go to irc and get help. And stop flashing odin files not for your phone if you don't know what you're doing. Roms don't include a radio, so flashing them isn't going to fix your problem.
Sent from my SCH-I500 using XDA App
Not to mention, if you have cell south then you have a showcase, not a mesmerize. Hopefully that'll help you in the future. They are different, even if just slightly.
Sent from my SCH-I500 using XDA App
This isn't my first goat roping.. I've been flashing phones since the early Nokia days. I'll tell you what there isn't though, I list of radios and what hardware/carrier they are good for. I have a T-Mobile HD2 and soon a G2X and at least in the HD2 thread they warn which radios are ONLY for the T-Mobile variant.. in a RADIO Sticky thread. Can you blame me.. EVERY one of these phones whether a Fascinate, Mesmerize.. or in this case a Showcase "branded as a Galaxy S" all have the hardware model number of SCH-i500! I only found the Mesmerize threads warning of problems AFTER I had convinced myself that the phone in my hand was a Fascinate after searching the model number on google, and the first stop was XDA Fascinate forums. I think XDA needs to invest in grouping the phones better as the list on the main page is growing out of control.. would also help in the confusion and problems such as what I have encountered.
It's not xda's fault you assumed that everything for a fascinate would work for a showcase. A little research would have yielded the obvious answer that no, they are not all the same. Why else would there be separate forums for them? And separate versions of roms for the mes/showcase? Because they are different. And the radios are not universal, which is why you no longer have data. Again, go to the mes irc and they can get you back on track with a showcase flash.
Sent from my SCH-I500 using XDA App
What I am getting at is that ALL of these SCH-i500 model phones shouldn't have their own main thread.. mesmerize, fascinate, galaxy s, showcase, etc etc.. just because carrier X has given them a unique branding name.. hell, I didnt even know this phone was a "Showcase", it says Galaxy S on the back of the cover.. if you look here under galaxy S it has a model of i9000! If the hardware is in fact identical, the main thread should be devoted to it.. such as HTCs code names. Yes.. assumptions are bad but I did do a good bit of research.. it was only until I F'd up and had to search for the problem I was having that even more searching revealed that the phone I had wasn't a fascinate. Now the problem at hand.. the phone isn't bricked, its just the radio flash has changed something.. and even flashing back to a compatible radio didn't change this certain thing back. If it could be changed it should be able to be changed back.
Black6spdZ said:
What I am getting at is that ALL of these SCH-i500 model phones shouldn't have their own main thread.. mesmerize, fascinate, galaxy s, showcase, etc etc.. just because carrier X has given them a unique branding name.. hell, I didnt even know this phone was a "Showcase", it says Galaxy S on the back of the cover.. if you look here under galaxy S it has a model of i9000! If the hardware is in fact identical, the main thread should be devoted to it.. such as HTCs code names. Yes.. assumptions are bad but I did do a good bit of research.. it was only until I F'd up and had to search for the problem I was having that even more searching revealed that the phone I had wasn't a fascinate. Now the problem at hand.. the phone isn't bricked, its just the radio flash has changed something.. and even flashing back to a compatible radio didn't change this certain thing back. If it could be changed it should be able to be changed back.
Click to expand...
Click to collapse
All galaxy s phones are not the same, which is exactly why they have separate forums. You have not flashed a radio that is compatible for your phone because, as I said, roms do NOT include the radio. There is not a standalone radio flash available for the showcase. Your only option to get this fixed is to go to the mes irc chat and get what you need there.
Sent from my SCH-I500 using XDA App
I've been to the mesmerized IRC channel and I have d/l the EB11 Showcase rom which in fact included the radio. It did not fix the data issue. Are you trying to say all SCH-I500 model phones are not the same hardware apart from differing software? Do they have different ram or flash ammounts? From everything I've seen they are identical: 1 GHz Hummingbird Cortex A8, 384 MB RAM, 512 MB ROM... difference ROM/software. As I've said before.. somehow flashing the fascinate radio "EC01" has changed some internal register and flashing back to the EB11 SC radio will not change the appropriate register back. I've seen much harder problems fixed by people of the XDA forum.. just not enough users with SC phones to warrant an investigation by the people who would know how to correct this particular problem.
Sent from my HD2 using XDA App
The hardware is probably identical except the actual wireless transceiver that is built for each carriers network. In some cases, you can use a different radio (the software that operates the transceiver) and it will work. But the problem with any software not written expressly for your device is not the device itself, rather the problem is that the software does not contain the proper id, settings, and configuration for your carrier. That is why everything on xda always carries with it the "at your own risk" disclaimer.
That being said, most of the folks in the irc are experienced devs, who would probably be glad to try and help you remedy the pickle you're in, if you asked nicely. If you go in there with a "this is your fault, fix it" sort of attitude, then you may be **** out of luck.
Do you have to brown nose them? No. But it couldn't hurt. They put up with a lot of **** here, and fortunately they keep providing us new and exciting software to experiment with. For free.
That's my two bits. Do what you will.
Sent from my SCH-I500 using XDA App
I have all the respect in the world for the development.. they make our phones more than just a communicating device but a fun gadget and hobby for some. I'm well aware of the risks for this hobby.. I've had my share of mistakes believe me. Its more a gripe about xda-dev forum than this device.. back when there were only a dozen phones on here it was hard to mistake them apart.. I bought an O2 xda II s because there wasn't a GSM phone like it at the time.. now we have literalle a hundred different model phones and now different branding of the same phone on different carriers.. organization here is critical.. almost overwhelming. My first search gave me a result.. but not exactly the correct information. Cellular south is not large enough to have their own device threads.. I've known that for a long time. The only info I had was it was called a galaxy s and had a model of sch-i500. My search of galaxy s landed a model of i9000.. I knew that was not correct so I figured CS just slapped the name galaxy s on another device.. marketing blah. My next search of the model landed the fascinate device which looked identical so I figured I had it.
Sent from my HTC HD2 using XDA App
Edited the OP
Well, now that we have berated you enough (Lol) lets see if we can help you remedy the situation. So calls and texts work, but no data. Is there a data icon? 3g or 1x?
If you can gain access to the hidden menu you may be able to learn a bit more about whats causing this. At one point my phone (for whatever reason) was stuck in 1x only. I opened the hiddenmenu and changed it to force evdo (3g) waited till it changed to 3g mode, and then switched it back to hybrid.
Sometimes tinkering makes a world of difference. Im not really sure what else to tell you from here... I'm no dev by any means.
Btw, some of the info in the hiddenmenu is generic. For example, I have uscc yet even on a stock rom some of the messaging configurations have crap related to vzw (verizon wireless). If you screw something up, a fresh reflash of the Odin package should set the hiddenmenu options back to default again.
Hopefully someone with more experience than me, who knows all about radios and the like, will step in and direct you further.
Edit: Btw, wolfstar, I'm sorry dude I didn't mean to hijack your thread. My dumb ass didn't pay close enough attention to realize that there's two people in this thread with similar problems...
Sent from my SCH-I500 using XDA App
davidbruington said:
-snip-
Click to expand...
Click to collapse
Not a problem, lol. I did get my problem fixed though. I'm not gonna lie, I have NO idea how, but I did.
To answer your question, no, I did not have 3G or 1x by my signal. Just the signal bar.
To answer how I fixed it, I wish I could tell you guys. I went to the IRC and someone pointed me to a stock ROM which I flashed, and it didn't work. That was an EB11 rom I do believe. Then I did some searching and apparently I found out that no one really has the full stock EB11 rom because the modem would never get fully flashed, and I was like, maybe that's my problem because I went from EC10, which was not supported for my device but for some reason still gave me signal to call people and what have you, to EB11. Well I was like, since there is no EB11 I'll go to the one below which is DJ20. When I did, it didn't work. I was so disappointed. Turned out the DJ20 rom didn't have the modem in it at all, because I check my About Phone menu and I still had EB11 for the baseband. Well I did the *228 just for the giggles, (NOTE: I have been doing the *228 every time I flashed a rom when trying to fix my issue, just to see if maybe it will fix something.) and let my phone reboot. When it turned back on, still no data. This was my last straw, because I had honestly run out of every option I had left. I set it down to think what else there could be to do, picked it back up and unlocked it and BAM, 3G. I have no idea how, or why, but somewhere in what I did it fixed it. Maybe when I went back down to DJ20 and did *228 it downloaded what little bit I was missing in the transition from DJ20 to EB11. It's my only hypothesis.
Thank you guys for all the help. I know you guys didn't have the answers but at least you tried.
ALSO. I did go through my settings with each flash, to make sure they were correct, and they were all on. So I know that my data was on in each flash.
I hope that maybe someone can use this little bit of info one day to either AVOID this or FIX it. Goodluck!
Glad you got it fixed! yeah I remember reading something about cell south demanding its packages removed or something? Apparently they are uberstingy. Anyway, good job and thanks for posting it here for others.
Sent from my SCH-I500 using XDA App
crap.. I could have sworn I too flashed back to a dj20 rom but maybe not. The roms contain APN settings correct? would anything BUT an original Showcase rom in theory not work? It doesnt make sense because even after flashing to the EB11 Showcase rom my data still did not work.. its almost like there is some NVRAM that stores APN settings that must be set by an original flash. Wolf,after you flashed EB11 did *228 give you a failure every time you tried it?
Black6spdZ said:
crap.. I could have sworn I too flashed back to a dj20 rom but maybe not. The roms contain APN settings correct? would anything BUT an original Showcase rom in theory not work? It doesnt make sense because even after flashing to the EB11 Showcase rom my data still did not work.. its almost like there is some NVRAM that stores APN settings that must be set by an original flash. Wolf,after you flashed EB11 did *228 give you a failure every time you tried it?
Click to expand...
Click to collapse
No, every time I did *228 it was always successful and it would reboot my phone, but even after it rebooted it was still the same. Check your About Phone and see if you have the EB11 Baseband, if you, try what I did and get the DJ20 ROM and do the *228.
I can gladly say that I still have 3G/1x with no problems.
I want to return to stock on my tmobile branded HTC sensation 4G. I have flashed the radio, eng s off, and CSL recovery.
I am going to give them a shot at fixing my reception issues before I destroy the phone and buy something else.
Did you have reception problems before flashing your radio or after? I think you should be fine with having a rom since HTC released their bootloader if its a big deal and your really worried just flash a stock rom on that bad boy and call it a day. Just my 2 cents new to the site so hopefully a vet will chime in here for help
Though I've never returned to stock on my phone, you just need to download one of the TMOUS RUUs in this thread:
[ROM][11 May] Shipped Pyramid ROM Collection
There are two listed for TMOUS (there was only one when last I checked the thread), but it supposedly doesn't matter which one you pick according to one of the posts later on in the thread.
They're big old files, but just run the .EXE and it ought to walk you through every necessary step to proceed properly.
Good luck, and let us know how it goes!
Thank you very much for the great responses.
Yes I had reception problems on all 3 sensation 4g's I've had my hands on. It's terrible. Side by side, on the same tower, it gets far lower reception than my old Motorola Cliq (piece of slow crap.)
It's ridiculously low and drops calls. It's so unreliable at my house that I have to use WiFi calling and take a drop if I get more than 30' from my extremely good wireless router. meh. crap.
To the other gentleman, than you very much. I figured it included the radio, but I was unsure about the bootloader/recovery. I will start there and then figure out if there is anything else I need to fix before I send it in. I don't want any more BS from them. I'm sure they are just going to send it back and say "nothing is wrong".
They have said that it is comparable to reception on their other models. If this is the case, this will be the VERY last HTC phone I ever own, and our company has just gotten to the point that I can invest in things such as this for business. If we only get 2 at a time, every 6 months or so, That is $10,000 in lost business in the next ten years, provided they are only $500 phones.
chisleu said:
Thank you very much for the great responses.
Yes I had reception problems on all 3 sensation 4g's I've had my hands on. It's terrible. Side by side, on the same tower, it gets far lower reception than my old Motorola Cliq (piece of slow crap.)
It's ridiculously low and drops calls. It's so unreliable at my house that I have to use WiFi calling and take a drop if I get more than 30' from my extremely good wireless router. meh. crap.
To the other gentleman, than you very much. I figured it included the radio, but I was unsure about the bootloader/recovery. I will start there and then figure out if there is anything else I need to fix before I send it in. I don't want any more BS from them. I'm sure they are just going to send it back and say "nothing is wrong".
They have said that it is comparable to reception on their other models. If this is the case, this will be the VERY last HTC phone I ever own, and our company has just gotten to the point that I can invest in things such as this for business. If we only get 2 at a time, every 6 months or so, That is $10,000 in lost business in the next ten years, provided they are only $500 phones.
Click to expand...
Click to collapse
If I may be so bold as to make a suggestion and ask a few questions....
1. Have you tried reverting to stock and see if you still have the same problems with reception?
2. Are you aware that the Sensation suffers from the grip of death?
3. Have you noticed performance with reception after flashing a new ROM in comparison to stock?
I think I may have some insight to the real problem but need this info first.
mystikal87 said:
If I may be so bold as to make a suggestion and ask a few questions....
Click to expand...
Click to collapse
Best 3 Stooges voice: "Sauwtainly"
mystikal87 said:
1. Have you tried reverting to stock and see if you still have the same problems with reception?
Click to expand...
Click to collapse
Yes, They (3 different phones) had this problem from day 1. Purchased from different places, at different times.
mystikal87 said:
2. Are you aware that the Sensation suffers from the grip of death?
Click to expand...
Click to collapse
Yes, but this isn't to what I refer. Holding the phone in a weird way to make the radios D/C isn't my problem so much as the design that allows this to happen in the first place is my problem. If I set the phone down, I get more bars than if I hold it normally. If this is the difference between 2-3 and 1-2, I can get dropped calls. My wifi range (max performance on) is 1/10th of my tablet and 1/20th of my laptop.
Even without touching the phone, just setting it on a wood counter top, it has less reception than my Motorola Cliq or Mytouch 4g, even when on the same tower. The cliq's reception does not change if I pick it up.
It's a bad design. If it is what HTC considers acceptable, then their phones aren't acceptable to me. It's cool. I'm not really that pissed about it. I just won't buy another. There are options.
mystikal87 said:
3. Have you noticed performance with reception after flashing a new ROM in comparison to stock?
Click to expand...
Click to collapse
No, I've found no increase in reception with any change I've made. I've flashed 5 different radios other than stock with no changes in this department.
I have heard people have speed changes, but I was not tracking that so I can't really respond to that.
mystikal87 said:
I think I may have some insight to the real problem but need this info first.
Click to expand...
Click to collapse
Hope you have some help.
I've already tried a new back. It did nothing. There simply aren't enough towers in my area (all edge towers anyway) to support a phone with such poor reception. My Cliq had no issues with dropped calls in many of the areas I drive through, but this sensation just can't make it down my parents road without dropping.
The reason I ask is that I think that the Radio-Interface-Layer (RIL) files must be screwing with your radio. The RILs are like drivers for your radio. Different radios work with different RILs depending on your location. Long-in-short-version, Since the Sensation is fairly new, we are still exploring what works best and therefore your mileage may vary.
You may want to check this thread
And check out your RIL version. To check to see what RIL you have run getprop "gsm.version.ril-impl" in Terminal Emulator or adb shell and it will print out the RIL version.
T-Mo users should utilize HTC-RIL 2.2.0159HMQ if not running 2.3.4 ROMS
2.3.4 ROMS require HTC-RIL 2.2.0169HMQ. The matching radio versions are included in the thread posted above.
Hope this helps.
If that fails, tonight, TMOUS released an OTA update. See if you can get it through Settings-> About Phone -> HTC Software updates.
The changes for the T-Mo update can be found here
Hope this helps!
EDIT : I am assuming that you have a T-Mobile Sensation 4G and not an unbranded HTC Sensation and that you current location is in fact Myrtle Beach, SC. But then again, I hate assumptions and I really should have asked >.< **having a simpson 'doh' moment here**
Change your cid to all ones and flash the stock ruu.exe and send it back to tmobile.
Sent from my HTC Sensation Z710e using XDA Premium App
charlieb620 said:
Change your cid to all ones and flash the stock ruu.exe and send it back to tmobile.
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I'm sending it to HTC, not tmobile.
I will play with the MILs right now (installing the tmo one)
I'm on stock RUU now, but it did not replace the PVT S-OFF and recovery crashes and requires a battery pull to reboot. It goes to a icon of a phone with a red triangle thingie on it.
EDIT: MIL's match.
EDIT: Texts from 10076200000 is tmobile related. WTF it does is WTF.
chisleu said:
I'm sending it to HTC, not tmobile.
I will play with the MILs right now (installing the tmo one)
I'm on stock RUU now, but it did not replace the PVT S-OFF and recovery crashes and requires a battery pull to reboot. It goes to a icon of a phone with a red triangle thingie on it.
EDIT: MIL's match.
EDIT: Texts from 10076200000 is tmobile related. WTF it does is WTF.
Click to expand...
Click to collapse
Could be trying to push the OTA update. Have you tried applying the OTA update?
iNFORMATION
I have personally reset my phone a couple of times using the tmo ruu and know that it sets your phone back to absolute stock, with no root and only being s-off. What this means is, if you wish to reroot then you are going to have to go back through the rooting process.
As far as the symbol that you are seeing when you try to do an ota update? The reason that you are seeing the phone with a red triangle is because your phone is being recognized as being rooted and once rooted htc will not allow an ota to your phone. You have to trick HTC into thinking that the phone is not rooted in order to get the ota, there is a thread in the forums for this. I do not remember which thread it is, however, I know that it works as I did it for all four of the HTC sensations that I own.
Massive thanks to PulpZilla for letting me have his OP. I will now be able to take care of the updates a lot easier. Mate, this was a nice move. And even though the "Thanks" at the bottom say they where for me, they are still counted to your name. I did not get them from you
-=Introduction=-
This Thread serves as collection and information point for all Data regarding the HOME BUTTON / SCREEN ISSUE or as HTC sometimes likes to call it: HELICOPTERING GLITCH.
It also serves technical and factual discussion in order to maybe find ways to overcome or work around the issue.
For any and all discussion regarding civil, legal or other types of action against HTC we now have a new thread, named:
Operation Rolling Thunder
It is run by Gibarian. Please head over there for discussing actions and options. I would also like to encourage everyone to move discussions of "Buy or not to Buy" this phone over to that thread. So we can keep this clean for rather technical and news things. Apart from that, I would also like to express that i outspokenly support the campaigning as long as it stays civil and serves the sole purpose of raising public awareness and thus creates the necessary pressure on HTC. I would like you to support the current campaign there too to help our issue getting taken more serious. Up till now HTC has delivered nothing but empty promises.
Please refrain from stupid actions/posts/reviews.
Thank you.
Sneakyghost
-=Problem Description=-
Main Symptom:
The capacitive Home Touch Button sometimes likes to press itself. When in an app or the home screen without or with the finger near the home button it seems to get pressed a few quick times in succession without actually being touched.
Click to expand...
Click to collapse
Additionial symptoms:
- continuous/odd vibration
- multiple screenshots being saved to disk without the user interacting with the phone
- the virtual buttons appear locked/dead/without function [NOTICE] From Base 2.21 onwards, this can turn into the main symptom and the screen switching can disappear.
- long-press menues coming up randomly (On Stock JellyBean 3.16 this would be Google Now popping up all the time)
Click to expand...
Click to collapse
Occurrence and reproducibility:
Mainly related to GSM activity, rarely on WCDMA only setting. It seems to be related to low GSM signal (1 to 2 bars), switching between networks, calls coming in or building up, seldom wifi and 3g connections. The occurrence still seems rather random as it is hard to purposely reproduce the situation. The best chance to trigger the misbehaviour or malfunction is if signal coverage is low, 3G/HSDPA (or: WCDMA) is not available, try to build up a call or start a heavy data transmission on edge. A few people report the issue only after the first 2- 4 weeks of use.
Also noteworthy: it seems to hit phones in complete unaltered, stock state as well as heavy customized and unlocked phones.
Click to expand...
Click to collapse
-=Documentations and Discussions=-
Discussion on the Vodafone UK forums: http://forum.vodafone.co.uk/t5/HTC-One-Series/Home-screen-button-problem/td-p/1082393
Discussion on the O2 Germany Forum: http://forum.o2online.de/t5/Software-Firmware/HTC-One-S-Home-Knopf-Problem/td-p/259614
Discussion on the SwissCom Forum: http://supportcommunity.swisscom.ch...onie/HTC-One-S-Home-Knopf-Problem/td-p/121958 (NEW)
Discussion on the Android-Hilfe.de Forum: http://www.android-hilfe.de/htc-one...usgeloest-durch-bestimmte-netzfrequenzen.html
Discussion on the Handy-Faq.de Forum: http://www.handy-faq.de/forum/htc_one_s_forum/251792-display_springt_hin_her_home_ansicht.html
User contributed Video: http://www.youtube.com/watch?v=LOb1LuWA7N8
User Contributed Video: http://youtu.be/kvPOZsk9I_I
User contributed Video: http://www.youtube.com/watch?v=mEKwMkuisqE
Disassembly video, bottom Antenna, US Model: http://www.youtube.com/watch?v=b0jGY2N2h1U
Disassembly Video, complete EU Model: http://www.youtube.com/watch?v=1lBT15PgpYw
LeeDroid mention of HTC's own theory: http://forum.xda-developers.com/showpost.php?p=26819259&postcount=707
Related:
http://www.youtube.com/watch?v=B6xlZFcgPlo (similar issue on Galaxy Nexus) (Thanks to SageKing for pointing this out!)
https://plus.google.com/112413860260589530492/posts/1a4hY7VeqiG (Google Engineer talking about the Galaxy Nexus problem)
http://maps.mobileworldlive.com/ Site to see which operator uses what frequency in which country - cross check against Affected users Spreadsheet!
-=News Articles=- (please send in other articles if you find any as we will pass them on to HTC at some point):
http://www.geeky-gadgets.com/htc-one-s-touch-button-bug-makes-phone-go-crazy-26-06-2012/
http://www.phonearena.com/news/HTC-One-S-touch-button-bug-makes-the-phone-go-crazy-video_id31606/
http://www.chip.de/artikel/HTC-One_S-Handy-Test_55316948.html
http://www.chip.de/news/HTC-One-S-Probleme-HTC-bezieht-Stellung_57834622.html --> Chip cites HTC here, yet no source is given.
-=Attempted fixes=-
- Disabling GSM/EDGE completely (no calls in rural areas, Issue not fixed)
- Setting Accessibility → Touch & Hold delay to medium (reported ineffective by some users starting HERE
- Factory Reset (multiple users had tried this, was recommended by different support agents, did not help at all)
- different Radio (there had been different radios involved, but not all radios seem to be affected. Still needing evidence)
- Exhchange SIM Card. (has been done by several users, did not help at all)
- Root device, Unroot device, flash Custom, flash stock, unlock Bootloader, relock bootloader. (did not help at all)
- Removing bottom cover (Mobile Radio Antenna), cleaning spring contacts, examining hight (make sure contact is made) - Not fixed
- Setting Display illumination to Auto Brightness (did not help at all)
- Run CM9/CM10/MIUI/JB Builds. Did not change anything.
- New Radio 1.06s.50.02.27_2_10.08.50.04L (19th of July 2012) Betters it for most users considerably,did not help all Users
- New Radio 1.06es.50.02.31_10.09a.50.04L (21st of August 2012) Worsens the effects clearly for most users, did help some very few. Upgrade NOT recommended!
- New Radio 1.08es.50.02.21_10.09c.50.04L (14th of September 2012) Some users report failure and behavior similar to the 1.06es radio.
- New Radio 1.08ts.50.02.16_10.08e.50.04L (ca. November 2012) Similar to the 1.08es radio
- New Radio 1.09ts.50.02.04_10.08g.50.04L (ca. November 2012 Only my Test-Results available, which where just as bad as 1.08 based Radios.
- New Radio 1.11.50.05.28_10.27.50.08L (24th of December 2012) Worse than the 1.08 radios, but some users also reported a Fix
-=Working Fix(es)=-
none known
Update 4th July 2012: HTC begins to claim towards some users now, they were soon be rolling out a software fix. 4 weeks later, they still say the same.
Update 21st July 2012: HTC has not officially acknowledged the Issue, but allowed this Info from HTC Elevate moderator Jason Dunn to be shared: "A software based Fix is possible and being worked on. A release date is not available but it will come".
Update end of July 2012: HTC released a new RUU (RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe) with new Radio. Betters it for most users considerably Semi-FIX. Not good for all.
Update 30th August2012: HTC Released a new RUU (RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed .exe) This Firmware does not help most users but rather worsens the effects again. Upgrade of Radio not recommended!
Update 14th September 2012: HTC released a new OTA to Vodafone Customers going by the Name of 2.38, containing a new Radio 1.08es, which does not solve anything. Like the previous 2.31 WWE release, it seems to make matters worse again.The other carriers succedingly released their updates with either the 1.06es or the 1.08es radio. Only T-Mobile released a 1.08ts variant. None fixed the Issue.
Update 24th December 2012: HTC finally released JellyBean Firmware 3.16 to their customers. It became obvvious only hours later that it did not fix anything. I myself have a worse HBI problem than on 2.31. Plus, reception and Data-Switching got worse too.
-=Workarounds=-
- Disable Home Button: User Beatnix has found out how to disable the Home button completely. It can then be replaced by the App "Button Savior"Obsolete
- Recommended: Custom ROM allowing button remaps. Viper ROM with Venom Tweaks has given me almost a hassle free Experience during the past month due to its ability to map functions to the buttons that either do nothing or do not disturb too much.
- Recommended: After countless tests with all sorts of Radio/Wifi-Partition/Base Version Combinations it is very obvious that the 1.06s Radio from Base 2.21 is by far the best, least bugged Radio.
Note: A "Brick Downgrade[/UL]" might be required, if you are already on or above Firmware Version 1.78, as Radios can only be flashed on lower hboot versions. Here is a [URL="http://forum.xda-developers.com/showthread.php?t=1990043"]Tutorial
-=What Now?=-
If you are feeling like getting active i would like to invite you to join Gibarians Operation Rolling Thunder which is designed to make our Issue heard. We feel that we have been quietly waiting for a fix long enough and that waiting any longer will just make HTC believe that they do not need to take any further action, so Gibarian has designed a campaign to make the Issue more public and make it obvious to HTC that there is need for urgent action.
At the time of writing, some People have been waiting 6 month for a fix and had not gotten a replacement, nor any other compensation. They have just been left out in the dark with a nearly unusable phone. So, feel free to make yourself heard! Also, if you just have a story to tell, feel free to add it at Gibarian's Thread "Operation Rolling Thunder". You are warmly invited to share your sufferings there and also discuss recommendations for other (potential) buyers.
-= IMPORTANT: Report your device here if affected =-
PLEASE:
file a report with your vendor (most likely your carrier) and ask for repair/replacement
file a report with HTC. Ask for repair/replacement if your Vendor refuses.
This is very important, as this is the only means by which HTC can tell the severity of the issue!
Jason Dunn of HTC Elevate and Richard Willis of HTC Consumer Communications EMEA encourage everyone to report to HTC.
Please also report here: (For updating your Entry please contact Sneakyghost or Zoesdad70)
[UPDATE 11.10.2012]
Here is a new Report Sheet where everyone with a Serial xx26 and higher can report his FULL serial and Contact Details.
Personal Information: This Sheet can only be accessed by me (the Results page) and is only used to be forwarded to HTC. I kindly ask you to leave contact details for the sole purpose of possible further questions. Your data will remain with me and there will be no abuse.
Thank you.
LINK: http://goo.gl/5gAR8
What do we do that for? I am currently talking with another HTC Digital Consumer Communications Manager for the EMEA region and he is trying to find out about the new devices. If it is a lot of them, HTC wants to fix that in time. To be able to do so, they need to know as early as possible. So, your help is greatly appreciated and in the end, will help all. Thanks.
Click to expand...
Click to collapse
-=Statistical Data of affected users=-
Updated 7.01.2013
Total number of reports:
793
- Areas where this has been reported:
Portugal, Spain, France, Belgium, Netherlands, Great Britain, Ireland, Swiss, Germany, Austria, Denmark, Sweden, Poland, Estonia, Latvia, Czech Republic, Russia, Ukraine, United Arab Emirates, Israel, Malawi, Ethiopia, Niger, Iran, Malaysia, China, Vietnam.
Please pay attention to this! It is mainly northern Europe and Russia. Up till now four reports from the US.
- Serial - Numbers first digits that had been reported as affected:
FA28 (2x)
HT23 (183x)
HT24 (77x)
HT25 (18x)
HT26 (7x)
HT27 (3x)
MB22 (1x)
SH23 (149x)
SH24 (190x)
SH25 (27x)
SH26 (35x)
SH27 (1x)
SH28 (1x)
- Base Versions reported (Entries cleaned up, corrected Base Versions according to reported Radios. This assumes that all reporters used either RUU or OTA).
1.09 (2x)
1.11 (8x)
1.15 (1x) (odd Thailand version - never seen anywhere else)
1.47 (1x)
1.53 (16x)
1.70 (6x)
1.77 (40x)
1.78 (273x)
1.84 (5x)
2.15 (2x)
2.21 (10x)
2.31 (338x)
2.35 (3x)
2.38 (20x)
- Black device count:
577
- Grey device count:
185
- Baseband versions reported:
0.15.31501S.16_3_10.12.31501S.06L
0.15.31501S.19_10.12.31501S.06L
0.15.31501S.19_2_10.13.31501S.06L
0.16.31501S.17_10.23.31501S.10L
0.16.31501S.17_2_10.23.31501S.10L
0.16.31501S.19_2_10.23.31501S.10L
1.06s.50.02.27_2_10.08.50.04L
1.06es.50.02.31_10.09a.50.04L
1.08es.50.02.21_10.09c.50.04L
1.08ts.50.02.16_10.08e.50.04L
1.09es.50.02.07_2_10.09d.50.04L
16.11.20.02U_16.05.20.11_M2
16.12.20.02U_16.05.20.16_M2
16.13.20.02U_16.05.20.24_M
16.13.20.02U_16.05A.20.23_M
Concluding:
All the numbers peak at xx23 and xx24 serials. Base 1.78 and 2.31 are reported most often. My Guess: the March and April devices are worst combined with those two bases.
Source of these figures is the Google Spreadsheet, Anyone wanting to add can do so. Please feel welcome to put in your details via the Form linked in the top left Cell of that table, the top right cell of the table holds another spreadsheet-form for only the newer xx26 and up serials. It is designed so that it remains private because you can put in your contact details so that HTC can contact you. They are currently investigating the newer devices and might need your help.
-=END NOTICE=-
If you came here to find information you were helped hopefully. Please help other people with the same issue by raising your voice and add a report. Please include your Country, your first part of the Serial (“SH23”), Carrier Base, Baseband, Phone color etc. Best is to update the Spreadsheet directly.
Same problem here, although it hasn't happened in a while. I have the phone rooted but even before it was rooted it happened.
interesting. Since you've rooted and changed the ROM it hasn't happened?
Same one here.
I think it has something to do with the gsm-mode. When i'm in an area without HSDPA(only G-Mode, sometimes also in Edge) or when i manually switch the mode to 'only GSM', the switching appeares.
The strange thing is that this is not always the case.
I don't know if this is a hardware error or has something to do with the recent update. I can't compare this because my phone came back from RMA the day the Update was released. On my 'old' phone (before RMA) i never had that problem, but that was before the update.
*edit*: Still on Stock Rom.
Greets,
**Jürgen**
opiswahn said:
Same one here.
I think it has something to do with the gsm-mode. When i'm in an area without HSDPA(only G-Mode, sometimes also in Edge) or when i manually switch the mode to 'only GSM', the switching appeares.
The strange thing is that this is not always the case.
I don't know if this is a hardware error or has something to do with the recent update. I can't compare this because my phone came back from RMA the day the Update was released. On my 'old' phone (before RMA) i never had that problem, but that was before the update.
*edit*: Still on Stock Rom.
Greets,
**Jürgen**
Click to expand...
Click to collapse
funnily enough it seems to happen more when there's less light? also it still happened when i had WiFi on so i'm not exactly sure of the cause. Hopefully it is only a software glitch and something that can be fixed in custom ROMs!
Has someone fixed the problem with a custom rom? Or has that problem with a custom rom?
I'd like to know if i have to RMA ma phone again or if it's a simple software glitch...
after more testing it looks like you're right it seems to happen when the phone is searching for a GSM signal on edge?! really weird...must be others out there having the same issue?
Sure, that problem have more people. I have reported it to HTC this day. The problem is the Edge we think. It can be reproduced if you turn on Gsm.
I hope HTC make a update to solve the problem, but more people must report I think.
P. S. I'm on Trickdroid Rom, this happens on custom Rom to.
Gesendet von meinem HTC One S mit Tapatalk
PulpzillA said:
after more testing it looks like you're right it seems to happen when the phone is searching for a GSM signal on edge?! really weird...must be others out there having the same issue?
Click to expand...
Click to collapse
A whole bunch of people have this problem over on the UK Vodafone HTC One S forum
I have this problem whenever I try to press space, I end up hitting home. I noticed that if you slide your finger down from the screen onto the touch buttons, it registers as a button press. Whereas on my Desire S, if I was sliding my finger down (i.e. scrolling a list), even if I went past the screen and onto the touch buttons, it would still continue to scroll. Only if I let go of the screen and then touched the buttons again would it press. I'm pretty sure that's how it should be.
Lamyron said:
Sure, that problem have more people. I have reported it to HTC this day. The problem is the Edge we think. It can be reproduced if you turn on Gsm.
I hope HTC make a update to solve the problem, but more people must report I think.
P. S. I'm on Trickdroid Rom, this happens on custom Rom to.
Gesendet von meinem HTC One S mit Tapatalk
Click to expand...
Click to collapse
Did you wrote a Mail or did you call some support?
*Edit*
Ok, i just had a chat with a support-lady from HTC, she told me HTC knows of this problem and they are working on an update for this. But there is no release-date for this update.
*Edit2*
This doesn't seen to be a hardware problem, thats good news so far. Everyone who has this problem should report to HTC, to increase the pressure for the fix. This was a hint from the support-lady
I had same problem.
I gave my phone at warranty service, they checked it and approved the problem.
I managed to get the phone to seller and exchange to new one, but I know if I would repair it at service, they would replace back cover (had little chipping), battery and MOTHERBOARD.
So I suggest you to bring it to warranty (if the return period is over) and they should fix it...
PulpzillA said:
interesting. Since you've rooted and changed the ROM it hasn't happened?
Click to expand...
Click to collapse
Just to clarify. I have the phone rooted but still on the stock ROM. And yeah, it seems to happen when its not on 3g.
Here is a video of the problem:
http://www.youtube.com/watch?v=mEKwMkuisqE
Please post if you are concerned by the problem.
Conditions foir this issue to happen:
No wifi.
EDGE with low signal. numerous siwtch of the phone between 3G and EDGE.
then you shall reproduce the issue.
Thats exactly it. Just report to HTC to increase the awareness of this problem, so the fix comes out faster.
Really annoying now as the phone is barely usable on GSM signal! Gonna have to complain to HTC. This shouldn't happen whatsoever. It's a simple thing to test for?! Can't believe it wasn't picked up...
Don't know if its worth wiping and seeing what happens?
Sent from my HTC One S using xda premium
Guys, I turned off the data roaming sound in the network settings and havnt had this problem since. Though I.only turned it off last night but it hasn't happened since.
Sent from my HTC One S using XDA
Interesting! thanks for the tip. will try this out and see.
shoffobroff said:
Guys, I turned off the data roaming sound in the network settings and havnt had this problem since. Though I.only turned it off last night but it hasn't happened since.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Unfortunately that didn't work for me.
I sent mail to HTC support to inform them about problem.
They advise me to try new sim card.
I have new sim card now, but problem still exist
I'll send phone back tomorrow, but I think that next one will be affected by the same issue.
This has been getting worse for me. Seems to happen particularly when outside? Otherwise; exactly as described; when switching to and from Edge.
Neither Vodafone nor HTC UK are aware of the problem. HTC global suggested I hard reset. Currently awaiting next useful repair suggestion...
Okay lets start from the beginning.... about a year ago I switched to Verizon ONLY so that I can get 4g as they have the best 4g in my area. (Detroit). I loved it at first...smoking hot 4g almost everywhere I went. When my home internet went out I could tether to my phone... life was good. Sometimes when entering a building I would drop to 3g but my desk and PC are by a picture window so I always had 4g to tether with.
Then came that update a couple months ago.. don't remember the update number but it was the one that was pulled. Every since then I can only get 4g when I am in a prime area outdoors near a tower. This makes the phone almost worthless to me because I use it to play an online game and surf the internet at work, not to mention I no longer have a backup connection for my PC... without 4G I might as well be using a cheap flip phone. I have 3 S3's on my account and they all show this same behavior change.
I have tried changing the sim card.. flashing many different radios and am currently running Jelly Beans build 15 ROM to see if a different ROM might help. (I am rooted and unlocked) So far nothing has helped.. I have also tried having my SIM reprovisioned.
I ran across this thread http://forum.xda-developers.com/showthread.php?t=1530203 in the HTC forums discussing hardware antenna mods and even some success claimed and was wondering if anybody has experimented with this with the S3??? I have already had the phone apart looking for ideas but I am afraid this is out of my league without some assistance.
Also while sitting in the house I still get good reception based on DBM, currently at 82 as I type this with only a 3G signal and even drops to 1x on occasion, So what is the deal with being able to get 4g outdoors with a lesser signal while only 3G while indoors?? Toggling airplane mode and other tricks I have tried will not get me 4g indoors.
Now... if it came down to it can I give my current phones a try on AT&T to see if that helps anything? Also does anybody remember what radio firmware we where on before the OTA of death?? I may have missed a radio or two in my testing,
Any advice, opinions, suggestions... any input is appreciated. I am somewhat OCD so I will not rest until I resolve this issue or switch carriers.
Thanks in advance.
OK I don't know if I missed it but do you have a custom recovery ? If so flash a different radio and see which does your phone like . invisiblek has all in one packages that are easily flashable . charge your phone and don't interrupt the process . try md3 radio .
jmichaels1982 said:
OK I don't know if I missed it but do you have a custom recovery ? If so flash a different radio and see which does your phone like . invisiblek has all in one packages that are easily flashable . charge your phone and don't interrupt the process . try md3 radio .
Click to expand...
Click to collapse
Been down the list and installed them all last night... took me hours because I wanted to test each radio for a few min before trying the next. Just got off the phone with verizon and samsung 3 way call, samsung will repair the phones if I send them in, but I would be without phones for about 2 weeks,,, damn.
Update.. don't know if it will help but I filed an FCC complaint. Don't know how well it will work but Sprint bent over backwards over FCC complaints.
Which firmware package are you using. Mf1 was the one sent out to fix md3 or whatever that botched one was. Mb1 was the one before that I think. Just flash the mb1 firmware. You can also flash the mf1 firmware. Filing a FCC complaint is a bit extreme for something you can fix by flashing a new firmware package.
Sent from my GT-P5113 using xda premium
bbqsfire said:
Which firmware package are you using. Mf1 was the one sent out to fix md3 or whatever that botched one was. Mb1 was the one before that I think. Just flash the mb1 firmware. You can also flash the mf1 firmware. Filing a FCC complaint is a bit extreme for something you can fix by flashing a new firmware package.
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
I am currently using MB1 along with the associated rpms on the jelly beans rom. MF1 never solved anything for me, except reduce the overheating and battery life a little. All 3 of my phones are pretty much garbage now. From what I am hearing the bad update put some phones in a non repairable status.
A possibly unrelated issue is that my phones seem to be a different version than most.... I have watched many S3 teardown videos... and in every one a small screw was used to hold the sim card/sd card slot into place. My phone has no such screw nor a place to put one... the assembly just snaps into place and is held in by the surrounding hardware. I think I may have a very early release of the phones.. all 3 are 32 gig models and from what I understand they didn't sell very well on verizon, last time I checked they had quit even listing the 32 gig option.
I have tried to exhaust all options before complaining to the FCC. One thing I would like to play with some more is APN values but have had very little luck because it always reverts back to the same APN and if I try to force anything I get no data at all.
I am also willing to void the warranty one one phone by trying internal antenna mods but I cant do this alone and there seems to be nobody here that has tried it . At the very least the wifi antenna looks easy to mod... just spiral some copper wire around it and spay it with some kind of non conductive coating should help a little. and that ridiculous thermal pad to keep the cpu cool should be trashed and replaced with copper shims and quality thermal paste.
While there is not a lot of room inside for modding I think we could make some small changes that will help.
With the lack of phone hardware modding support on cell phones in general I will probably jump ship to a S4 since it comes in a 32 gig flavor..and I intend on trying an AT&T sim in the phone to see how it performs there.
My wifes phone that has never been modded/rooted/unlock and is on the latest update is much worse than mine... she is stuck in 1x mode most of the time and cant even download her voicemail without a long struggle.
We are in a prime LTE area so there is no excuse for this.
My Mf1 firmware actually gave me more bars and a faster connection. That is to bad it messed up your lte.
Sent from my GT-P5113 using xda premium
Okay, so I know this phone doesn't exactly win the spec war, but it's awesome and would make a fantastic rooted phone. Unfortunately there isn't a forum here on XDA for the device (either because it's too new or there isn't a demand for it)
Do you guys think a forum will be made for this device? It'd be nice to at least have a place to say what root methods DON'T work (I've tried a few)
Thanks for the help, XDA rules!
I second this. I am planning on buying a new phone and after researching numerous phones out there based on my tastes and constraints, I think this phone works very well (another is Samsung Galaxy Exhibit 2). One flaw that I heard is the amount of storage in this phone is around 4gb. Without a way to put apps on an external SD card (which I believe would require a custom ROM), the storage would probably fill up pretty quickly. So it'll be great if XDA opened a forum for this phone.
As a side note if anyone can point to other devices that fit my needs I would be grateful:
- Less than 4.2" screen (preferably 4").
- Android only
I don't have any financial constraints or any favorite companies.
Thanks!
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
bbradf44 said:
What root method did you find worked? Did you try framaroot? Also have you found any Roms?
Sent from my SPH-D710VMUB using Tapatalk 2
Click to expand...
Click to collapse
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
habitforming said:
I used Motochopper, worked like a charm. make sure you have the LG Optimus f3 drivers on your computer.(found on LG website)
Click to expand...
Click to collapse
Ratified. Motochopper worked flawlessly for me as well.
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
wolfu11 said:
richardpwnsner said:
Ratified. Motochopper worked flawlessly for me as well.[/QUOT
Anyone find a tethering ap that works?
Click to expand...
Click to collapse
Do tethering apps need to be phone specific? I don't have data, but I'll let you know if I come across one.
Click to expand...
Click to collapse
Bad news
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
inyourface09 said:
I have created the recovery tree, and have created a recovery.img for this phone. ok now heres the bad news OUR lg optimus f3 has a stock 3.4 kernel with a locked bootloader. Even worse news is that 3.4 "locking" features a sha5 hash system for its image/partitions (recovery, boot, and bootloader). Even worse news there is no known (or atleast what i know or have heard) way to get around this. The phone will be forever locked until lg updates or allows said lock to be removed. I have flashed the recovery and have had no damage to my device but it just sticks at "unsecure recovery" and does a hard reset (factory restore) every time i try to play with it which is a huge flaw if you ask me.
I have hexedited the bootloader and found that there is indeed "juicy" strings within that may tell to a future unlock these strings being
-Device UnLock!, so Boot Success!!
-oem unlock
-ERROR: Could not do normal boot. Reverting to fastboot mode
Also these strings could just be defualt with all lg bootloaders meaning....there is no hope.
My phone is without a soul and I will never be buy lg again.
If anyone is able to get into fastboot
1. PM ME
2. run : fastboot oem unlock
Again root for this phone works great as long as you dont touch recovery, bootloader, or boot partitions
Click to expand...
Click to collapse
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
richardpwnsner said:
Ugh. Thanks for the work. This is bad news indeed. I'll keep poking around and let you know if I find anything.
Click to expand...
Click to collapse
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Will motochopper work on any carrier version of this phone? Thanks!
jjfad said:
Will motochopper work on any carrier version of this phone? Thanks!
Click to expand...
Click to collapse
I've seen confirmations on three carriers (can't remember which ones off the top of my head, sorry [edit-well, T-Mobile and Virgin Mobile come to mind now]), so I'd assume the answer is yes. Regardless, I have yet to see anyone complain about adverse affects, so no reason not to try (though, grain of salt—I'm brand new to android).
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Steve5400 said:
For anyone that has this, how are the antennas on this phone?
I just ordered one from tmo and am hoping to get better reception at my house than from my Samsung or HTC.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
They seem better and with WIFI calling built in the phone hasn't skipped a beat.
Check my way!
http://forum.xda-developers.com/showthread.php?t=2420178&highlight=rooting+lg+optimus+f3
I failed rooting my phone with Windows system, maybe cause I'm not familiar with the process or I was just to lazy, but it does work if you use motochopper. Try looking it up youtube. You could try my method, it should work on Jellybean 4.1.2!
richardpwnsner said:
Out of curiosity, any chance Loki would work? I'd be willing to give it a go if there's a decent chance—still within the 14 day exchange window .
Click to expand...
Click to collapse
BAHAHA me to man i think im down to 10 days. Im trying to get some attention but i need someone who knows little endian, and their way around bootloaders. Id be willing to donate to someone who can help me out, also to support the other 3 variants (if the aboot differs).
I have a recovery created also and a device tree (needs gpio support for kernel).
And to awnser your question, yes loki will work IF i can get the needed values so that when recovery/boot is read into memory that it overwrites the security check feature in aboot. If the wrong values are give you may end up with a brick (very slim chance)
My return window just closed . If it helps, you can pull the open source from LG's website and merge it with the android source. I also discovered an even easier solution: set up the LG Sync application, and select the "upgrade recovery option". Then, when it begins downloading, remove your phone, set Windows (or your relevant OS) to show hidden files and folders, and go the the Program Data folder. There should be something like "PHONEAX" under the LG Electronics folder that will contain the full stock kdz file when the download is complete.
It's really kind of surprising that there's absolutely no dev love out there for the F3. I suppose it's because the phone is entry level, but it's really not that bad but for the storage. I got it as a gift, so no complaints here—of course, if anyone wants to donate a Note or Galaxy gratis, I suppose I'd be willing to switch .
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
yutzyscott said:
I had a Galaxy S4 from Verizon. I switched to T-Mobile Because believe it or not the network is stronger where I work. Also, there pricing on plans cannot be beat. But, I digress. The Galaxy S4 being a Verizon device never really functioned the way it was supposed to on T-Mobiles network. It was unlocked however was still useless for 4G LTE and while I could do better than edge in some places, those places were few and far between. I started to assess what it is I actually used my phone for these days. I'm not into modding with custom ROMS and kernels anymore and I'm not much of a multi-tasker either so I decided that I did not need the super power device anymore. The specs on this phone are perfect for what I need my phone to do. Its been a long time since I have gone beyond rooting to remove bloat and tether. I agree that the storage on this sucks. I don't understand why there are any devices anymore that come with less than 32gb internal. storage is the cheapest thing that can be added to a device and its not as though it uses much physical space. other than the storage I will say that I am impressed with the quality of this device and I don't know that I would even put this as low as "entry level device." I would say its more of a mid-grade device. I am also happy with the reception on this device and its nice to have a compact phone again that actually fits comfortably in my hand and on my belt.
Click to expand...
Click to collapse
No argument here. I like it well enough, but I'm (1) a closet geek; and (2) a heavy multitasker, so given the option I'd prefer something with more screen space (I just graduated from law school, so I do a lot of reading on the go). As a phone, however, you really couldn't ask for more—the size otherwise pretty much perfect, it's relatively snappy with most applications, and once debloated the stock launcher is pretty good.
That being said, the second I see a safe way to deal with the bootloader pop up, I'm diving in, no question .
Decided to share my home screens.
Sent from my LG-P659 using XDA Premium 4 mobile app