Related
I have upgraded my XDA with a rom from the kitchen and now the phone will not work it keeps asking me for a GID: code. the sim is not locked as it works fine in a differant phone and i have tryed a differant sim in the xda and still get the GID: code window. can anyone tell me what is this and how do i get past it.
rom ver: 3.17.03 eng
date 05/15/03
radio ver: 4.21.00
protoco ver: 32s54
Well ive read most of the other chains and there is lots about unlocking sim and using XDAunlock but they also say if you have the special edition rom you dont need XDAunlock as itis included which i have.
If i click the sim unlock it tells me the sims is unlocked but when i enable the phone i still get the GID code window.
Any help would be good as i am now without a phone.
This is weird: the ordinary SIMlock used is some phones is technically called SID-lock. As I understand, the GIDlock feature is used to lock to a specific SIM. Why your phone would suddenly have a GIDlock enabled after upgrading your PDA ROM is beyond me. Are you sure upgrading the ROM is only thing that's different? Is it a 900/1800 or a 900/1900 phone? What RSU version is in there? What ROM did you have before? What ROM did you base your new kitchen ROM on? Do you have a serial cable or cradle?
Questions, questions, questions...
Thanks for your reply.
i have only upgraded the rom. its a 900/1800
not sure of the RSU device info is
rom ver: 3.17.03 eng
date 05/15/03
radio ver: 4.21.00
protoco ver: 32s54
this is a v-old XDA and the rom was so old it could not upgrade via usb /cradle (sorry forgot what the rom was but reading another chain who had the issue of not being able upgrade via usb i had the same rom as him. so i saved the ce+boot from a work mates xda to sd card and upgraded it. all was ok i then downloaded the rom from the kitchen and upgraded it via the cradel (usb).
I still have the sd card and have tryed reloading the ce+boot but when i boot up i still get the gGID: code window. so reloaded the kitchen rom and thats where i am now.
the rom i used i got from http://cuba.calyx.nl/~jsummers/ROMkitchen/
3.17.03 ENG O2-Euro .
here is all the info on my XDA i hope this helps some one.
model pw10a1
platform pocketpc
imei : 350312010009954
cpu : arm sa1110
speed 206 mhz
ram 32 mb
flash : 23 mb
flash chip : 28f128
data bus 23 bits
rom ver :3.17.03 eng
rom date : 05/15/03
radio vertion : 4.21.00
protocol ver : 32s54
We roughly know where the GIDlock code is stored in the phone ROM. And if you have a serial cable, we probably (maybe) have the AT command to extract the data. However: since 4.20 they obfuscated the other (SIDlock) code, and they may also have obfuscated this one. So no promises: It's a bit of a project, and as long as you're the only one with this problem it's kind of a waste: I'd rather spend the time on stuff that is useful to all of us.
Let's first try this: maybe it helps to reset the phone... Could you try resetting it using the menu from the bootloader? To do this, soft-reset the phone while keeping the power button pressed, and then (after "WAIT" is gone) press the top-right (calendar) button, select the fourth option from the menu using the rocker switch and then press the center of the switch.
I still need to know if you have (access to) an XDA serial cable.
I have tryed the soft reset no joy
i done have access to a serial cable only the usb.
please try to help,,,,
i i do get hold o a serial what do i need to do?
I'd like you to hook up a serial cable, start a terminal program at 115.200 bps, put the device in bootloader mode as described above, and then enter "dualser<enter>" followed by "AT%UREG?3FE004,FFFFFFFF<enter>", and then cut and paste the result here...
Ive got hold of a serial cable and connected it up. booted xda and see HTC botlader for (wallaby) etc.etc on screen.
but when i type the dualser i do not 1. see what i typed & 2. there is no responce from the device.
hyperT is set to
com 1
BPS = 115200
data b = 8
parity = none
stop b = 1
flow c = (tryed none, hardware, xon/xoff.
i know the typerT works as i have commected to a modem and can see at when i type it. tryed typing ate1 when connected to the xda (as this turns on echo but still no joy.. dose the xda have a differant echo on command.??
i do not beleve i have a duf cable as when i boot up i can see info from the xda come on the screen.. any comments would be good. ill see if i can find a differant cable for now and retry.
Ok i havegone a got a cable from 02 and connected it up.
i still have the same situation. i can see the xda boot on hyperT but my key strokes have not affect..
what now....
ok that was a game and some but here is the results.
i hope this means someting to you..
Code:
at%ureg?3fe004,ffffffff
+EXT_UREG
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFF000000000000
00000000000000000000FFFFFFFFFFFF
FFFF000000000000FFFFFFFF00000606
00000000
ok
nex_uk said:
i hope this means someting to you..
Click to expand...
Click to collapse
I would say your GIDlock is set to "00000000" (eight times zero). And your SIM pin is set to 0606 ?
(I'm glad it's all zeroes, because the obfuscation algorithm (I now know GIDlock also obfuscates) doesn't touch it that way, otherwise I would have to rip out the manipulator source.)
Try entering it normally first (i.e. through the box that asks for it). If that doesn't work, try entering "AT%LCKGID=0,00000000".
Hope this works...
Still have no clue why on earth your phone would have decided to turn it on...
Thanks Peter Poelman.
I have done that and now the window is gone. but my phone will not get a signal.
the At now looks like this.
AT-Command Interpreter ready
at%ureg?3fe004,ffffffff
Code:
+EXT_UREG
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFF000000000000
0000FFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFF0000FFFFFFFFFFFFFFFF02020606
00000000
OK.
ive tryed registering on network bit dose not find any.
ill reload the xda rom and try again and let you know.
thanks again for you helo so far...
nex_uk said:
I've tryed registering on network but does not find any.
Click to expand...
Click to collapse
I'd say the phone part in your device got very very confused at some point, possible not even connected with the new OS ROM. The dump already looks kind of funny, and I wouldn't be surprised if your phone has lost all of its configuration data, resulting in it being broken. You may (at your very own risk, I've never done this!!!), try the GSM Debug/Calibration mode from the bootloader. I've always been curious to see what it does, and in your case it may actually do some good.
Loading new ROMs will probably not help. You could try (again, at your own risk) doing an RSU upgrade before trying the calibration from the bootloader. But I'd say this device probably needs to go back in for repairs.
(And you might want to check, using the bootloader) that it's not inadvertently set to the wrong band or something)
Thanks..
we the reload of rom has started so ill wait for it to finish then ll try RSU upgrade (ill down load a new one from 02) thenif i still have no joy ill post the at string first so you can see if you see anything if not (what the hell) ill try GSM Debug/Calibration the xda is shagged so it cant break it..
as this is a second hand XDA do you know of anyone that can fix it in the UK.???
any ho ill let you what happens..
l chck the boo after the reload as this is 02 (uk) it should be 900/1800 right.
Just set the band manually via the bootloader (use calendar button in the bootloader).
You guys are great read the submerged post by my earlier on the result fixed mine also.
GID CODE 0000000
it think it must be the default.
just made a call
Thanks BTW Will try and leave my xda alone for a while
= SUBMERGED =
it it works, - leave it alone
it is doesnot ask
Hi Peter Poelman ...
You may (at your very own risk, I've never done this!!!), try the GSM Debug/Calibration mode from the bootloader. I've always been curious to see what it does, and in your case it may actually do some good
Click to expand...
Click to collapse
Actually, during doing RSU upgrade to a friend's XDA, since it didn't work from the first time, I selected this function from the bootloader. It kept the XDA veryyyy slow with a mark on the phone signal as if there is a continues call running. I couldn't stop it except by a hard reset, then applied TMO R6.24 and then it worked fine.
I 'm not sure it's just a coincedence or it was THE reason that made the new RSU works
Hi guys, I tried to debrand my x10i to the UK generic firmware today using this guide : xperiax10.net/2010/04/14/debrand-your-xperia-x10-tutorial/comment-page-1 Once the software had installed and the update service said it was complete i tried to restart my phone. The phone took a long time to begin to start up but after the sony ericsson screen i got a yellow exclamation mark.
I've tried doing what it says at the end of the guide to solve this but even after deleting the full '13740270’ folder the update service says my phone software is up to date and the only option is to exit(no option to re-install software).
I also tried installing the pc companion to see if i could do anything with it but i can't do anything with it cause i can't start the phone to 'mount' it.
I've also now downloaded the flash tool that is mentioned but I can't follow the Howto.txt file.
Here's a copy of it: Hi,
Loader.sin must be there. All other sin files are optional.
1.) Open regedit and search the String :
"USB\Vid_0fce&Pid_adde\"
You will find the "DeviceInstance" should look like this :
"USB\Vid_0fce&Pid_adde\1&23cfa456&7&8"
copy the last part "1&23cfa456&7&8" into the DeviceID.txt file. Don't paste any free lines/blocks before or after!
2.) Start X10flash.bat
3.) Connect X10 in flash Mode:
a) Power down
b) Hold "back" Key
c) conncet USB cradle on PC
If the LED is green everythin is good!
4.) Press ENTER
Can anyone help me out of this mess please? All help would be great.
Sorry for such a long post, i'm freaking out here!
just flash everything not just the loader.sin
What part don't you understand of the howto?
Its still fixable, its happen to me before!
just follow the method mentioned and u'l b fine. I'm new to this stuff and I managed to do it so I'm sure you can pull it of an all.. hope all works out well for ya!!
Sent from my X10i using XDA App
aussiebuddha said:
just flash everything not just the loader.sin
What part don't you understand of the howto?
Click to expand...
Click to collapse
I opened regedit on my pc and searched for the string but I found 2 strings, one with the device instance 5&d5a958b&0&1 and the other was 5&279093f8&0&1.
I tried using the first instance and followed the instructions but it was still not working. As soon as the i hit enter after i've put the phone in flash mode I got this error: imagebam.com/image/8b6dd486702065 (check the link, i can't post them just now as i'm new) and then the phone come out of flash mode, tries to restart and goesback to the yellow exclamation mark!
I then tried the other device instance and had the exact same problem.
Anyone able to help me?
spookyfish101 said:
I opened regedit on my pc and searched for the string but I found 2 strings, one with the device instance 5&d5a958b&0&1 and the other was 5&279093f8&0&1.
I tried using the first instance and followed the instructions but it was still not working. As soon as the i hit enter after i've put the phone in flash mode I got this error: imagebam.com/image/8b6dd486702065 (check the link, i can't post them just now as i'm new) and then the phone come out of flash mode, tries to restart and goesback to the yellow exclamation mark!
I then tried the other device instance and had the exact same problem.
Anyone able to help me?
Click to expand...
Click to collapse
Try the second string.
I had 2 strings as well and the second worked for me.
I tried both of the strings but i got the same error that i posted in the pic before during the flashing for both of them.
I'm doing it exactly as it says to in the howto file.
Maybe try another usb slot?
Sent from my X10i using XDA App
Mobzter said:
Maybe try another usb slot?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Just tried that and i'm having the same problem, does anyone have any other ideas or would anyone recommend using the davinciteam to reflash it?
Edit: Can someone confirm that i don't need to put the firmware files into the same folder when i'm trying to use x10flash.bat?
Sure the files must be in same directory.
If you have problems try using omnius.
Regards
Thanks, Omnius worked for me and i've now gone from having a half dead phone to having the latest update!
Thanks to everyone that helped me out!
is anyone else having this issue? we're typing in the serial # and beta key perfectly. we're not mistaking O's for 0's; 1's for I's, or anything. we are indeed choosing Windows and HTC Evo 4G on the website. we're doing everything absolutely perfect but it's still giving us an invalid beta key.
we're on hardware version 4.
learn how to copy and paste into command prompt.
we're doing that, still no go. absolutely nothing is working.
Double check the S/N that reports when you start the tool, just to make sure you are entering the same alpha/numeric the phone reports to the program. Use that S/N to generate your key.
I've been rooting phones all morning, hardware 003 and 004 with no problems at all.
Same here, I've done 3 today, with not a single problem to report.
cnstarz said:
is anyone else having this issue? we're typing in the serial # and beta key perfectly. we're not mistaking O's for 0's; 1's for I's, or anything. we are indeed choosing Windows and HTC Evo 4G on the website. we're doing everything absolutely perfect but it's still giving us an invalid beta key.
we're on hardware version 4.
Click to expand...
Click to collapse
From where are you getting your serials?
Deleted message
having the same issue can not get it to work at all i have tried it all!
the same
I got 2 rooted yesterday. and the one I was trying to do today, did not take at all..something is wrong somewere..
CMD
I dont know how comfortable you are with CMD but, What I did was use CMD prompt navigate to the folder and .exe for the revolutionary tool. Put in the command copy and then pasted it from the website. I put my folder on the desktop
Like this
CMD.EXE
CD users\whatever your name is here\desktop\what ever the folder name is
then revolutionary.exe
it launched found the phone and i pasted in what was needed by mouse and pressed enter and then the magic happened. Mileage may vary happy rooting
I had the same problem. You have to use the same key as provided with the download u can't download the program and go back for the key
Sent from my finally rooted EVO
I had this same problem, everything going smooth until running the revolutionary.exe and pasting the Beta key. Seems when you go to the revolutionary site for the key, the file that gets downloaded is attached to the key, so go ahead and unzip the file to your c: location again and when it asks, just copy and replace all the files and go through the steps and it should accept the Beta key this time and finish, it did for me. I hope this helps.
do you have the latest rev exe....there is a ver4 out.......
oski252 said:
do you have the latest rev exe....there is a ver4 out.......
Click to expand...
Click to collapse
That has to be the problem that I was having along with most of everything getting the error.
They/I was using version 3 revolutionary with the Key gen that's basically set for version 4.
No way for a old version to confirm key gen that isn't built in that tool.
This is the solution!
jokerinhand1119 said:
I had the same problem. You have to use the same key as provided with the download u can't download the program and go back for the key
Sent from my finally rooted EVO
Click to expand...
Click to collapse
THANKYOU!!! That's what I needed to do as I was using the revolution.exe from the zip I got from the larger zip from the root instructions. Once I used the v4 from the revolution site it worked like a charm! yea!
Another fix would be to try it on another computer. I was having the same issue on my Ubuntu laptop so I tried it on my Ubuntu desktop and it fire right on up. Hope this does help some that are still having problems. It work so don't give up and its really worth it .
Listen and follow closely i made a thread already how to fix this
When you generate your beta key it is imperative that u generate it from the same revolutionary zip you downloaded, the reason people get invalid key is 99.9% because it wasnt generated from the same revolutionary file downloaded,
2nd important its alot easier to copy the beta key in the box and paste to command prompt.
Do this by highlight, key in box , copy it, then open revolutionary.exe.
When the cmd prompt opens take your cursor to the top corner of cmd box and right click go to edit then paste, this is because the beta key is easily fudged up and case sensitive.
Remember to have the fast boot unchecked, usb debug on, and charge only on. And have the modified drivers installed
if fails re download the revolutionary for windows or mac or whatever comp your on and regenerate the key from that specific download and open the exe. From that one, and erase all others. You will get zerging root
then when done choose recovery in hboot then youll get a blue cwm screen choose install zip fine the su-2.3.6.3-ef gh signed.zip that should be on the root of your sd card, and install, that pushes the actual superuser to your device
now your rooted fully with cwm
I am trying to root a friends EVO, and it is not working for me either. I have tried everything listed here and still get invalid key.
Fastboot unchecked, Debugging on, New HTC driver as listed installed, Antivirus turned off, Phone on Charge only.
hopeless
EDIT: EVerything is fine, I finally read and comprehended that I was supposed to use the SERIAL# showing on the Revolutionary screen to enter in to generate the key. Once I was smart enough to figure that out, DONE!! Phone rooted and flashing AMONRA as I type. HOOAH!!
You have to put your s/n not anyone's else, make sure your not confusing o with 0. Capitals matter, I just rooted and it works.
Sent from my PC36100 using XDA App
If you can not get the generated beta key to work for the 2.3.3 revolutionary root, and it keep saying invalid beta key???
The fix is you must generate the key from the same revolutionary zip file you downloaded can not be used from different one and copy and past it from the beta key box, just hilight and copy then open the revolutionary.exe and put your mouse pointer at the top of the cmd box not in it, then right click scroll to edit then paste.
Remember 99.9% of invalid beta key response is because it has to be regenerated from a fresh revolutionary download and from the same one so , if all fails delete all your revolutionary downloads and start of and do the copy and paste.
I don't see how its a 'fix,' since that's how its supposed to be done from the beginning. I think most people are getting errors because the missed a value, or didn't get the letter case correct, because it IS case sensitive.
I have only downloaded the revolutionary tool once. I generate a beta key from the website for each phone s/n. I have rooted 6 GB EVO's w/o downloading a new .zip
v3 and v4 use different beta keys so you need to make sure your revolutionary tool is v4
Sent from my EVO 4G
Please help!!!!!
1. Should the serial number in the terminal box match the serial number on the phone?
2. I have tried all methods of the beat key and its still saying invalid key. SOo my question is, is there another way to get a beta key?
3. Is there any other way besides revolutionary to root the evo 4g?
If you guys can please answer these questions i would highly appreciate it.
Should the serial number in the terminal box match the serial number on the phone?
Yes
2. I have tried all methods of the beat key and its still saying invalid key. SOo my question is, is there another way to get a beta key?
Are you going to the website to generate the beta key? Someone above noted to copy the serial number from the command prompt. That saves yourself from typos.
3. Is there any other way besides revolutionary to root the evo 4g?
No
If you guys can please answer these questions i would highly appreciate it.
Sent from my PC36100
I can say that I tried my key a total of six times and got the invalid key response every time until I copied and pasted on the seventh.
I knew beforehand that it was case sensitive because this was the second Evo I rooted. My brother (his phone) and I both checked the characters every time and they matched every time. The first four times I tried from one download, the last two I downloaded separate files.
My theory is that for some unknown reason (im not smart at this stuff) when you first get an invalid key, it might continue to be invalid until you do the copy / paste.
Not sure if thats possible, but thats my guess.
He is right this is not a fix but actually how it is supposed to be done. Also I have used the same zip on multiple phones so that is a false statement. Now if all drivers are loaded up properly you will see your serial number in the cmd window. If that number is different than the one on the back of the phone you may have bigger problems but I would go with the one seen in the cmd box
Enter you info properly and the beta key that is produced can be copied and then as stated in the revolutionary thread- right click on the task bar of the cmd and click paste to enter your beta information. Much safer than writing it down and hoping you entered it correctly
One other things- If you have an older Evo with an older HBoot then you can try Unrevoked root method if not then yes you have to keep trying Revolutionary
If anyone needs help with this task PM me.
I never had any problems with the beta key it worked the first time .
Sent from my PC36100 using Tapatalk
pfcland said:
I never had any problems with the beta key it worked the first time .
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most don't but a few do seem to have issues
hey, new to this but this seemed to work for me.. i verified (several times) on my phone, and everything on there said that my hboot version was 2.15.. (I even verified by powering down, holding the power/volume down button), and revolutionary still did not work.. but i noticed on the revolutionary exe. it said my phone had the 2.16, so i tried a different beta key with the 2.16 hboot option and now it seems to be working.. not sure if this helps.... worked for me..
help new phone i done this b4 no problem now it wont work
put in new sn got new key and wont go in ugh
I am having a slightly different problem, and I think its probably user error. I downloaded revolutionary-0.4prep4.zip and unzipped it into a new folder on my desktop. I tried running the 'revoluationary' application (double clicked it), i get a cmd box that flashes and disappears and that's it. What am i doing wrong or missing? Running windows7 64, dl'd the windows version. my phone is on and connected via usb.
Thanx
Try right clicking and running as administrator.. Did you also install the drivers, and is HTC sync installed
I did try running as admin. And I thought I had installed the drivers. I do have HTC Sync installed, too. I'll double check the drivers, though.
---------- Post added at 12:59 PM ---------- Previous post was at 12:53 PM ----------
tammerlane said:
I did try running as admin. And I thought I had installed the drivers. I do have HTC Sync installed, too. I'll double check the drivers, though.
Click to expand...
Click to collapse
Ok, I reinstalled HTC Sync and drivers just to be sure, ran revolutionary as admin, and it still flashes onscreen and disappears. I've even tried a different USB port, for whatever that was worth. My phone itself it is set to charge only, does that make a difference?
DO NOT HAVE SYNC IMSTALLED! You need to remove it and any other HTC thing installed when you installed sync.
SYNC causes issues with revolutionary.
You should download the drivers from the wiki which can be gotten to by the revolutionary site. They are all you need.
Sent from my PC36100 using XDA App
ack, that was it. thank you for pointing me in the right direction. problem solved!
tammerlane said:
ack, that was it. thank you for pointing me in the right direction. problem solved!
Click to expand...
Click to collapse
You guys have got to stop improvising and follow directions to the letter....It works believe me I have done quite a few phones already. Use the right drivers and it will work out for you... Good luck...
Ok people getting an invaled beta key. I mad the mistake of downloading the file and using the s/n from the back of the phone under the battery. That is not the sn you need. After you download the file and run it under admin it will ask you for the beta key. The serial number you need is the number right before the space provided for the beta key. In other words the serial number you need is in the comand prompt not on the phone.
Mine won't even get past the waiting for device, I'm using the same method that I used on my wifes EVO and mine before I took it in for a screen replacement. Only difference is I'm no longer using my laptop. I'm using a desktop now and it ain't working.
Sent from my PC36100 using XDA App
Thanks a lot, you helped me fix my problem
Im trying to use revolutionary-0.4pre4 so i can install CM7 but when i try to use revolutionary it says "invalid beta key"
Ive filled in the form on there site correctly but i gives me the same key but never works!
Can anybody help me?
Serial Number is a 12 digit alphanumeric code, not your device IMEI. Once you have ensured this is the case, and the key still doesn't work, copy paste it. Google "Copy Paste into a Command Prompt" and follow it.
Thank you that has worked it looked like a I but was in fact a 1
HELP
Im having the same problem i an htc sensation 4g and it keeps saying invalid beta key i have hboot 1.18.0000 and i entered that correctly and the serial number i used is the correct one it isnt the imei number ive tried copying and pasting the beta key countless times and i have typed it in countless time its aggravating if anyone has any info on why this is happening or how to fix this i would really appreciate it
Exact beta key
Lol i had the same problem when i rooted but i found out it needs to be exact pin point precision, say you have a I or l try a 1 instead . Hope i helped