I've been reading these forums for a long time, learning exploring and trying. However I have not been posting many questions, because generally with a bit of research I've solved and answered my questions here in the forums.
Technomancer has released a fantastic ROM of Cyanogen Mod 7, Gingerbread based, for the Galaxy Tab.
To date I have flashed my Magic through various flavours of ROM's and not bricked it, I'm currently using an HD2 with a NAND based CM7 build as my daily device and have managed to flash Technomancer's CM7 onto my Galaxy Tab.
I am not a developer, I have some experience of Linux, OSX and Windows and can clearly follow instructions and provide feedback. I'm well aware of the risks of flashing these devices and accept the chances of a brick.
So here it is, an open offer of assistance and a desire to learn more. I cannot post in the Dev forums for the obvious reasons.
Maybe I should have posted more stupid questions rather than learn by research.
Cheers
Related
hello everyone i am fairly new to the world of android ive only had 2 android phones the first was a samsung transform which i rooted and had everything done to it that was possible but recently traded it for an echo and to my dismay cannot root it so i am gonna try and build my own custom rom just dont know how to do it ive been looking online for guides but it seems like everyone i found only works with htc? if someone could please guide me in the right path on finding guides on building roms that would be awsome i am curious to learn this whole process thanx
This probably isnt the right place for your post, a section called Android Development for your specific phone would be a great place to start a thread.
As for the question though, there generally speaking are no guides for building roms. Most people will start small, with mods or themes, then slowly grow into full roms. Although based on your post, your phone cannot be rooted, so how are you expecting to install the rom without root?
HI all , i lunched this thread after weeks of googling and usless search for a new stock or custom rom to update my phone (samsung sgh-i857 doubletime) it's a dual screen phone with querty built-in keyboard it's from at&t and it is stuck on android 2.2.2, i'm very sad that they and after years from lunching it didn't back it up with a single soft update -_- ... and i know that there are users who bought this phone like me and seek help.. i know that it's not this easy but if you are a devloper help us by creating a custom rom for it ....if you are a user of this phone please support this thread by commenting so we can get an update for it :good: ps: i attached informations for it's cpu
Hello good sir, I like you am a noobish Doubletime user who is struggling to update it to Gingerbread. So far I have been somewhat able to use the Cyanogenmod source code and I have built a CWM Recovery for the device but that seems to have hard bricked it... I ordered a new one off ebay for $15 and I'm ready to start cooking. You have my support!
Just an update.
I have a plan I have on how to get this runnin.
1. Port CWM to the DoubleTime through Cyanogemod 6.
2. Get a working version of Cyanogenmod 6 working on the DoubleTime to hopefully free up some space.
3. Find if Gingerbread can run on Froyos kernel.
From there I'll either be building a GingerBread compatable kernel or Cyanogenmod 7 depending on compatability. Any advice or help would be very appreciated.
Being new to ROM building I'm a little lost and hesitant on flashing things but here's what I know so far.
The DoubleTime uses a Qualcomm MSM7230 same as the HTC Vision. I forked it's Github respiratory and I'll be using it as a base as recommended by the Cyanogenmod porting guide.
The partitions sizes (as a accurately as I can estimate them) are:
/cache=21.05MB
/data=176.65MB
/system=194.38MB
I may need to know the recovery partition size but I'm not sure how to find that out.
I have the recovery.img and the boot.img as well as the zImage. So as soon as the repo sync is done I'll be on my way.
I'm back again today with somewhat mixed news, I can find most of the partitions and their names (I've learned a lot today) but I can not seem to find the boot, recovery or ramdisk partitions. I'm already boggled by the what seems to be unconventional naming setup for partitions. Put all of my "notes" in a text docement in the attachments section. Any help with this is very appertiated. I can type and post anything into the ADB shell you need me too.
I'm beginning to feel like I'm talking to myself, I probably am...
Upon reading forum rules and such it has come to my attension that this is the wrong forum for this kind of thread, So I have made a new thread in the Miscellaneous Android Developement Forum that will hopefully be more useful at getting more proffesional and opinionated help.
http://forum.xda-developers.com/showthread.php?t=2651728
hello. as most users have stock based modded roms, why don't separe the cyanogen? these roms confuse users with rare problems too...... i hope this solution because this is sometimes a problem
easiest, just to go cm homepage.
i don't need cm... the cm's rom invade the android development note 3, i ask why isn't there the separation
Most users don't use stock based roms many many use CM and without CM their would be a none to poor development scene .
One of the basics is if you don't understand then don't use modded firmware .
i asked for forum organization, and not for say that cm is better or not than stock based.... your answer is not pertinent to my question. goodbye
myabc said:
i don't need cm... the cm's rom invade the android development note 3, i ask why isn't there the separation
Click to expand...
Click to collapse
What? CM "invades" Android development? :laugh: You can guess who the first team was, to modify Android and present it as a custom ROM in the Android Development section. What's actually invading the Android Development section are all those "Stable, ROCK SOLID,® 100% Stable | BETTARY LAyF ◄◄©" TouchWiz ROM's! Those need a seperate section called "Stock ROM's with community bloatware instead of OEM bloatware claiming to break the barriers of physiks and being faster than light and breaking the first and second law of thermodynamics"... Not all of them of course. Exceptions are there.
Know where you are and why you are here!
Checklist of Things to Do w/ Axon 7
1. Unlock Bootloader - DONE
2. Flash TWRP - DONE
3. Get Root Access, along with Root apps - DONE
4. Flash Cyanogenmod 13.1 - PENDING
Who is interested in seeing Cyanogenmod 13.1 running on the ZTE Axon 7 as much as I am? If so, please post on this thread. Hopefully, the right people will check this out and get the ball rolling on this project.
Why don't you build it ? ?
We are never happy ... let the devs work ... on the other hand they have a life and bills to pay !
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
like tupirujp says.
If you want your question answered just contact Cyanogen directly.
***Thread Cleaned*** (removed negative, counterproductive comments/quotes, for a fresh start)
Some concerned users brought this thread to the attention of Moderation staff.
A good practice is to have the dev needing the device (Unjustified Dev) set up their own donation link, express their desire to dev for the device, and put out a little description of the work they intend to do for that device (ie; unlock bootloader, Roms , Kernels, etc)...
Otherwise, third party donation links usually only raise suspicion, mistrust, and rarely accomplish the goal of helping the dev get a device.
I applaud those who want to support developers (they certainly deserve the support), let's make sure we do it in a way that isn't counterproductive to the goal or the donation process.
Thanks for your cooperation.
Well, in order to build a rom you need:
Device Tree
Kernel
Vendor/Proprietary files
We have versions of the first two already loaded on GitHub. It's a (hard) matter of someone figuring out what proprietary files we need and then going through the iterative testing to ensure all the hardware components are working. So, let the devs have time with the phone to see what they can figure out and we'll start seeing development.
Please Cyanogenmod come to this device..
Mod Edit:
You have already raised this in Q and A. One question at a time please, in one place.
Thanks
A good rom is Lineage OS 14.1 Official for the S4. It is stable and good for daily usage.
There are pinned posts at the top of the Galaxy S4 General subforum that should be of help in actually rooting the device, though actually rooting it is not difficult. The main question I ask people lately when it comes to a ROM is whether they care about having Touchwiz features or not, as that will narrow down the available choices. From there, only by trying out the ROMs will you find one you like.
Before flashing anything, I recommend booting into download mode to confirm the model number.
Try it and find out. I don't use LineageOS so I can't tell you if it will or will not work. @audit13 no longer has his S4 if I recall so he's not going to be able to tell you, unless he used it in the past. Asking your questions on the forum is more than sufficient, though you will have to be patient when it comes to replies. PMs are dicey. I ignore tech support PMs and audit13's stance on them is unknown to me.
I no longer use an S4 but it's important to know the exact model number before flashing anything. The 9500 is very different, internally, than the 337 and 337m.