The tools didn't work in my new cp1 #87

Closed
opened 2019-05-02 09:21:15 -07:00 by wxredstar · 8 comments
wxredstar commented 2019-05-02 09:21:15 -07:00 (Migrated from github.com)

Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the steps, but it didn't have any effect. Maybe sony have patched and upgraded the OS. Does anybody succeed recently

Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the steps, but it didn't have any effect. Maybe sony have patched and upgraded the OS. Does anybody succeed recently
HappyZ commented 2019-05-02 09:32:27 -07:00 (Migrated from github.com)

when you say it didn't have any effect, you mean even from step 1 it didn't
print any messages on the screen after flashing the fw.pkg?

  1. did it reboot?
  2. are you able to get into diagnosis mode?

On Thu, May 2, 2019 at 11:21 AM wxredstar notifications@github.com wrote:

Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the
steps, but it didn't have any effect. Maybe sony have patched and upgraded
the OS. Does anybody succeed recently


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HappyZ/dpt-tools/issues/87, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDVEKT642RIFMGKJGUBC5DPTMIHZANCNFSM4HJ74AEQ
.

when you say it didn't have any effect, you mean even from step 1 it didn't print any messages on the screen after flashing the fw.pkg? 1. did it reboot? 2. are you able to get into diagnosis mode? On Thu, May 2, 2019 at 11:21 AM wxredstar <notifications@github.com> wrote: > Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the > steps, but it didn't have any effect. Maybe sony have patched and upgraded > the OS. Does anybody succeed recently > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/HappyZ/dpt-tools/issues/87>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABDVEKT642RIFMGKJGUBC5DPTMIHZANCNFSM4HJ74AEQ> > . >
wxredstar commented 2019-05-02 09:44:46 -07:00 (Migrated from github.com)

Flashing pkg all succeed in Step1, step2 and step3, but adb can’t find device.
The system reboot after flashing pkgs.
I can get into diagnosis mode by pushing power key and home key.

| |
wxredstar
|
|
邮箱:wxredstar@126.com
|

Signature is customized by Netease Mail Master

On 05/03/2019 00:32, HappyZ wrote:
when you say it didn't have any effect, you mean even from step 1 it didn't
print any messages on the screen after flashing the fw.pkg?

  1. did it reboot?
  2. are you able to get into diagnosis mode?

On Thu, May 2, 2019 at 11:21 AM wxredstar notifications@github.com wrote:

Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the
steps, but it didn't have any effect. Maybe sony have patched and upgraded
the OS. Does anybody succeed recently


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HappyZ/dpt-tools/issues/87, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDVEKT642RIFMGKJGUBC5DPTMIHZANCNFSM4HJ74AEQ
.

--
BR | Yanzi Zhu
https://happyz.me


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Flashing pkg all succeed in Step1, step2 and step3, but adb can’t find device. The system reboot after flashing pkgs. I can get into diagnosis mode by pushing power key and home key. | | wxredstar | | 邮箱:wxredstar@126.com | Signature is customized by Netease Mail Master On 05/03/2019 00:32, HappyZ wrote: when you say it didn't have any effect, you mean even from step 1 it didn't print any messages on the screen after flashing the fw.pkg? 1. did it reboot? 2. are you able to get into diagnosis mode? On Thu, May 2, 2019 at 11:21 AM wxredstar <notifications@github.com> wrote: > Hi, I bought cp1 several weeks ago. I use HappyZ's tools following the > steps, but it didn't have any effect. Maybe sony have patched and upgraded > the OS. Does anybody succeed recently > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/HappyZ/dpt-tools/issues/87>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABDVEKT642RIFMGKJGUBC5DPTMIHZANCNFSM4HJ74AEQ> > . > -- BR | Yanzi Zhu https://happyz.me — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
HappyZ commented 2019-05-02 12:57:11 -07:00 (Migrated from github.com)

Hi there, ADB is indeed slow to start now as I wasn't using a stock adbd service. Instead I used insecure adbd from Chainfire (for good if anything bricks). From my own experience, you do have to wait for a while (1-2min sometimes) for adbd to kick off (after device boots up). If not appearing, try several times the following:

# unplug and plug back in the cable
adb kill-server
adb devices
Hi there, ADB is indeed slow to start now as I wasn't using a stock adbd service. Instead I used insecure adbd from Chainfire (for good if anything bricks). From my own experience, you do have to wait for a while (1-2min sometimes) for adbd to kick off (after device boots up). If not appearing, try several times the following: ``` # unplug and plug back in the cable adb kill-server adb devices ```
wxredstar commented 2019-05-03 04:58:26 -07:00 (Migrated from github.com)

MBP:platform-tools kang$ adb kill-server
MBP:platform-tools kang$ adb devices
List of devices attached

  • daemon not running; starting now at tcp:5037
  • daemon started successfully

Hi, HappyZ, I tried many times, but adb didn't attach any device. Maybe sony has patched the backdoor in new OS.

MBP:platform-tools kang$ adb kill-server MBP:platform-tools kang$ adb devices List of devices attached * daemon not running; starting now at tcp:5037 * daemon started successfully Hi, HappyZ, I tried many times, but adb didn't attach any device. Maybe sony has patched the backdoor in new OS.
HappyZ commented 2019-05-03 17:26:34 -07:00 (Migrated from github.com)

hi you can try the old pkg in my commit history: e766bb7187/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img/FwUpdater.pkg and see if this can work.

Use the same fw update firmware method. Do not download the old code other than the PKG.

In this old version, you will need to address unauthorized problem, on your computer (Mac or Linux),

mv ~/.android/adbkey ~/.android/adbkey_bak
cp adbkey ~/.android/adbkey
adb kill-server
adb devices

the adbkey file is at e766bb7187/python_api/assets/adbkey

hi you can try the old pkg in my commit history: https://github.com/HappyZ/dpt-tools/blob/e766bb71870ad56222c28bcbede49b0f6708b4b2/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img/FwUpdater.pkg and see if this can work. Use the same `fw` update firmware method. Do not download the old code other than the PKG. In this old version, you will need to address `unauthorized` problem, on your computer (Mac or Linux), ``` mv ~/.android/adbkey ~/.android/adbkey_bak cp adbkey ~/.android/adbkey adb kill-server adb devices ``` the `adbkey` file is at https://github.com/HappyZ/dpt-tools/blob/e766bb71870ad56222c28bcbede49b0f6708b4b2/python_api/assets/adbkey
wxredstar commented 2019-05-04 19:28:20 -07:00 (Migrated from github.com)

Hi HappyZ , I connectd my cp1 to a Windows pc. The computer found usb storage device(my mac pc detected nothing but sony digit paper app well done), then I used adb, it works well with your official pkgs. I'm using koreader now. Thank for your great work!

Hi HappyZ , I connectd my cp1 to a Windows pc. The computer found usb storage device(my mac pc detected nothing but sony digit paper app well done), then I used adb, it works well with your official pkgs. I'm using koreader now. Thank for your great work!
lifuli123 commented 2019-07-31 06:43:21 -07:00 (Migrated from github.com)

dear wxredstar,how do you solve the issue? I used windows also,but use adb devices ,I can not find the dpt. 3ks!!!
image

dear wxredstar,how do you solve the issue? I used windows also,but use adb devices ,I can not find the dpt. 3ks!!! ![image](https://user-images.githubusercontent.com/22239909/62216713-dd171d00-b3db-11e9-8435-e448dbb7d49e.png)
stevenvo commented 2020-06-21 01:50:09 -07:00 (Migrated from github.com)

hi you can try the old pkg in my commit history: e766bb7187/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img/FwUpdater.pkg and see if this can work.

Use the same fw update firmware method. Do not download the old code other than the PKG.

In this old version, you will need to address unauthorized problem, on your computer (Mac or Linux),

mv ~/.android/adbkey ~/.android/adbkey_bak
cp adbkey ~/.android/adbkey
adb kill-server
adb devices

the adbkey file is at e766bb7187/python_api/assets/adbkey

Just download your adbkey and it worked for me! thanks mate.

> hi you can try the old pkg in my commit history: https://github.com/HappyZ/dpt-tools/blob/e766bb71870ad56222c28bcbede49b0f6708b4b2/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img/FwUpdater.pkg and see if this can work. > > Use the same `fw` update firmware method. Do not download the old code other than the PKG. > > In this old version, you will need to address `unauthorized` problem, on your computer (Mac or Linux), > > ``` > mv ~/.android/adbkey ~/.android/adbkey_bak > cp adbkey ~/.android/adbkey > adb kill-server > adb devices > ``` > > the `adbkey` file is at https://github.com/HappyZ/dpt-tools/blob/e766bb71870ad56222c28bcbede49b0f6708b4b2/python_api/assets/adbkey Just download your adbkey and it worked for me! thanks mate.
Sign in to join this conversation.
No description provided.