This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - critor
Pages: 1 ... 21 22 [23] 24 25 ... 137
331
« on: June 14, 2013, 07:39:26 am »
Persy, could you please add the "width=550" parameter to your last image bbcode in the 1st post?
Thanks.
332
« on: June 08, 2013, 10:02:11 am »
After some tries,I'm sure that pin 21 and pin 19 can't be TCK.
To critor: can I dump the OS with a CX running CM OS?
Maybe.
333
« on: June 06, 2013, 07:29:47 am »
You can't install Ndless? Why?
But wait... you're using a CX CAS?
Does the TI-Nspire CM prototype have CAS or not?
334
« on: June 06, 2013, 05:29:07 am »
Strange, I've allready tried this and it did work.
Maybe he didn't use the latest nLaunch CX version.
The original leaked version had no support for TI-Nspire CM OSes.
TI-Planet hosts an enhanced version called 'nLaunchy' where the CM OSes support has been added.
335
« on: June 06, 2013, 05:16:10 am »
It might be possible to send the OS to a computer which does act like it's another calculator.
This has been done once to dump non-CAS CX OS 3.0.2.1793, and we're currently discussing this.
For the dumping with two calculators, you need to be able to send an OS between them, and a special Ndless tool on the receiving unit.
So in theory, you need two calculators which share the same model ID, and OS/Ndless 3.1 on the receiving unit.
It *might* be possible to let the TI-Nspire CM sending its OS to the TI-Nspire CX with:
Choice A) installing on the CX a tool from Levak which does enable the 'CM' mode (this was in order to install the disctionnary)
Choice B) using nLaunch on the CX in order to run the CM OS 3.1
Choice C) using a hacked nsNandMgr on the CX in order to change its model ID from non-CAS CX to non-CAS CM
We can't be sure the OS transfer will work as we don't know which calculator does check and how before the OS is sent.
I'm confident with choice B.
Choice C might be dangerous.
Please give us time - let us think about it: we don't want you to make anything dangerous, and we don't want to make you try many things.
And if you can dump it with a simple tool acting as another calculator on the computer, this will be much easier.
336
« on: June 06, 2013, 05:04:18 am »
In theory, no.
The model ID is different, and the transfer will be denied.
337
« on: June 05, 2013, 06:41:53 am »
Yes we have tools which do print the Boot1/Boot2/Diags data on RS232, but adapting them for your OS would require to dump the OS first. I've just sent an email, asking if somebody had an idea to help you. Let's see in the next few days... In the worst case, money isn't a problem. 
338
« on: June 05, 2013, 06:30:52 am »
The exploits used by Ndless on production OS 3.1 are likely present on your development OS 3.1.
If Ndless 3.1 doesn't work, a special tool or light Ndless could be developped for your model.
I can see several ways for now:
- installing Ndless 3.1 and running Polydumper CX (which might not work if your OS is too different - you'll have to solve your battery problem first)
- sending the OS to another Ndlessed production TI-Nspire CM
- using specific tools exploiting some flaws, but developing them will be easier and faster if the OS is dumped first
- lending the calculator to one of us if you trust us
339
« on: June 05, 2013, 06:20:47 am »
Ok, fine. Ndless 'might' work. It depends if most syscalls addresses are the same or not. If Ndless works, you can dump everything with Polydumper CX. For exemple, Ndless 1.7/2.0 was designed for OS 1.7.2741, but could also be used with the older OS 1.7.2733 we managed to dump after the release. Using a charged rechargeable battery from another TI-Nspire CM/CX, TI-Nspire TouchPad or TI-84 Plus C Silver Edition should solve your problem.
340
« on: June 05, 2013, 06:10:29 am »
You should stop trying to install an OS on your prototype.
You may just manage to erase your special 3.1.0.236 development OS, and you can't install released production OSes on your prototype as it's using the development RSA keys instead of the production RSA keys.
We have never dumped any TI-Nspire CM development OS - if you erase the OS, the calculator will remain unusable - we'll have no way to repair it.
That's why the 1st priority should be to try to dump your 3.1.0.236 development OS.
If you find a production TI-Nspire CM, this can be performed quite easily.
341
« on: June 05, 2013, 04:57:57 am »
Ok, great! We need to dump it now  Would you be ok to try some dumping tools? Nothing dangerous, but it might require several tries. By the way, can you check the Diagnostic Software menu and version? Hold Esc+Menu+Minus while pressing reset. (the minus on the right near the plus - not the sign minus)Thanks again for this great discovery. The easiest way but not the cheapest is having two TI-Nspire CM and to star by dumping the OS. You send the OS to the Ndlessed production unit, and I've got an Ndless tool which does get it before the installation is triggered (and aborted as it's a development OS). Once the OS is dumped, it can be studied/tested on emulators, and some specific tools for dumpes the Boot1/Boot2/Diags can be developped.
342
« on: June 04, 2013, 08:31:59 pm »
Great - very interesting! It's not a prototype which was given by TI for evaluation to some teacher/student, it's clearly a prototype coming from the development team - congratulations! Would it be possible to have a picture of the back of the case? It usually have interesting informations about prototypes in the serial, like the EVT/DVT/PVT codes. Could we also have a picture of the ASIC 'Texas Instruments' chip? The labels are visible on the last image but not readable, and they're not visible in the previous image. As reference, here are pictures of the production TI-Nspire CM-C boards: http://tiplanet.org/forum/gallery/image_page.php?album_id=119&image_id=1359
343
« on: June 04, 2013, 01:24:17 pm »
The big hole is for the J04/debug connector which is supposed to have JTAG and is not soldered on production models.
For now, can we have the OS/Boot2/Boot1 versions?
Thanks.
It doesn't boot up,and I don't know what to do now.Any pinout information about J04?I have a Jlink
Unfortunately, as far as I know nobody has achieved (tried?) a JTAG connection on TI-Nspire CX/CM for now. It's a proprietary connector, we don't know much about the pinout. Does it at least turn on or not at all? Please, don't throw it away - even if your prototype is not working, it has the J04 connector missing on production models, and this could be very useful. Could we have a picture of the back with its serial visible in order to identify what kind of prototype it is? Could we have a picture of the motherboard once opened with those strange wires connections? And could we have a big picture of the J04 connector, as you have the only one which leaked in the world for now? Thank you very much.
344
« on: June 04, 2013, 05:34:10 am »
The big hole is for the J04/debug connector which is supposed to have JTAG and is not soldered on production models.
For now, can we have the OS/Boot2/Boot1 versions?
Thanks.
345
« on: May 23, 2013, 06:22:11 am »
We don't ask you to censor anything (neither video nor code). It's a treasure hunt, you have the right to share/confront your discoveries and ask for the help of the whole Internet. Just remember that only the best entry will give the right to choose between all prizes, including the TI-Nspire CX and the TI-84 Plus C. The second best entry will only choose among what's left...
Pages: 1 ... 21 22 [23] 24 25 ... 137
|
Show Posts
