Get Diagnosis Mode and Patch Updater Script failed

redirus commented

2019-11-14 06:31:45 -08:00

(Migrated from github.com)

r-6-105-25-172:dpt-tools-master yy$ python3 dpt-tools.py -ip xxx
===========
 DPT Tools
===========
Thanks for using DPT Tools. Type `help` to show this message.
Supported commands:
    fw        -- update firmware
    diagnosis -- enter diagnosis mode (to gain adb, su, etc.)
    exit/quit -- leave the tool

>>> fw
[info] Please make sure you have charged your battery before this action.
>>> Please enter the pkg file path: /Users/yy/Downloads/fw.pkg 
>>> Pleae confirm /Users/yy/Downloads/fw.pkg is the pkg file to use [yes/no]: yes
[info] fw updating in progress.. do NOT press anything..
[info] Success!
**I do not see this.**
"You will see multiple lines printing, starting with the LICENSE. For every step, it will print the files being changed and pause for 30s. You can press the HOME key to bypass the waiting.
 **I enter diagnosis model to check."**

>>> Black square on the screen? [yes/no]: yes
>>> Enter the serial port [/dev/tty.usbmodem01]: /dev/tty.usbmodem14201
[error] failed to login..
[info] got out of diagnosis

I worked on my Mac and the rpt version is 1.6.02.06240.
I followed all the instructions. Any suggestions?

``` r-6-105-25-172:dpt-tools-master yy$ python3 dpt-tools.py -ip xxx =========== DPT Tools =========== Thanks for using DPT Tools. Type `help` to show this message. Supported commands: fw -- update firmware diagnosis -- enter diagnosis mode (to gain adb, su, etc.) exit/quit -- leave the tool >>> fw [info] Please make sure you have charged your battery before this action. >>> Please enter the pkg file path: /Users/yy/Downloads/fw.pkg >>> Pleae confirm /Users/yy/Downloads/fw.pkg is the pkg file to use [yes/no]: yes [info] fw updating in progress.. do NOT press anything.. [info] Success! **I do not see this.** "You will see multiple lines printing, starting with the LICENSE. For every step, it will print the files being changed and pause for 30s. You can press the HOME key to bypass the waiting. **I enter diagnosis model to check."** >>> Black square on the screen? [yes/no]: yes >>> Enter the serial port [/dev/tty.usbmodem01]: /dev/tty.usbmodem14201 [error] failed to login.. [info] got out of diagnosis ``` I worked on my Mac and the rpt version is 1.6.02.06240. I followed all the instructions. Any suggestions?

HappyZ commented

2019-11-18 20:30:10 -08:00

(Migrated from github.com)

Sorry for the late response. When you say "I do not see this", what did you see?

It looks like there have been several people reporting this, I'll check their firmware updates this weekend to see what is going on. BTW, when did you purchase your device?

Sorry for the late response. When you say "I do not see this", what did you see? It looks like there have been several people reporting this, I'll check their firmware updates this weekend to see what is going on. BTW, when did you purchase your device?

redirus commented

2019-11-18 21:11:47 -08:00

(Migrated from github.com)

Sorry for the late response. When you say "I do not see this", what did you see?

It looks like there have been several people reporting this, I'll check their firmware updates this weekend to see what is going on. BTW, when did you purchase your device?

I just bought it. The production date is Sep 2019. I did not see anything but the dpt just restarted and showed update failure.
Sony just upgraded the new firmware. If you keep updated on this, the problems will be of little importance if you can not fix it quickly.

> Sorry for the late response. When you say "I do not see this", what did you see? > > It looks like there have been several people reporting this, I'll check their firmware updates this weekend to see what is going on. BTW, when did you purchase your device? I just bought it. The production date is Sep 2019. I did not see anything but the dpt just restarted and showed update failure. Sony just upgraded the new firmware. If you keep updated on this, the problems will be of little importance if you can not fix it quickly.

HappyZ commented

2019-11-23 21:12:37 -08:00

(Migrated from github.com)

Please refer to #141 . It seems they have fixed the updater script in diagnosis mode after Sept. 2019.

HappyZ commented

2019-11-23 21:31:47 -08:00

(Migrated from github.com)

Just a bit more info. The new firmware does not fix the updater script bug. But it seems they choose to fix the bug for devices only after Sept. 2019.. What a weird decision..

redirus commented

2019-11-23 22:16:51 -08:00

(Migrated from github.com)

Sorry but still confused. Do you mean that we can not root devices produced after Sep 2019 even when we update to the newest firmware now?

HappyZ commented

2019-11-24 17:04:23 -08:00

(Migrated from github.com)

Yes. to clarify:

For devices manufactured after Sept 2019 (based on what people reported), they can no longer be rooted as they have a secured updater script in diagnosis mode.

For devices made before then, even with the latest firmware, they can be rooted, as they have an insecure diagnosis mode.

Yes. to clarify: For devices manufactured after Sept 2019 (based on what people reported), they can no longer be rooted as they have a secured updater script in diagnosis mode. For devices made before then, even with the latest firmware, they can be rooted, as they have an insecure diagnosis mode.

redirus commented

2019-11-24 23:17:30 -08:00

(Migrated from github.com)

Thanks. I got some sense about 'weird'. I guess new solutions may come up in the near future.

duanliyu commented

2020-04-27 17:24:50 -07:00

(Migrated from github.com)

Thanks. I got some sense about 'weird'. I guess new solutions may come up in the near future.

请问目前有解决方法了吗？

> Thanks. I got some sense about 'weird'. I guess new solutions may come up in the near future. 请问目前有解决方法了吗？

HappyZ commented

2020-04-27 17:49:35 -07:00

(Migrated from github.com)

Right now unless you know the official diagnosis password, no.

I know someone was looking into other possible exploits. But I haven't heard from him since then.

Right now unless you know the official diagnosis password, no. I know someone was looking into other possible exploits. But I haven't heard from him since then.

Get Diagnosis Mode and Patch Updater Script failed #142