http://support.razerzone.com/mobile/razer-phone. At the bottom of the page is 4 download links for source code for the Razer phone. Hope this kick starts the dev scene here.
and so it begins. send me a private message on irc for alpha quality test builds. (links in signature, /msg jcadduono hi)@jcadduono I summon you! lol
Is this what you will need to Build Twrp for our phones?
I'm really hoping the answer is yes. I'm twitching over here without root.
And on that note if you need a tester count me in.
Well we tried. So close but yet so far :crying:and so it begins. send me a private message on irc for alpha quality test builds. (links in signature, /msg jcadduono hi)
(not dangerous, just mostly non-functional to get values i need to make it functional)
update: the device does not have a recovery partition, so i am unable to support it, perhaps @Dees_Troy or someone else that is familiar with A/B devices can look at it?
while it might be possible to flash the image to boot partition, without a copy of original razer phone boot image you would have no way to ever boot your device again.
too risky for me to work with, sorry guys!
![]()
i will upload my source trees for kernel & device tree for anyone who wishes to take it upon themselves
proof it is an A/B device: (man why didn't you guys tell me earlier! lol)
![]()
A/B has nothing to do with Treble.I could be wrong but I think a/b would mean the razer is setup for treble.
Been doing a lot of reading on this as well but looks like we have reached another dead end. Our phones don't have a recovery partition. The recovery.img is now inside the Boot.img like on the Pixel phones. So even though we have the Kernel sources now with out the original Boot.img we can not boot into a custom recovery. All we can now is wait on Razer to release the system images which they seem to be taking their sweet time withNot that this is any help, but for the Xiaomi Mi A1 (if I'm reading all this right) it's a A/B type device. They got twrp working and here is the link to the page and link to source code
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472 Xda page
https://github.com/mohancm100/recovery_device_xiaomi_tissot Source code page
Do you mean to temporarily boot into twrp through fastboot?We Can try to verify if fastboot boot twrp.img work. My Razer Will arrive in Italy in 1 week
It won't. The fastboot boot command is not recognized by the device.We Can try to verify if fastboot boot twrp.img work. My Razer Will arrive in Italy in 1 week
Thanks for your effortand so it begins. send me a private message on irc for alpha quality test builds. (links in signature, /msg jcadduono hi)
(not dangerous, just mostly non-functional to get values i need to make it functional)
update: the device does not have a recovery partition, so i am unable to support it, perhaps @Dees_Troy or someone else that is familiar with A/B devices can look at it?
while it might be possible to flash the image to boot partition, without a copy of original razer phone boot image you would have no way to ever boot your device again.
too risky for me to work with, sorry guys!
![]()
i will upload my source trees for kernel & device tree for anyone who wishes to take it upon themselves
proof it is an A/B device: (man why didn't you guys tell me earlier! lol)
![]()
I hate A/B devices on paper it sounds good but imo it's really nothing special especially for us who hit the update button anyway and have to sit there waiting. not to mention the issues it causes for custom ROMS.and so it begins. send me a private message on irc for alpha quality test builds. (links in signature, /msg jcadduono hi)
(not dangerous, just mostly non-functional to get values i need to make it functional)
update: the device does not have a recovery partition, so i am unable to support it, perhaps @Dees_Troy or someone else that is familiar with A/B devices can look at it?
while it might be possible to flash the image to boot partition, without a copy of original razer phone boot image you would have no way to ever boot your device again.
too risky for me to work with, sorry guys!
![]()
i will upload my source trees for kernel & device tree for anyone who wishes to take it upon themselves
proof it is an A/B device: (man why didn't you guys tell me earlier! lol)
![]()
Yep. It's an A/B device without a recovery partition. This is why I decided to leave it to the professionals instead of attempting to flash my own hacky build of TWRP. I pulled it off for the Z2 Play but I'm not taking chances on my Razer since it has become my primary device.I hate A/B devices on paper it sounds good but imo it's really nothing special especially for us who hit the update button anyway and have to sit there waiting. not to mention the issues it causes for custom ROMS.
Thanks for all of the effort! :3Yep. It's an A/B device without a recovery partition. This is why I decided to leave it to the professionals instead of attempting to flash my own hacky build of TWRP. I pulled it off for the Z2 Play but I'm not taking chances on my Razer since it has become my primary device.
I have purchased the device for Dees_Troy (just did this today, so hold your horses) to do an officially supported port of TWRP. He's explained to me that it should be possible to pull partition images to serve as factory images once he gets TWRP working on the device. I'll likely host them myself once we get something going.
I spoke with Dees_Troy and can confirm that this user did indeed buy a Razer Phone for him. Major props to you.I have purchased the device for Dees_Troy (just did this today, so hold your horses) to do an officially supported port of TWRP. He's explained to me that it should be possible to pull partition images to serve as factory images once he gets TWRP working on the device. I'll likely host them myself once we get something going.