View Single Post
Old 08-03-2017, 12:22 PM   #2356
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 912
Karma: 3000002
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by coplate View Post
@knc1

this is what I was thinking about in the previous post.

As I recall from the bricking, it is because of a bad uBoot.

I wonder if it is possible to put the uBoot and uImage from from 5.8.10, and the rootFS from PW3-4gb 5.7.4.

I can inspect the rootFS with TestDisk, and I cannot see anything hardware specific in it ( at least, nothing major, all of that shoudl be in the kernal uImage. ), and I have a strong suspicion this would work.

I am going to do this with the PW3-4G I have at home, just as a proof of concept, but to test on PW-32 I would need a volunteer to possibly brick thier device.

@anhyeuviolet, do you think your friend would be interested in testing this at all?
Before it comes to that point, perhaps there is someone with the device that is willing to do a serial JB? With that done it should be possible to retrieve some of the information you are interested in and then run some test software developed specifically to diagnose the situation.

Dave
dhdurgee is offline   Reply With Quote