Hello everyone.
I'm SafinWasi. I know I'm new to the Fire Phone forums,but I found something big,so I thought that I should post it here.
It seems that unlike the Kindle Fire Tablet series which used a TI OMAP based chipset,the Fire Phone uses a Qualcomm MSM based chipset. That being said,we should now have access to the Fire OS images for modding.
To those who have root:
Please use the following steps to get the boot and recovery images:
Using ES File Explorer,mount system and "/" path as rw- and navigate to /dev/block/msm_sdcc.1/by-name/ and copy "boot" and "recovery" to sdcard.
Please send the two images to me via PM or post it in this thread so that I may open them up for examining.
Click to expand...
Click to collapse
A big thanks to @I am M3 for helping me out to find these. And to the Moderators: Please move my thread if it is misplaced.
Thank you.
SafinWasi said:
Hello everyone.
I'm SafinWasi. I know I'm new to the Fire Phone forums,but I found something big,so I thought that I should post it here.
It seems that unlike the Kindle Fire Tablet series which used a TI OMAP based chipset,the Fire Phone uses a Qualcomm MSM based chipset. That being said,we should now have access to the Fire OS images for modding.
To those who have root:
A big thanks to @I am M3 for helping me out to find these. And to the Moderators: Please move my thread if it is misplaced.
Thank you.
Click to expand...
Click to collapse
Thank you once again for getting the ball rolling on this. I had (almost) lost hope!
Absolutely certain root is needed to pull any of the files. I have tried every method possible through ES (e-mail, BT, MMS, copying the file to /sdcard/, etc.)
Another thing I can try is to obtain root on my phone. Someone mentioned towelroot has many different versions floating around, I've only tried the v3 from geohot's site. I'll find some other sources & see if I can't get lucky.
I am M3 said:
Thank you once again for getting the ball rolling on this. I had (almost) lost hope!
Absolutely certain root is needed to pull any of the files. I have tried every method possible through ES (e-mail, BT, MMS, copying the file to /sdcard/, etc.)
Another thing I can try is to obtain root on my phone. Someone mentioned towelroot has many different versions floating around, I've only tried the v3 from geohot's site. I'll find some other sources & see if I can't get lucky.
Click to expand...
Click to collapse
No problem mate. If I can get a recovery working on this thing I can almost certainly port CM. But Amazon still hasn't posted the source code for Fire Phone
Sent from my device running CyanogenMod 11
SafinWasi said:
No problem mate. If I can get a recovery working on this thing I can almost certainly port CM. But Amazon still hasn't posted the source code for Fire Phone
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Judging by the 35,000 units sold, and not much interest / activity for this phone on XDA, I doubt anyone's requested it. I sent the following email to Amazon which "escalated" my issue, & also sent the email directly to Jeff Bezos. It's a long shot but let's hope it makes some noise. By AOSP guidelines, they are required to release the device's source code.
The Android Open Source Project (AOSP) has compliance guidelines for companies which produce & distribute devices containing the Android operating system. The recently released Fire Phone operates on the Fire OS, which is a modified version of Android 4.2 "Jelly Bean".
In order to comply with the AOSP guidelines, Amazon is required to release the source code for the Fire Phone device, which it has not.
Please make the source code available for download.
Thank you.
Click to expand...
Click to collapse
You rubbed it in their face mate!
Sent from my device running CyanogenMod 11
SafinWasi said:
You rubbed it in their face mate!
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Wow haha that was quick! Now we just need someone with root to pull the files.
@Dilbert1959 - Seems your device has root. Please follow @SafinWasi's guide above to pull the requested files.
Since the boot loader is locked, I doubt that custom recoveries would be possible, but SafeStrap is definitely a probability.
r3pwn said:
Since the boot loader is locked, I doubt that custom recoveries would be possible, but SafeStrap is definitely a probability.
Click to expand...
Click to collapse
I know. BTW,I added you to the github repo for fire phone source.
Sent from my device running CyanogenMod 11
SafinWasi said:
I know. BTW,I added you to the github repo for fire phone source.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Thanks. Do you have the phone?
Sent from my iPod touch using Tapatalk
r3pwn said:
Thanks. Do you have the phone?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Nope
Sent from my device running CyanogenMod 11
If anyone knows of a safe place for me to download old versions of towel root I can try to help with pulling the image. AT&T for some reason can't find my phone on their network so it's basically a paperweight and don't mind trying to help with this. If there are other methods I can try to root let me know as well. I can give them a shot when I have some down time.
pogfanatic said:
If anyone knows of a safe place for me to download old versions of towel root I can try to help with pulling the image. AT&T for some reason can't find my phone on their network so it's basically a paperweight and don't mind trying to help with this. If there are other methods I can try to root let me know as well. I can give them a shot when I have some down time.
Click to expand...
Click to collapse
Ok. Please contact Dilbert1959
Sent from my device running CyanogenMod 11
SafinWasi said:
Ok. Please contact Dilbert1959
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
I requested the tr.apk from @Dilbert1959 but have not gotten anything yet, however I used Google & tried all versions with no luck. Another thing we're not sure of - if those who have root did so before the 3.5.1 update.
Yeah I just contacted him as well. Will see what happens. Sadly my phone appears to be at 3.5.1.
Sent from my Z Ultra using XDA Free mobile app
pogfanatic said:
Yeah I just contacted him as well. Will see what happens. Sadly my phone appears to be at 3.5.1.
Sent from my Z Ultra using XDA Free mobile app
Click to expand...
Click to collapse
Hmmm... @Dilbert1959 you can post it here as well.
SafinWasi said:
Hmmm... @Dilbert1959 you can post it here as well.
Click to expand...
Click to collapse
@SafinWasi and all - I posted the APK in a separate thread in this same sub-forum. In retrospect, I should've just posted in this thread.
EDIT: I believe Towelroot will only work on this phone if you haven't updated to 3.5.1. I'm searching for a way to revert my phone to 3.5 to test this. The Amazon AWS site only has the most recent version available for download.
2ND EDIT: @SafinWasi - I found the old 3.5 OS download link in another thread. The file has a *.bin extension and is 1.12GB. We know through the recovery we can "update via ADB" which will prompt you to adb sideload an update file. I'm thinking I'll try this to get back on 3.5 & towelroot it.
Fire OS 3.5 (thanks to @ONYXis) - https://s3.amazonaws.com/fire-phone-updates/update-fire-phone-121_1.0.1_user_101012120.bin
First of all, I take no credit for these images. I received these from @Dilbert1959 who has confirmed root access using towelroot on Fire OS 3.5. I simply compressed the images to an acceptable file size for XDA.
@SafinWasi - Feel free to move these images to the OP.
I am M3 said:
First of all, I take no credit for these images. I received these from @Dilbert1959 who has confirmed root access using towelroot on Fire OS 3.5. I simply compressed the images to an acceptable file size for XDA.
@SafinWasi - Feel free to move these images to the OP.
Click to expand...
Click to collapse
Thank you and yes,I will move them to the OP
Sent from my device running CyanogenMod 11
SafinWasi said:
Thank you and yes,I will move them to the OP
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
EDIT
And to anyone who has successfully downgraded to 3.5 and has rooted their phone,please do a system dump with the following commands:
Code:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img"
adb pull /sdcard/system.img"
Sent from my device running CyanogenMod 11
SafinWasi said:
EDIT
And to anyone who has successfully downgraded to 3.5 and has rooted their phone,please do a system dump with the following commands:
Code:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img"
adb pull /sdcard/system.img"
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
PLEASE.
Related
can someone please get this to work on our tablet pleasssseeeee
http://d-h.st/Doq - apk
PC Jona said:
can someone please get this to work on our tablet pleasssseeeee
http://d-h.st/Doq - apk
Click to expand...
Click to collapse
+1 if someone could modify the app to work on the n7
second version optimum app
PC Jona said:
can someone please get this to work on our tablet pleasssseeeee
http://d-h.st/Doq - apk
Click to expand...
Click to collapse
there's a different version here: http://api.viglink.com/api/click?fo...0yig8pj3i718&jsonp=vglnk_jsonp_13543304821342
It might work for you if the unity version doesn't
momcat1 said:
there's a different version here: http://api.viglink.com/api/click?fo...0yig8pj3i718&jsonp=vglnk_jsonp_13543304821342
It might work for you if the unity version doesn't
Click to expand...
Click to collapse
Page won't open
momcat1 said:
there's a different version here: http://api.viglink.com/api/click?fo...0yig8pj3i718&jsonp=vglnk_jsonp_13543304821342
It might work for you if the unity version doesn't
Click to expand...
Click to collapse
That link works on my Asus Transformer Prime! Thanks!
yea it worked awesome.
only thing you have to clear data on app after you close it because it says unsupported device. but good stuff regardless.
thanks.
just waiting for the official app to work on the nexus now -_- theyre so stupid.
nvm spoke to soon it only works on my one s.
great.
yeah i got it to work on my mytouch 4g with a simple build.prop edit but not my Nexus 7. it might have something to do with the app seeing it as a tablet and not a phone, is there a way to trick it to think its a phone?
---------- Post added at 02:56 AM ---------- Previous post was at 02:19 AM ----------
momcat1 said:
there's a different version here: http://api.viglink.com/api/click?fo...0yig8pj3i718&jsonp=vglnk_jsonp_13543304821342
It might work for you if the unity version doesn't
Click to expand...
Click to collapse
says "Version not supported"
does this work yet anyone?
the option on my galaxy note or my nexus 7 from google play is missing to download the dam app
ANYONE !
You would think they would support the New Nexus devices especially the 10 and the N7 ( the most popular 7inch out ATM) but no they go and promote the K-fire and HD because well they have a contract with them and give out one free with a two year agreement so we loose and Cablevision won't add supported devices for a longtime. Look how long we had to wait to get android support.
there has to be way to root the nex 7 and spoof build as the kindle or some crap this is getting rediculous or to hide the imei if it does have one , not sure
sonkameja said:
there has to be way to root the nex 7 and spoof build as the kindle or some crap this is getting rediculous or to hide the imei if it does have one , not sure
Click to expand...
Click to collapse
the kindle one works but we have an outdated version Kindle is at 3.0.1 the one available in that link is 3.0
Some how got it to work on my Nexus 7!
I am not responsible for what can happen to your device!
Now what I did was the following:
-Edited my build.prop to match the kindle fire build.prop
-Rebooted my device
-Went to this site: http://www.optimum.net/ExploreOptimum/featuredtl?id=57070183 clicked on the PlayStore link and installed
I can upload the build.prop file if anyone needs it, but I am not responsible for what can happen to your device!
solidmac said:
-Edited my build.prop to match the kindle fire build.prop
I can upload the build.prop file if anyone needs it, but I am not responsible for what can happen to your device!
Click to expand...
Click to collapse
2 questions... how is it working? I had tried side loading previously, but w/o changing build.prop
also, does this seem to effect other apps? (the build.prop changes)
Havent seen it effect any of my apps yet! make sure to back up your OG build.prop
https://www.dropbox.com/s/nwzovlxmb4xicyz/build.prop.zip
solidmac said:
Havent seen it effect any of my apps yet! make sure to back up your OG build.prop
https://www.dropbox.com/s/nwzovlxmb4xicyz/build.prop.zip
Click to expand...
Click to collapse
Thank you. I can confirm that this works as advertised. I had to use ES File Explorer and mount my system partition, but once I did that I was able backup and then copy over your modified build.prop file...
Ridiculous that one has to do this, but its doable
anyone got the new apk file? they updated to version 3.0.4 and it's not working on my Galaxy Nexus
BUMP!!!
anyone has 3.0.4????????
Does this method still work?
nope
SysAdmNj said:
Does this method still work?
Click to expand...
Click to collapse
this method does not work on my samsung note 10.1 .....ive tried various different build props and they all cause bootloops.
there has to be a better way.
criticalera said:
this method does not work on my samsung note 10.1 .....ive tried various different build props and they all cause bootloops.
there has to be a better way.
Click to expand...
Click to collapse
Happened to me too. Stopped trying.
EDIT: Sorry guys, I won't be maintaining this anymore. I really apologize, but there's just too much to do nowadays. I will still maintain my carbon builds. (These boot and work without modification right now, for some reason my slim build won't boot, and I don't really have time to figure out why, because it could be an issue on my side or their side)
The moderators can end this thread if they wish to.
Carbon: http://forum.xda-developers.com/showthread.php?p=46548342
I shall still leave my jellybean build here though.
Downloads:
http://d-h.st/Kkh (November 8, 2013)
http://d-h.st/SMD (November 15, 2013)
GAPPS: slimroms.net --> Downloads --> addons
Are you really the dev of these ROMs? They seem a bit untrustworthy, since you or anyone else hasn't tested them.
Sent from my Amazon Kindle Fire using xda app-developers app
404-Not Found said:
Are you really the dev of these ROMs? They seem a bit untrustworthy, since you or anyone else hasn't tested them.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
He is compiling them. The Kindle fire base and the kernel is developed by Hashcode. Slim, AOKP, and Carbon implementations are all created by their perspective developers. Does that answer your question? Compiling a Rom is just a matter of setting up the proper environment and repositories then letting it rip. Well there`s a bit more to it than that but you get the jist.
Yeah he's exactly right. ^ also, I test the first build to make sure it does work and then I put it out if anyone wants to use it. I am building these myself. I can take screenshots of the builds straight from my computer if you'd like.
I may not be able to maintain all these ROMs, but I'd like to put the options out there. I might have to request for other people to maintain the aokp and slimbean thread if life gets too busy. I was originally only planning on maintaining carbon.. So I will keep going with that.
Thanks for the ports. Slimbean runs well, no real problems or quibbles I've found so far.
36 hours and one full cycle into this one and all is good. Seems SlimBean has settled in nicely on my KF. Thanks androidsftw! Your efforts to bring this variety of ROMs for us is greatly appreciated here!
Thepooch said:
He is compiling them. The Kindle fire base and the kernel is developed by Hashcode. Slim, AOKP, and Carbon implementations are all created by their perspective developers. Does that answer your question? Compiling a Rom is just a matter of setting up the proper environment and repositories then letting it rip. Well there`s a bit more to it than that but you get the jist.
Click to expand...
Click to collapse
I guess that does answer my question, but I find it a rare event like this to happen.
404-Not Found said:
I guess that does answer my question, but I find it a rare event like this to happen.
Click to expand...
Click to collapse
Actually, it's not rare at all.
Not sure why people are being skittish about using the ROM, I've run it for about a week now and it's rock solid stable! Fast and smooth...definitely one of the best 4.3.1 ROMs out.
Edit; Ive been using a few of the KitKat 4.4 system apks ( Play services, email, GEL Launcher, keyboard...) from here without any issues, making this Rom just that much more awesome. Can't wait for SlimRom to get updated to the new base!
Sent from my Amazon Kindle Fire using xda app-developers app
erad1 said:
Not sure why people are being skittish about using the ROM, I've run it for about a week now and it's rock solid stable! Fast and smooth...definitely one of the best 4.3.1 ROMs out.
Edit; Ive been using a few of the KitKat 4.4 system apks ( Play services, email, GEL Launcher, keyboard...) from here without any issues, making this Rom just that much more awesome. Can't wait for SlimRom to get updated to the new base!
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
To be honest with you I already have cm 11 and aosp built for the kindle fire. Unfortunately I can't test either until twrp releases a new build with kitkat support. I attempted to build twrp from source.. And it did build.. But let's just say the recovery doesn't work well xD.
androidsftw said:
To be honest with you I already have cm 11 and aosp built for the kindle fire. Unfortunately I can't test either until twrp releases a new build with kitkat support. I attempted to build twrp from source.. And it did build.. But let's just say the recovery doesn't work well xD.
Click to expand...
Click to collapse
That sounds great! Would this be of any help with the recovery issue?: http://forum.xda-developers.com/showpost.php?p=47024590&postcount=13
http://goo.im/devs/Hashcode/otter/recovery/flash-zip/
I think this one will help you.
themoto said:
http://goo.im/devs/Hashcode/otter/recovery/flash-zip/
I think this one will help you.
Click to expand...
Click to collapse
Thanks but I don't need it I've had recovery working for the past two weeks since TWRP has already released a build that works with kitkat.
TWRP 2.6.3.1
themoto said:
http://goo.im/devs/Hashcode/otter/recovery/flash-zip/
I think this one will help you.
Click to expand...
Click to collapse
Is there a flashable zip of 2.6.3.1 out there?
androidsftw said:
Thanks but I don't need it I've had recovery working for the past two weeks since TWRP has already released a build that works with kitkat.
TWRP 2.6.3.1
Click to expand...
Click to collapse
Sent from inside the time vortex
johnadelic said:
Is there a flashable zip of 2.6.3.1 out there?
Sent from inside the time vortex
Click to expand...
Click to collapse
I'm not sure, I just do it the manual way with fastboot.
androidsftw said:
I'm not sure, I just do it the manual way with fastboot.
Click to expand...
Click to collapse
The better way...
Download flashify from play store.
Download twrp 2.6.3.1 IMG
Open flashify n flash
------------------------------------------------------
If I was Helpful, click thanks
Sent from my air powered ceiling fan
The first gen and HD Kindle have people active on the 5.0 development, just wondering if power user here is working on a 2nd gen rom for us.
Wrong section to post.
Sent from my PAC'ed Amazon Tate using Tapatalk
No, I think he posted in the right section. And no I don't think anyone is working on a 5.0 ROM sorry, no one really builds for the Otter2 (KindleFire2) anymore but me and I rarely do that. Since Hashcode moved on to work for Linaro we are pretty much dead in the water, sorry bud.
Ok, thanks man. Do you think it would be too much work to port Hashcode's Kindle 1st gen ROM to the 2nd gen?
theplagueisback said:
Ok, thanks man. Do you think it would be too much work to port Hashcodes Kindle 1st gen ROM to the 2nd gen?
Click to expand...
Click to collapse
Well... Porting is not possible.
I have a first gen. What hashcode did was he made a new partition layout, bpotloader, and recovery for it, which made it COMPLETELY different from Amazon's device. So hiss 5.0 for pur device is OtterX. Anyways, ROMs can't be ported between two devices anymore. So unless hashcode is working for it, its done.
theplagueisback said:
Ok, thanks man. Do you think it would be too much work to port Hashcode's Kindle 1st gen ROM to the 2nd gen?
Click to expand...
Click to collapse
Porting between the two has never gone well..can I try and make a 5.0 ROM yes. Its been one of those things I've been meaning to do just haven't gotten around to doing yet.
I hear ya, what can we do, if you guys ever come up with something I'll gladly give it a try
Thanks!
obsolete1 said:
Porting between the two has never gone well..can I try and make a 5.0 ROM yes. Its been one of those things I've been meaning to do just haven't gotten around to doing yet.
Click to expand...
Click to collapse
Please, please do this.
hashcode pushed all the changes for compiling 5.0 to github, just a matter of making a few changes in otter2 device tree. I will compile it today and see what needs to be done. Don't expect too much because cm-12.0 is still alpha.
Update
cm-12.0 uses an android partition layout, hashcode uses a different bootloader and twrp for OtterX. Unless someone can make cm-12.0 work on Amazon partition layout we won't get it.
Could the otterx stuff be ported over?
Itsbricked said:
Could the otterx stuff be ported over?
Click to expand...
Click to collapse
I have been looking at the tuna partitions and they use the same layout as amazon so could be done. Using the otter cm-12.0 repositories it won't compile so I'll compare it with cm-11.0 and try again.
stevemp said:
I have been looking at the tuna partitions and they use the same layout as amazon so could be done. Using the otter cm-12.0 repositories it won't compile so I'll compare it with cm-11.0 and try again.
Click to expand...
Click to collapse
Otter has cm12 repos? Cm12 has Ben made for otterx, of whose partitions are different.
Sent from my Amazon Otter using XDA Free mobile app
androvista said:
Otter has cm12 repos? Cm12 has Ben made for otterx, of whose partitions are different.
Sent from my Amazon Otter using XDA Free mobile app
Click to expand...
Click to collapse
The otter-common and omap4-common has cm-12.0 updates, just not the otter2 device repository. So far I haven't been able to compile otter2, going to keep working on it. But today I will be upgrading to Fedora 21.
stevemp said:
The otter-common and omap4-common has cm-12.0 updates, just not the otter2 device repository. So far I haven't been able to compile otter2, going to keep working on it. But today I will be upgrading to Fedora 21.
Click to expand...
Click to collapse
Well, me and Lovejoy and joshua failed @ lollipop billions of times till hash helped. Just pm him and ask kindly whether he will continue support. Hash is God:thumbup:
Sent from my Amazon Otter using XDA Free mobile app
In theory Otter2 is buildable. I don't have the device to test.
Hashcode said:
In theory Otter2 is buildable. I don't have the device to test.
Click to expand...
Click to collapse
I'll be happy to test it out if it helps.
theplagueisback said:
I'll be happy to test it out if it helps.
Click to expand...
Click to collapse
+1
I'll help test if needed. I did want to restore back to factory, but I lost all my PC backups. I'm loving LP on my LG G2, so having it on my KF2, or even Ubuntu touch/Firefox etc to play with would be great.
Sent from my LG-D802 using Tapatalk
i can test too!
i hope in a lollipop rom for this otter2 now that it's out of official cyano support
In case anyone else is having issues using TWRP with CM 13 encryption, the issue is already fixed in TWRP code, they just haven't released a new build. So I've done my own build off nightly sources.
Hopefully this will help out anyone else who can't get TWRP 3.0.2 to access encrypted /data .
https://www.androidfilehost.com/?fid=24588232905720187
*edited link to use a better hosting service
Nice idea, however, you appear to have chosen quite possibly the worst hosting website in the history of man! Why do I need to sign up to be able to download a file? Makes no sense to me. Thanks anyway.
Why don't you submit the fix to the OFFICIAL TWRP thread?
lmulli said:
Nice idea, however, you appear to have chosen quite possibly the worst hosting website in the history of man! Why do I need to sign up to be able to download a file? Makes no sense to me. Thanks anyway.
Click to expand...
Click to collapse
I'm happy to host anywhere else, I just happened to already have an account there. What's the preferred hosting location these days?
Orion116 said:
Why don't you submit the fix to the OFFICIAL TWRP thread?
Click to expand...
Click to collapse
I didn't create the fix myself. It's already in the official TWRP sources. They just haven't released a new build since fixing it. It's also worth noting that the bug is not device specific. If I understand correctly it appears in all MM devices that use hardware encryption.
I didn't post in the official thread because this isn't an official build.
little2slo said:
I'm happy to host anywhere else, I just happened to already have an account there. What's the preferred hosting location these days?
Click to expand...
Click to collapse
for xda https://www.androidfilehost.com
Gerriitw said:
for xda https://www.androidfilehost.com
Click to expand...
Click to collapse
Done. Thanks for the tip.
Is there a reason why I cannot seem to use "adb" or "adb shell" while booted into this copy of TWRP?
Hello fellow XDA members, I recently purchased a Le Pro 3 and a Le S3 during the flash sale and would like to use Cyanogenmod on my devices. I was wondering if anyone on this forum has ever ported a ROM before as I have not, and only know about the CM porting guide and opensource.le.com for the kernel source. If anyone has any tips or would like to assist me in porting CM13 to the Pro 3 please reply to this thread or PM me. Thanks, and let's hope LeEco releases the source soon!
Love to help but this isn't my department ????. But we should probably see more support in a couple more days once they start arriving here
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
dr4stic said:
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
Click to expand...
Click to collapse
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
limitlesscodes said:
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
Click to expand...
Click to collapse
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
dr4stic said:
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
Click to expand...
Click to collapse
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
limitlesscodes said:
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
Click to expand...
Click to collapse
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
dr4stic said:
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
Click to expand...
Click to collapse
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Not a lot. I've identified the CAF tag the sources are based on and have been working to separate the relevant LeEco mods from the less relevant ones. I've also been attempting to remove the leeco specific things from the drivers that i'm keeping since they're a horrible mess and CM won't be able to make use of them anyway. I've also been finding the appropriate open versions of the drivers and taking the latest ones instead.
The mods from LeEco seem to be a mess, the dmesg output I got from a user on the chinese model (the x720) had segfaults from the modifications just after boot. The logcats are so full of errors I was unable to get the user to send me a full logcat from boot.
Interestingly enough, the chinese system rom looks like it came from a Le Max2. This makes sense since it's LeEco's first msm8996 device, and the Le Pro3 is the second one. I imagine the kernel sources work across a number of the 8996's.
Can you send me the link to where you got the open drivers.
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Please share the sources.
Sent from my LEX727 using Tapatalk
ceo.mtcl said:
Please share the sources.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
here
limitlesscodes said:
here
Click to expand...
Click to collapse
Thank you so much!
limitlesscodes said:
here
Click to expand...
Click to collapse
This is not a International version? Its USA version? Where is the International source code?
Here's a mega mirror in case the drive link goes down.
https://mega.nz/#!7Ek3HYaB!1H0WibOjwlg1P0vaaJ2qcrAAsl-PjruB9-_X1ECqfnw
Wish i could help more, but it looks like the kernel source is in there too, perhaps that means a fully functional cm13 rom that works AT LEAST as well as the stock rom. VERY EXCITE!
+1
I'm also waiting for CM13.
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
:good:
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
giogio1 said:
:good:
Click to expand...
Click to collapse
Waiting for CM 14.1
http://opensource.le.com