Related
I'm somewhat new to the whole idea of rooting an android device, and flashing custom roms. I've rooted my phone successfully, but there doesn't seem to be a custom rom tailored to my phone anywhere on the web. Is there any way I could use a custom rom (looking at CyanogenMod) for a different device on my own?
Any and all help is appreciated.
Phone: Samsung Galaxy Centura (SCH-S738C)
Carrier: StraightTalk
Android Version: ICS 4.0.4 (Stock OS)
Kernel Version: 3.0.8-1207620 (Original Phone Kernel)
christabelle said:
I'm somewhat new to the whole idea of rooting an android device, and flashing custom roms. I've rooted my phone successfully, but there doesn't seem to be a custom rom tailored to my phone anywhere on the web. Is there any way I could use a custom rom (looking at CyanogenMod) for a different device on my own?
Any and all help is appreciated.
Phone: Samsung Galaxy Centura (SCH-S738C)
Carrier: StraightTalk
Android Version: ICS 4.0.4 (Stock OS)
Kernel Version: 3.0.8-1207620 (Original Phone Kernel)
Click to expand...
Click to collapse
U can port ur own rom for ur device from the custom rom of a similar device with same specs if available with the help of dozens of tutorial in xda.
But you ll have to put a lot of hardwork on learning and implementing it, also have to sacrifice much of ur time. Indeed if you don't wanna do that, just wait until some devs to come up to cook rom for ur device if ur device model is new
Hit thanks rather than typing it
parkourkarthik said:
U can port ur own rom for ur device from the custom rom of a similar device with same specs if available with the help of dozens of tutorial in xda.
But you ll have to put a lot of hardwork on learning and implementing it, also have to sacrifice much of ur time. Indeed if you don't wanna do that, just wait until some devs to come up to cook rom for ur device if ur device model is new
Hit thanks rather than typing it
Click to expand...
Click to collapse
I think I'll take a look at some of the tutorials and give that a go. I aim to have as much control over my device as possible.
christabelle said:
I think I'll take a look at some of the tutorials and give that a go. I aim to have as much control over my device as possible.
Click to expand...
Click to collapse
Sure u can if are patient enough
Good luck:thumbup:
i have a Galaxy Centura too, but im gonna wait for Area51 to come out with a ROM for it. sounds like they have been working on it for a little bit. but the phone is pretty new, only been out for like 2 months i think.
Sch s738c help
christabelle said:
I'm somewhat new to the whole idea of rooting an android device, and flashing custom roms. I've rooted my phone successfully, but there doesn't seem to be a custom rom tailored to my phone anywhere on the web. Is there any way I could use a custom rom (looking at CyanogenMod) for a different device on my own?
Any and all help is appreciated.
Phone: Samsung Galaxy Centura (SCH-S738C)
Carrier: StraightTalk
Android Version: ICS 4.0.4 (Stock OS)
Kernel Version: 3.0.8-1207620 (Original Phone Kernel)
Click to expand...
Click to collapse
Can you tell me how you rooted that device Please
I have it but haven't found a working. Root method
Thanks
Harry.
Sent from rooted lg f60 (thanks to unjustified dev)
my device is not sopported cm rom. can i install cm
I have Jiake V8 and I can't find a recovery either TWRP or CMW. my device is not supported and it has Android 4.2.2 JB. Is there any other way I can install a recovery and port a custom ROM. if so can you give a clue please.
I would like to put KitKat on my phone and I have not done the OTA 4.3 update, so my baseband has not been updated. Whenever I try to figure out how to put KitKat on my phone, I find threads that say something like the following.
Don't update to 4.3 or you'll never get a custom boot image
OK, we figured out how to root 4.3, but you still shouldn't do it
All KITKAT roms are based on AOSP or their derivitives, which you need to update to 4.3 to get
But don't update to 4.3 because it isn't worth it, I mean, the camera sucks on AOSP
Here is a list of 25 KITKAT roms, each more awesome than the last!
Here is a 4.3 update without the baseband, if you haven't updated, use this, it is the best of both worlds
We wont be updating the above rom, because we are so excited about these KITKAT roms!
Hey I just updated to AOSP (CM, AOKP, etc) KITKAT and it is lame, how do I get TW back?
Does that sound about right? If I want KITKAT I should just stop wanting KITKAT and that will solve all my problems?
If you take the 4.3 update you will be stuck on 4.3 (or until Verizon decides to upgrade). It can be rooted and now you can flash other 4.3 ROMs with safestrap, but you will never be able to run a custom recovery/kernel. So even if you wanted to try AOSP you wouldn't be able to. I don't know who told you you have to upgrade to 4.3 to try AOSP but that is completely off base, in fact it's the complete opposite!
What are you currently running? Is your bootloader unlocked? If you are curious about AOSP I would definitely give it a try. In my experience TW ROMS tend to be more stable and have every bit of hardware working (camera, bluetooth, etc). AOSP ROMS are quicker, smoother, have newer features and are more easily customized. It's really a matter of preference.
If you really want to try KK and be on the bleeding edge you should. Kit Kat ROMs run very well on this phone. If something like a 100% working camera or bluetooth is extremely important to you I would stay on TW. However, devs are constantly working on the ROMs and working out these kinks.
BattsNotIncld said:
If you take the 4.3 update you will be stuck on 4.3 (or until Verizon decides to upgrade). It can be rooted and now you can flash other 4.3 ROMs with safestrap, but you will never be able to run a custom recovery/kernel. So even if you wanted to try AOSP you wouldn't be able to. I don't know who told you you have to upgrade to 4.3 to try AOSP but that is completely off base, in fact it's the complete opposite!
What are you currently running? Is your bootloader unlocked? If you are curious about AOSP I would definitely give it a try. In my experience TW ROMS tend to be more stable and have every bit of hardware working (camera, bluetooth, etc). AOSP ROMS are quicker, smoother, have newer features and are more easily customized. It's really a matter of preference.
If you really want to try KK and be on the bleeding edge you should. Kit Kat ROMs run very well on this phone. If something like a 100% working camera or bluetooth is extremely important to you I would stay on TW. However, devs are constantly working on the ROMs and working out these kinks.
Click to expand...
Click to collapse
OK, thanks for the info.
How do I know which baseband a rom is for? I found the TouchWiz 4.3 Download List. Does that basically mean that, if it isn't on that list, it is probably for the old baseband?
I tried flashing some Gummy nightlies and Carbon - both failed. On TWRP, the only message I get is "install failed"
I know troubleshooting that is a different thread, but I'm not sure where to start to figure it out.
ragendem said:
OK, thanks for the info.
How do I know which baseband a rom is for? I found the TouchWiz 4.3 Download List. Does that basically mean that, if it isn't on that list, it is probably for the old baseband?
I tried flashing some Gummy nightlies and Carbon - both failed. On TWRP, the only message I get is "install failed"
I know troubleshooting that is a different thread, but I'm not sure where to start to figure it out.
Click to expand...
Click to collapse
Update your recovery.
That thread is what will work on the Verizon 4.3 update. You're fine flashing anything because you never took it, just follow the directions in each rom thread. You could flash those roms as well.
Sent from my HTC6525LVW using Tapatalk
Hey guys I am fairly new to android and really new to this rooting and custom rom thing and I've been doing my research with what a rooted android w/ custom rom could look like and what it could further do.
I was hoping that my rooted phone is compatible with Custom Roms like Cyanogen Mod, AOKP, etc. Unfortunately my phone isn't listed in any listed devices in the well known Custom Rom Sites but I still proceeded with installing Cyanogen Mod since everyone seems to be using it. I don't even know if there are more of these eye candy useful mods that makes the ios look miserably locked up while hoping at least one of these custom rom is compatible with my crappy awesome phone. But upon installation process of Cyanogen Mod WITHOUT awareness that it really isn't compatible, it stated in that page that I could (STILL)use their Custom Rom at my own risk. Beyond that I stopped the installation process in fear of destroying my phone.
I was wondering whether you guys could enlighten me about the compatibility of Huawei Y220-U10 to Custom Roms. I've seen Huawei Y210's on youtube that's using a custom rom but unfortunately ALL of them who's demonstrating their phones are speaking in Spanish. I also installed ROM Installer but I can't seem to see 'FEATURED'? Maybe because it's the free version?
Now I am willing to take the risk, starting from the bottom meaning derooting my phone, wiping it clean, rerooting it and flashing that Custom Rom but I'm seeking advice from much more experienced users because if you guys tell me that it is a BIG NO NO I guess I'll just have to stick with the Go Launcher and wait until I get a much better, stronger, faster android smartphone which has a friendlier compatibility to everything android. And how come I can't access facebook nor yahoo from any web browser in my phone? is it a virus? Please clarify my theories.
Much Regards, Jom
P.S. Phone is running at 2.3.6 and rooted with Kingo Android ROOT
Hello @Jom Apa Welcome to Android / XDA!
"BIG NO NO!" You can't flash ROMs not made for your device because of the underlying hardware incompatibilities. You might completely kill your phone.
Give me a few minutes while I search for ROMs you can use
UPDATE: Unfortunately I haven't been able to find any custom firmware for your device nor Github entries for the chipset used. Seems you'll either have to stick with stock or create your own custom ROMs there are a lot of support here on XDA, Let the learning begin!
Cheers!
Hey im still running Android 4.4.2 CleanRom and its been a while since ive been around. I feel a bit outdate and was wondering what i should upgrade to. Not looking to do nightly's as i do not have the time, just looking for something new and stable. Let me know what you think. Thanks.
-Cam
camf3xu said:
Hey im still running Android 4.4.2 CleanRom and its been a while since ive been around. I feel a bit outdate and was wondering what i should upgrade to. Not looking to do nightly's as i do not have the time, just looking for something new and stable. Let me know what you think. Thanks.
-Cam
Click to expand...
Click to collapse
Hi, here on xda we dont compare roms, sorry. its just taboo of the worst kind. Also please post questions in the question and answers portion of the forum, thanks and cheers.
I'll go ahead and reply with respect to the split between KitKat and Lollipop. You'll note a bunch of Lollipop-based ROMs appearing. Some have chosen to flash those, to be on the cutting edge. However, the Xposed Framework - one of the most useful customization tooks in the Android world - has not been updated to work with the "ART" (Android Run Time) and instead is only still compatible with Dalvik-based system. The developer of Xposed has indicated that he may work on updating XPosed at some point, but there is no firm commitment or timeline.
I personally will not be upgrading to Lollipop as I find that the tweaks made available by the Xposed Framework and the plethora of modules built for it, are simply too important me to lose by upgrading to what isn't all that radically different of an Android update.
But to each his own. Thought I'd give you a bit of the background.
P.S. Anything by Santod is quality work (NuSenseSix, UnSenseSix, etc). He really knows Android.
Nothing beats stock as far as stability. For newest, well, the newest official software is stock as well until VZW releases Lollipop.
Sacred cows make extra tasty steaks. That said, I'll make recommendations. I think Fluent is as reliable as the stock 4.4.4 and more so than some of the more radically tweaked 4.4.4 ROMs out there built from non-Verizon sources. NuSense is solid as well, but hasn't been updated in a while, is minimally modified, and is based on the oldest of the lollipop releases. if 4.4.4 is all you want, Clean ROM 3.0 was a solid runner for me.
If you can do your own mods then I would go with Lollipop as you don't need xposed if your looking for stable stick to 4.4.4 for now.. Make sure you upgrade your firmware before if you haven't as you r still on 4.4.2 ROM I'm taking a guess your haven't updated firmware.
Tigerstown said:
If you can do your own mods then I would go with Lollipop as you don't need xposed if your looking for stable stick to 4.4.4 for now.. Make sure you upgrade your firmware before if you haven't as you r still on 4.4.2 ROM I'm taking a guess your haven't updated firmware.
Click to expand...
Click to collapse
What do you mean by doing your own mods? Short of coding them, I'm not sure how one would go about getting Samsung Milk to work, or cleaning up the Notification menu, or a bunch of other things that just aren't commonly built into customized ROMs. If you do know of a way to get such things working in Lollipop, do let me know - I'd then be able to make the switch!
godhamba said:
What do you mean by doing your own mods? Short of coding them, I'm not sure how one would go about getting Samsung Milk to work, or cleaning up the Notification menu, or a bunch of other things that just aren't commonly built into customized ROMs. If you do know of a way to get such things working in Lollipop, do let me know - I'd then be able to make the switch!
Click to expand...
Click to collapse
I was just saying if you know how to decompile apks an make code changes an recompile your make your own mods.
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
https://youtu.be/RxoNMuIPQbw
jaaa1976 said:
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
Click to expand...
Click to collapse
Thanks bro...
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
vinydasilveira said:
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
Click to expand...
Click to collapse
You really have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
moto maxx (xt1225) running rom stock of nexus 6. totally unstable. stock 7.1.1
*Kernel AOSP - Quark (This is merely @bhb27 LOS kernel or his standalone, there is NO such thing as "Kernel AOSP -Quark")
*Stock 7.1.1
Click to expand...
Click to collapse
Why would we want to run something like that (unstable Nougat ROM) on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our Quark phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the Quark custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the Quark custom ROMs actually use the SAME kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that YouTube post means is someone took @bhb27 kernel code and managed to horribly port a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the Quark kernel.
The reason why "stock" ROMs are not done are because they are boring. You wouldn't have the LED notification for instance that @bhb27 created, nor all the options present in Revolution Remix and crDroid. Even @calsurferpunk's LOS ROM is more of a hybrid -- LOS + some of the more popular options in RR. We already HAVE up to date 7.x Nougat ROMs. And they run well. How many more do you want?
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
What people WANT are Oreo ROMs. The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
ChazzMatt said:
You have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
Why would we want to run something like that on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the custom ROMs use the same kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that post means is someone took @bhb27 kernel code and managed to horribly run a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the right kernel.
The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
Click to expand...
Click to collapse
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
vinydasilveira said:
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
Click to expand...
Click to collapse
It's about the kernel. The kernel is the foundation of all ROMs. You notice the YouTube video is merely a Nexus 6 NOUGAT ROM that doesn't run well on Quark. Because we have Nougat compatible kernel right now.
@bhb27 actually said he is using some of the Nexus 6 stuff for CLUES to adapt the Quark kernel for Oreo. But it's not easy. Until you have a compatible kernel, no Oreo ROMs will run on Quark. @bhb27 has actually gotten Oreo Resurrection Remix to run on Quark. Have you not seen the screenshots? But at this point it's still unstable.
Once you have a kernel, you can have 100 Oreo ROMs on Quark in a week -- if you find 100 people willing to port the ROMs. It's almost plug and play (for dev maintainers who have those skills). This is why we have had so many "drive by" ROMs dropped into this forum and then those people walk away without ever updating them. They were taking advantage of @bhb27's kernel work. Take ROM, plug in kernel, done. But they never stuck around to keep them updated, or even test them thoroughly, and some didn't even own a Quark phone. One of them even used @bhb27's advanced standalone kernel (not his LOS stock kernel) in their ROM without his permission, so it made their ROM seem better than the other ROMs. It's the same kernel anyone can download and install themselves, but @bhb27 wants you to install that one yourself as it's more complex. He doesn't want it installed as a default kernel -- he doesn't include it in his own ROMs.
He's working on an Oreo-compatible kernel but while everything about Moto Nexus 6 is open source (thanks to Google), it's not the same with Moto Quark. Yeah, even LG Nexus 4 has Oreo, but again, it's totally open source so easier to adapt.
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
about the video posted on my channel, I just made a joke at home. I know the limitations, I know the hardware is different. it was only a joke of those who do not have much knowledge, but search knowledge, the kernel used is a custom ROM 7.1.1, I did not say that the kernel is stock 7.1.1.
I admire the work of the developers, when I use a custom ROM, I can imagine how much work it has done to make it functional with few bugs. :good:
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
bhb27 said:
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
Click to expand...
Click to collapse
perfect explanation... I admire your work