Look: http://android.modac...ad-all-nvitems/
!!!___ I HAVE NVITEMS READ FROM OMC, IN FTM MODE__!!!
Started by
glossywhite
, Oct 21 2011 04:29 PM
#1
Posted 21 October 2011 - 04:29 PM
Yessss! I have read out NVITEMS using QPST on Windows, by putting a clean, brand new OMC into FTM mode:
Look: http://android.modac...ad-all-nvitems/
Look: http://android.modac...ad-all-nvitems/
#2
Posted 21 October 2011 - 04:37 PM
#3
Posted 21 October 2011 - 04:40 PM
#4
Posted 21 October 2011 - 04:43 PM
This is exciting news! wouldn't flashing an nvitems back up from an unlocked skate to a locked state unlock the latter?
#5
Posted 21 October 2011 - 04:44 PM
What do these locations mean, though? Someone help me out here 
#6
Posted 21 October 2011 - 04:48 PM
#7
Posted 21 October 2011 - 04:49 PM
whatcolour, on 21 October 2011 - 04:43 PM, said:
This is exciting news! wouldn't flashing an nvitems back up from an unlocked skate to a locked state unlock the latter?
No it doesn't - I've tried. I'm pretty sure the lock itself is in amss.mbn.
If you like my work or if I helped, click the Plus button.
#8
Posted 21 October 2011 - 05:00 PM
#9
Posted 21 October 2011 - 05:01 PM
glossywhite, on 21 October 2011 - 05:00 PM, said:
Yes okay, but I am not so daft as to try and flash stuff to my phone, no offence. I want to decode what my unlock code is, from the hex, without flashing anything at all.
Yeah - that's probably where I went wrong - I wish you luck
If you like my work or if I helped, click the Plus button.
#10
Posted 21 October 2011 - 05:03 PM
#11
Posted 21 October 2011 - 05:06 PM
#12
Posted 21 October 2011 - 05:06 PM
#13
Posted 21 October 2011 - 05:14 PM
#14
Posted 21 October 2011 - 05:15 PM
#15
Posted 21 October 2011 - 05:16 PM
Well putting 30303030000000 into a hex to decimal converter gave 13563782403981312. Might be worth a punt?
If you like my work or if I helped, click the Plus button.
#16
Posted 21 October 2011 - 05:17 PM
glossywhite, on 21 October 2011 - 04:29 PM, said:
Yessss! I have read out NVITEMS using QPST on Windows, by putting a clean, brand new OMC into FTM mode:
Look: http://android.modac...ad-all-nvitems/
Look: http://android.modac...ad-all-nvitems/
Looks like what you get when you don't have the sp code right (or the flash code).
At least fairly often (I know of a few instances at least) to read all the nvitems from diag mode you need either a hardcoded sp code
or a device specific flash code (even then you cannot get them all with QPST - Can with Revskills or PSAS though)
(Far too much stuff is all 0000's)
#17
Posted 21 October 2011 - 05:18 PM
#18
Posted 21 October 2011 - 05:20 PM
unrandomsam, on 21 October 2011 - 05:17 PM, said:
Looks like what you get when you don't have the sp code right (or the flash code).
At least fairly often (I know of a few instances at least) to read all the nvitems from diag mode you need either a hardcoded sp code
or a device specific flash code (even then you cannot get them all with QPST - Can with Revskills or PSAS though)
(Far too much stuff is all 0000's)
At least fairly often (I know of a few instances at least) to read all the nvitems from diag mode you need either a hardcoded sp code
or a device specific flash code (even then you cannot get them all with QPST - Can with Revskills or PSAS though)
(Far too much stuff is all 0000's)
Any idea what this code could be for the OMC? What was it for the OSF?
If you like my work or if I helped, click the Plus button.
#19
Posted 21 October 2011 - 05:22 PM
#20
Posted 21 October 2011 - 05:27 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account




Back to top









