Closed GoogleCodeExporter closed 8 years ago
Could you be a little more specific? What type of phone was connected? What
errors were presented? If there is not any too-personal information could you
perhaps share a 'log' from the logging tab
For example: When I connect a phone that does not make use of all 8 NV items
which are written, I would expect you would get several 'decoder' errors when
the program tries to interpret the results... is that what you are talking
about?
If so I think this is expected behavior, but perhaps there is a better way to
handle this situation? any suggestions?
Original comment by chromableedstudios
on 13 Jul 2012 at 1:17
Here is the a screen shot of the error
Original comment by websling...@gmail.com
on 13 Jul 2012 at 2:30
Attachments:
This was an LG Optimus from Sprint
Original comment by websling...@gmail.com
on 13 Jul 2012 at 2:30
i seen errors like this as well, on most HTC EVOs and a Few Droid X2's!
1 Error was when i write the MDN it re-writess 00000000000!
2. other errors are when i do xxxxxxxxxx@mycricket.com the whole thing dose not
go into the boxes they are to, they go to the password box for some reason?
other times i see Arrow+? and other errors!
3. i only us this software now to get the SPC code, other then that, im scared
it will brick another phone!
i need the 16 Digit Password for the SCH-u365
Original comment by soarespa...@gmail.com
on 13 Aug 2012 at 7:19
As indicated in an earlier post, all these "Errors" are, is likely an nv item
which is either not in use or is in a "locked" state because you either haven't
sent mode offline before attempting to read/write values (you should always
send mode offline before playing with nv).. or because the SPC or 16 digit SP
has not been entered in order to unlock the NV..
I am quite curious about the case where you said it was not correctly writing
the phone number, if you would provide the log from the logQ tab of the session
either here or by email (from connect to disconnect) I could probably tell you
what happened... again I would guess either mode offline was not set or spc had
not been sent perhaps could cause this behavior.
This is BETA software so there is some risk it could "brick" or otherwise allow
you to do harm to your phones(For example I don't think cdmaDevTerm checks to
make sure you enter MDN in proper format, or if you even type the right number
of digits for an mdn, so if you do not know what you are doing it could be easy
to go wrong). This branch is not in the current branch of development since it
has been ported to a library, if there is a bug, it may still be present in the
library though so please continue to provide bug reports.
Original comment by chromableedstudios
on 20 Aug 2012 at 12:27
[deleted comment]
Original comment by chromableedstudios
on 21 Aug 2012 at 11:13
As a final close to this issue, with version 2.7+ the messaging system has been
reworked to avoid the use of messageboxes-- there is still the potential for
errors to be thrown, but now they are caught and logged ideally.
Original comment by chromableedstudios
on 10 Oct 2012 at 5:19
Original issue reported on code.google.com by
rokette...@gmail.com
on 11 Jul 2012 at 1:44