Related
Hi Guys,
Can somebody point out what are the compatiable Custom ROM for p1010...
I am looking for best custom ROMS ..
Cheers!!!!!
Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.
samcortez said:
Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.
Click to expand...
Click to collapse
This is correct. CleanROM is the only "non-stock" ROM available for the 1010 and technically is not a "Custom" ROM. It is based upon a "Stock" Gingerbread firmware with some "bloat" removed and some theme's added. Also, Scott from Scottroms (the developer of CleanRom) I believe has sold his Galaxy Tab and will not be providing future updates.
Motafoca is indeed working on a CyanogenMod (CM) build for the P1010 but to my knowledge he is the ONLY developer doing so. Let's all wish him luck and support him in his journey because once he is successful it will open the door to other developers.
FYI, I have created an in-depth thread specifically for the GT-P1010 that can be viewed HERE.
I will be updating that thread and adding the details above to it. My hope is that we can all discuss our "forgotten" P1010's in that thread so as to be able to find all the information more easily.
I'm one of the testers of motafoca. And well, actually, we are trying to ort cyanogenmod 7.2, but the zip doesnt works, p1010 is a little complicate. And motafoca is working on 4 devices at same time. Soo its hard. I think that in march we finish with cyanogenmod 7.2 (note: the biggest problem is do a flashable rom of cyanogenmod, after that, is just pick the drivers of gingerbread from the source)
Thanks Guys for that information...
Since previous development thread was closed, I've been getting a lot of pms. Everyone thanks for the kind words and for offering me help. Thumbs up for this great community.
The reason I didn't post the link was because my laptop or my upload server let me down. At least that is what I saw when I woke up.
No big deal, thought I would upload it upcoming weekend. But as we all might know, today oos 2.2.1 was released. My custom oos was based on 2.2.x, so I was thinking to rebuild this rom again based on the latest software. Meaning it will take a couple of weeks before it will be ready.
So far this briefing. If you have questions regarding this rom, for now please ask in this thread.
Link to original thread:
COSX
To the features, just add the viper4android... And try to make the files app show the root directory too.
I feel you should post ur 2.2.1 build directly when its ready..take your time and i do support what u stand for!! and if possible add network speed indicator
Since there was no answer to this on the original thread, what do you mean by theme support? Layers?
I'll be patiently waiting for your release
But, for playing purpose, are there any guide somewhere to create a moded rom from a stock rom ?
I've been looking but all i could find was from 2012
I don't think it's as simple a remove/add apks from the rom zip :cyclops:
Request
Please donot remove the stock oos camera which has manual focus iso exposure .... __/\__ please
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!
Hi, I found a ROM around the web of Android Nougat 7.1 for our Z3. It seems is under development but it boots and works. I don't know the issues or problems that it has so I wanted to post it to try it and make known. The rom is here: dl.myself5.de/leo/CarbonROM/
It is not my project, is from Myself5 that I think is user of XDA. All the recognitions towards him.
If this topic is not in the correct forum, please the admins move it.
I'll check that. I have a z3 free to test
Enviado desde mi F8331 mediante Tapatalk
ipsilonf said:
Hi, I found a ROM around the web of Android Nougat 7.1 for our Z3. It seems is under development but it boots and works. I don't know the issues or problems that it has so I wanted to post it to try it and make known. The rom is here: dl.myself5.de/leo/CarbonROM/
It is not my project, is from Myself5 that I think is user of XDA. All the recognitions towards him.
If this topic is not in the correct forum, please the admins move it.
Click to expand...
Click to collapse
That rom IS 5.1 Lolipop, not Nougat.
Are you actually serious?
What do you think, why is there no thread for this already? Everyone I shared this link with I told its very early WIP, and not to share it.
I uploaded the builds so that I can download them to my laptop, and that some people who wanted a 7.1 build were able to use it.
While you even know that those are my builds, you did at no point think about sending a PM to me, asking if its ok to create a thread for it.
With that, I just deleted all prereleases of Carbon from my server, never ever expect me to release some preview or WIP builds again.
That does not only count for leo. Have fun being responsible for the deletion of all testbuilds for leo, aries, sumire and i9100.
@caqo71 that assumption is wrong. CR-5.1 is the internal versioning number for Android 7.1 (same as CM is using 14.1). Those builds were Android 7.1.0_r7.
I reported the thread, hoping to get it closed, and I will reference it every time someone asks me where the preview builds did go to. Have a very fun time on XDA.
EDIT: In case it was unclear: I am not against you posting builds of Carbon on XDA, of cause the whole team invites people to compile Carbon for their devices. What I am sepecifically against here, is that, instead of putting your own effort in here, and compiling it on your own, you made a thread about my builds, which is totally not ok, especially not without asking me.
Thread closed.
You cant just share stuff you find on the internet. You need to follow the forum rules (rule 12) before you decide to share it
Hey all you Sharp 306sh users!
I love this phone and decided to start a ROM port to Oreo 8.0.0!
To date here's what i got
1. Device tree built
2. ASOP stock rom built successfully
Here's what I need to get done next
1. Access bootloader to flash images
2. Test for vendor blobs needed so I can make the vendor tree (if required)
Your help on this would be greatly appreciated as I am just getting my feet we in this process, this is a great phone and I would love to see it updated.
Please let me know if you are interested in helping with this project!
Edit 8/6/2018: Device tree is on Github,
https://github.com/RobertCC18/sharp-306sh-rom
More to come once kernel is built!
Edit 10/12/2018:
I am uploading the first test build so I can get some help with the debug. THIS ROM IS GETS STUCK AT THE SHARP BOOT LOGO AND IS NOT READY FOR PRODUCTION DEVICES!!!!
That being said, any help and logs that you can send are greatly appreciated.
This zip can be flashed through TWRP, check the downloads section
XDA:DevDB Information
Android 8 Rom [stock], ROM for the Sharp Aquos Crystal
Contributors
RobbotCC
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-07-15
Last Updated 2018-10-12
Great! I´ve got a 306SH model, i can be a tester... waiting for your first zip :highfive:
Awesome.
I tried this exact same thing before, but gave up soon after I couldn't diagnose what stopped my device from booting with my custom ROMs, as I could never find the logs.
It looks like you're making more headway than me, so I'd love to test it, or even just help out.
Keep on going! A GitHub would be great progress.
Update 7-4-18
Update - 7/24/2018
Recompiling Kernel with debug drivers included - current compiled kernel missing RAM Console support
Github repo coming soon!
Great! Always wanted a custom room on this phone. I can test it and try it out too
Good progress.
Make sure to keep us updated, once you have a GitHub repo, development should speed up.
I'm sure there are a few techies with this phone that would love to contribute to your ROM, myself included.
By the way, you said ASOP instead of AOSP in the original post.
Rhioun said:
Make sure to keep us updated, once you have a GitHub repo, development should speed up.
I'm sure there are a few techies with this phone that would love to contribute to your ROM, myself included.
By the way, you said ASOP instead of AOSP in the original post.
Click to expand...
Click to collapse
Thanks, whoops on the typo!
Been busy with work but hoping to upload device tree, kernel base and current build, waiting for kernel to finish building with RAM console drivers.
Update 8/6/2018
Github Created
https://github.com/RobertCC18/sharp-306sh-rom
Device tree is added, kernel coming soon!
About accessing the bootloader to flash images, I believe we've done this before.
Tewilove, the man behind rooting the 306SH managed to access it, and made a custom one to flash, if I do remember correctly.
https://forum.xda-developers.com/aquos-crystal/general/temp-root-306sh-t3129456
Worth a look.
No development in a while. We all hope you're still there.
I visited the Github and just found it to be text files and folders. Could you possibly post the WIP kernel or other vendor blobs on there,
so we have at least a basis to begin work on?
Thanks,
This is an amazing idea. My 306SH is rooted and ready for action.
Rhioun said:
No development in a while. We all hope you're still there.
I visited the Github and just found it to be text files and folders. Could you possibly post the WIP kernel or other vendor blobs on there,
so we have at least a basis to begin work on?
Thanks,
Click to expand...
Click to collapse
Yes I am still here and working on this, just haven't had much time lately. I will try to get the kernel and vendor blobs up within the next few days
Been waiting for a custom ROM for this phone. I'm ready to test it
Any update on the development of the ROM??????
Any progress?
Status Update
dzvxo said:
Any progress?
Click to expand...
Click to collapse
Hey everyone,
Sorry for the delay in development but I hit a major snag with the kernel build and am still working on overcoming it. The needed defconfig is missing so I found one that should get us close, at the very least it should allow us to see the RAM debug messages on boot failure.
Also, my internet has been to slow to upload the kernel to github but I have an upgrade and should be able to get it uploaded within the next couple days.
Please share any information that you find regarding this phone here on XDA and beyond, any info you can provide will help me get this up and running faster!
Hey, how's everything going? Any luck?
What's up with it?
Hey All,
Sorry for the delayed responses, this phone seems to be a lost cause. But I am not a quitter lol!
I am hopeing to get back into the swing if things here in the next few weeks and will post more updates and files here shortly
Current problems:
No debugging enabled
Kernel needs patched to support Android 6+
We wish you the best of luck!