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

What work would be needed to get this one oneplus 3 #27

Open
hughdavenport opened this issue Aug 30, 2016 · 13 comments
Open

What work would be needed to get this one oneplus 3 #27

hughdavenport opened this issue Aug 30, 2016 · 13 comments

Comments

@hughdavenport
Copy link

I would be interested in learning the process, and helping out as much as I can :)

@retsifp
Copy link
Contributor

retsifp commented Aug 31, 2016

Here is a description how it works for the Fairphone FP2. I think it could be possible that it works very similar with the Oneplus 3, you'll have to create a file like this one and then do the corresponding steps. 😉

@hughdavenport
Copy link
Author

Cool, that looks doable. One question, where do you get the http://storage.googleapis.com/fairphone-updates/526aa40f-3657-4c85-82ef-ff82ebc3d1b1/FP2-gms63-1.6.2-ota.zip from?

Cheers,

Hugh

@retsifp
Copy link
Contributor

retsifp commented Sep 4, 2016

I think there are two ways to get this URL:

  • Search the Internet for it. Fairphone does publish this URL when it releases a new Firmware, maybe OnePlus does as well. (Edit: Found it.)
  • Spoof the updater-request (The updater on your phone). This can be tricky if it is HTTPS-Protected, but on my Fairphone there is the possibility to switch to HTTP, so I can easily spoof it by recording the traffic in my router and analyzing it via wireshark.

Regards,
Thomas.

@hughdavenport
Copy link
Author

Would it be based on the original oneplus rom? otherwise I'm using paranoid android, so would they be supplying the update?

I've tried using the original boot img option (dd'd it from recovery), but that gets into an endless boot, until I flash back the original so probably not a good go.

@retsifp
Copy link
Contributor

retsifp commented Sep 4, 2016

You'll always have to use the boot.img that comes with your ROM. So if you use paranoid Android, use their update-package to extract the boot.img.

@hughdavenport
Copy link
Author

Hmm ok, got the boot.img from the rom zip that I flashed it with and ran the build script, but still getting endless boot loop. Do you know any way I can get logs from device while booting?

@Lrs121
Copy link

Lrs121 commented Sep 4, 2016

It may be related to issue #24 where the modified boot image does not boot.

@hughdavenport
Copy link
Author

Cool, commented on that. Might try stock or CM as well to see if I have similar issues.

@hughdavenport
Copy link
Author

CM works fine with their extracted boot.img run through this. Well didn't test that it had superuser working after boot, but it booted after flashing, which is a good sign

@hughdavenport
Copy link
Author

Ok, CM boots, has root, and superuser app works once phone booted. Will investigate how to get it working with PA as I was hoping to try that out :)

@hughdavenport
Copy link
Author

Oh, for contributing it back, how should I name the folders? Based on the rom name and version?

@Lrs121
Copy link

Lrs121 commented Sep 5, 2016

ive only setup stock images in the past. the trick is to have the boot.img available for download, like how it is with the nexus and nvidia devices (i use these as an example because im most familiar with them).
the typical format is like this known-imgs/manufacturer/device-codename/rom-version-number
with the rom-version-number being a plain text file that includes the download link and how far the download has to be extracted to get to the boot.img
for example known-imgs/nexus/shamu/NPD90G

@hughdavenport
Copy link
Author

Cool. Though i guess it may not be necessary to create a patch as i could just install the zip on the public site and that patched it fine. I guess it could be helpful for people wanting to do it manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants