Hi all,
after an hour of mooching through the registry a few caught my eye which im not sure what they do.
they are.....
local machine/hardware/builtin/AXCON
axcondrvr.dll
has priority256 with a dword value of 101 ?????
could this be the g-sensor driver?
___________________________________________
local machines/system/imageupdate/updateapp/
update app
might provide a driver (uldrui.dll) we can use for flashing new images.
_________________________________________________
localmachine/system/simlock/
has one key in it which reads **123456##
numbers will be different i had nines and eights and twos in mine.
i tried it by starting my phone up with a 02 sim instead of orange and put in code.
it beeped with the * and # and didnt display them in the box but took the numbers but wrong password
what could this be for?
also.....................
do we need the pcmcia drivers folder in the registry?
any help appreciated
The simlock code, can we find new lines ( phone company numbers ) to replace this ?
to be honest it may just be a defunct option? i have played around with the registry but each time i had to hard reset and it got annoying in the end.
i would suggest paying someone to unlock your phone for ya as its safer and it works.
if you want to explotre your registry just google for wm6.5 regedit and you should find a remote one so you can edit on your pc rather than the phone screen
Call me a normal boring old user if you like, but I'm determined not to touch the registry on my phone. Too much chance of breaking things.
worst case scenario you have to hard reset your phone. if your not comfy working with the reg then dont lol i guess a 'normal' user would have no need to touch the registry under normal circumstances, but then theres the rest of us who are to nosy for our own good who must rummage through the hundreds of keys and mess with the values just to see hwat happens lol
How you guys going to HKEY ? Need some extra program?
ce300 said:
How you guys going to HKEY ? Need some extra program?
Click to expand...
Click to collapse
I go through total commander, which is a great all around filexplorer it's free and you can also access your registry.
hi all i have been using Bell titan for long time.
I just received Telus TP2 as a gift.
guys i would like to find out its epst code.(tried MSL grabber it does not work)
can some suggest good rom to make it work on bell cdma.
as i understand tp2 supports bell cdma band.
thanks in advance
Not going to happen legally without a meid change
Try this Worked for me
From PPC Geeks
Originally Posted by AycheDub
Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
Check to see that the file \Temp\ATDbg0.txt has been created.
Return the values back to what they were (most likely 0) waiting the same amount of time as above.
Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:
Code:
Tx:AT+HTC_RMSL=0\r
Rx:+HTC_RMSL: 354201\r\n0\r
Tx:AT+HTC_ROTKSL=0\r
Rx:+HTC_ROTKSL: 216112\r\n0\r
The numbers next to the Rx: +HTC_RMSL line should be your MSL. You may see a couple of different instances of this number within the text file - try one, if it doesn't work, try the next. The file ATDbg0.txt will either be in \temp or \ATDbg.
Hope this works for you.
it works
thanks it long process but it worked
arshiv said:
thanks it long process but it worked
Click to expand...
Click to collapse
You're welcome
I was one of the people that did the initial backup methods (telling you how to backup your certificate and rsa keys) or using cat which doesn't actually backup your wimax.img properly. After hours of playing around in a hex editor I finally got my 4g working again, and i'll explain how
****EDIT****
I added a hex converter you can use for your rsa key if you are too lazy to find one on google. I say to use hex instead of text replace because it's safer in regards to \n's
I was too lazy to make a gui for it but its haxt.net/evohex.php?rsa=yourrsa&cert=yourcert [obviously replace it with your 2 values]
Also, don't try to flash this image without editing it. The rsa key is invalid until you put your valid key in!
***********
Note - this won't work for anybody who actually has no idea what their RSA keys/certificate is.
So there are a few things you need first.
1. Your phones wimax mac address (take out your battery and look at the sticker)
2. Your RSA private key
3. Your Certificate
4. The wimax image file template I attached here in the zip
To simplify, use XVI32 freeware hex editor. If you search "BEGIN" you will see begin rsa key and begin certificate. You need to copy these values for later use.
Download the template file and open it in the hex editor.
Our template's mac is 00:18:41:81:8B:5C
Our templates Certificate is :
http://pastebin.com/vEnKFtS8
Our templates RSA Certificate is :
http://pastebin.com/gJbrh3ii
Convert both of these strings to hexidecimal and write them down! (it will look like a bunch of 4D 49 49 44 6B 44 43 43 41 6E 69 67 41 77 49 42 41 67 49 51 5A 4F 75 35 44 5A 4C 55 44 76 44 57 4B 57 2F 36 6D 48 66 4C 4F 54 type stuff)
If you don't know what your rsa key or certificate is, open it up in a unix friendly text editor(on windows i recommend notepad++). Search case sensitive for BEGIN. You will see the begin rsa key and begin certificate. Copy all of the text in between with no spaces or newlines! Now convert these both to hex and write them down.
Hit search -> replace on xvi32, click hex search and paste your converted hex for the templates RSA key.. and then replace with the hex value of YOUR rsa key. Do the same thing for the certificate as well.
The length of our templates rsa key might be different than yours, and your ending file size MUST be the same as your starting file size(the template is 12,582,912 bytes). There are a bunch of null characters in the template after --END KEY--- you might need to add or remove some to correct this! Just click on one and press the delete key if you have to
Now the only thing you have to do is fix your mac. In your new wimax partition file, text search for 00:18:41:81 to Replace that mac with your mac but subtract 1 from the last digit(if your mac was 00:23:76:EC:214 put 00:23:76:EC:213).
Replace the first 2 of the 3 instances with your mac -- minus 1. (If it ends on a letter, B would become A, C would become B, etc.
The last instance of your mac, put the actual mac address with nothing subtracted as it appears on the sticker under your battery.
Once you have saved the file.. name it something like wimax_fixed_resized.img and copy it to your sdcard.
Boot to fastboot and run "fastboot erase wimax"
Reboot to your recovery and adb shell in.
type "mount /sdcard" so you can run flash_image properly.
Run flash_image wimax /sdcard/wimax_fixed_resized.img
(or whatever you named it)
Profit!
One highly recommended addition to this is to use the correct ROM base version while you do this for testing if your wimax restored correctly. Quite often firmware/wimax mismatches will cause things to not auto connect, or various odd issues (true story)
Thanks for writing this up - I was planning on doing it at some point with a full guide on how to backup and restore the whole nine yards, but this will do in the meantime for people who want to restore things.
At first I thought this was for people who had lost their own RSA keys lol.
Great tutorial nonetheless.
haxt said:
I was one of the people that did the initial backup methods (telling you how to backup your certificate and rsa keys) or using cat which doesn't actually backup your wimax.img properly. After hours of playing around in a hex editor I finally got my 4g working again, and i'll explain how
****EDIT****
I added a hex converter you can use for your rsa key if you are too lazy to find one on google. I say to use hex instead of text replace because it's safer in regards to \n's
I was too lazy to make a gui for it but its haxt.net/evohex.php?rsa=yourrsa&cert=yourcert [obviously replace it with your 2 values]
***********
Note - this won't work for anybody who actually has no idea what their RSA keys/certificate is.
So there are a few things you need first.
1. Your phones wimax mac address (take out your battery and look at the sticker)
2. Your RSA private key
3. Your Certificate
4. A wimax.img from an evo that has has an intact wimax partition(borrow a friends nandroid backup).
To simplify, use XVI32 freeware hex editor. If you search "BEGIN" you will see begin rsa key and begin certificate. You need to copy these values for later use.
Next, open up the backup you got from a friend and save the certificate/rsa information between the ---BEGIN --- and ---END --- tags.
Now that you have the rsa key/certificate for both it is time to run a str_replace.
(Make sure to look at the original file size of the backup you got of someones wimax.img. Once you are done the file size needs to be the same).
Take YOUR rsa key and convert it to hexidecimal.. you can find tons of sites that will do this .. just google convert string to hex (it will be a long string of stuff like 4D 49 49 44 6B 44 43 43 41 6E 69 67 41 77 49 42 41 67 49 51).
Next, take your buddies RSA key and convert it to hex as well.
Open a copy of your buddies backup now and this will be used as the template for your new wimax partition. Hit search -> replace. For the hex to search paste your buddies RSA key you converted to hex.. and for the replace with.. put the hex of your rsa key.
Repeat these last steps for the certificate as well (convert to hex and replace your buddies certificate with your own certificate text)
REMEMBER!!!! if the length is not the same of the certificate/key you can fix this by adding or removing the blank bytes at the end of the ---END RSA or --END CERTIFICATE area.
You should be able to save the file now and the size should be exactly the same as the original backup you borrowed.
Now the only thing you have to do is fix your mac. In your new wimax partition file, search for 00: to locate the mac address of your buddies partition. You might find a few random ones first but just look at the surrounding text to know it's their mac. Replace that string with your mac but subtract 1 from the last digit(if your mac was 00:23:76:EC:214 put 00:23:76:EC:213).
Replace the first 2 of the 3 instances with your mac -- minus 1. (If it ends on a letter, B would become A, C would become B, etc.
The last instance of your mac, put the actual mac address with nothing subtracted as it appears on the sticker under your battery.
Once you have saved the file.. name it something like wimax_fixed_resized.img and copy it to your sdcard.
Boot to fastboot and run "fastboot erase wimax"
Reboot to your recovery and adb shell in.
type "mount /sdcard" so you can run flash_image properly.
Run flash_image wimax /sdcard/wimax_fixed_resized.img
(or whatever you named it)
Profit!
Click to expand...
Click to collapse
is there any way to break it down anymore? and do you have to use a buddies backup? i have my RSA keys i made a backup a while ago... cant you just use one of your old backups and replace wimax? thanks in advance and thanks for the post.
Great post, had been wondering how to actually restore the wimax keys once you had 'em.
Question for any devs that may have them: are the RSA keys generated by or linked to MAC ID somehow? Would it be possible to use backups of an one phone's keys with the another phone's baseband MAC ID?
I'll try to clean up the post to make it an easier read tomorrow but if you have an intact backup of your wimax image you can just restore it with flash_image or fastboot.. or just restore the nandroid backup. This is just for people that have the key itself but the image they have might be corrupted. If it would help everyone I can take a working wimax.img and remove the RSA keys so you can just download it as a template and put your keys in
I updated the thread.. has a template file in there too with dummy certs and keys to make it easier for you guys.
This is a big deal bro. Thanks!
Has anyone been having issues connecting to 4G? I've been having some issues where it authenticates, launches then disconnects. My keys are present but not really sure what else to do from here.
NYCHitman1 said:
Has anyone been having issues connecting to 4G? I've been having some issues where it authenticates, launches then disconnects. My keys are present but not really sure what else to do from here.
Click to expand...
Click to collapse
Does it get to the "Obtaining IP Addres..." then moves to "Disconnected"?
Caanon said:
Does it get to the "Obtaining IP Addres..." then moves to "Disconnected"?
Click to expand...
Click to collapse
That's exactly what it does.
Sent from my PC36100 using XDA App
NYCHitman1 said:
That's exactly what it does.
Click to expand...
Click to collapse
Good news and bad news...
Bad news is that I wasn't ever able to fix it. I tried flashing up and down all the radios I could find, trying all the radio/rom combos I could think of. RUU'd even, and no dice.
Good news is that it might not have actually been your fault. I ended up biting the bullet and going to the Sprint store to explain what was going wrong. The tech looked at it and said, "Let me guess, this happened after an update, right?" Apparently this is a "known issue" to Sprint, and it actually ended up happening to the tech herself about a week before it happened to mine. They ordered me a refurb no charge (I have insurance, but didn't have to use it I don't think) and got it a few days later. New one connects to 4g no problem, and 4g on CM works like a charm (thanks toast and shin!).
Caanon said:
Good news and bad news...
Bad news is that I wasn't ever able to fix it. I tried flashing up and down all the radios I could find, trying all the radio/rom combos I could think of. RUU'd even, and no dice.
Good news is that it might not have actually been your fault. I ended up biting the bullet and going to the Sprint store to explain what was going wrong. The tech looked at it and said, "Let me guess, this happened after an update, right?" Apparently this is a "known issue" to Sprint, and it actually ended up happening to the tech herself about a week before it happened to mine. They ordered me a refurb no charge (I have insurance, but didn't have to use it I don't think) and got it a few days later. New one connects to 4g no problem, and 4g on CM works like a charm (thanks toast and shin!).
Click to expand...
Click to collapse
Damn! I really don't want to go through all that trouble right now. Lol, eff it. I'll wait for the next best thing.
Sent from my PC36100 using XDA App
Question, wouldn't it be easier to just backup the existing wimax.img and restore it if/when needed using recovery? Or does this method address something that can't be done via recovery?
Sticky
Sent from my HTC EVO 4G running Frost 4.0 using XDA app.
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
ericvbp21 said:
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
Click to expand...
Click to collapse
Flash the WiMAX radio again and Update Profile, it will grab the keys from the carrier based on your phone's programming information
aph said:
Flash the WiMAX radio again and Update Profile, it will grab the keys from the carrier based on your phone's programming information
Click to expand...
Click to collapse
i flashed the wimax radio and updated the profile but it still does the same thing. any idea? I do have the RSA keys so i don't know why it doesn't grab 4G....
Well I thought I lost my RES keys after doing haxts back up, after I checked using Explorer and there was no res_OEM.key file. I did the back up again, still no file. I used Astro on my phone and the files where there. (res_OEM.key 4,575 KB & res_OEM.keycat 16,863 KB. Now a day later and the files show up using Explorer? I did do a winmax back up before I did anything and that is still there. Bottom line, if you think you lost you res keys after doing a backup, check it with a file manager program on your phone.
ericvbp21 said:
i am confused when it come to this. is there a video or something. i know for a fact that i lost my RSA keys and i have used the "WiMAX Keys Checker" to check it and it say they are missing. but during my first initial backup i see the "img" file in there. i can't connect to 4g anymore so i am guessing for some reason it can't read it when i restore to the old version of my evo or when i change rom. i need some serious slow help
Click to expand...
Click to collapse
I have my keys (WiMAX Keys Checker) but i can only connect when i do a restore of the orginal EVO rom from backup, but on all other roms(elite II for now) it just saids searching and never conects. Please help
edit drop and broke the phone that im talking about.. got new one thur insurance and rooted it and and 4 g works with no problme wonder what i ddi when i root the first phone
hi i was fooling around with my new lg thrill and now my imei's been zero'ed out everything seems to work fine but i don't want to use it on the network because of my sketch imei.
heres what ive tried so far:
- tried the o2x method of using telnet (hyperterminal) and using the at command but i keep getting IMEI WRITE ERROR or something along those lines.
- tried looking around for some kind of system files like sammy's nv_data.bin but i haven't found anything yet. anybody know which file/s on the lg android filesystem store the imei?
ANY IDEAS
i mean worst case scenario i'll play dumb and have att replace it, but i dont want to drive all the way over to att and make up a bs excuse. id rather fix it at home.
thanks everyone! i really screwed up and once i get this fixed up i'll make sure i have proper backups before trying stuff out.
I didn't find too ... nv_data.bin i think is just for samsung and other ... i don't know what's for lg ... try to do a hard reset ... if that doesn't work you will need to go to att
i have the phone set up exactly how i want right now so i was hoping i could repair the imei and then do a nandroid backup or something
anyone know where the imei's stored on the lg phones? i read its in lgdrm somewhere but all i see are .cer files which i can't read or make sense of with notepad, a hex editor, or sqlite 3... :?
if i can figure this out soon i'll try factory reset and if taht doesnt work then i'll try to get it replaced by att.
My apologies if I have posted this in the wrong section
I'm in the middle of a big project that involves
LP getting some photos from a friend's phone the phone is an LG KP 202 clamshell it hasn't been turned on for about 7 years but it has the only pictures in existence of her first born child.
I managed to get into service mode by pressing a key combination and sure enough the photos are on there and everything seems ok but because it is a uart type interface it isn't as easy as plugging it in to a PC and dragging the files off
And to compound the problem someone has tried to network unlock it but I entered the wrong code too many times so there is no chance of a straight nck code unlock I have even been in contact with Vodafone Australia who will unlock those phones for free usually and I've tried the nck code but nothing happens
I tried various things with different USB cables and rs232 dongles and anything I could find but none of it worked so in the end of brought a z3x box
I have managed to make a backup of the phone now with the box and end up with a 32 megabyte dot bin file. I jump straight on to Kali Linux and tried pretty much everything. Autopsy binwalk etc etc With the best results seem to come from digital forensic framework and carvergui. Indeed I am carving out the photos I'm looking for but unfortunately they all seem to be corrupted. Some of the pictures may only contain about the first centimetre of quality data and then the rest is just multicolour pixelated garbage eventually grey blank. Some are almost complete and have the bottom centimetre of the photo with garbage data
I don't have any training or qualifications at all I'm just a bit of a hack in my spare time I know a little bit about the way things work but I'm not sure why this is happening because you can see that the data on the phone is in good condition because the photos display perfectly on the screen. I have been thinking that it may be due to the fact that the LG phone is based on a Linux system and I'm transferring it onto a Windows system and then back on to Linux and it may have something to do with the dos Linux file conversion but being binary data I'm not so sure.
I have tried ripping the data from the phone at low and high speeds but it seems to make no difference and I'm not even sure which part of her phone I'm actually downloading whether or not the user data partition (let's call it) is part of what im extracting or whether these images are just remnants of background caching processes etc
There seems to be (let's call them) 2 partitions and they are like this. The first one is "code data" and the second one called alchemy data I'm assuming that the code data contains the system files and the alchemy contains user data + other sorts of files it's very hard for me to tell because I think the positions are roughly equal size and dff reports them as part of a raid array so i doubt it's reporting correctly. And besided that, in the specifications it says it's only got a whopping 4 megabytes of user memory.
I do have the z3x box so I am able to unlock the phone but I'm not sure how much of the data I'm going to overwrite and if anyone could give me a clue or help me out in any way I'd really appreciate it if there's anything else you want to know just get back to me I'm pretty much at the end of skill set on this one but really need to get at those photos thanks guys cheers
I don't think my failure is in my approach but more in the execution and probably a few minor settings tweaks might see me to the finish line but I'm just not sure what they are
Just a side note isn't it amazing how far we've come in just seven years and with that in mind seeing that the dump is only 32 megabytes I could probably put it on send space if anyone's interested thanks again
edward.snowden said:
My apologies if I have posted this in the wrong section
I'm in the middle of a big project that involves
LP getting some photos from a friend's phone the phone is an LG KP 202 clamshell it hasn't been turned on for about 7 years but it has the only pictures in existence of her first born child.
I managed to get into service mode by pressing a key combination and sure enough the photos are on there and everything seems ok but because it is a uart type interface it isn't as easy as plugging it in to a PC and dragging the files off
And to compound the problem someone has tried to network unlock it but I entered the wrong code too many times so there is no chance of a straight nck code unlock I have even been in contact with Vodafone Australia who will unlock those phones for free usually and I've tried the nck code but nothing happens
I tried various things with different USB cables and rs232 dongles and anything I could find but none of it worked so in the end of brought a z3x box
I have managed to make a backup of the phone now with the box and end up with a 32 megabyte dot bin file. I jump straight on to Kali Linux and tried pretty much everything. Autopsy binwalk etc etc With the best results seem to come from digital forensic framework and carvergui. Indeed I am carving out the photos I'm looking for but unfortunately they all seem to be corrupted. Some of the pictures may only contain about the first centimetre of quality data and then the rest is just multicolour pixelated garbage eventually grey blank. Some are almost complete and have the bottom centimetre of the photo with garbage data
I don't have any training or qualifications at all I'm just a bit of a hack in my spare time I know a little bit about the way things work but I'm not sure why this is happening because you can see that the data on the phone is in good condition because the photos display perfectly on the screen. I have been thinking that it may be due to the fact that the LG phone is based on a Linux system and I'm transferring it onto a Windows system and then back on to Linux and it may have something to do with the dos Linux file conversion but being binary data I'm not so sure.
I have tried ripping the data from the phone at low and high speeds but it seems to make no difference and I'm not even sure which part of her phone I'm actually downloading whether or not the user data partition (let's call it) is part of what im extracting or whether these images are just remnants of background caching processes etc
There seems to be (let's call them) 2 partitions and they are like this. The first one is "code data" and the second one called alchemy data I'm assuming that the code data contains the system files and the alchemy contains user data + other sorts of files it's very hard for me to tell because I think the positions are roughly equal size and dff reports them as part of a raid array so i doubt it's reporting correctly. And besided that, in the specifications it says it's only got a whopping 4 megabytes of user memory.
I do have the z3x box so I am able to unlock the phone but I'm not sure how much of the data I'm going to overwrite and if anyone could give me a clue or help me out in any way I'd really appreciate it if there's anything else you want to know just get back to me I'm pretty much at the end of skill set on this one but really need to get at those photos thanks guys cheers
I don't think my failure is in my approach but more in the execution and probably a few minor settings tweaks might see me to the finish line but I'm just not sure what they are
Just a side note isn't it amazing how far we've come in just seven years and with that in mind seeing that the dump is only 32 megabytes I could probably put it on send space if anyone's interested thanks again
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA.Try posting your query in Android Q&A,Help and Troubleshooting or in one of the noob friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you!
Good Luck
___
v7
XDA Assist