Develop Bugs

Looking for a ROM

Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.

xelasha said:
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
Click to expand...
Click to collapse
From one newbie to another, you should read the sticky posts... they are full guides and information about flashing your phone's ROM / Radio etc.
The forum 'Search' facility is your friend, it like's to be used. That's what I did and found all I needed to know about the available ROM's and Flashing process without having to ask a single question.

The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon (in Mac OS X 10.2 and higher, this was replaced with a silhouette of the Apple logo on a blank gray screen) suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
rajas
new rom

AGPS Patch Wildfire S 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

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

[XAP] WP7 Root Tools 1.2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download here: www.wp7roottools.com
NEW: WP7 Root Tools 1.2 is released! It includes an Accent Color editor and Internet Sharing unlock now.
WP7 Root Tools
With this tool you get root-access to your WP7 device. The current version contains the Policy Unlock Installer, a registry-editor, a file-explorer with many file-operations, certificate-stores, a policy-editor, a tweaks-section and an Accent color editor. This is your all-in-one system-tool for Windows Phone 7.
If you like this app, you can donate to buy me a beer (or two).
With WP7 Root Tools I attempt to open up the system in a gentle way, so that users stay in control of their device, while homebrew apps can get more control to get the maximum power out of your Windows Phone device!
Supported Devices
Samsung first and second generation devices with Interop Unlock
LG devices
HTC first generation devices with Mango v1 drivers (SPL 4.x or lower)
Samsung first generation devices with custom ROM and Full Unlock
HTC first and second generation devices with custom ROM and Full Unlock
NOKIA devices with custom ROM and Full Unlock
Your phone needs to have at least INTEROP-UNLOCK. If you get error 0x81030120 when you deploy WP7 Root Tools to your device, then please read this guide! WP7 Root Tools will also work on devices with Full Unlock. If you want to know more about the different types of unlocks or if you want to know why WP7 Root Tools may or may not run on your WP7 device, you should read this guide.
License Agreement
WP7 Root Tools and WP7 Root Tools SDK are Copyright by Heathcliff74 / www.wp7roottools.com in 2012 - 2013
This license governs use of the "WP7 Root Tools" software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
You are free to redistribute the software, as long as the copyright, conditions and disclaimer of this license are present whenever you distribute any portion of the software.
The software is licensed "as-is". You bear the risk of using it. The developer gives no express warranties, guarantees or conditions. To the extent permitted under your local laws, the developer excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
Redistributions of the copyrighted software may not be sold, nor may they be used in a commercial product or activity without first obtaining explicit permission of the developer.
Don't be stupid, make a backup!!
This tool is still in alpha stage. That means not yet properly tested. This tool also provides you with high privileges with which you can alter low level settings and data on this device. All this may result in unexpected and undesired behavior, which may ultimately damage your device. Use this tool with care and use it at your own risk. The developer of this tool cannot be hold responsible for any kind of damages, caused directly or indirectly by using this tool.
You can find backup-programs here on XDA. For example WP7 Easy Backup Tool by MarcHoover or WP7 Backup App by hx4700 Killer.
Installation
On devices with custom ROM and Full Unlock, the installation of WP7 Root Tools will be pretty straight-forward. You install the XAP and it works. On devices with stock ROM's WP7 Root Tools need to install Root Access. The first time it runs, a 2-phase-installation will start. The app will inform you to start the first install-phase. Then the device will reboot after a few seconds. After the reboot you need to start WP7 Root Tools again immediately! Then the second phase of the installation will start and your device will be rebooted again. After the second reboot you are ready to use WP7 Root Tools.
Update to a new version
If you have an earlier version of WP7 Root Tools installed and you have WP7 Root Tools Policy Unlock, I strongly advise to UPDATE the app, instead of doing a full install-cycle. Many XAP installers will do a full install-cycle. That can lead to problems, because during the installation WP7 Root Tools will temporary loose its Root Access. In that case WP7 Root Tools needs to do the 2-phase-installation again. This is usually not a problem, but future OEM- or OS-updates could make it possible that the reinstall will not be possible. So, to be on the safe side, first make a backup of the device (use a backup tool from the XDA forums) and then use a XAP installer that has the possibility to update an app. One such utility is XAPDeployX 0.9.
Registry Editor
The registry editor in WP7 Root Tools allows full Root Access to the registry. Be very careful with your tweaks, because this may profoundly influence the behavior of your device.
To delete a registrykey or -value you can tap-and-hold the item and choose delete in the context-menu.
The new version also has Advanced Search functionality.
File Explorer
The file-explorer supports all file- and folder-operations, like copying, moving, renaming and deleting files and folders. To select multiple files at once, you can tap an item on the left, which will pop up selection-boxes.
When you select files and folders with the selection-boxes, the file-operations can be chosen from the Applicationbar. It is also possible to tap-and-hold an item and choose the file-operation from the context-menu.
You can tap on an item to launch or open it. It might be necessary to give the app that needs to open the file root-privileges first. The new version of WP7 Root Tools allows you to give Root Access to System Apps like Office Mobile. So if you've given Root Access to Word, you can tap txt-files in any location to open them with Word. The new version will also allow you to give Root Access to Homebrew Native executables. The file-explorer shows whether an executable is "Installed" or "Not installed". If you tap (or tap-and-hold) on an executable that is not yet installed, you can choose to unlock the executable, give Root Access and launch it.
The new version also has Advanced Search functionality.
Certificate Installer
You might wonder why I created a certificate installer, because it is already possible to add certificates. When you email a certificate to yourself and tap that attachment, WP7 will install it. But if you install like this, the certificate will always be installed in the "Root" certificate store. With my certificate installer you can also install in "CA", "My" and "Code Integrity" stores. This may be very useful for hacking attempts. You can install a certificate by browsing to the ".cer" file and tap it. The possibilities for getting a certificate file on your phone will follow below. If you start installing certificates on your phone you should consider making backups in advance. I once experienced Zune going totally bezerk after installing certs. Zune took 100% and lost connection with the phone all the time. Everything was back to normal when I deleted the certs. In this version there is no view on the certificate stores available yet. In a future version you will be able to view the contents of all the certificate store and also uninstall certificates from there.
Certificate Store
You can browse the 4 certificate stores. Tap-and-hold will show a context-menu. You can delete certificates or save them as a .cer file. Be aware that if you delete a certificate you can do severe damage to the system. So, be careful with that!
Policy Editor
The Policy Editor will show a list of all the installed apps. You can use the Policy Editor to give other homebrew app a "trusted" status. With this you will give the app Root Access privileges. So be very careful to which app you give Root Access!! You are responsible for giving access to an app! If you are not sure, read the forums to decide if an app is trust-worthy. The new version will also show System Apps. This is done because for devices that make use of Policy Unlock, it is useful to give Root Access to System apps sometimes. For example to open txt-files outside the My Documents folder.
It is also possible to launch apps from this list, by tapping on the app. But some apps will fail to start from here, because their default task is not configured correctly. This is not an issue in WP7 Root Tools, but those apps were simply not designed to be launched like this. They are listed anyway, because it could be useful to give Root Access to these apps.
Policy Unlock v2 also allows xap-packages with special configs to automatically give unlock Native Homebrew executables when the app is given Root Access. Read more in the "For developers" and "Desktop Sync" sections.
I've been working on unlocking Native Executables for a really long time now. Ever since I started this thread on XDA. I know it has been possible to run native executable using Full Unlock. But Full Unlock is only possible on WP7 devices with unlocked bootloaders. With the introduction of WP7 Root Tools Policy Unlock v2 also devices which have only Interop Unlock can now run these programs! But that was not the only goal. This unlock has become a prestige-project for me. Because I wanted to fully understand and control the WP7 Policy Engine. I now finally succeeded in doing this
So, is Policy Unlock v2 the same as Full Unlock?? No. But almost! Unfortunately, Policy Unlock still doesn't allow you to run Homebrew drivers, like the DFT Bluetooth stack. Later on I will try to apply the Policy Unlock hacks on the drivers too.
Tweaks
WP7 Root Tools adds a few Search-providers for Internet Explorer. You can choose it here. There are some more tweaks to customize your devices. From WP7 Root Tools 1.2 on, there are tweaks for unlocking Internet Sharing and for running Automatic Data Configuration. If your operator has blocked Internet Sharing, WP7 Root Tools can attempt to configure Internet Sharing and bypass the barrier that is installed on the phone. This probably won't work on LG devices, because their drivers don't support Internet Sharing. This unlock is only meant to unlock the operator barrier. Running Automatic Data Configuration can be useful when you switched 3G network and your phone has wrong settings for the data connection or the settings have become otherwise defective. If you have more ideas to add to this page, leave me a note.
Accent Color Editor
Add your own accent colors and select colors in real-time. Fully compatible with WP7.8.
Multi-language
The current version supports 18 languages: English, Dutch, Russian, German, Portuguese, Chinese, Hungarian, Czech, Spanish, Slovak, Polish, Italian, Greek, French. And these languages are available in separate downloads: Turkish, Arabic, Albanian and Serbian. The translations are done by volunteers and some elements by translation-engines. So the translations may not be perfect. Following versions will improve and add more translations.
For developers
I also created an SDK for developers, who can use to profit from Root Access. It provides a way to gain access to the filesystem and the registry (and more) from their managed Silverlight application. No need to worry about COM interop and C++ anymore! The package contains a read-me with short instructions. More details and examples will follow soon here on this site!
The new WP7 Root Tools has Policy Unlock v2 to unlock Homebrew Native Executables. You can do that using the WP7 Root Tools Explorer. But if a developers want to use such binaries in an app, it would be very user-unfriendly if the user needed to unlock these binaries manually. For this purpose I added functionality in the WP7 Root Tools Policy Editor. When an app is give Root Access, it will scan the app for a file called RootAccess.xml. If present, the xml is parsed and the binaries that are listed will automatically be given Root Access too. This is the format for RootAccess.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<RootAccess>
<Executable File="Native\NativeApp.exe" />
<Executable File="Native\NativeWinApp.exe" >
<Destination Path="\Windows\NativeWinApp.exe" />
</Executable>
<Library File="Native\NativeLib.dll" />
<Library File="Native\NativeWinLib.dll" >
<Destination Path="\Windows\NativeWinLib.dll" />
</Library>
</RootAccesss>
Take these notes into account:
The Destination paths are optional
Libraries are signed in Source and Destination
Executables are signed in Source and Destination
Executable gets policies in Source and Destination
File-path-attribute-value is relative to app path
Destination path is absolute
The first app that makes use of this feature is Ultrashot's WMDC Launcher, which can be used for Desktop Sync, as described in the next section. Ultrashot will soon make Opera Mini compatible with Policy Unlock too.
Desktop Sync
Ultrashot has released WMDC Launcher some time ago. Back then it was only possible to use that on devices with Full Unlock. With the introduction of Policy Unlock v2, it is also possible to run the app on devices that are compatible with WP7 Root Tools. Ultrashot has added RootAccess.xml to the xap-package, so the app will automatically be configured when it is given Root Access. Warning: it may take a while to apply on all unlocks, so be patient and let WP7 Root Tools do its job.
After WMDC Launcher is installed, given Root Access and lauched, you can use it to sync file-system and registry with your PC. On the PC you need to have Zune installed and running, and you need to have Windows Mobile Device Center installed and running. After that you Windows Phone will show up as Mobile Device in Windows Explorer.
For unrestricted remote Registry editing you can use Registry Workshop, or similar. In the registry editor you have to connect to the Mobile Device.
Thanks!
Special thanks to these people:
HD2Owner: for a lot of patience, learning me how to make my own test-ROM's.
Ultrashot and Cotulla: for a lot of nice hacking-chat-sessions and exchange of ideas.
CeesHeim: for providing a test-device.
AndrewSh, Ondraster and many others: for moral support.
Thanks to these people for helping with the translations: AndrewSh, HD2Owner, Paulo Santos, Reker Chen, Balcsida, Tukacs Gábor, Pavel "Paulos" Valach, Esteban Reche, David E. Salazar Paris, Brano Grenuš, Budniu, Fabio Di Peri, Chemeng, Alexandre Thouvenin, Orhan Bozkurt, Hassan Selim.
Version history
0.1 - 2011/04/04 - Initial release: only registry-editor
0.2 - 2011/04/13 - Performance improvements and minor fixes
0.3 - 2011/04/14 - Bugfix in registry-editor
0.4 - 2011/06/14 - File browser added
0.5 - 2011/06/24 - File Explorer with basic file operations and certificate installer
0.6 - 2011/09/17 - Compatible with Interop-Unlocked Samsung Mango devices
0.7 - 2011/09/17 - Bugfix in registry-editor
0.8 - 2012/01/02 - Session and Multi-Tasking awareness + Mango UI improvements (better responsiveness)
0.9 - 2012/03/28 - Complete rewrite of the app (many device supported, full root access, policy-editor, etc)
0.10 - 2012/09/02 - Many user interface enhancements, Multi-file operations added, Improved performance in file-explorer, Shell handling added in file-explorer, better error handling and reporting and lots of small bug-fixes.
0.11 - 2012/09/03 - Bug-fixes and better device support.
0.12 - 2012/11/12 - Policy Unlock v2, 16 languages, launch apps from applist, applist also includes all system-apps now, advanced file-system-search, advanced registry-search, certificate Stores, tweaks-section, many bug-fixes and performance improvements.
0.13 - 2012/12/04 - Many bug-fixes and performance-improvements.
1.0 - 2013/01/05 - Bug-fixes and User Interface-improvements.
1.1 - 2013/03/26 - Added Accent Color editor and bug-fixes
1.2 - 2013/05/07 - Added color values to Accent Color editor, improved data-connection speed tweak, added Internet Connection Sharing unlock, added Automatic Data Configuration function, added shell-handler in Explorer for provxml-files, removed wrong buttons on Device tab, disabled cache for filesystem and searches, removed ads for better Root Tools experience

- Reserved -
- Reserved -

I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.

Useless guy said:
I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.
Click to expand...
Click to collapse
Nope, not quite, I am not best to describe the full problem but essentially there's another certstore stored on the device, when phone boots in to update mode it uses that cert store located in the ROM
Sent from my Samsung Focus S using XDA Windows Phone 7 App

These are great things
Thank you my friend

Useless guy said:
I have a question - can I add my cert to store (authority store, though I don't know which) in order to acquire ability to install self-signed cabs? My LG Panther has locked bootloader, so it looks like the only way to update at least to 7004.
Click to expand...
Click to collapse
The answer is: I'm not sure. It is not possible to add certs to a store for updating. But it might be possible to change the file which keeps the certs for cab updating. It needs more research. Some of this has already been discussed here.
Heathcliff74

Really good work......like it .......
Thank you....

Did you missed all trusted ?

djtonka said:
Did you missed all trusted ?
Click to expand...
Click to collapse
I considered implementing that. But I think it is dangerous. If there will ever become some type of malware on WP7, you would be very vulnerable. So I decided not to implement such option.
Heathcliff74

You are the Boss
Does registry expolorer keeps last opened location after restart or reopen cos only File explorer can do this so far?

How to unlock the native code?
I have installed opera mobile but don't work...
Inviato da mio OMNIA 7 usando Board Express Pro

A bug or a normal behavior?
First of all, i would like to really thanks you for this great tool. I would like to just ask some questions:-
I updated my wp7root tool 0.11 using XapHandler, and Everything went ok. After that i needed to open the Office hub but to my surprise it didn't work. I did a soft-reset just to find out that my start screen is Black . To be honest i got panicked though i have an update that i can reinstall. After few mins digging i found out that certain feature in the phone a still working (like search, voice commands etc.) I used the voice command and opened Wp7root Tools 0.12 and went through Policies just to find out that almost every System Apps were untrusted including Start App. When i trusted Start App i got my Start Screen back .
My questions are:-
1. is this (the untrusted start app) a bug?
2. Is it intentional that all the System App to be untrusted? if not
3. Do you have a list of System Apps that were trusted Originally?
Hope you have answers to those q.
Thanks

djtonka said:
You are the Boss
Does registry expolorer keeps last opened location after restart or reopen cos only File explorer can do this so far?
Click to expand...
Click to collapse
Dunno which registry editor you've been using. But my registry-editor does remember its last location.
Jonny Rosworth said:
How to unlock the native code?
I have installed opera mobile but don't work...
Inviato da mio OMNIA 7 usando Board Express Pro
Click to expand...
Click to collapse
Ultrashot is working on that. It needs a little bit of tweaking to be compatible with Policy Unlock.
kurdland said:
First of all, i would like to really thanks you for this great tool. I would like to just ask some questions:-
I updated my wp7root tool 0.11 using XapHandler, and Everything went ok. After that i needed to open the Office hub but to my surprise it didn't work. I did a soft-reset just to find out that my start screen is Black . To be honest i got panicked though i have an update that i can reinstall. After few mins digging i found out that certain feature in the phone a still working (like search, voice commands etc.) I used the voice command and opened Wp7root Tools 0.12 and went through Policies just to find out that almost every System Apps were untrusted including Start App. When i trusted Start App i got my Start Screen back .
My questions are:-
1. is this (the untrusted start app) a bug?
2. Is it intentional that all the System App to be untrusted? if not
3. Do you have a list of System Apps that were trusted Originally?
Hope you have answers to those q.
Thanks
Click to expand...
Click to collapse
Ok. That's remarkable. I have no clear answer. Can you tell me which device and which ROM (stock, custom, ..) you use and which OS version and which OEM firmware?
It sounds to me that this is some form of Inception between Full Unlock and Policy Unlock (that should normally work, but I can't possibly test all different devices and unlock at forehand).
Normally only very few system apps are defined to have Root Access. And "Start" is NOT one of them. I don't have a cleanly installed device to check which apps should have Root Access, but there are really only a few. I don't understand why the Startmenu would need Root Access in your case. And it is not a bug that "Startmenu" is not having Root Access. It actually surprises me that you could fix it this way.
Heathcliff74

Hi Heathcliff74 i´ve the same thing on my rom,i am using the mirolg tangoromhttp://forum.xda-developers.com/showthread.php?t=1751911 and !updated! my old roottools with sending the xap to my email account and downloading it on my device,after update (xap deployer by ultrashoot) i had to give roottools fullacces/trusted permissions for running,as the man obove said,there is nothing of the system marked as trusted(in roottools),but all is running correctly !

Omnia7xdax said:
Hi Heathcliff74 i´ve the same thing on my rom,i am using the mirolg tangoromhttp://forum.xda-developers.com/showthread.php?t=1751911 and !updated! my old roottools with sending the xap to my email account and downloading it on my device,after update (xap deployer by ultrashoot) i had to give roottools fullacces/trusted permissions for running,as the man obove said,there is nothing of the system marked as trusted(in roottools),but all is running correctly !
Click to expand...
Click to collapse
Just to be clear: You do NOT have a problem with missing Startmenu, right?
Because most system apps should NOT have Root Access. If your system apps do NOT have Root Access, but everything works fine, then there is NO problem!

Heathcliff74 said:
Dunno which registry editor you've been using. But my registry-editor does remember its last location.
Ultrashot is working on that. It needs a little bit of tweaking to be compatible with Policy Unlock.
Ok. That's remarkable. I have no clear answer. Can you tell me which device and which ROM (stock, custom, ..) you use and which OS version and which OEM firmware?
It sounds to me that this is some form of Inception between Full Unlock and Policy Unlock (that should normally work, but I can't possibly test all different devices and unlock at forehand).
Normally only very few system apps are defined to have Root Access. And "Start" is NOT one of them. I don't have a cleanly installed device to check which apps should have Root Access, but there are really only a few. I don't understand why the Startmenu would need Root Access in your case. And it is not a bug that "Startmenu" is not having Root Access. It actually surprises me that you could fix it this way.
Heathcliff74
Click to expand...
Click to collapse
Thanks for the quick answer!
Sry i didn't menssion that i have an original HTC ROM, with dev. unlock and introp-unlock installed. My device is HTC HD7, Os version 7.10.8773.98 and OEM firmware 2250.21.51101.
Hope those info will help you. I will try to make a video clip reproducing the event, hopw that will help you even more.
Yours
Omar

kurdland said:
Thanks for the quick answer!
Sry i didn't menssion that i have an original HTC ROM, with dev. unlock and introp-unlock installed. My device is HTC HD7, Os version 7.10.8773.98 and OEM firmware 2250.21.51101.
Hope those info will help you. I will try to make a video clip reproducing the event, hopw that will help you even more.
Yours
Omar
Click to expand...
Click to collapse
Hm. The fact that you have a stock ROM makes this only more weird. I still can't think of a possible explanation.
Did you toggle Root Access for system apps before the problem occurred? Any other remarkable things you've done with your phone that may explain this?
Did you use earlier versions of WP7 Root Tools without problems?

Sry,yes i ahve absolutely no problems,everything works fine,i was only not sure if the systemapps must have no permissions

Heathcliff74 said:
Hm. The fact that you have a stock ROM makes this only more weird. I still can't think of a possible explanation.
Did you toggle Root Access for system apps before the problem occurred? Any other remarkable things you've done with your phone that may explain this?
Did you use earlier versions of WP7 Root Tools without problems?
Click to expand...
Click to collapse
Hi again!
No i didn't toggle it Before the problem. I just installed it then when i tried office, it didn't work and then i found out about the problem. And to be honest i really didn't do anythink remarkable either. My privous experiance with WP7Root Tools and really good, didn't have any problem Before.
Please check your PM i sent you a link to the video clip i did about the problem. OBS!!! No sound
Yours
Omar

Awesome and great job.... Your hard work is very much appreciated!!
WP7 Root Tools v 0.12 alpha updated just fine and is functioning perfectly on my HD7 running Deepshining 7.8.
Thank you!

2175.2907.8858.13030 New firmware available on navifirm

So someone flashed this new rom? What changes? I translated from china lumia 900's forum, here results.
1 used the State Bank 2175.2905.8858.12480 version as mastering.
The 2. Transplantation Lumia900 latest 2175.2907.8858.13030OEM.
3. Latest FULLUNLOCK V4 unlock procedure.
4. Using latest unlocking supporting software the Root rights management, gravity sensor, XAP deployment, file management, WM Device Center, the search key settings and Quick Start 7 software, and all models have added language to facilitate domestic players to use.
5. Supports XBOX game support IE ​​deploy, support for unlimited XAP deployment of PC.
6. Delete multiple languages, or English only reserved yet.
Other registry optimization, debug mode, the default time zone correction.
If you deploy third-party software requires full unlock permission, be sure to set it as a trusted Root rights management, or it may not work properly, no matter what the time, Root permissions to manage the software, you can not delete, or may some other unknown problems. The first time after the start of the Brush to wait a minute or a the Welcome Message pop-up in use. Remember! ! !
http://translate.google.com/translate?hl=ru&sl=auto&tl=en&u=http%3A%2F%2Fwww.wpxap.com%2Fthread-564190-1-1.html
http://www.wpxap.com/thread-564190-1-1.html

2907 is MX (Mexico?) country variant. Anyway works fine for me, better than 2905. Faster and more stable.

2175.2907.8858.13030
wow that's great! downloading!!!!!!!!!!! :fingers-crossed:

Hi there,
can you tell me what's the difference between 12480 and 13030 firmware?
In my custom rom i used the 12480 because it's the latest offical rom for all countrys...
13030 is only for Mexico?
Any recommendations?

Ok, somebody help me out here. I might be stupid. NaviFirm doesn't show this ROM for me. Is there a downloas link on the chinese web page somewhere that I cannot seem to find?

Even the Mecixo one has all languages in.

General Sony Xperia 10 iii Additional LTE/5G Band Unlocks

Hi,
The 10 iii uses the Snapdragon X51 Modem. This modem seems to be in very few phones at the moment, however, the modem is the same on the OnePlus Nord N10 5G and Nokia X20 . Both of these devices are available in the US and contain some additional bands that the 10 iii does not.
With the Xperia 10 iii most likely not receiving a US Customized firmware in the future, is there any path forward with modifying the bands that are available on the modem?
Currently, my progress is as follows...
1. Root the 10 iii with Magisk -​
This is easily done by downloading firmware with XperiFirm, extracting the boot.sin, "unsinning" it to get a boot.img, patching the boot.img with Magisk, and then flashing the modified boot.img with fastboot. To do this, the bootloader must be first unlocked. Simply use the factory method of unlocking the bootloader. Generate a code for the Sony Xperia 10 ii (as the 10 iii isn't listed yet, but the codes are interchangeable, this applies to all iii devices like the 5 and 1, just use the ii codes). Unlocking the bootloader will wipe the device and lose the Sony DRM keys.​​2. Qualcomm QPST Connection -​
Most Qualcomm modems support their QPST application. This diagnostic application allows you to interface with the modem on your phone and change it's parameters. The process to connect to that application involves installing their modem drivers, opening the com port on your pc to connect to your phone, and initiating the connection.​​Here is a guide on setting it up that pertains to the 1 ii, but is relevant to most Sony devices. Note that the "enable Qualcomm diag" step contains a correction for us.....​"setprop persistent.sub.eng 1" should be "setprop persist.usb.eng 1" and installing the drivers (9018, not 9020) on the device in device manager should contain the "MI_00" hardware ID instead.​​3. Digging in to the files​
Here is where my roadblock begins and expertise falls off. The modem contains many xml files that can be edited to set bands, enable data features, etc. Most relevant files appear to be in the "policyman" folder. However, my efforts on actually having any edits make any impact have been a zero sum game. Making changes to the band_set_01 and carrier_policy files seems to make no difference on enabled bands, how it connects to my network (Verizon), etc.​​​​Any one have any ideas or thoughts? Is this path forward even possible?
Below are links to the policyman files that I extracted from the modem. Feel free to download them and view/modify. If other modem files would like to be looked at, just let me know. Most other files seem to be an unknown file format and not easily modified xml.
Here is a copy of the stock 10 iii policyman folder (note my carrier_policy is standard Verizon) - Download
Here is a copy of a modified band_set_01. I basically added all Verizon bands to all rf_band_lists that could be US related.
I have tried various carrier_policy changes. Also attempted to use generic/pre-made ones from other devices that contain more defined rules. Here is an example of one I tried from a OnePlus 9
Thanks!
​​​​

Hi, were you really able to root the phone the way you described? Or is this just the theoretical steps? Because currently it's not even possible to unlock the bootloader on this phone (yet, hopefully) which would forbid the flashing of a modified boot.img as far as I know.
Looks like we'll have to wait some more before anything really moves for this phone.

combinedfleet said:
Hi, were you really able to root the phone the way you described? Or is this just the theoretical steps? Because currently it's not even possible to unlock the bootloader on this phone (yet, hopefully) which would forbid the flashing of a modified boot.img as far as I know.
Looks like we'll have to wait some more before anything really moves for this phone.
Click to expand...
Click to collapse
Yes, the device is able to be rooted normally with Magisk. To unlock the bootloader, just generate a code for a Xperia 10 ii, they work just fine. Note that unlocking the bootloader will wipe the device and lose DRM keys. https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code I have edited the OP to include this step.

I can help you to list all devices supported bands and 4G & 5G combinations if you like to contribute log to cacombos.com/contribute. Qualcomm diag option is best for Sony devices when rooted.
You can't edit firmware defined combinations because these are compiled and signed by Qualcomm. To edit these have to recompile from source and sign. And of course the firmware source is not public and signing keys are very secure.

olkitu said:
I can help you to list all devices supported bands and 4G & 5G combinations if you like to contribute log to cacombos.com/contribute. Qualcomm diag option is best for Sony devices when rooted.
You can't edit firmware defined combinations because these are compiled and signed by Qualcomm. To edit these have to recompile from source and sign. And of course the firmware source is not public and signing keys are very secure.
Click to expand...
Click to collapse
I planned on contributing to your website!
I know I stop logging with ctrl+c, but, is there a limit to amount of qmd1 files that are created per proc_type?
The example on ca combos looks like it moves on to the next proc_type automatically? Below is my current terminal.
Code:
XQ-BT52:/sdcard/diag_logs $ su
ogs -f /sdcard/diag_logs/Diag.cfg -m /sdcard/diag_logs/Diag.cfg <
diag_mdlog: command = o
diag_mdlog: command = f
diag_mdlog: command = m
diag:main: kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
diag: No Session is active for the given mask
diag_mdlog: Closing diag_fd_temp
diag_mdlog: Warning output directory already exists: /sdcard/diag_logs
diag_mdlog: Proceeding...
diag_mdlog: Diag_LSM_Init succeeded.
REMOTE PROCESSOR MASK 0
diag:kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
logging switched
Output dirs /sdcard/diag_logs --- /sdcard/diag_logs
diag: check_for_diagid_cmd DIAG_GET_DIAG_ID
diag_mdlog: Reading mask for MSM, proc_type: 0
Reading the mask file: /sdcard/diag_logs/Diag.cfg
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
creating new file /sdcard/diag_logs/diag_log_20210703_1119471625325587206.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1123011625325781935.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1127191625326039079.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1131261625326286642.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1136221625326582083.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1140061625326806999.qmdl

@olkitu I stopped the logging after about 20 minutes. Submitted the logs to cacombos.

Archerpunk said:
@olkitu I stopped the logging after about 20 minutes. Submitted the logs to cacombos.
Click to expand...
Click to collapse
Got it and now supported combinations of this device listed here: https://cacombos.com/device/XQ-BT52 (HW combos).
During logging seems you have only enabled LTE bands 4 and 5.
This device sold in US? This is global model - same sold in Europe too. Device missing US combinations.
Archerpunk said:
I planned on contributing to your website!
I know I stop logging with ctrl+c, but, is there a limit to amount of qmd1 files that are created per proc_type?
The example on ca combos looks like it moves on to the next proc_type automatically? Below is my current terminal.
Code:
XQ-BT52:/sdcard/diag_logs $ su
ogs -f /sdcard/diag_logs/Diag.cfg -m /sdcard/diag_logs/Diag.cfg <
diag_mdlog: command = o
diag_mdlog: command = f
diag_mdlog: command = m
diag:main: kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
diag: No Session is active for the given mask
diag_mdlog: Closing diag_fd_temp
diag_mdlog: Warning output directory already exists: /sdcard/diag_logs
diag_mdlog: Proceeding...
diag_mdlog: Diag_LSM_Init succeeded.
REMOTE PROCESSOR MASK 0
diag:kernel supported: NUM_PERIPHERALS = 7, DIAG_CON_ALL: 255
logging switched
Output dirs /sdcard/diag_logs --- /sdcard/diag_logs
diag: check_for_diagid_cmd DIAG_GET_DIAG_ID
diag_mdlog: Reading mask for MSM, proc_type: 0
Reading the mask file: /sdcard/diag_logs/Diag.cfg
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
diag: Determining contents of directory /sdcard/diag_logs for circular logging ...
creating new file /sdcard/diag_logs/diag_log_20210703_1119471625325587206.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1123011625325781935.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1127191625326039079.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1131261625326286642.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1136221625326582083.qmdl
creating new file /sdcard/diag_logs/diag_log_20210703_1140061625326806999.qmdl
Click to expand...
Click to collapse
No limits but file size by default max 100MB and then create new one automatically.

olkitu said:
Got it and now supported combinations of this device listed here: https://cacombos.com/device/XQ-BT52 (HW combos).
During logging seems you have only enabled LTE bands 4 and 5.
This device sold in US? This is global model - same sold in Europe too. Device missing US combinations.
No limits but file size by default max 100MB and then create new one automatically.
Click to expand...
Click to collapse
Yes, it appears this device only supports bands 4 and 5 for the Verizon Network.
It isn't sold in US, but is sold globally. Most other regions (EU, Asia, Etc) seem to have specific customized firmware with mostly similar bands.
Is there a way to export all the CA combos in a format for the Carrier Policy?

Archerpunk said:
Yes, it appears this device only supports bands 4 and 5 for the Verizon Network.
It isn't sold in US, but is sold globally. Most other regions (EU, Asia, Etc) seem to have specific customized firmware with mostly similar bands.
Is there a way to export all the CA combos in a format for the Carrier Policy?
Click to expand...
Click to collapse
For now there is no tool to export Qualcomm format out.

Was hoping this thread would bear some fruit because if band difference is a solely software matter these days, rooting should allow us full access to all the features of any damn phone.

Archerpunk said:
Hi,
The 10 iii uses the Snapdragon X51 Modem. This modem seems to be in very few phones at the moment, however, the modem is the same on the OnePlus Nord N10 5G and Nokia X20 . Both of these devices are available in the US and contain some additional bands that the 10 iii does not.
With the Xperia 10 iii most likely not receiving a US Customized firmware in the future, is there any path forward with modifying the bands that are available on the modem?
Currently, my progress is as follows...
1. Root the 10 iii with Magisk -​
This is easily done by downloading firmware with XperiFirm, extracting the boot.sin, "unsinning" it to get a boot.img, patching the boot.img with Magisk, and then flashing the modified boot.img with fastboot. To do this, the bootloader must be first unlocked. Simply use the factory method of unlocking the bootloader. Generate a code for the Sony Xperia 10 ii (as the 10 iii isn't listed yet, but the codes are interchangeable, this applies to all iii devices like the 5 and 1, just use the ii codes). Unlocking the bootloader will wipe the device and lose the Sony DRM keys.​​2. Qualcomm QPST Connection -​
Most Qualcomm modems support their QPST application. This diagnostic application allows you to interface with the modem on your phone and change it's parameters. The process to connect to that application involves installing their modem drivers, opening the com port on your pc to connect to your phone, and initiating the connection.​​Here is a guide on setting it up that pertains to the 1 ii, but is relevant to most Sony devices. Note that the "enable Qualcomm diag" step contains a correction for us.....​"setprop persistent.sub.eng 1" should be "setprop persist.usb.eng 1" and installing the drivers (9018, not 9020) on the device in device manager should contain the "MI_00" hardware ID instead.​​3. Digging in to the files​
Here is where my roadblock begins and expertise falls off. The modem contains many xml files that can be edited to set bands, enable data features, etc. Most relevant files appear to be in the "policyman" folder. However, my efforts on actually having any edits make any impact have been a zero sum game. Making changes to the band_set_01 and carrier_policy files seems to make no difference on enabled bands, how it connects to my network (Verizon), etc.​​​​Any one have any ideas or thoughts? Is this path forward even possible?
Below are links to the policyman files that I extracted from the modem. Feel free to download them and view/modify. If other modem files would like to be looked at, just let me know. Most other files seem to be an unknown file format and not easily modified xml.
Here is a copy of the stock 10 iii policyman folder (note my carrier_policy is standard Verizon) - Download
Here is a copy of a modified band_set_01. I basically added all Verizon bands to all rf_band_lists that could be US related.
I have tried various carrier_policy changes. Also attempted to use generic/pre-made ones from other devices that contain more defined rules. Here is an example of one I tried from a OnePlus 9
Thanks!
​​​​
Click to expand...
Click to collapse
In lte_feature_ca_mcc entries of each operator, you need to edit them and add combinations for your operator