Printable View
i have flashed the K790i with the flash files of K800i but after again flashing with K790i there is no network how can be this solved any guide
i have tried to use the other phone GDFS already i have a back up of original GDFS of that phone
as a thread told me that to backup first ur original and then play with it
any one help or guide what should i use
i have setool3
i have cruiser
just need a procedure
NAEEM FAROOQUI
K790i CID49RED
K790 isn't compatibile with K800's firmware, cuz he doesn't have a videocall camera, so there is another structure inside the phone, like mohdumer said, only thing that you can do is to customize...
WARNING: Do Not Use Any Other GDFS For Your Phone Since GDFS Is Unique To Your IMEI. Just Reflash Your Phone, Customize It And THEN Rewrite Your Origanal Backed Up GDFS.
Follow This Step By Step Guide Which Uses XS++ 3.1 XS++ 3.1 Guide-Flashing,Customizing,Recovering - Top Sony Forums
first write back your oringal gdfs back-up from your phone, then get some k790firmware or k818i firmware and re-flash the phone,
the k790 uses different bands to the k800i thats why you can't get a signal, there is no point flashing a k790 to a k800i, or k800i to k790,
You Find A Lot That A K790 Can Be Converted To K818 But Please DONT TRY Cause It Will Damage Your GDFS And Again You Wont Get Signals. The Most You Can Do Is Customize Your K790.
HUM.
Then, K790 is possible convert to K818?
With do I do this?
Quote:
Originally Posted by mohdumer
i have flash that mobile i think 20 times with different flash files of K790i from the first error but it never taken back the signals what should i do how i customize
where will be the first GDFS backup of my phone ??
sorry to ask this little questions but first time i made mistake at any of the SE phone
NAEEM FAROOQUI.
Copy pasted from SETool forum...
Just follow this procedure carefully...
-----------------------------------
Case:
Let's say you have a DB2020 phone with some GDFS issue, say you wrote K800 firmware to a K790 and now you have "no network".
Solution:You'll have to rewrite the original GDFS. Sadly, most users never back it up before proceeding with whatever operation they intended to do in the first place. This is done through the "Read GDFS" button in SETool, btw http://www.mobile-files.com/forum/im...ilies/wink.gif. it will produce a .bin-file named with the phones IMEI and can be found in your SETool basedir. Take good care of it.
Now, lets say you didn't back up the phones GDFS and did something to screw it up. Then you have a problem, because rewriting it with another phones GDFS will screw the security units and the phone will be bricked. Generally a bad thing, right http://www.mobile-files.com/forum/im...ilies/wink.gif?.
Luckily, there is a way to solve this and the procedure is as follows:
Use only COM/UFS interfaces!
1 (Optional): Back up the corrupt GDFS (yes, even though it's corrupted, so you have a full backup just in case). Again: "Read GDFS". Move it to a safe place on your HD, this is to avoid accidentally deleting it and for avoiding confusion with all the other txt-files that will appear later on.
2: Create a scriptfile (a normal txt-file will do) with the following contents:
Code:
gdfsread:00020e5a
gdfsread:00020e48
gdfsread:00010851
gdfsread:00000006
gdfsread:0000000E
gdfsread:00000013
gdfsread:0000001C
gdfsread:00000018
gdfsread:000000AA
Now save it. Name it "readsecunits.txt" or whatever. Select the file in SETool's MISC-field and press "Write SCRIPT".
All the read units will be stored in a single file named by the phone's IMEI.
rename it as "secunitsbackup.txt" to avoid confusion
3: Apply the GDFS from a working DB2020 phone.
- Read it out from the source phone (it will be stored in the SETool basedir named by the source phone's IMEI)
- Check "Format GDFS" in "Settings" and write it to the damaged phone by selecting it in the MISC-field and pressing "Write GDFS".
if you have CID52 phone, NOT CHECK "format GDFS"
Do NOT turn the phone on afterwards.
4: Now, you'll have to write back the original units. Apply the "secunitsbackup.txt" you created by selecting it in the MISC-field and pressing "Write SCRIPT".
Voila, it should have done the trick.
I'll ask the_laser to produce some DB2020 GDFS files in case you don't have a working phone to read from.
another method of quick recovery (without all mess with gdfs backup/write/etc)
create and execute following script
gdfswrite:000000ACXX
set XX to valid for your phone:
;00 MS_GSM900
;01 MS_EGSM900
;02 MS_DCS1800
;03 MS_PCS1900
;04 MS_GSM900_DCS1800
;05 MS_EGSM900_DCS1800
;06 MS_GSM900_PCS1900
;07 MS_EGSM900_PCS1900
;08 MS_DCS1800_PCS1900
;09 MS_GSM900_DCS1800_PCS1900
;0a MS_EGSM900_DCS1800_PCS1900
;0b MS_GSM850
;0c MS_GSM850_PCS1900
;0d MS_EGSM900_GSM850
;0e MS_DCS1800_GSM850
;0f MS_EGSM900_DCS1800_GSM850
;10 MS_EGSM900_GSM850_PCS1900
;11 MS_DCS1800_GSM850_PCS1900
;12 MS_EGSM900_DCS1800_GSM850_PCS1900
You Sure Flash correct customize pack because network problem relate to customize pack.Quote:
Originally Posted by nnaeem11
2)if gdfs is damage use setool2(box) and write new gdfs phone(because your phone is cid49)
ok so if i flash my phone with valid firmware (ie same model) is there any way somthing like this problem could happen to me? or is this only posible with incorrect model of firmware
oh ya, aswell if it were to happen, could u re-flash your phone with the sony ericson flash tool, that gives you back branded firmware, and have it work?
nothing gona work men i have even downgraded my set to least version but sony always says no update available
NAEEM FAROOQUI.
now can you tell me is it possibale?