Hi,
Form some month, I was usingthis rom on my htc touch pro2: RUU_Rhodium_S2_HTC_FRA_2.07.406.1_Radio_Rhodium_4.49.25.91_Signed_Ship
Thanks to this web xda helping me to install this rom instead of the one comming with my orange (french mobil phone operator).
Then, due to personnal reason I had to re-install an old rom from my operator:
_HTC Touch Pro2_WM6.5_RUU_Rhodium_S_Orange_FR-B2B_1.90.73.1_Radio_Rhodium_4.49.25.17_Signed_Ship
Untill this point, I did not get any trouble.
But this morning i tryed to install the Energy Rom:
|RHODCMDA|.¸¸.·´¯`·.¸¸.- Energy -.¸¸.·´¯ * |Sep 29| 21916|21680 * Sense 2018
(forum.ppcgeeks.com/cdma-tp2-upgrades/86489-rhodcmda-energy-sep-29-21916-21680-sense-2018-a.html)
At the first reboot, my phone freezed at the screen showing the release installed:
B 80
R 4.49.25.17
P 61.44tc.25.32u
D Energy
As my phone is not detected any more by my computer, I can't do anything.
I'm looking if there is someting usefull in the xda-tools.
I found a thread name "unlock, flash and even relock your TP via the SD card!", i will investigate on it.
To help me, don't you have any ideas that can help me?
Is there any hope ?
Thx
Akaiah.
PS.
relocate my post if he is not at the right place.
Just hold voldown key while resetting your phone and flash new ROM, preferably the stock one .
Yep, upgrade from sd-card worked perfectly.
As a reminder:
- choose the rom you want to install.
- extract the .nbh file from the rom.
- rename this file into "RHODIMG.NBH" and place it at root on your sd-card.
- Soft-reset your htc TP2 while pressing "power" and "VolDown".
You will get the nice red/green/blue screen (keep pressing) then, a grey screen asking you if you wanna install RHODIMG.nbh.
- release both buttons and press "power", to install
- or press "volDown" to cancel .
Every thing is right now.
Thanks
Akaiah.
PS.
Any idea why Energy rom did not work for me ?
akaiah said:
Untill this point, I did not get any trouble.
But this morning i tryed to install the Energy Rom:
|RHODCMDA|.¸¸.·´¯`·.¸¸.- Energy -.¸¸.·´¯ * |Sep 29| 21916|21680 * Sense 2018
(forum.ppcgeeks.com/cdma-tp2-upgrades/86489-rhodcmda-energy-sep-29-21916-21680-sense-2018-a.html)
At the first reboot, my phone freezed at the screen showing the release installed:
B 80
R 4.49.25.17
P 61.44tc.25.32u
D Energy
As my phone is not detected any more by my computer, I can't do anything.
I'm looking if there is someting usefull in the xda-tools.
I found a thread name "unlock, flash and even relock your TP via the SD card!", i will investigate on it.
To help me, don't you have any ideas that can help me?
Is there any hope ?
Thx
Akaiah.
PS.
relocate my post if he is not at the right place.
Click to expand...
Click to collapse
I believe Orange France is a GSM network and you tried to install a CDMA ROM. Go here for the GSM version of the Energy ROM.
Good luck.
So,
First, sorry...
I stressed for nothing and opened this thread without realy reading the forums and searching for answer to my problem.
All the answers are on the forum, I should have done a more research before posting.
About CDMA/GSM: my tp2 is a RHOD100 -> GSM (according to different thread).
I will try the gms version of Energy.
Thanks.
Akaiah.
akaiah said:
So,
First, sorry...
I stressed for nothing and opened this thread without realy reading the forums and searching for answer to my problem.
All the answers are on the forum, I should have done a more research before posting.
About CDMA/GSM: my tp2 is a RHOD100 -> GSM (according to different thread).
I will try the gms version of Energy.
Thanks.
Akaiah.
Click to expand...
Click to collapse
I think you'll enjoy it. I use the 21680 CHT and am quite pleased with it.
The thread I linked to in my last post is full of great info. Please read the first several pages, as they have the answers to 90% of the questions that come up. If not, a search will usually turn up a solution. And, lastly, there are many great members to help if needed.
Enjoy...
AGPS Patch Wildfire S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!
Dude i have question about the Patch
1st i already done this on my Wildfire S : http://forum.xda-developers.com/showthread.php?t=1239713
Im with the Latest Stock EU 2.3.5 ROM and i must to tell you
that after i donte this gps.conf file now when u turn on my GPS even from cold start i need 2 to 5 seconds to Lock the Satelites
But i saw just your pach now and wondering to try it too.
So what does the patch do exactly?
And can you tell me witch one to install i mean will be better for me and my stock ROM?
Thank you in advance!
P.S Now im cheking what is writen inside your gps.conf file if you need i can give you mine i don`t know do is posible the GPS to lock for 1 seconds but im sure that my gps.config work because im using GPS all the time and befor to edit it i waiting 3 times more for satelites. this is why im interesting in your pach too
tsalta said:
Dude i have question about the Patch
1st i already done this on my Wildfire S : http://forum.xda-developers.com/showthread.php?t=1239713
Im with the Latest Stock EU 2.3.5 ROM and i must to tell you
that after i donte this gps.conf file now when u turn on my GPS even from cold start i need 2 to 5 seconds to Lock the Satelites
But i saw just your pach now and wondering to try it too.
So what does the patch do exactly?
And can you tell me witch one to install i mean will be better for me and my stock ROM?
Thank you in advance!
Click to expand...
Click to collapse
Good question. First, that user used my work as a base for his article. I spoke with him on that because no credit was given. Apparently, someone else gave him my work and my explanations to be a basis and didn't inform him that it was verbatim something I said.
However, my patch does more than what is discussed there especially if you choose the 3.x trunk. The reliance on NTP.ORG is not the most prudent choice. So, I created my own centrally controlled DNS pool for NTP servers that have proven to be reliable across cellular networks. NTP.ORG pools thousands of servers that do not always have the best networking transmissions. This causes issues to phones who are served that NTP server by NTP.ORG.
Next, v3.x uses my own centrally maintained xtra.bin file. My server and its mirrors have proven to provide users with that data file much faster than Qualcomm servers. Further, we use a series of scripts to ensure that we are serving the most reliable file. Sometimes, Qualcomm files aren't reliable enough for our tastes. We replace it with a custom file when Qualcomm falls below a minimal reliance threshold.
Literally, a large number of ROM developers bake this into their ROMs on already supported devices. From that, thousands of users operate with this patch daily. My servers are sending xtra.bin files and NTP server information constantly.
I always recommend the "Google Build" to all users. Most ROM dev's use the 3.1 Google Build in their ROM's at this time. Other builds are available for those who want Network specific options.
The alternate build is for those who have an old Qualcomm GPS chipset that cannot handle particular data processing. This resolves that problem.
My GPS is working good but I'll test this tomorrow out of curiosity.
I stumbled upon your thread a couple of weeks ago and posted a link to it in a GPS thread for wildfire s, just never got round to trying it.
Thanks.
intel007 said:
My GPS is working good but I'll test this tomorrow out of curiosity.
I stumbled upon your thread a couple of weeks ago and posted a link to it in a GPS thread for wildfire s, just never got round to trying it.
Thanks.
Click to expand...
Click to collapse
Let me know how it goes. I'm looking forward to supporting more devices officially. Right now, I'm on target to do official support for 7 more devices including this one if all goes well.
crypted said:
Good question. First, that user used my work as a base for his article. I spoke with him on that because no credit was given. Apparently, someone else gave him my work and my explanations to be a basis and didn't inform him that it was verbatim something I said.
However, my patch does more than what is discussed there especially if you choose the 3.x trunk. The reliance on NTP.ORG is not the most prudent choice. So, I created my own centrally controlled DNS pool for NTP servers that have proven to be reliable across cellular networks. NTP.ORG pools thousands of servers that do not always have the best networking transmissions. This causes issues to phones who are served that NTP server by NTP.ORG.
Next, v3.x uses my own centrally maintained xtra.bin file. My server and its mirrors have proven to provide users with that data file much faster than Qualcomm servers. Further, we use a series of scripts to ensure that we are serving the most reliable file. Sometimes, Qualcomm files aren't reliable enough for our tastes. We replace it with a custom file when Qualcomm falls below a minimal reliance threshold.
Literally, a large number of ROM developers bake this into their ROMs on already supported devices. From that, thousands of users operate with this patch daily. My servers are sending xtra.bin files and NTP server information constantly.
I always recommend the "Google Build" to all users. Most ROM dev's use the 3.1 Google Build in their ROM's at this time. Other builds are available for those who want Network specific options.
The alternate build is for those who have an old Qualcomm GPS chipset that cannot handle particular data processing. This resolves that problem.
Click to expand...
Click to collapse
OKay thank you i already install Patch 3 Google you recomend will chek and will see how its working and will write a coment here
TEST: I install the Google one that you recomend And i test it outsite from cold Start what i mean is just restart the device and RUN the GPS after 6-7 Seconds IS done and what i saw i have Locked 11 Satelites this is alot i think.
So this is when i run the GPS for 1st time after sistem rebot
After this if i run it again there is not time to lock the satelites i mean the satelites are lock for 1-2 seconds almost imideately after run the GPS
So im guessing your pach is working Because the result is cool and 11 Satelites is serious
How fast received data is "expiring" ? I'm asking this because my phone rarely has internet connectivity while using gps (mobile internet disabled).
__DS__ said:
How fast received data is "expiring" ? I'm asking this because my phone rarely has internet connectivity while using gps (mobile internet disabled).
Click to expand...
Click to collapse
The xtra.bin data files upon creation are valid for 24 hours. The least amount of time from my server (v3.x uses it) is 23 hours if you download it right before rebuilds.
Version 3.1 flashable works great on the marvelc.
Sent from my HTC_A510c
Hello Bigchillin what file and method did you use for our version of the phone i am running S-off rooted 2.3.4 insink71Marvelc rom
Turtlejoe22 said:
Hello Bigchillin what file and method did you use for our version of the phone i am running S-off rooted 2.3.4 insink71Marvelc rom
Click to expand...
Click to collapse
If you want to give it a try before you hear a response from him, I'd start off with the v3.1 Google build. That is used almost all the time. It's also the version ROM dev's include in the ROM's that do include this patch.
But what method should i use ??
Turtlejoe22 said:
But what method should i use ??
Click to expand...
Click to collapse
I prefer flashing the file from my SD card in recovery mode.
Sent from my Desire HD using XDA App
btw, where downloaded file stored in phone filesystem ?
__DS__ said:
btw, where downloaded file stored in phone filesystem ?
Click to expand...
Click to collapse
It depends on what files you are discussing. Do you mean the files that the patch flashes? If so, it flashes gps.conf and suplrootcert to your /system/etc/ directory.
I used the version 3.x trunk cwm flashable zip. Just download and flash just like any other zip.
Sent from my HTC_A510c using Tapatalk
crypted said:
It depends on what files you are discussing. Do you mean the files that the patch flashes? If so, it flashes gps.conf and suplrootcert to your /system/etc/ directory.
Click to expand...
Click to collapse
No, downloaded file with gps info.
__DS__ said:
No, downloaded file with gps info.
Click to expand...
Click to collapse
Good question. In theory, it should be downloaded and stored in /data/ but that never happens. The daemon, gpsd, is in charge of downloading and parsing it. Various configurations operate differently. I would imagine yours downloads, parses, and stores it as data within its general gps temp files containing operative information.
Sorry I cannot be more specific at this point. My work focuses on better retrieval of information, time, and enabling extra variables which permit faster processing of the GPS data.
I haven't played with the internal guts and libs of the GPS system itself. I have found the internal structure is fine as it is based on our work thus far; the problem for many of us lies in the gps.conf configuration and latency for data downloads.
I install it via the ADB push i think this is even more easy because no need to put the file in the storage card then go in recovery and flash it etc
Its simple download just the ADB conect the device run the bat press 3 or whatever you want hit enter and you are ready then will ask you for rebot its a job for a seconds super easy so i flash it like this
Dear Denizens of XDA!
I've finally fixed my phone upon giving up hope a few months ago. In short points, here is my story:
Installed Freedom.apk (by-pass in-app purchases)
Updated to the latest firmware without removing apk
Could no longer connect to official Google servers (ie playstore, gmail) BUT internet worked
Went to LG for quote on fix, stated that I need to replace motherboard ($250)
Gave up for months until TODAY.
Disclaimers:
I did not develop any of these programs but merely stumbled upon them. I do hope that this solution works for you but I cannot guarantee anything.
Do these at your OWN risk. I cannot and will not be held liable for any further damages caused by following my steps.
My phone:
LG G3 D855K from Telstra August 2014.
(crappy) 2GB ram, 16GB storage model.
Resources:
[Link 1] http://xdafirmware.com/drivers/Download/LG/LG-Mobile-Driver_v3.13.2.zip
[Link 2] http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG+Flash+Tool+2014.zip
[Link 3] http://devtester.ro/projects/lg-firmwares-country.php?country=Australia
I'll give special thanks to these people; I did NOT receive any consult or speak to them but they have provided the tools in which I used to fix my LG G3 which would no longer connect to the Playstore and other important Google services. Many thanks to:
- quangnhut123 (http://forum.xda-developers.com/member.php?u=2181463)
- http://ro.linkedin.com/in/ipetcu/ (website: DEVTESTER.RO)
'How I did it':
1 - Download and install the LG USB drivers from [Link 1]
2 - Download and extract [Link 2]
3 - Download your relevant LG G3 Firmware from [Link 3]! Type in your IMEI code to find the exact software/firmware that you require.
4 - Copy the downloaded .kdz file (should be ~1GB) into the same folder as the [Link 2].
5 - https://www.dropbox.com/s/19z8yubtt9qldrh/Steps_part1.PNG
6 - https://www.dropbox.com/s/vjdhthyhne50w0t/Steps_part2.PNG
7 - https://www.dropbox.com/s/1f9rkqq32pxncgv/Steps_part3.PNG
7.5 - Please note that the language settings are not necessary. I've simply set it to English so I could read the messages/notifications.
8 - LG Software will pop-up again and let it do its own thing.
9 - An error message of Server couldn't be connected or something of the like will appear. Do NOT press exit.
10 - Look at your phone and you'll see that the firmware updating logo/downloading.
11 - Once your phone reaches 100%, the program on the computer may freeze and be required to be shut down. (This is okay once it's complete).
12 - Allow your phone to reboot, this may take 5-10 minutes.
13 - You'll get the applications being optimized.
14 - Just before you press start the phone may reboot, that's fine as well.
15 - Enjoy!
If you have any issues with the actual flash tool software, please check the 64-page thread AND use the search bar.
http://forum.xda-developers.com/showthread.php?t=2797190
Unfortunately, I did not expect this to work for me so I do not have any video footage of me actually attempting this procedure.
If you have any other questions or queries please do leave a comment below. I am not an avid user of XDA but will try and respond when I can do so.
Worked? Thank me? (Sorry if I'm optimistic!)
The only thanks I would like to receive if this works is if you can download the firmware from [Link 3], keep a backup, and re-upload it somewhere to share with other users in need.
If you do decide to re-upload, please do keep the details of the firmware.
I hope that this solution does work for you.
And one final reminder that if you do copy what I did, you proceed to do so at your own risk.
Good luck.
I know this is a couple of months old but wanted to say thanks for posting this - had a G3 stuck on the firmware update screen, couldn't boot into download mode etc... Took a while searching and installing about 26 different flash tools but finally this method worked. Cheers!
lowfields said:
I know this is a couple of months old but wanted to say thanks for posting this - had a G3 stuck on the firmware update screen, couldn't boot into download mode etc... Took a while searching and installing about 26 different flash tools but finally this method worked. Cheers!
Click to expand...
Click to collapse
And I know I'm pretty late to reply but I'm glad it helped you as well.
I did the same thing as you and took me a while of researching to find a solution. Albeit I've now jumped ships and no longer own the LG G3.
Good luck for the future
KDZ at DevTester
Hi ...
Was anyone able to download de KDZ files for LG-D855K (any version) lately?
Is so, have you used a Download manager or not? Which Download provider?
I can't reach csmgdl.lgmobile.com
Dude. I live in Indonesia. I can't reach csmgdl.lgmobile.com. It would great appreciate if someone can mirror this link http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW060506432109876543213/D855K10H_00.kdz.
My phone can't connect wifi and mobile cellular. After flash Marshmallow Global Firmware D855.
thanks
Download Manager for KDZ Files
otavio_aon said:
Hi ...
Was anyone able to download de KDZ files for LG-D855K (any version) lately?
Is so, have you used a Download manager or not? Which Download provider?
Click to expand...
Click to collapse
I discovered that this site (LG Mobile) is, in fact, not responding properly to the browser file request ... but the files are there.
I used Xtreme Download Manager to download it. Just manually input the desired file link ... and it'll do its magic!
Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
jenningsthecat said:
Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
Click to expand...
Click to collapse
Doh! I solved the problem myself by watching a YouTube video. The LineageOS directions are correct but a bit confusing - the video clarified the procedure by showing someone doing it with phone in hand and computer connected. Case closed!
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Giropedal said:
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Click to expand...
Click to collapse
Sure! The video is here:
. There are no verbal instructions - the soundtrack is just music. As I watched the video I was pausing it and following the written instructions on the LineageOS site: https://wiki.lineageos.org/devices/a5y17lte/install. I forget what it was now that I had missed, but the combination of the video and the instructions got me sorted out. Good luck! And if you you find an earlier version of LineageOS for the A5 2017 please post it. My phone works great, but I find Oreo really annoying and I'd like to install a more sensible version.