GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > No More Supported Solutions (Dead Products) > No More Supported H/W Products > Griffin Products > MT-BOX


Reply
 
LinkBack Thread Tools Display Modes
Old 08-11-2007, 16:08   #1 (permalink)
No Life Poster
 
Seedy's Avatar
 
Join Date: Dec 2001
Posts: 1,175
Member: 8102
Status: Offline
Thanks Meter: 118
How did I lose a credit for same phone !


Unlocking a phone and first time could not connect. Second time it worked but it used up another credit.

I had a long pm discussion with 911GT lsat week about this were I had lost a credit and he said it is impossible

Now that the ppl that know me I am not a con artist and couple of logs is not the issue (well it is !!) but MT Team can you pls check this out for me as I have lost 2 credits already which is 40 Euros !!!

Surely as this is the first time I have used MT Pro for 2 days you can check what phones I have unlocked ??

Same thing happened last week as well

An honest answer is appreciated

Model: RM-209 (7373)
V 03.90/06-10-06/RM-209 (c) Nokia.
Production serial number CEI2xxxxx
Product code 0543810
Module code 0203099
Basic production code 0534038
Flash code
Order number
Long production SN
MCU SW V 03.90/06-10-06/RM-209/(c) Nokia.
HW 1002
PCI
RFIC 17211721
DSP pb06w14v21
PPM V 03.90/06-10-06/RM-209/(c) Nokia. /C
Retu 32
Tahvo 53
Content Pack Content: voda_payt_uk/V 03.90/06-10-06/RM-209/(c) Nokia. //
IMEI: 3562910113xxxxx
WARNING: VPP pin is not connected, disabling VPP.
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
Counters 0/10, 0/3
Phone is in: Local mode
Imei: 3562910113xxxxx
W 03.90/06-10-06/RM-209/(c) Nokia.
Auto backup SIMLOCK...
=================================
bb5bckup\3562910113xxxxx.pm
134 : 0 0x1 bytes
134 : 1 0x2000 bytes
134 : 3 0x1 bytes
134 : 4 0x1 bytes
134 : 5 0xA bytes
134 : 6 0x1 bytes
134 : 7 0x1 bytes
134 : 8 0x1 bytes
134 : 9 0x28 bytes
=================================
===================================
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
===================================
Using Account: bb5xxxxxxxxxxxxxxxxxxxxx
Connect...
Resp:
o/0110/hello there
Login...
OK, available count
74;

busy, waiting...
Server Response OK.
===================================
Connect TPs
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
(shortened) as post will be too long
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Canceling detect on User request....
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Phone is in: Local mode
Scanning files, please wait...
Done
Model: RM-209 (7373)
V 03.90/06-10-06/RM-209 (c) Nokia.
Production serial number CEI2xxxxx
Product code 0543810
Module code 0203099
Basic production code 0534038
Flash code
Order number
Long production SN
MCU SW V 03.90/06-10-06/RM-209/(c) Nokia.
HW 1002
PCI
RFIC 17211721
DSP pb06w14v21
PPM V 03.90/06-10-06/RM-209/(c) Nokia. /C
Retu 32
Tahvo 53
Content Pack Content: voda_payt_uk/V 03.90/06-10-06/RM-209/(c) Nokia. //
IMEI: 3562910113xxxxx
WARNING: VPP pin is not connected, disabling VPP.
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
Counters 0/10, 0/3
Phone is in: Local mode
Imei: 3562910113xxxxx
W 03.90/06-10-06/RM-209/(c) Nokia.
Auto backup SIMLOCK...
=================================
bb5bckup\3562910113xxxxx.pm
nBackup file already exists! SKIPPING backup
=================================
===================================
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
===================================
Using Account: bb5xxxxxxxxxxxxxxx
Connect...
Resp:
o/0110/hello there
Login...
OK, available count
73;

busy, waiting...
Server Response OK.
===================================
Connect TPs
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx

TPs OK
UNLOCK SUCCESSFULL
SUCCESSFULL
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Open on Mcc Mnc: 23415F
Sim Status: Not locked
  Reply With Quote
Old 08-11-2007, 16:40   #2 (permalink)
No Life Poster
 
Join Date: Dec 2003
Location: Baltchik,Bulgaria
Age: 50
Posts: 1,250
Member: 47236
Status: Offline
Thanks Meter: 58
first 74 number is count from before
second 73 is log counted for your phone bro


check now count will be 73 and after press UNLOCK button will be 72 after next phone
So GT didnt eat your logs



BR
  Reply With Quote
Old 08-11-2007, 16:45   #3 (permalink)
No Life Poster
 
Seedy's Avatar
 
Join Date: Dec 2001
Posts: 1,175
Member: 8102
Status: Offline
Thanks Meter: 118
Quote:
Originally Posted by vascof1 View Post
first 74 number is count from before
second 73 is log counted for your phone bro


check now count will be 73 and after press UNLOCK button will be 72 after next phone
So GT didnt eat your logs

BR
Check before you type !!

-When I started I had 74
-I could not unlock - so when I started the SAME phone again I had 73

How's that not losing ??

I check now and I only have 72 and I have only unlocked ONE phone
  Reply With Quote
Old 08-11-2007, 17:58   #4 (permalink)
No Life Poster
 
electrolandgsm's Avatar
 
Join Date: Aug 2005
Location: romania-bm
Age: 40
Posts: 1,422
Member: 174315
Status: Offline
Thanks Meter: 123
as far as i know(is not sure..i only suppose that) the server has already build-in counter for each box and each imei.
so...i think counter that is showed by mt box ..is not 100% the real one.
the server keep the real counter..so you don't lose your credits.
maybe i am wrong..not sure
  Reply With Quote
Old 08-11-2007, 18:07   #5 (permalink)
No Life Poster
 
Seedy's Avatar
 
Join Date: Dec 2001
Posts: 1,175
Member: 8102
Status: Offline
Thanks Meter: 118
Quote:
Originally Posted by electrolandgsm View Post
as far as i know(is not sure..i only suppose that) the server has already build-in counter for each box and each imei.
so...i think counter that is showed by mt box ..is not 100% the real one.
the server keep the real counter..so you don't lose your credits.
maybe i am wrong..not sure
I hope you are correct - we await a response from MT Team.

Would be very grateful if they physically checked what I have said in their server to confirm I am telling the truth
  Reply With Quote
Old 08-11-2007, 18:37   #6 (permalink)
No Life Poster
 
Join Date: Dec 2003
Location: Baltchik,Bulgaria
Age: 50
Posts: 1,250
Member: 47236
Status: Offline
Thanks Meter: 58
counter shown at MT GUI is just the same from the server,
so once again

CHECK YOUR COUNTER BEFORE UNLOCK AND AFTER UNLOCK

you will see that there isnt any logs `eating`
you will be counting for every IMEI


BR
  Reply With Quote
Old 08-11-2007, 18:45   #7 (permalink)
No Life Poster
 
Seedy's Avatar
 
Join Date: Dec 2001
Posts: 1,175
Member: 8102
Status: Offline
Thanks Meter: 118
ok i think i give up !
  Reply With Quote
Old 08-11-2007, 18:49   #8 (permalink)
No Life Poster
 
Join Date: Dec 2003
Location: Baltchik,Bulgaria
Age: 50
Posts: 1,250
Member: 47236
Status: Offline
Thanks Meter: 58
Quote:
Originally Posted by Seedy View Post
Unlocking a phone and first time could not connect. Second time it worked but it used up another credit.

I had a long pm discussion with 911GT lsat week about this were I had lost a credit and he said it is impossible

Now that the ppl that know me I am not a con artist and couple of logs is not the issue (well it is !!) but MT Team can you pls check this out for me as I have lost 2 credits already which is 40 Euros !!!

Surely as this is the first time I have used MT Pro for 2 days you can check what phones I have unlocked ??

Same thing happened last week as well

An honest answer is appreciated

Model: RM-209 (7373)
V 03.90/06-10-06/RM-209 (c) Nokia.
Production serial number CEI2xxxxx
Product code 0543810
Module code 0203099
Basic production code 0534038
Flash code
Order number
Long production SN
MCU SW V 03.90/06-10-06/RM-209/(c) Nokia.
HW 1002
PCI
RFIC 17211721
DSP pb06w14v21
PPM V 03.90/06-10-06/RM-209/(c) Nokia. /C
Retu 32
Tahvo 53
Content Pack Content: voda_payt_uk/V 03.90/06-10-06/RM-209/(c) Nokia. //
IMEI: 3562910113xxxxx
WARNING: VPP pin is not connected, disabling VPP.
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
Counters 0/10, 0/3
Phone is in: Local mode
Imei: 3562910113xxxxx
W 03.90/06-10-06/RM-209/(c) Nokia.
Auto backup SIMLOCK...
=================================
bb5bckup\3562910113xxxxx.pm
134 : 0 0x1 bytes
134 : 1 0x2000 bytes
134 : 3 0x1 bytes
134 : 4 0x1 bytes
134 : 5 0xA bytes
134 : 6 0x1 bytes
134 : 7 0x1 bytes
134 : 8 0x1 bytes
134 : 9 0x28 bytes
=================================
===================================
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
===================================
Using Account: bb5xxxxxxxxxxxxxxxxxxxxx
Connect...
Resp:
o/0110/hello there
Login...
OK, available count
74;

busy, waiting...
Server Response OK.
===================================
Connect TPs
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
(shortened) as post will be too long
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
No communication with phone. Delaying 5 sec
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Canceling detect on User request....
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Phone is in: Local mode
Scanning files, please wait...
Done
Model: RM-209 (7373)
V 03.90/06-10-06/RM-209 (c) Nokia.
Production serial number CEI2xxxxx
Product code 0543810
Module code 0203099
Basic production code 0534038
Flash code
Order number
Long production SN
MCU SW V 03.90/06-10-06/RM-209/(c) Nokia.
HW 1002
PCI
RFIC 17211721
DSP pb06w14v21
PPM V 03.90/06-10-06/RM-209/(c) Nokia. /C
Retu 32
Tahvo 53
Content Pack Content: voda_payt_uk/V 03.90/06-10-06/RM-209/(c) Nokia. //
IMEI: 3562910113xxxxx
WARNING: VPP pin is not connected, disabling VPP.
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
Counters 0/10, 0/3
Phone is in: Local mode
Imei: 3562910113xxxxx
W 03.90/06-10-06/RM-209/(c) Nokia.
Auto backup SIMLOCK...
=================================
bb5bckup\3562910113xxxxx.pm
nBackup file already exists! SKIPPING backup
=================================
===================================
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Closed on Mcc Mnc: 23415F
===================================
Using Account: bb5xxxxxxxxxxxxxxx
Connect...
Resp:
o/0110/hello there
Login...
OK, available count
73;

busy, waiting...
Server Response OK.
===================================
Connect TPs
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx

TPs OK
UNLOCK SUCCESSFULL
SUCCESSFULL
V 03.90/06-10-06/RM-209 (c) Nokia.
IMEI: 3562910113xxxxx
Operator: 8000000000000000
Profile bits: 2341500000000000
Open on Mcc Mnc: 23415F
Sim Status: Not locked
so

in this log you post two counts bro 73 and 74 am i right

you are tried second phone for 72
at last check your MT-box log file

BR
  Reply With Quote
Old 08-11-2007, 18:51   #9 (permalink)
No Life Poster
 
Seedy's Avatar
 
Join Date: Dec 2001
Posts: 1,175
Member: 8102
Status: Offline
Thanks Meter: 118
lost the will to live - forget it !!
  Reply With Quote
Old 08-12-2007, 04:09   #10 (permalink)
Freak Poster
 
Join Date: May 2006
Posts: 245
Member: 281761
Status: Offline
Thanks Meter: 4
Yes this is a question from me too. I believe they track what you unlock by imei and you only burn a credit if they see an imei they haven't seen already. That's how it should work right? So if they take a credit off for an imei they have already seen that's just wrong. So the code on their side that has to remember which imei's they've previously seen has to be rock solid. That is they cannot have it burn a credit until they've recorded the imei they've seen otherwise if there's some kind of error you lost your credit but the server doesn't know it's seen this imei before and when it sees it again it will burn another credit.

The act of updating the log counter and recording which imei they have seen has to be an automic operation. either all or nothing.

Quote:
Originally Posted by Seedy View Post
Check before you type !!

-When I started I had 74
-I could not unlock - so when I started the SAME phone again I had 73

How's that not losing ??

I check now and I only have 72 and I have only unlocked ONE phone
  Reply With Quote
Old 08-12-2007, 04:21   #11 (permalink)
Freak Poster
 
Join Date: May 2006
Posts: 245
Member: 281761
Status: Offline
Thanks Meter: 4
The way it's suppose to work is that it's only supposed to charge you a credit when it sees a new iemi. so the code that records which iemi's it's seen is important. The idea is that regardless of whether you succeed or fail the unlock you are charged the credit whenver the iemi is new. The idea being is that when you go back with the same phone again it won't charge the credit but the code that checks whether or not it's seen this iemi before has to be rock solid in order to not charge the credit for the same phone.

The code isn't written to only take off the credit when it detects a successful unlock because if it was like that people would figure out a way to stop that "trip" from happening in order to avoid the credit charge.
  Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
i lose 8logs for same phone F@RUK S Seking Server 2 04-06-2008 08:24
lost 1 credit for clear phone lock k800i why .:Cairo:. Cruiser Suite 7 01-21-2008 05:01
i lose 2 logs for same phone F@RUK S SAGEM JTAG UNLOCKER 1 12-19-2007 22:56
How to use trial siemens credits for MT box? KUBAT1 MT-BOX 2 04-14-2007 19:01

 



All times are GMT +1. The time now is 09:32.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.24718 seconds with 9 queries

SEO by vBSEO