Anonymous
19th January 2003, 04:00 PM
This message contains all postings in this thread
dated before January 19th 2003
Subject: Manipulator:what if it breaks?
From: anonymous
Date: 13 Jan, 2003 09:37:03
I have PPC from T-mobile Czech, ROM ver. 3.14.02 ENG, 09/27/02,
Radio version T310. You says on your www that you have tested
XDA manipulator on Radio versions 4.06, 4.10. Do you thing, that
it might work with my XDA?
In case I screw my phone, is there any way to repair it?
Subject: Breaking it with manipulator
From: XDA developers
Date: 13 Jan, 2003 09:40:56
You can always try: SID and GID lock are very, very unlikely to
harm the phone, counter reset is slightly more risky, and IMEI
change is the most risky. On the other hand, we do pretty
rigorous checking to see if the IMEI really is where we expect
it to be. They could always cause our software to break the
phone if they were evil, but we think using it on versions up
until now is pretty safe.
Given the server traffic we've been seeing over the last few
days, we would know by now if the Manipulator broke phones.
> In case I screw my phone, is there any way to repair it?
Depends... Maybe not... We're not making money here, so we're
not in the business of guartanteeing anything. The only thing we
do with warranties is void them. :)
Subject: counter reset
From: hatch
Date: 16 Jan, 2003 04:19:39
may i ask for your findings for resetting call counter on the
XDA? what are the possible risk for using this? thank you for
your much appreciated help.
Subject: Counter reset
From: XDA developers
Date: 16 Jan, 2003 08:26:59
The counters have their own 4k block in the ROM. This is because
the device can only erase 4k blocks, so it erases and then write
4 bytes per call. These 4 bytes are the low-order 16 bits of
incoming and outgoing call durations. When the block is full it
re-writes the high-order bits at the beginning and starts over.
If there exist ROM versions where this counter is somewhere
else, then resetting the counter would overwrite the wrong
block, with possible bad consequences. But we haven't had any
reports of the XDA Manipulator breaking a phone, just one single
report of failing to write an IMEI (creating an IMEI that ends
in all zeroes instead, but leaving the phone functional).
Subject: thanks
From: hatch
Date: 17 Jan, 2003 00:50:01
thanks for that quick detailed explanation, im just waiting for
my serial cable andd will try the reset, my readio version is
4.10 o probably mo unlikely problem maybe encountered. will
update xda-dev fof my progress. thanks so much. :)
dated before January 19th 2003
Subject: Manipulator:what if it breaks?
From: anonymous
Date: 13 Jan, 2003 09:37:03
I have PPC from T-mobile Czech, ROM ver. 3.14.02 ENG, 09/27/02,
Radio version T310. You says on your www that you have tested
XDA manipulator on Radio versions 4.06, 4.10. Do you thing, that
it might work with my XDA?
In case I screw my phone, is there any way to repair it?
Subject: Breaking it with manipulator
From: XDA developers
Date: 13 Jan, 2003 09:40:56
You can always try: SID and GID lock are very, very unlikely to
harm the phone, counter reset is slightly more risky, and IMEI
change is the most risky. On the other hand, we do pretty
rigorous checking to see if the IMEI really is where we expect
it to be. They could always cause our software to break the
phone if they were evil, but we think using it on versions up
until now is pretty safe.
Given the server traffic we've been seeing over the last few
days, we would know by now if the Manipulator broke phones.
> In case I screw my phone, is there any way to repair it?
Depends... Maybe not... We're not making money here, so we're
not in the business of guartanteeing anything. The only thing we
do with warranties is void them. :)
Subject: counter reset
From: hatch
Date: 16 Jan, 2003 04:19:39
may i ask for your findings for resetting call counter on the
XDA? what are the possible risk for using this? thank you for
your much appreciated help.
Subject: Counter reset
From: XDA developers
Date: 16 Jan, 2003 08:26:59
The counters have their own 4k block in the ROM. This is because
the device can only erase 4k blocks, so it erases and then write
4 bytes per call. These 4 bytes are the low-order 16 bits of
incoming and outgoing call durations. When the block is full it
re-writes the high-order bits at the beginning and starts over.
If there exist ROM versions where this counter is somewhere
else, then resetting the counter would overwrite the wrong
block, with possible bad consequences. But we haven't had any
reports of the XDA Manipulator breaking a phone, just one single
report of failing to write an IMEI (creating an IMEI that ends
in all zeroes instead, but leaving the phone functional).
Subject: thanks
From: hatch
Date: 17 Jan, 2003 00:50:01
thanks for that quick detailed explanation, im just waiting for
my serial cable andd will try the reset, my readio version is
4.10 o probably mo unlikely problem maybe encountered. will
update xda-dev fof my progress. thanks so much. :)