Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get Diagnosis Mode and Patch Updater Script failed #142

Closed
redirus opened this issue Nov 14, 2019 · 9 comments
Closed

Get Diagnosis Mode and Patch Updater Script failed #142

redirus opened this issue Nov 14, 2019 · 9 comments
Labels
Help Needed need help/testers Question Further information is requested

Comments

@redirus
Copy link

redirus commented Nov 14, 2019

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
Copy link
Owner

HappyZ commented Nov 19, 2019

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?

@HappyZ HappyZ added Help Needed need help/testers Question Further information is requested labels Nov 19, 2019
@redirus
Copy link
Author

redirus commented Nov 19, 2019

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
Copy link
Owner

HappyZ commented Nov 24, 2019

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

@HappyZ
Copy link
Owner

HappyZ commented Nov 24, 2019

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..

@HappyZ HappyZ closed this as completed Nov 24, 2019
@redirus
Copy link
Author

redirus commented Nov 24, 2019

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
Copy link
Owner

HappyZ commented Nov 25, 2019

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
Copy link
Author

redirus commented Nov 25, 2019

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

@duanliyu
Copy link

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

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

@HappyZ
Copy link
Owner

HappyZ commented Apr 28, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Needed need help/testers Question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants