happyz
/
dpt-tools
1
0
Fork 0
Code Issues 11 Pull Requests Packages Projects Releases Wiki Activity

Cannot flash modified boot.img to obtain ADB access #42

New Issue
Closed
opened 2018-12-22 15:43:52 -08:00 by tartakis · 2 comments
tartakis commented 2018-12-22 15:43:52 -08:00 (Migrated from github.com)
Copy Link

I am stuck at the above step. My steps:

  1. Issue restore-bootimg command
  2. Copy boot-1.4.01.16100-mod-happyz-181214.img to the attached mass storage device, rename it to boot.img.bak, eject mass storage device, press return
  3. The script reports the md5 checksum of the boot.img.bak file I backed-up with backup-bootimg command before and not of the new file

Any ideas?

Thanks!

I am stuck at the above step. My steps: 1. Issue `restore-bootimg` command 2. Copy `boot-1.4.01.16100-mod-happyz-181214.img` to the attached mass storage device, rename it to `boot.img.bak`, eject mass storage device, press return 3. The script reports the md5 checksum of the `boot.img.bak` file I backed-up with `backup-bootimg` command before and not of the new file Any ideas? Thanks!
HappyZ commented 2018-12-22 15:48:21 -08:00 (Migrated from github.com)
Copy Link

it's probably due to unsuccessful umount in the tool which didn't check properly. Have you patched the updater bash? If so, you can directly flash the pkg with this boot img in the normal boot up mode. It's at https://github.com/HappyZ/dpt-tools/tree/master/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img

another way is to reboot into diagnosis mode and retry the restore without copying the file

it's probably due to unsuccessful umount in the tool which didn't check properly. Have you patched the updater bash? If so, you can directly flash the pkg with this boot img in the normal boot up mode. It's at https://github.com/HappyZ/dpt-tools/tree/master/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img another way is to reboot into diagnosis mode and retry the restore without copying the file
tartakis commented 2018-12-22 16:27:46 -08:00 (Migrated from github.com)
Copy Link

I seem to have resolved the issue by issuing rm boot.img.bak from the command line in the diagnosis mode. When the mass storage device appeared, the file boot.img.bak was still there! But this time the right file (judged from the md5 checksum) was flashed.

I seem to have resolved the issue by issuing `rm boot.img.bak` from the command line in the diagnosis mode. When the mass storage device appeared, the file `boot.img.bak` was still there! But this time the right file (judged from the md5 checksum) was flashed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
develop
Labels
Clear labels   
Customized PKG

customized pkg related discussions

  
Dup

This issue or pull request already exists

  
Enhancement

New feature or request

  
Help Needed

need help/testers

  
Invalid

This doesn't seem right

  
Official PKG

official pkg related discussions

  
Question

Further information is requested

  
Script Bug

Something isn't working

  
Taobao PKG

taobao fw related discussions

  
Wont Fix

This will not be worked on

No Label
Customized PKG
Dup
Enhancement
Help Needed
Invalid
Official PKG
Question
Script Bug
Taobao PKG
Wont Fix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: happyz/dpt-tools#42
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?