Related
I'm making the transition from my old Droid X to the VZW Galaxy S3, and I have a few questions. The flashing process between these two phones are quite different and perhaps another ex-Droid X user (or just an all around knowledgeable person) could help me out.
1. To my knowledge, we were never able to flash Kernels on the Droid X because of its locked bootloader. So how does Kernel flashing work? Are there certain kernels that only pair with certain roms, or can you flash any kernel you like with any rom? I have a feeling it's the former, as I've already seen kernels categorized i.e. Touchwiz Kernels or CM10 based kernels.
2. With the Droid X, all roms were flashed using CWM. But with this phone that's not always the case right? Some may require a kexec method or even a custom recovery image, correct?
3. I've seen a few roms recommend backing up IMEI / MEID / EFS data before flashing. Is something I should consider doing whenever I flash, just as one would do a nandroid backup?
4. I've seen a few threads mentioning flash count, resetting flash count, etc. Should I be concerned with flash count? If so, why?
5. With the Droid X, before you could flash a rom, you had to make sure the firmware you were on was compatible with whatever rom you were trying out. For example, if you wanted to try cm7 you had to flash over the stock froyo kernel. If you wanted to try miui you had to flash over a stock gingerbread kernel. However, it would seem, with the S3 you can flash any rom (whether it be an ics rom or a jb rom) over stock 4.0.4. Is this correct? Can you flash an ics rom over the top of a jb rom? Or do you always have to revert back to ics stock?
6. Is Odin the Samsung equivalent of rsd lite?
D-meist said:
I'm making the transition from my old Droid X to the VZW Galaxy S3, and I have a few questions. The flashing process between these two phones are quite different and perhaps another ex-Droid X user (or just an all around knowledgeable person) could help me out.
1. To my knowledge, we were never able to flash Kernels on the Droid X because of its locked bootloader. So how does Kernel flashing work? Are there certain kernels that only pair with certain roms, or can you flash any kernel you like with any rom? I have a feeling it's the former, as I've already seen kernels categorized i.e. Touchwiz Kernels or CM10 based kernels.
2. With the Droid X, all roms were flashed using CWM. But with this phone that's not always the case right? Some may require a kexec method or even a custom recovery image, correct?
3. I've seen a few roms recommend backing up IMEI / MEID / EFS data before flashing. Is something I should consider doing whenever I flash, just as one would do a nandroid backup?
4. I've seen a few threads mentioning flash count, resetting flash count, etc. Should I be concerned with flash count? If so, why?
5. With the Droid X, before you could flash a rom, you had to make sure the firmware you were on was compatible with whatever rom you were trying out. For example, if you wanted to try cm7 you had to flash over the stock froyo kernel. If you wanted to try miui you had to flash over a stock gingerbread kernel. However, it would seem, with the S3 you can flash any rom (whether it be an ics rom or a jb rom) over stock 4.0.4. Is this correct? Can you flash an ics rom over the top of a jb rom? Or do you always have to revert back to ics stock?
6. Is Odin the Samsung equivalent of rsd lite?
Click to expand...
Click to collapse
1. Flashing kernels has been made as simple as flashing ROMs
2. kexec is outdated since the bootloader got unlocked. You can also still use CWM on this or there's another recovery that people like called TWRP (Download an app called EZ-Recovery from the play store, youll need it to flash any recovery)
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
4. I haven't tripped the flash count. Basically all it is is a way for Verizon to tell if you been f'in with your phone. I Believe that only AOSP/AOKP ROMs can trip it, not stock ROMS
5. It's a bit simpler flashing between ROMs on this phone. Just wipe data/factory reset and flash away. For the most part.
6. Yes it is basically.
Check the guide out in my sig, it'll explain how to do most everything in detail.
Brian Gove said:
1. Flashing kernels has been made as simple as flashing ROMs
Click to expand...
Click to collapse
To Elaborate on this just a bit, yes it is as easy as flashing roms but you were correct in saying that there are aosp kernels and there are tw kernels. just make sure the os version (ICS, JB) and the framework (TW, AOSP) match your rom and you are good to go!
Relentless D said:
To Elaborate on this just a bit, yes it is as easy as flashing roms but you were correct in saying that there are aosp kernels and there are tw kernels. just make sure the os version (ICS, JB) and the framework (TW, AOSP) match your rom and you are good to go!
Click to expand...
Click to collapse
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.
D-meist said:
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.
Click to expand...
Click to collapse
If you are just getting your feet wet with tw roms, you might consider giving Bean's a try. I've been using Build 9 since it dropped and it's smooth.
imo, it's themed just enough to not look like a straight tw rom, the performance is great and the battery life is fantastic as well.
I've tried synergy once or twice and was never quite completely satisfied with it.
D-meist said:
Thanks Brian and Relentless. Going to cut my teeth on an easy TW rom for starters, probably Synergy.
Click to expand...
Click to collapse
I haven't run CM or MIUI or any other AOSP ROM on this phone so take this with a grain of salt;
If you want cool stuff and constant bugs/lack of normal features go with the AOSP....
If you want some cool stuff and a nice stable daily driver... go with the TW ROMs. I've been running Synergy since 1.2(or 3 I cant remember lol) and I love it. Everything works on it, it's stable, and it's currently being ported to Jelly Bean so I can't wait for that shtuff. Eschelon and the rest of his team are good about listening to feature suggestions/requests too when they got time so more and more will be added.
Brian Gove said:
I haven't run CM or MIUI or any other AOSP ROM on this phone so take this with a grain of salt;
If you want cool stuff and constant bugs/lack of normal features go with the AOSP....
If you want some cool stuff and a nice stable daily driver... go with the TW ROMs. I've been running Synergy since 1.2(or 3 I cant remember lol) and I love it. Everything works on it, it's stable, and it's currently being ported to Jelly Bean so I can't wait for that shtuff. Eschelon and the rest of his team are good about listening to feature suggestions/requests too when they got time so more and more will be added.
Click to expand...
Click to collapse
Relentless D said:
If you are just getting your feet wet with tw roms, you might consider giving Bean's a try. I've been using Build 9 since it dropped and it's smooth.
imo, it's themed just enough to not look like a straight tw rom, the performance is great and the battery life is fantastic as well.
I've tried synergy once or twice and was never quite completely satisfied with it.
Click to expand...
Click to collapse
The moral of the story...Try out a few different roms What is amazing for one person might not be for the next. I'm flashing new roms every few days because I always want to see what else is out there.
Relentless D said:
The moral of the story...Try out a few different roms What is amazing for one person might not be for the next. I'm flashing new roms every few days because I always want to see what else is out there.
Click to expand...
Click to collapse
Yea I had beans for a little while... I honestly cant remember why I switched. I was just suggesting he stick with the TW ROMs period cuz I dont feel the AOSP ROMs are anywhere near stable enough yet.
Don't want to hijack OP's thread, but do any of you know how to check flash counter?
I will be getting my FOURTH sg3 this week, and this is the first time I will be returning a phone that I had rooted/unlocked/rommed. I'm all back to stock, just want to make sure I don't get a bill for $600.
Kreeker said:
Don't want to hijack OP's thread, but do any of you know how to check flash counter?
I will be getting my FOURTH sg3 this week, and this is the first time I will be returning a phone that I had rooted/unlocked/rommed. I'm all back to stock, just want to make sure I don't get a bill for $600.
Click to expand...
Click to collapse
haven't tried it but this is the best I've found searching around real quick.
http://forum.xda-developers.com/showthread.php?t=1781471
Brian Gove said:
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse
davefields3 said:
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse
I honestly don't know. One of the devs for Synergy ROM said something to the effect its "a weird Samsung reboot code and so the phone automatically restores a bad backup of your IMEI. It's a fluke thing"
It's 100% random when flashing anything I believe.
If u use the synergy Rom to flash it automatically has a script to back up your meid number and stuff. I've flashed synergy official cm10 nightlies without a hitch. Just make sure that u obtain root and unlock the bootloader and flash recovery. Thus far I've had no problems. Btw synergy Rom is the best one out there. Jellywiz is a jb Rom it is awesome but only thing that doesn't work is sms at the present time. If u want to back up ur meid best tool to use is qpst just Google it. Also all in one tool that has been great for me unlocking obtaining root and stuff is Verizon gs3 casual tool. In order to use that tool u mist have java se framework which u can find at the java website. Any questions feel free to shoot me a message! Good luck!
Sent from my SCH-I535 using xda app-developers app
chrisharper9643 said:
If u use the synergy Rom to flash it automatically has a script to back up your meid number and stuff. I've flashed synergy official cm10 nightlies without a hitch. Just make sure that u obtain root and unlock the bootloader and flash recovery. Thus far I've had no problems. Btw synergy Rom is the best one out there. Jellywiz is a jb Rom it is awesome but only thing that doesn't work is sms at the present time. If u want to back up ur meid best tool to use is qpst just Google it. Also all in one tool that has been great for me unlocking obtaining root and stuff is Verizon gs3 casual tool. In order to use that tool u mist have java se framework which u can find at the java website. Any questions feel free to shoot me a message! Good luck!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Just to clarify. Synergy is a stock tw based rom and CM10 is well a cm based rom. Two different monsters and roms entirely.
Sent from my SCH-I535 using Tapatalk 2
U r right but both can be flashed the same way
Sent from my SPH-L710 using xda app-developers app
davefields3 said:
Brian Gove said:
3. Losing IMEI is a royal paiin in the arse, but it's rare. Either way you want to back it up. I believe the guide on how to do so is in the Development Forum.
How "rare" is it to lose the IMEI after flashing? And is losing your IMEI a possibility flashing any ROM or just certain ones like CM10 or AOSP, or are TW and Stock roms susceptible to this as well?
Click to expand...
Click to collapse
I found this thread which looks like the Synergy guys made a script to backup IMEI. I gave it a go and was succesful in backing it up. Seemed much easier than the QPST method. Don't know if it will actually restore, but hopefully I'll never have to find out.
Click to expand...
Click to collapse
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
Actually, most of the times, you can flash a kernel that's based off of a different source base on a different base ROM as long as they are the same Android version (same framework). VRALG7 did not change much other than some of the apps and on the kernel side, I don't believe anything has changed. That should go true for radio too. For the OP, did you come from wipe everything and flash clean? Also, I am not sure what kind of modification the ULE went through but it may be lacking some libs or ramdisk since the rom is so damn light. Go and pull the boot.img from original ULE and see if the original kernel causes the same issue.
I installed the KT747 kernel. It runs GREAT with this ROM! No lag, super smooth & fast. Thx for the replies! KTweaker app is Awesome! The unresponsive / frozen lock screen is gone! CleanROM ULE + KT747 = Winner!
Sent from my SCH-I535 using xda app-developers app
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
I agree! Scott updated Clean ROM yesterday to 2.5 which is based off of the new G7 baseband. As Scrosler states in the OP, a new clean kernel is not available yet, so when you flash the new 2.5 you will be on stock. It's worth updating though! I'm sure an updated/upgraded kernel and mods will be out soon enough.
I had that same issue
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
SO what I did, made surei have no cpu apps runnung to be set on boot ( major problem when using titanium as a restore agent )
Then I flashed scotts clean kernel ( whatever the lastest edition is ).
Then right then and there wiped cache, and dalvik and then fixed permission.
THEN HERE IS WHERE ITS VERY IMP. I LET THE PHONE SIT FOR 10 MINS BEFORE TOUCHING IT AGAIN.
Now i am running smooth .
This is on .lk 0.9 which is essentially the same as lk .10
Hey guys, I have had a Bionic for the past 18 months or so....forgive me if my questions sound silly....
Recently, I was given a S3 to use. Before I take the plunge and get it activated, I was tryign to learn about the ROMS etc out there.
- I see there are TouchWiz ROMS and AOSP roms. I'm assuming the TouchWiz ROMS are based on stock rom just tweaked and debloated and teh AOSP ROMS are the ones built from scratch?
- I see there are kernels around....same, AOSP and TW. Is it safe to assume if I use AOSP, I need to get an AOSP kernel? If I install for example the latest Liquidsmooth....do I have to do the kernel 1st? or does the ROM have the kernel built in?
- Do I have to unlock the bootloader? Or is that what the kernel does?
Again, sorry for the dumb questions....my Bionic was simpler to do...with less options....
Thanks in advance
docluv01 said:
Hey guys, I have had a Bionic for the past 18 months or so....forgive me if my questions sound silly....
Recently, I was given a S3 to use. Before I take the plunge and get it activated, I was tryign to learn about the ROMS etc out there.
- I see there are TouchWiz ROMS and AOSP roms. I'm assuming the TouchWiz ROMS are based on stock rom just tweaked and debloated and teh AOSP ROMS are the ones built from scratch?
- I see there are kernels around....same, AOSP and TW. Is it safe to assume if I use AOSP, I need to get an AOSP kernel? If I install for example the latest Liquidsmooth....do I have to do the kernel 1st? or does the ROM have the kernel built in?
- Do I have to unlock the bootloader? Or is that what the kernel does?
Again, sorry for the dumb questions....my Bionic was simpler to do...with less options....
Thanks in advance
Click to expand...
Click to collapse
1. AOSP is the original Android OS untouched by any company. Touchwiz is Samsung's version Android.
2. You don't need a custom kernel but it can optimize your phone for increase in battery life.
3. All ROMs have kernels built-in they have to or else it won't work .
4. You must unlock the boot loader in order to flash anything.
Gotcha..!
Thank you!
So is it safe to assume, you flash ROM 1st, then you flash kernel? At 1st glance, I like the Liguidsmooth ROM, but people are also raving about the KT747 kernel. SO I would have to flash his AOSP version...
I have seen some radios also...Is that advisable to do?
jmxc23 said:
1. AOSP is the original Android OS untouched by any company. Touchwiz is Samsung's version Android.
2. You don't need a custom kernel but it can optimize your phone for increase in battery life.
3. All ROMs have kernels built-in they have to or else it won't work .
4. You must unlock the boot loader in order to flash anything.
Click to expand...
Click to collapse
Yes that is correct but you must first root your phone. The bionic had a larger margin of error when it came to rooting.
Yes, 1st thing I'm going to do is root and unlock the bootloader....
One last Q...
I see people are having GPS lock issues on some ROMs (eg Liquidsmooth), compared to stock. Would that be a kernel type off issue? Would updating the kernel to the KT747 fix this?
jmxc23 said:
Yes that is correct but you must first root your phone. The bionic had a larger margin of error when it came to rooting.
Click to expand...
Click to collapse
It is a ROM issue so the devs have to make a fix for it.
This is an awesome device but why aren't there any roms out for this device I see one but that it..would like to see some development progress for this device please
any updates? i cant find any, but its still a bit tough to navigate this board for me
marcviado said:
This is an awesome device but why aren't there any roms out for this device I see one but that it..would like to see some development progress for this device please
Click to expand...
Click to collapse
User's from the mini/ultra/maxx all use this forum since it's all basically the same phone... If you're on the Ultra there is one custom ROM available in the development section as they belong...the only ROM I've seen is the PAC ROM, provides much customization and lots of features... Our ultra and I believe the other two models do not have an unlocked boot loader so you can't flash a custom ROM or kernel without that...if you have the Dev version of the maxx then you can go ahead and unlock your boot loader and enjoy the Rom(s)
Sent from my XT1080 using Tapatalk
ahjee said:
User's from the mini/ultra/maxx all use this forum since it's all basically the same phone... If you're on the Ultra there is one custom ROM available in the development section as they belong...the only ROM I've seen is the PAC ROM, provides much customization and lots of features... Our ultra and I believe the other two models do not have an unlocked boot loader so you can't flash a custom ROM or kernel without that...if you have the Dev version of the maxx then you can go ahead and unlock your boot loader and enjoy the Rom(s)
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
i have safestrap installed, so i could flash ROM's, but im not interested in the very initial stages of ROM's...but am i right where i could flash it?
im in the middle of the OTA update right now anyways..so bye root for now...
Well the ota can be rooted and I have safe strap as well but without an unlocked boot loader you cannot flash Roms or kernel's... Having safestrap does not mean you can flash away, the boot loader is what matter's buddy. Sorry to be the bearer of bad news...but if you want root after the ota check out the development section... Jcase already has taken care of that
Sent from my XT1080 using Tapatalk
ahjee said:
Well the ota can be rooted and I have safe strap as well but without an unlocked boot loader you cannot flash Roms or kernel's... Having safestrap does not mean you can flash away, the boot loader is what matter's buddy. Sorry to be the bearer of bad news...but if you want root after the ota check out the development section... Jcase already has taken care of that
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
im new to android flashing, and bootloaders and all of that, but im only going off of my past experiences with my droid 4.
what i thought: a locked bootloader meant no custom kernels. as long as i have a custom recovery such as safestrap, i could flash ROM's, which is why there are ROM slots. i had eclipse ROM on my droid 4 even though that had a locked bootloader.
where am i getting confused? did the rooting process take care of the bootloader? or did ss bypass that?
tortoracer said:
im new to android flashing, and bootloaders and all of that, but im only going off of my past experiences with my droid 4.
what i thought: a locked bootloader meant no custom kernels. as long as i have a custom recovery such as safestrap, i could flash ROM's, which is why there are ROM slots. i had eclipse ROM on my droid 4 even though that had a locked bootloader.
where am i getting confused? did the rooting process take care of the bootloader? or did ss bypass that?
Click to expand...
Click to collapse
You're right, you can flash roms with a locked bootloader. However you cannot flash a kernel (boot image) with a locked bootloader. So far though, no stock based roms that I know of for this phone. I don't know if that's because safestrap is still in beta or what.
hawkswind1 said:
You're right, you can flash roms with a locked bootloader. However you cannot flash a kernel (boot image) with a locked bootloader. So far though, no stock based roms that I know of for this phone. I don't know if that's because safestrap is still in beta or what.
Click to expand...
Click to collapse
whats a non "stock based" ROM? i have only had phones with a locked bootloader, so im a bit confused there. what would be different? would it be seen, or would that only be how the phone does stuff internally?
marcviado said:
This is an awesome device but why aren't there any roms out for this device I see one but that it..would like to see some development progress for this device please
Click to expand...
Click to collapse
There aren't custom ROMs because there isn't a need for one, IMO.
This is the cleanest, most stable, coolest OS I've ever experienced anywhere.
I can't imagine a custom ROM out there that I would prefer.
redddog said:
There aren't custom ROMs because there isn't a need for one, IMO.
This is the cleanest, most stable, coolest OS I've ever experienced anywhere.
I can't imagine a custom ROM out there that I would prefer.
Click to expand...
Click to collapse
as with the ROM i had with my droid 4, the ROM isnt definitely something completely different from the factory. it could be de-bloated, include apps that work well with the device, disable/remove apps that nobody uses. tidy up the framework of the stock ROM.
i would love a pre-cleaned ROM, wifi tether, or really just a deodexed ROM at this point.
tortoracer said:
im new to android flashing, and bootloaders and all of that, but im only going off of my past experiences with my droid 4.
what i thought: a locked bootloader meant no custom kernels. as long as i have a custom recovery such as safestrap, i could flash ROM's, which is why there are ROM slots. i had eclipse ROM on my droid 4 even though that had a locked bootloader.
where am i getting confused? did the rooting process take care of the bootloader? or did ss bypass that?
Click to expand...
Click to collapse
The droid 4 used a method called kexec which highjacked the boot process and allowed a custom bootloader to run instead of the phones locked bootloader. Hashcode has stated that kexec may never work for the new moto line but there's always hoping. This is why I just ordered the developers edition.
Sent from my Droid Razr Maxx on JB 4.3 kexec
nukeruss said:
The droid 4 used a method called kexec which highjacked the boot process and allowed a custom bootloader to run instead of the phones locked bootloader. Hashcode has stated that kexec may never work for the new moto line but there's always hoping. This is why I just ordered the developers edition.
Sent from my Droid Razr Maxx on JB 4.3 kexec
Click to expand...
Click to collapse
i thought without an unlocked bootloader you could not install custom roms, i knew you couldn't with kernels but i thought no roms either... i am mistaken i assume by the response of the others, or can you not do either? Either way, if you can't use a custom kernel then most custom roms will not work anyhow
ahjee said:
i thought without an unlocked bootloader you could not install custom roms, i knew you couldn't with kernels but i thought no roms either... i am mistaken i assume by the response of the others, or can you not do either? Either way, if you can't use a custom kernel then most custom roms will not work anyhow
Click to expand...
Click to collapse
Incorrect. The Droid X had a locked bootloader, but it had a fairly large dev community. No custom kernels, but there was a good amount of ROM's available.
sfreemanoh said:
Incorrect. The Droid X had a locked bootloader, but it had a fairly large dev community. No custom kernels, but there was a good amount of ROM's available.
Click to expand...
Click to collapse
That would mean roms either came with no kernel baked in or they used to stock kernel then. I never had a phone without the boot loader being unlockable that being said how the devs and community spoke it came off as without it being that way no ROM was flashable but it was likely due to that most Roms come with a kernel baked in which is usually not stock. Anyway, thanks for correcting and informing me. Having a locked boot loader is new to me.
So I assume if I can manage to remove the kernel from the ROM zip I could flash the PAC ROM in our development section?
Sent from Ahjee's phone which is likely better than your lesser phone that doesn't have as many processors and can't run games as smoothly as this beast of a phone does stock
ahjee said:
That would mean roms either came with no kernel baked in or they used to stock kernel then. I never had a phone without the boot loader being unlockable that being said how the devs and community spoke it came off as without it being that way no ROM was flashable but it was likely due to that most Roms come with a kernel baked in which is usually not stock. Anyway, thanks for correcting and informing me. Having a locked boot loader is new to me.
Click to expand...
Click to collapse
I believe (at least on the DX) flashing just didn't touch the kernels at all, so we were always running the stock kernel. But I'm not a dev, so don't quote me.
On the droid x and RAZR (prior to kexec) all ROMs were built using the stock kernel. The doid x had an official cm build using the stock kernel. Using the stock kernel for custom ROMs like cm makes it much more difficult to get everything going smooth because the kernel has been optimized to work with the stock ROM which may be a couple versions of android behind.
Sent from my Droid Razr Maxx on JB 4.3 kexec
---------- Post added at 08:31 PM ---------- Previous post was at 08:19 PM ----------
Look at this post from the nook color thread. Unlocked boot loader with awesome devas equals a device that never dies. The nook color is currently on 4.3 and will probably get 4.4 before long.
That's right. Big ups to Cicadaman for that first Froyo port, "Nookie Froyo", which was invaluable for helping get that first CM7 (gingerbread) build booting (like months and months before GB showed up officially in BN's bastardized android, I might add!) Dalingrin joined in soon after and we and a few others got it polished together.... God, this was what, late 2010 or early 2011. It's hard to believe Android didn't even have even basic tablet support for soft buttons... requiring Tablet Tweaks... Oh, how time flies... :silly: ...and the nook color is still kickin'...
Sent from my Droid Razr Maxx on JB 4.3 kexec
nukeruss said:
On the droid x and RAZR (prior to kexec) all ROMs were built using the stock kernel. The doid x had an official cm build using the stock kernel. Using the stock kernel for custom ROMs like cm makes it much more difficult to get everything going smooth because the kernel has been optimized to work with the stock ROM which may be a couple versions of android behind.
Sent from my Droid Razr Maxx on JB 4.3 kexec
---------- Post added at 08:31 PM ---------- Previous post was at 08:19 PM ----------
Look at this post from the nook color thread. Unlocked boot loader with awesome devas equals a device that never dies. The nook color is currently on 4.3 and will probably get 4.4 before long.
That's right. Big ups to Cicadaman for that first Froyo port, "Nookie Froyo", which was invaluable for helping get that first CM7 (gingerbread) build booting (like months and months before GB showed up officially in BN's bastardized android, I might add!) Dalingrin joined in soon after and we and a few others got it polished together.... God, this was what, late 2010 or early 2011. It's hard to believe Android didn't even have even basic tablet support for soft buttons... requiring Tablet Tweaks... Oh, how time flies... :silly: ...and the nook color is still kickin'...
Sent from my Droid Razr Maxx on JB 4.3 kexec
Click to expand...
Click to collapse
sorry if it is a dumb question, but what exactly is a kernel? a ROM is like the operating system i assume, but..?
tortoracer said:
sorry if it is a dumb question, but what exactly is a kernel? a ROM is like the operating system i assume, but..?
Click to expand...
Click to collapse
not a stupid question dude, there's a lot going on with these phones and it takes to get educated and even more to be properly educated haha...things i think i know, i don't as you can tell lolol but the kernel is the engine so to speak, it's what makes the ROM or OS run how it does...the kernel has a bigger affect on battery life than the rom itself, well in my opinion but it's really a combination of the two together.
The kernel is what controls the CPU and GPU frequencies and whatnot
Ultra/Maxx/Mini
You guys say they're basically the same phone so everyone uses one forum, so can we install ROMs made for the other Droid devices?
My guess is probably not, so WHY are they not separated- silliest thing they could have done- I had to track this forum down over a week after I thought XDA just didn't support the Droid Maxx, and still don't understand what's going on.
I also have the same question as the OP: How can there not be a full root process/massive ROM list already for the Maxx with such a big community and such a popular phone line?
We're still waiting on a proper root
That said, anyone have any fun alternatives until then? Favorite/not well-known launchers or other themes?
PS Anyone have an Aviate Launcher invite left?
Thanks!
Vonsk said:
You guys say they're basically the same phone so everyone uses one forum, so can we install ROMs made for the other Droid devices?
My guess is probably not, so WHY are they not separated- silliest thing they could have done- I had to track this forum down over a week after I thought XDA just didn't support the Droid Maxx, and still don't understand what's going on.
I also have the same question as the OP: How can there not be a full root process/massive ROM list already for the Maxx with such a big community and such a popular phone line?
We're still waiting on a proper root
That said, anyone have any fun alternatives until then? Favorite/not well-known launchers or other themes?
PS Anyone have an Aviate Launcher invite left?
Thanks!
Click to expand...
Click to collapse
Off the top of my head, the kernel is still signed by moto and cannot be modified.
Sent from my XT1080 using Tapatalk
I have been using Custom Rom's for a while. But this is usually to bring a phone up to the latest possible Android version well after the manufacturer has stopped updating a device . I have been using Nexus devices so typically this is 18 months after a model is first introduced. Bit of a sore point with me coming from iPhones which get supported for much longer period. but I digress.
In the case of the Moto G. I question whether it is beneficial ATM to install a custom ROM? I have tried a couple, but have been quite disappointed up till now with reliability and performance.
So for now I have stayed with the standard Moto G Rom. Then tweaked it a little by doing the following.
1. Unlocked the phone
2. Rooted using TWRP (couldn't get CWM to work right)
3. Eliminated the Unlocked warning screen at start up :- http://forum.xda-developers.com/showthread.php?t=2548530
4. Changed the 3G data to H, H+ format :- http://forum.xda-developers.com/showthread.php?t=2600654
5. Installed Qualcomm-optimized bionic and dalvic from here :- http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120 (thanks @drfr )
6. Installed a new Faux123 Kernel, flcon_umts-faux123-kk-005u-signed.zip from here :- http://faux.romhost.me/falcon_umts/kk44/
7. From Play store installed the xposed installer
8. From Play Store added module Gravity box (KK)
9. From Play Store added module Ringer & Notification Volume
10. Installed the Apex launcher
11. From Play Store purchased Faux123 Kernel Enhancement Pro (couldn't find a free tool that worked!)
Result is a very stable ROM together with most of the little tweaks that I like to get from a Custom ROM. Plus everything works great. The current Antutu result is 19860.
So my general question, what is the advantage of using a Custom Rom, when for at the moment at least, the manufacturers ROM is fully up to date and with a few simple tweaks provides Custom Rom like appearance, together with great stability and performance?
As far as I know, the stock rom has a lot of optimizations for the Moto G hardware. For instance, its based on F2FS which is something the GPE Moto G does not have going for it.
Sent from my XT1034 using Tapatalk
grahamgo said:
...
Click to expand...
Click to collapse
That´s exactly the way I see things too. Played around with custom ROMs for a while and then came back to stock + all the enhancements you mentioned. Just a note to the point 5 of your list. Optimized dalvik and bionic are already included in stock ROMs.
I have this way of thinking too. So just going through the steps 1, 2, 3, 7, 8 and 10. My phone is excellent.
drfr said:
That´s exactly the way I see things too. Played around with custom ROMs for a while and then came back to stock + all the enhancements you mentioned. Just a note to the point 5 of your list. Optimized dalvik and bionic are already included in stock ROMs.
Click to expand...
Click to collapse
Thank you, I didn't know that, funny but I could swear that Antutu improved! I am still trying to decide if Point 6. Faux123 is really worth it. The 1.6gh/z over clocking is working and I am still getting two days of average use per charge. Can't decide either way really......
Same here, at this point, custom roms (non stock based) are non sense, since the stock is almost Aosp and updated as hell. Xposed is all you need.
Sent from my XT1032 using XDA Premium 4 mobile app
All you need is Xposed, Faux kernel and the optimized Dalvik :S
Enviado desde mi iPod touch con Tapatalk
Correct me if I am wrong but the stock roms from moto are equipped with the Qualcomm-optimized bionic and dalvik patches, aren't they?
If not where can I find this patches?
Soerdroid said:
Correct me if I am wrong but the stock roms from moto are equipped with the Qualcomm-optimized bionic and dalvik patches, aren't they?
If not where can I find this patches?
Click to expand...
Click to collapse
1. http://forum.xda-developers.com/showpost.php?p=48932223&postcount=430
2. http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120
Great antutu result. Mostly due to the overclock. CM based roms doesnt have working overclock yet.
Im far away from that 19860 antutu score, any tips? I installed faux kernel and optimizers from qualcomm and cant get even close to 18000.
Enviado desde mi XT1032 mediante Tapatalk
grahamgo said:
I have been using Custom Rom's for a while. But this is usually to bring a phone up to the latest possible Android version well after the manufacturer has stopped updating a device . I have been using Nexus devices so typically this is 18 months after a model is first introduced. Bit of a sore point with me coming from iPhones which get supported for much longer period. but I digress.
In the case of the Moto G. I question whether it is beneficial ATM to install a custom ROM? I have tried a couple, but have been quite disappointed up till now with reliability and performance.
So my general question, what is the advantage of using a Custom Rom, when for at the moment at least, the manufacturers ROM is fully up to date and with a few simple tweaks provides Custom Rom like appearance, together with great stability and performance?
Click to expand...
Click to collapse
True. But its for now and that is because this is a brand new phone also with multiple variants like 1031/2/3
Hence creating a kind of obstruction for a successful ROM dev
Furthermore you don't just dev a ROM to get an Android update.
Its for the different features that people are looking for.
You might wanna try xposed modules.
Hell l0tta options there. Not for now but then for future.
Also then small little tweaks from other phones can be ported to this one.
There are just countless things that you can customize once you are rooted.
I had a Galaxy Ace duos CDMA which had no custom ROM.
But once I got it rooted my phone was so much better.
I had an extended internal memory with my SD card.
The bloatware that covered the small little internal memory was completely removed.
And it was so much faster and Functional with those rooted apps.
If that small little phone could do some magic with rooting.
Then this is a beast.
Half the new functionality that we get on the updates are actually the features of apps that work on rooted phones.
Wifi hotspot for an instance.
Agreed that in the current scenario its really not so useful but rooting your phone is a gift to yourself
Sent from my XT1033 using xda app-developers app
How you guys were able to use Faux with Dalvik? Faux only works on my phone with ART. If i try Dalvik, com.android.phone force closes all the time. I also have tried the new dalvik, no luck either.
And that prevents me to use XPosed, cause it doesn't have an ART version. And i really miss GravityBox...
Can someone explain me how to do it?
Moto G Dual Sim (XT1033) with KitKat 4.4.2
checked the system/lib in my motog stock(nongpe) and doesnt have all the files from the Qualcomm-optimized Dalvik & Bionic libraries so can I have the latest version links to flash?Thanks
tsimitsangaz said:
checked the system/lib in my motog stock(nongpe) and doesnt have all the files from the Qualcomm-optimized Dalvik & Bionic libraries so can I have the latest version links to flash?Thanks
Click to expand...
Click to collapse
Look into system/vendor/lib
Sent. Really?
yes checked.. I need to have ( libc.so, libm.so, libcutils.so, libdvm.so, libqc-opt.so, libcutils.so) and I have only libqc-opt.so from these files.
tsimitsangaz said:
yes checked.. I need to have ( libc.so, libm.so, libcutils.so, libdvm.so, libqc-opt.so, libcutils.so) and I have only libqc-opt.so from these files.
Click to expand...
Click to collapse
You do have all those files, they are not in the same folder. Just search harder.
intellq said:
How you guys were able to use Faux with Dalvik? Faux only works on my phone with ART. If i try Dalvik, com.android.phone force closes all the time. I also have tried the new dalvik, no luck either.
And that prevents me to use XPosed, cause it doesn't have an ART version. And i really miss GravityBox...
Can someone explain me how to do it?
Moto G Dual Sim (XT1033) with KitKat 4.4.2
Click to expand...
Click to collapse
No one?
intellq said:
No one?
Click to expand...
Click to collapse
Use this rom, stock, debloated, faux kernel and xposed. Clean and fast.
http://forum.xda-developers.com/showthread.php?t=2606943
[ROM]Nexus G+ Build 007[4.4.2]
Sent from my XT1032 using XDA Premium 4 mobile app
Alejandrissimo said:
Use this rom, stock, debloated, faux kernel and xposed. Clean and fast.
http://forum.xda-developers.com/showthread.php?t=2606943
Click to expand...
Click to collapse
That rom probably won't work in my phone. I'm on an XT1033 (dual sim)
Someone with stock was able to make faux + dalvik work?