Hi guys you know if it's possible to port cm 11.? If yes why nobody port Already?
Sent from my SM-P605 using XDA Free mobile app
It is an easier task for SM-P605 since it uses S800 CPU which has open source-ish drivers which can help devs a lot while compiling a rom from source. Looks like nobody wants to take on this yet since it requires lots of time and knowledge
SM-P600 & P601 & P602 are a bit unlucky since they use Exynos CPU's which we have less source and experience on. Somebody can port from Note 3 with experience in porting (should be easier than building ground-up drivers for now).
Cyanide? Rotfl
On a serious note though...
There have been (successful) bounties for new roms recently and I wonder if we could also get some CM / AOSP love
All we need is a willing CM dev & another bounty, right?
(I'm still on stock, no root, no knox tripping and I don't void my warranty for a touchwiz rom... I would for a CM / aosp rom + kernel though...)
edit: a working CM or AOSP rom + kernel would probably also attract more devs, since most roms are based on either one of them (e.g. slim, paranoid android, etc are all based on AOSP [with their own modifications of course])
I want to port it, but i'm not able to port a fully working ROM, and not have time to fix all.
Sent from my Nexus 5 using XDA Free mobile app
Wasn't clear from your post, did you try to port it but not get things working?
I will probably attempt to port CM11 to the P605. I just got one, and I've worked on OmniROM in the past but this is the first time I have tried to bring up a device from scratch so it will take some time (well, not really from scratch, I'm banking on the fact that the Note 3 and Note 10.1 2014 are quite similar so that that might hopefully save me some time). The other issue for me specifically is that the seal on the box was already broken when I got it so I might want to try to return it, if any issues crop up. So first I need to figure out if I can root it without tripping Knox so that I can do some diagnostic stuff and try and figure out if the device has any problems and/or was a returned device.
But if we're lucky, I think I can port CM, though most likely I won't have a lot of time to do this until mid-June so before then I'll just see what I can do in a short amount of time. Afterwards I'll attempt bringing up Omni as well but I'll attempt CM first since CM actually supports the Note 3 LTE (I tried doing an Omni bringup for Note 3 too, but ran into some issues and haven't had time to debug further).
Just noticed that cyanogenmod is apparently already working on a galaxy note 3 exynos build ( http://www.cyanogenmod.org/blog/this-week-in-cm-apr-26-2014 ) and since note 3 and note 10.1 2014 share the same hardware, i'm sure someone will be able to port it
(Xluco is doing pretty much the same thing with his kernel... porting features over from a note 3 exynos kernel)
I'm quite excited for this, cm will be reason enough for me to finally root my device and like I said a working cm rom + kernel will probably attract more devs (since a lot of roms are based on cm) [emoji106]
Gesendet von meinem SM-P600 mit Tapatalk
Related
I have started to port MIUI 7 Marshmallow rom from MI Max to Redmi Note 3.
Here is the MIUI 7 Marshmallow ROM: http://en.miui.com/download-302.html
Anyone working on the same project may contact, also anyone experienced in porting may contact too.
Initial ports will be closed released for testing and stable ports will be posted here.
MIUI8?good work
Me bro
Sent from my Redmi Note 3 using XDA-Developers mobile app
<rant>
It's fairly simple to "port" I guess, as far as I know the process consists of: downloading the MiMax ROM and copying over the hardware files from our Kenzo MIUI-7 ROM, of course before any of this your either going to need system dumps or a way to extract the firmwares, and even then you'll need to put together an update-script to properly flash it all, and then you can start testing stuff out to see what works/dosnt and then you rinse and repeat until everything works, I've done this before for another device and although it did boot, there were countless issues and the entire process is archaic and pointless tbh, building from source (but we can't since MIUI is closed source so id say just wait for MIUI8 lol) would be easier in some sense since having the source upfront helps you have an idea of wtf is actually going on compared to the guess work that is copying & pasting libs and stuff from /system/etc, my point is, just wait till June 28th or whenever were supposed to have MIUI-8 since hacking together an M based MIUI-7 for our device based on another devices firmware with "similar" hardware would just be painful and I'd feel sorry for you if you had to do such, then again I could be awfully wrong and the entire thing may work (it is quite possible) relatively easily considering the familiarity of the hardware, I just wouldn't expect it to be bugless, but someone please do prove me wrong, I'd be happy.
</rant>
DiamondBond said:
It's fairly simple to "port" I guess, as far as I know the process consists of: downloading the MiMax ROM and copying over the hardware files from our Kenzo MIUI-7 ROM, of course before any of this your either going to need system dumps or a way to extract the firmwares, and even then you'll need to put together an update-script to properly flash it all, and then you can start testing stuff out to see what works/dosnt and then you rinse and repeat until everything works, I've done this before for another device and although it did boot, there were countless issues and the entire process is archaic and pointless tbh, building from source (but we can't since MIUI is closed source so id say just wait for MIUI8 lol) would be easier in some sense since having the source upfront helps you have an idea of wtf is actually going on compared to the guess work that is copying & pasting libs and stuff from /system/etc, my point is, just wait till June 28th or whenever were supposed to have MIUI-8 since hacking together an M based MIUI-7 for our device based on another devices firmware with "similar" hardware would just be painful and I'd feel sorry for you if you had to do such, then again I could be awfully wrong and the entire thing may work (it is quite possible) relatively easily considering the familiarity of the hardware, I just wouldn't expect it to be bugless, but someone please do prove me wrong, I'd be happy.
Click to expand...
Click to collapse
1. I have ported Roms for Micromax canvas music, Micromax unite 2. They were mtk. I have themed complete rom for LG l 3 e405. It was Qualcomm.
2. Flashing will be block based. If what I have planned will work.
3. We have no other better option to get marshmallow right now. And I live in present.
4. Without trying I can't know if it is a good idea or not. What I will loose? Few hours. What many will gain? May be a stable marshmallow miui 7.
Be positive.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Sudeep Duhoon said:
3. We have no other better option to get marshmallow right now. And I live in present.
4. Without trying I can't know if it is a good idea or not. What I will loose? Few hours. What many will gain? May be a stable marshmallow miui 7.
Be positive.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Keep up good work my friend. Looking forward for this..
count me in bro, i have spare redmi note 3 to test and provide logcats or anything you want.
Sudeep Duhoon said:
I have started to port MIUI 7 Marshmallow rom from MI Max to Redmi Note 3.
Here is the MIUI 7 Marshmallow ROM: http://en.miui.com/download-302.html
Anyone working on the same project may contact, also anyone experienced in porting may contact too.
Initial ports will be closed released for testing and stable ports will be posted here.
Click to expand...
Click to collapse
nice work bro...
keep moving...
I think you will be founder of quick charge 2.0 for RN3 if you can port this rom :good:
Here you have a beta tester of your work men! Good luck
Nice..can you please port to MTK?
The leaked version of
Miui 7:http://forum.xda-developers.com/showthread.php?t=3377347
and cm13:http://forum.xda-developers.com/showthread.php?t=3350656
are stable enough now. Though the initial boot was failed of Port rom. I see no point of trying now.
Please close the thread.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Hello there
As the title tells you, i would like to have a clean OS for the Galaxy Tab A 7.0 (SM-T280)
With clean OS i mean a completely debloated rom without any extras. As slim as possible. Just a launcher and Core GApps (Playstore + Maps)
Maybe a debloated ROM or a debloation script. or a List of removeable Apps
I notices that the LTE version of the tablet, the SM-T285, allready got some non Touchwiz roms.
CM13 by Jedld and CM14.1 by Jedld
The best what could happen would be, if a developer from the T280 could make it compatible.
Jedld said:
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Click to expand...
Click to collapse
It would be great if someone could help
Greetings!
A month ago i inquired about the likeliness of a ROM for the 280. There was some work being done on it but unfortunately it stopped. As long as devs don't have the device, no work will be done for it. So unless we (requesters) bundle and buy a 280 for a dev (something unlikely to happen) we can only hope.
i want it to
Just orered this tab, was at special price, sad to hear this
I guess all we can do is root and debloat
russy23 said:
Just orered this tab, was at special price, sad to hear this
I guess all we can do is root and debloat
Click to expand...
Click to collapse
it is not ruled out that there will be development for this tablet
I'm currently searching for a port of A300FU Android M version, also working for a A300F.
Is there any such version?
Or a reason why there shouldn't be one?
There isn't one, as of yet, but I don't see why there couldn't be, aside of it being somewhat difficult to do it for TouchWiz ROMs.
Just asking because, I've till now, not come across a non-stock (CM or Lineage)version for the A3 (2015), where the encryption still seems works. And I guess since the A310-series uses no Qualcomm chip anymore, there would be some issues trying to use a port of these unless they are specifically modded to work with other hardware components and firmware :crying:
And I really want to have a version where the encryption works, otherwise I would probably buy next year just a new one and try my luck with some XPosed modules and root access instead and keep the Google integration for the better or worse >.<
I have been waiting quite some time for a custom rom for SM T819 but I haven't see much progress in this. I looked for a device with similar specs for our device and came across this device which already has a Lineage OS build available. Its practically the same device but with a different screen size.
LeEco Le 2 Specs: http://www.gsmarena.com/leeco_le_2-8053.php
LeEco Le 2 Lineage OS Github Repo: https://github.com/LineageOS/android_device_leeco_s2
It will be a good starting point as I think for getting a custom rom for this device with a great potential. I have read that having spec devices is a great start to porting a ROM from one device to another without specifically building it from the source. However it includes a few build prop tweaks and changing few lines on kernel which I have no technical expertise.
Looking forward for your thoughts.
It's true, personally I don't have this tab but I had experience with a Tab I used which was similar in specs with S4 Mini ..
You'll get bugs though and you can base device tree from the Leeco Phone to build ROMs
Anything new here?
Seems like @tuxing built a modified T813 LOS build for himself, but of course no LTE in there. https://forum.xda-developers.com/showpost.php?p=73992901&postcount=552
i really hate the lack of support for LTE Tablets :/
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
kinglolloman said:
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
Click to expand...
Click to collapse
Not that easy, but I had a nice chat session with @LuK1337 and he explained me how to get things built and boot on T819: https://forum.xda-developers.com/tab-s2/general/guide-build-lineageos-15-1-t819-t3721477
It's not that difficult as I thought. @LuK1337 told me it's simple and even I managed to get it working.
Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.
Plus almost no developers left for this now very old model .