FORUMS
Remove All Ads from XDA

Rooting Sony's e-reader DPT-RP1 and DPT-CP1

20 posts
Thanks Meter: 10
 
By sartrism, Junior Member on 11th August 2017, 05:55 AM
Post Reply Email Thread
21st November 2018, 01:46 AM |#101  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by yanzi

No I didn't do any reset. I thought it was encryption as I never saw password prompt before. I guess if you don't set password protections on device, there should be no prompt. I did check the modded boot.img before I made changes and the version on my device are matched. There may be something wrong with the su script that changes device behavior.

Can you validate in diagnosis mode the following file exists in /system parition?
first mount partition `/dev/mmcblk0p9` and assuming mount point is `/mnt/Lucifer/` then:

/mnt/Lucifer/bin/app_process
/mnt/Lucifer/bin/app_process32
/mnt/Lucifer/bin/app_process_init

And oh I did find a small bug in the script: you should `mv /mnt/Lucifer/bin/.ext/su /mnt/Lucifer/bin/.ext/.su`

I find where your problem could be. It shall miss file `/mnt/Lucifer/bin/app_process` and `/mnt/Lucifer/bin/app_process_init` due to some bugs I had in the script. Sorry about that. I'll write you a step-by-step guide to fix it.

I remember when I checked, app_process did not exist. I'm assuming that's where the problem is as that's a pretty essential file.

I just copied the latest official FwUpdater.pkg to my device and ran it with start_eufwupdater.sh. It booted fine to the setup screen after that, so at least I know that as long as I can boot into diag I can recover it.

Another thing I have found is that if you're in diag and run /usr/local/bin/mass_storage, it'll mount as a mass storage device to your PC. Copying files that way is much faster than through serial. Then eject, ctrl-c,
Code:
mount /dev/mmcblk0p16 /mnt/sd
 
 
21st November 2018, 01:58 AM |#102  
Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by silvertriclops

Restored my original boot.img and it still gets stuck at the welcome screen. How do you disable encryption on this? I thought it was enabled by default and nothing you can do to change it.

Or are you running this right after you run /usr/local/bin/factory_reset.sh?

edit just ran factory_reset and it definitely wipes data (I had everything backed up of course) but still gets stuck on the welcome screen

Download the following file:
app_process32_original.tar.gz

And do the following (in diagnosis mode):
```
mount /dev/mmcblk0p9 /mnt/Lucifer/
cd /mnt/Lucifer/bin
rm app_process
rm app_process32
rm app_process32_original
rm app_process_bak
rm app_process_init
ln -s /system/xbin/daemonsu /mnt/Lucifer/bin/app_process
ln -s /system/xbin/daemonsu /mnt/Lucifer/bin/app_process32
```

Then use the tool to upload file unzipped from above tar by:
```
push-file
> Local folder path: app_process_original
> DPT file path: /mnt/Lucifer/bin
```
Then:
```
cp /mnt/Lucifer/bin/app_process_original /mnt/Lucifer/bin/app_process_init
chown 0.2000 /mnt/Lucifer/bin/app_process_init
chmod 0755 /mnt/Lucifer/bin/app_process_init
```

This should solve the problem.
21st November 2018, 02:02 AM |#103  
Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by silvertriclops

I remember when I checked, app_process did not exist. I'm assuming that's where the problem is as that's a pretty essential file.

I just copied the latest official FwUpdater.pkg to my device and ran it with start_eufwupdater.sh. It booted fine to the setup screen after that, so at least I know that as long as I can boot into diag I can recover it.

Another thing I have found is that if you're in diag and run /usr/local/bin/mass_storage, it'll mount as a mass storage device to your PC. Copying files that way is much faster than through serial. Then eject, ctrl-c,

Code:
mount /dev/mmcblk0p16 /mnt/sd

That's elegant. Well, I was just reinventing the wheel then. Good to know it works!

Good to hear, I wrote you a small recovery steps also.. I fixed the script (hopefully) so it wouldn't make the same mistake again.
21st November 2018, 02:21 AM |#104  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by yanzi

That's elegant. Well, I was just reinventing the wheel then. Good to know it works!

Good to hear, I wrote you a small recovery steps also.. I fixed the script (hopefully) so it wouldn't make the same mistake again.

Hi, thanks for the all those involved, you guys are amazing!
Now I am also trying to install a-the ABD on my device, but it appears to be unauthorized,
So how do I fix it, do I just kill add server, and request for reboot?
Also, how would adbkey(provided) help in this process?
Thanks!
21st November 2018, 02:40 AM |#105  
Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Anti-paradox

Hi, thanks for the all those involved, you guys are amazing!
Now I am also trying to install a-the ABD on my device, but it appears to be unauthorized,
So how do I fix it, do I just kill add server, and request for reboot?
Also, how would adbkey(provided) help in this process?
Thanks!

You just need to follow the key pairing process and provide the adbkey. I agree it is not a great approach but..

Backup your original adbkey from ~/.android/adbkey to ~/.android/adbkey_bak
And replace it with the provided one

After you got su you can replace /adb_keys with your own public key.

---------- Post added at 10:40 AM ---------- Previous post was at 10:25 AM ----------

Quote:
Originally Posted by silvertriclops

I remember when I checked, app_process did not exist. I'm assuming that's where the problem is as that's a pretty essential file.

I just copied the latest official FwUpdater.pkg to my device and ran it with start_eufwupdater.sh. It booted fine to the setup screen after that, so at least I know that as long as I can boot into diag I can recover it.

Another thing I have found is that if you're in diag and run /usr/local/bin/mass_storage, it'll mount as a mass storage device to your PC. Copying files that way is much faster than through serial. Then eject, ctrl-c,

Code:
mount /dev/mmcblk0p16 /mnt/sd

Ok I have tested the su part of the script and it should fully work now. Plz let me know.
21st November 2018, 02:44 AM |#106  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by yanzi

You just need to follow the key pairing process and provide the adbkey. I agree it is not a great approach but..

Backup your original adbkey from ~/.android/adbkey to ~/.android/adbkey_bak
And replace it with the provided one

After you got su you can replace /adb_keys with your own public key.

---------- Post added at 10:40 AM ---------- Previous post was at 10:25 AM ----------



Ok I have tested the su part of the script and it should fully work now. Plz let me know.

Thanks!, but how would you push the existing adbkey to the device to replace the old one?
I tried add -push no success.
Any ideas on how to do that? (did it already)
still working on it...
Ok, so it is still not authorized,
I backup the adbkey, along with adbkey.pub, so here is what it looks like now:
adbkey adbkey_bak adbkey_bak.pub
where the adbkey is the given one
Now how can I fix this issue?
21st November 2018, 02:53 AM |#107  
Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Anti-paradox

Thanks!, but how would you push the existing adbkey to the device to replace the old one?
I tried add -push no success.
Any ideas on how to do that?
many thanks!

Assuming your adbkey is in `/magic/path/adbkey`
And the public key is in `/magic/path/adbkey.pub` (should not be needed but just in case, it's here)
Detailed steps in a terminal is:
```
adb kill-server
cd ~/.android/
mv adbkey adbkey_bak
mv adbkey.pub adbkey.pub_bak
cp /magic/path/adbkey adbkey
cp /magic/path/adbkey.pub adbkey.pub
adb devices
```
And I think this should work

And after you get su, replace the /adb_keys in device to your own adbkey.pub, and restore your own private and public keys.
21st November 2018, 03:24 AM |#108  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by yanzi

Assuming your adbkey is in `/magic/path/adbkey`
And the public key is in `/magic/path/adbkey.pub` (should not be needed but just in case, it's here)
Detailed steps in a terminal is:
```
adb kill-server
cd ~/.android/
mv adbkey adbkey_bak
mv adbkey.pub adbkey.pub_bak
cp /magic/path/adbkey adbkey
cp /magic/path/adbkey.pub adbkey.pub
adb devices
```
And I think this should work

And after you get su, replace the /adb_keys in device to your own adbkey.pub, and restore your own private and public keys.

A lot of thanks, solved!
Turns out I rename the wrong file, silly mistake there.
21st November 2018, 03:33 AM |#109  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by yanzi

Download the following file:
Attachment 4648071

And do the following (in diagnosis mode):
```
mount /dev/mmcblk0p9 /mnt/Lucifer/
cd /mnt/Lucifer/bin
rm app_process
rm app_process32
rm app_process32_original
rm app_process_bak
rm app_process_init
ln -s /system/xbin/daemonsu /mnt/Lucifer/bin/app_process
ln -s /system/xbin/daemonsu /mnt/Lucifer/bin/app_process32
```

Then use the tool to upload file unzipped from above tar by:
```
push-file
> Local folder path: app_process_original
> DPT file path: /mnt/Lucifer/bin
```
Then:
```
cp /mnt/Lucifer/bin/app_process_original /mnt/Lucifer/bin/app_process_init
chown 0.2000 /mnt/Lucifer/bin/app_process_init
chmod 0755 /mnt/Lucifer/bin/app_process_init
```

This should solve the problem.

I wasn't able to get that to work. But since it looks like you updated the script I might as well try that again. Going to take a break and bike a few miles then factory reset my DPT again so I can try your updated script with a clean slate (no pun intended)

Anyone want to set up a discord server? That would be easier than checking this thread every few minutes, and once a solution is found we could post it here.
21st November 2018, 03:46 AM |#110  
Junior Member
Thanks Meter: 3
 
More
sudo access declined
I tried to ssh into the device and try some sudo commands, but it seems that I am not able to gain this su access.
This is what pops up when I type "get-su-bin"
[info] Mounting /system partition..
[error] name 'folder' is not defined
How would this be fixed?
Thanks Again!
21st November 2018, 03:51 AM |#111  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by Anti-paradox

I tried to ssh into the device and try some sudo commands, but it seems that I am not able to gain this su access.
This is what pops up when I type "get-su-bin"
[info] Mounting /system partition..
[error] name 'folder' is not defined
How would this be fixed?
Thanks Again!

Open python_api/libDPT.py

Find this line:
Code:
if not self.diagnosis_mkdir(folder):
Replace it with:

Code:
if not self.diagnosis_mkdir(mountpoint):
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes