Printable View
Okay i was putting a patch on my phone using SE Tool 2 Lite to unlock the phone, and now after finishing the patch, the phone wont turn on. Anyone know of anyways to solve this? I dont get a white screen or anything, just doesnt do anything when i turn it on...
This is the code in the patch (from se-nse.net):
;W810 SW-R4EK001
;Remove SIM-Lock
;© IronMaster
;(p) m1ch43lzm
+44140000
d12c84: 70B5041CF1F2F4FA00230022011C1C20 F0B505213A22D1F71FFD0020F0BDC046
Any help is appreciated...Thanks.
Did you click on flash or write script or write GDFS? Setools2 Lite although an amazing tool has a high density of button, so you might have clicked the wrong one by mistake.
i clicked write script...
i followed this diagram:
http://img517.imageshack.us/img517/4...chpiccycp1.png
Additional info:
When i plug the phone into XS++, it recognizes it, but doesnt show any firmware or erom available on the phone, as shown below:
http://i79.photobucket.com/albums/j1...NoFirmware.jpg
This makes me think maybe i need to reflash the phone to get all that back. I tried restoring my GDFS that i had backedup the other day, but it doesnt do anything, it just hangs up at the part that says:
23:40:46| Sending db2010_cid49red_cs_r3a010.bin...
23:40:48| Applet ID: 070524 1030 AN2CXC1327364_COMPACT_SEMC_CS_LOADER__R3A010
23:40:48| This is a CHIPSELECT loader
23:40:48| Activating loader...
23:40:48| Activating GDFS..
Again any help is appreciated...
not good.. why should a vkp patch kill a phone?
Anyway as long as XS++ detects your phone it can be revived i think.
You include the .vkp in MISC section right?
I'm sorry I dont know a lot about GDFSs and your log says "cant open GDFS" quite a few times. I guess its damaged.
Alright, i ended up reflashing with wotan and fixing my own problem.
I am still curious as to why that patch screwed my firmware up?
You sure the patch works? where did you get it from?
if you get backup from your gdfs werite buckup to phone if dont have backup flash your phone by setool2lite
the patch same by youre phone firmware?
Try and remove the patch.
If you post the log, probably we can give you an answer...Quote:
Originally Posted by RUGUNIT
The log is there mate, scroll up