Related
Hey, new to the forums, recently purchased a GSM Hero.
I have done some development for free software (think freedom, not price) projects, and have become accustomed to git repositories and structured development.
Upon entering the world of custom Android ROMs (at least Hero ROMs) I have been sorely disappointed with the development practices going on, releases on file sharing sites and the like.
On top of this, none of the ROMs available suit my needs.
This is all fine, as I'm not developing those ROMs.
I have decided that I need to start working on my own custom ROM, however guides and documentation regarding this process are in short supply.
It would be much appreciated if someone could link me to some guides to starting my own custom ROM.
I intend it to be a light vanilla ROM, with none of the bloat that seems to perpetuate other ROMs, I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
naivemonarch said:
I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
Click to expand...
Click to collapse
Have you tried this one ? >[2.1] aychteesees-vanilla-cupcake< NOT the [3.0.1]verison ..this is still @dev
http://android.modaco.com/content/h...96/3-0-1-aychteesees-vanilla-cupcake-rom-gsm/
Give it a try [2.1] ! and tell us how it went ...
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
I'm downloading 3.0.1 as we speak, however I'd still like some resources on making my own ROM.
I'm interested on this documentation too....thanks
naivemonarch said:
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
Click to expand...
Click to collapse
That's weird , I have used almost everything ( apps ) with that ROM [2.1] ... and never get FC's
Did you flashed from Zero .. I mean with all he possible wiping . inlcuding SD ext partition wipe
???
That is a MUST ..!
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
Click to expand...
Click to collapse
There's Paul's (modaco) online kitchen, but if you want to compile by yourself, there's a plethora of gits on github (cyanogen, lokx, kiall to mention just a few).
Good question. Yeah it would be nice if there was a 'Cooking Class' thread on this forum like in some of the other forums. There is a decent tutorial however at HTCpedia.com under the HTC Hero ROM Development section, it's in the stickies there. However, I still have questions and that forum is not visited as much as xda.
Link to cooking thread:
http://htcpedia.com/forum/showthread.php?t=1404
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
Click to expand...
Click to collapse
As a start, I would read that thread I just linked above. Once you can dump the contents inside the system.img and then combine it with the boot.img to build an update.zip, then you are already halfway there - that's actually fairly easy. But knowing how to add custom kernels to the update.zip, making the custom ROM rooted, etc. are all stuff that I'm still working on. There's supposed to be a lot of info in the Dream/Magic forums, so I'll keep reading.
Android is still fairly new and very few people know how to use Linux, thus there's less support and less interest in wanting to cook for one's own Android device.
BTW, that thread I linked above is also found here.. Doh!
http://forum.xda-developers.com/showthread.php?t=551711
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
naivemonarch said:
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
Click to expand...
Click to collapse
If I eventually manage to find out I will post it here. My most important concern is making a rooted ROM from those shipped ROMs, as some people have been doing here.
Presenting the latest development version of the TeamWin Recovery Project's touch recovery for the HTC Wildfire S. TeamWin Touch Recovery now has official builds available through TeamWin and GooManager for the Marvel. With any luck MarvelC support will soon follow. Please visit the TWRP and TeamWin pages for more information.
Compiled for and tested on the original GSM Marvel. Always awaiting more testing from CDMA Marvel users. This software is provided without support or warranty: use it at your own risk.
Known Issues:
Fails on a handful of new GSM Marvel devices with updated/incompatible hardware, locking at the initial HTC splash screen.
Change Log:
XX:XX XX/8/2012 - Initial release of TWRP v2.2.2.0: Upstream code changes resolve the issues with formatting SD-EXT and partitioning the SD-Card. Includes the initial release of a revised 320x480 default theme with cleaner action pages, slightly larger buttons and more spacious checklists. First stable, full-featured and issue free release of TWRP for the HTC Wildfire S. Previous buggy versions have been removed from the revision history and can no longer be downloaded.
17:35 19/08/2012 PDT - Second release of TWRP v2.2.1.5: Issues with offmode charging resolved thanks to kalaker.
23:32 17/08/2012 PDT - Initial release of TWRP v2.2.1.5: Upstream code includes changes that resolve issues with the system rebooting during backup operations.
03:00 06/08/2012 PDT - Initial release of TWRP v2.2.1.4: Upstream code includes a handful of nice little bug fixes including a resolution for the mount issues.
23:05 05/08/2012 PDT - Minor aesthetic tweaks to the new theme.
02:29 05/08/2012 PDT - Third release of TWRP v2.2.1: Includes a carefully scaled v2.2 theme enabling the latest release's advanced features.
22:59 28/07/2012 PDT - Second release of TWRP v2.2.1: Corrected a glitch in my build environment that could have lead to issues and then forked it for dedicated platform builds. First dedicated MarvelC build.
23:58 27/07/2012 PDT - Initial release of TWRP v2.2.1: Compiled from the most recent code provided by: TWRP, Cryptomilk and the CyanogenMod ICS-Release branch.
22:55 09/07/2012 PDT - Maintenance release of TWRP v2.1.8: Reconfigured and shrank the kernel in order to utilize a less aggressive form of compression than LZMA. Switched from the CyanogenMod ICS branch to ICS-Release.
12:35 09/07/2012 PDT - Initial release of TWRP v2.1.8: Built using the ICS branchs of the CyanogenMod and Cryptomilk Marvel sources. Oversized image required LZMA compression.
To Do:
Build flashable .ZIP
Download Links:
TWRP for GSM HTC Wildfire S (Marvel) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 34f201ec8c8b0f0d2eae64c88ac3d888
TWRP for CDMA HTC Wildfire S (MarvelC) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 7c4d137a37098900ff3b2a9412ee8994
This is not the place for support.
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! THIS IS!
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. Please limit all discussion in this thread to development issues. I've started you off with some installation instructions as that was the first issue. I will update and check in as necessary. Enjoy!
You need to have the HTC drivers installed.
Then in cmd type:
fastboot flash recovery recovery.img.
Place the img file in the same folder as the adb files, so you won't have to specify a path.
Good luck,
Awesome work btw. :laugh:
WoefulDerelict said:
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES and I CLEARLY stated there would be ABSOLUTELY NO SUPPORT in my original post, it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! Ignorance and stupidity will not be tolerated.
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. I've started you off with some installation instructions as that was the first issue. Enjoy!
Click to expand...
Click to collapse
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
He means he wont be answering any questions in this thread.............he created another thread for discussion in the general section
Semantics...
Red5 said:
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
Click to expand...
Click to collapse
I believe the issue here is entirely one of semantics. In my lexicon support encompasses the magical realm of end-user hand holding. In no way do I feel it is necessary or reasonable to expect a user manual with warm and fuzzy walk-troughs of every possible thing you could want to do and some friendly advice with a hug every time the user has a problem with their FREE software. I certainly don't plan to offer any of the above.
I do; however, plan on maintaining my work. I'm quite interested in information that would allow me to improve the image or resolve a reproducible issue. I also have no qualms discussing the work with other developers, providing updates as the code base evolves, accepting proper issue reports or feature suggestions. I'd simply prefer to avoid getting bogged down by questions that could easily be answered by visiting the project's home page or querying Google. I find it quite counter productive to wade through user prattle when I'm trying to fix an issue or collaborate with another developer.
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
I'm not sure what you're asking.
marchelius said:
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
Click to expand...
Click to collapse
This should be compatible with any HTC Marvel based Wildfire S. I believe they are all based on the same SOC. The kernel should have support for all MSM7227 based graphics hardware.
WoefulDerelict said:
This should be compatible with any HTC Marvel based Wildfire S...
Click to expand...
Click to collapse
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Works perfectly on my phone. Mine is the A510e.
The joys of platform fragmentation.
marchelius said:
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Works perfectly on my phone. Mine is the A510e.
Click to expand...
Click to collapse
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
WoefulDerelict said:
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
Click to expand...
Click to collapse
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Main branch broken with CM9 on Marvel since updating to 2.2 code.
TWRP updated their main branch to v2.2 today. While I was hoping for the resolution of current issues their changes break my build with CM9. I'm stepping through the changes presently to see if I reason out what changed between 2.2 and 2.1.8 to cause the issue and correct the it. Stay tuned for more updates.
More please...
marchelius said:
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Click to expand...
Click to collapse
Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.
IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
It's ALIVE!
The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
Fresh revision.
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
WoefulDerelict said:
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
Click to expand...
Click to collapse
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Yea, I knew that.
eoghan2t7 said:
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
WoefulDerelict said:
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
Click to expand...
Click to collapse
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
eoghan2t7 said:
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)
4.4 images are building im coming here for developers help on getting this rom working
i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...
this post will get more colorful and easier to read over time:
Below is a quote from my google+ post on Xoom Community (join it.. its a great place)
STATUS UPDATE:
Xoom Wifi - LIFESTREAM ROM by LOGMD
Build 17 - Failed BUT we have:
-boot.img
-system.img
-kernel (supposedly)
I have managed to extract the system.img into a flashable Zip... but i KNOW the permissions are F*%#ked
I installed boot.img manually using fastboot but its left me in bootloops (not actually getting to the boot animation, looping on the moto logo)
i flashed the 4.2.2 EOS4 BigPart image because its compatible with the new partition layout and it doesnt bootloop... but it also doesnt get to bootanimation either...
BUT it did respond to ADB devices and came up as unauthorized device so obviously when i ADB SHELL it says device unauthorized...
I THINK that i need to build the boot.img with the BigPart patch but im not sure even if the kernel is just not working properly. if ive built it properly or whatever...
IF ANYONE knows any xoom developers or you are a xoom developer and know how to build kernels on a version of android thats not supported officially or if you think you could help me out then im all ears
Click to expand...
Click to collapse
BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!
we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!
PROGRESS
I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel
DISCLAIMER
I (LOGMD) am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary
REPARTITION
SYSTEM.IMG
BOOT.IMG (kernel, ramdisk etc)
THREADS OF LIFE (words stolen from Shadows Fall Album)
This is where you and I should use as a starting point for homework using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!
GOOGLE+
+LOGMD | +XDADevelopers | +XoomOwners
XDA-Forums
BLOG
OTHER (follow me)
Twitter | Facebook
I wish you luck. As your skill and luck is our luck.
Sent from my Xoom using XDA Premium HD app
subbed! anticipating great things!
way to be!! Super excited. Need guinea pigs? I'll help
sbeaber4 said:
way to be!! Super excited. Need guinea pigs? I'll help
Click to expand...
Click to collapse
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
I stupidly did not reserve posts so heres one more
boot.img
For the kernel, why don't ask to ElementalX ?
If we have a system.img but it's to large to flash through fastboot,
thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX
would that work?
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://forum.xda-developers.com/showthread.php?t=633246
I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
Incredible news!!
Love to see KitKat on Motorola Xoom!
Sent from my Xoom using Tapatalk 4
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.
I uploaded it here if you'd like to test it out
TWRP
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
pots22 said:
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
Click to expand...
Click to collapse
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
Elemental-X seems to have updated to beta with support for big partition.
4.4
hawkstorm said:
Elemental-X seems to have updated to beta with support for big partition.
Click to expand...
Click to collapse
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
pots22 said:
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
Click to expand...
Click to collapse
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Cameron581 said:
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
hawkstorm said:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
Click to expand...
Click to collapse
That makes no sense he removed apps and was on a parted kernel
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.
They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
4.4
Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2
http://download.cyanogenmod.org/
All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
Hi And Welcome To a Non-Tested Version of Android 6.0.0 on the xoom (Maybe 5.1.1 Not Sure) But back to the topic
This is mostly 5.1.1 but maybe with new of fixed features (I've never tested it as I said)
Here is how to install (I found this on another area)
1. ROOT YOUR DEVICE
2. Install BigPart TWRP
3. Wipe your system and flash the zip file
Here is the zip file
(I'm having Issues of Attaching The File So Please Wait)
XDA:DevDB Information
Android 6.0.0 or Android 5.1.1, ROM for the Motorola Xoom
Contributors
MichaelTech, Schischu, dreamcwli, michie
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
ROM Firmware Required: Rooted BigPart
Based On: OmniRom
Version Information
Status: Alpha
Created 2015-11-19
Last Updated 2015-11-19
so is this rom 5.1.1 or 6.0? id love to try it out...
I just resurrected my old xoom and converted it to bigpart.
waiting for the zip....
Waiting for test it.
Did you build this rom? If so, how can you not know what version of Android it is?
MichaelTech said:
(I've never tested it as I said)
Here is how to install (I found this on another area)
Click to expand...
Click to collapse
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
sdthelord said:
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
Click to expand...
Click to collapse
Based on this post, I think that, best-case scenario, he just kanged Schischu's 5.1.1 build and maybe themed it to look like 6.0. But I'm betting we never see a zip file.
As with everyone else I am curious to this. [6.0.0/5.1.1(Not Sure)] <--- this seems a little strange. It can only be one Android version. If it's 5.1.1 with some cherry picks and tweaks, that's great but just say.
Also some source would be good so we can establish what it actually is. Upload to androidfilehost or something similar if you can't attach.
P.S OmniRom wanted me to make a rom so perfectly fine
MichaelTech said:
P.S OmniRom wanted me to make a rom so perfectly fine
Click to expand...
Click to collapse
Look we shouldn't be fighting about whos rom it is It's just code that matters
MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Here is the error I keep getting
vBulletin Message
Invalid post specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
but nothing happened to this page so what is this problem
MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
brewer75 said:
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
Click to expand...
Click to collapse
I can when you solve my problem I keep having
MichaelTech said:
I can when you solve my problem I keep having
Click to expand...
Click to collapse
The Download is now available in the downloads tab
here is info
Modified Launcher3
Modified SoundRecorder
Modified PackageInstaller
Android 5.1.1 with tweaks
gapps and super su are not included so please download them
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
michie said:
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
Click to expand...
Click to collapse
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Download not possible. File not found.
MichaelTech said:
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Click to expand...
Click to collapse
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
michie said:
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
Click to expand...
Click to collapse
I mostly belive its android 5.1.1
MichaelTech said:
im a level 8 of 10 coder
Click to expand...
Click to collapse
How many more XP do you need before you level up to 9?
What a joke...
Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
Nice!
Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.
Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.
device boots up? display?
thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress
Maybe change the title with correct spelling of " Unofficial "
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments
@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.
krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app
@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse
Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?