Related
So after seeing many things that is said with the D2 I thought I should write a post like this. This is just to clear up confusion so users can have the knowledge to use in the future.
Every ROM for the D2 is AOSP
I have seen this said many times and it bugs me that people think that all ROMs are AOSP. As of now, there are actually only a few AOSP ROMs for the D2, cvpcs' Tanzanite/Obsidian, Cobalt, and blackdroid's Ultimate Droid. Other ROMs like rubiX, Liberty, ApeX, and Fission are basically Motorola ROMs with the blur applications replaced with AOSP applications. Now this does not actually make it AOSP. It has features from AOSP, but there is much more to it than the applications. These blur-based ROMs actually have other AOSP-like features, such as lock screen music controls and a few others. Now that also doesn't make it AOSP, those are just a few features that were originally modifications to AOSP to add more functionality to a ROM. That doesn't mean these ROMs are bad in any way. They are actually very good. The only downfall of them is the fact that they are limited to what can be done.
There can't be AOSP ROMs without a custom kernel.
Another statement I have been told or have seen several times. It is considered AOSP if it comes from Google's source. A kernel won't affect the fact that it was built from source. Although it would be ideal for a custom kernel with AOSP, it isn't needed.
A custom kernel is needed.
This is another incorrect statement. It would be nice to replace the kernel, but it isn't needed. The kernel that is provided to us from Motorola includes basically everything the end user would need. Also there is overclocking(although it isn't the easiest implementation) by adding a temporary module to the kernel that is erased after the phone is powered off.
Gingerbread won't come to the D2 until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the D2 has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.
Fantastic post. Very clear, informative and I learnt more in the 2 minutes reading your post than the hours I've spent reading other threads.
Top stuff.
"Most truths were once deemed blasphemy"
Whats taking so long for Gingerbread then?!
Nice write up, very informative.
Matt, can you check out the MIUI thread in D2 development? Another developer and I are working on the port but we need someone with really good D2 experience to look over the rom and tell us why it gets stuck on the moto logo each time, we would really appreciate it if you could check it out for us.
Thanks,
ljbaumer
P.S. nice post it's really clear and will help out noobs.
ljbaumer said:
Matt, can you check out the MIUI thread in D2 development? Another developer and I are working on the port but we need someone with really good D2 experience to look over the rom and tell us why it gets stuck on the moto logo each time, we would really appreciate it if you could check it out for us.
Thanks,
ljbaumer
P.S. nice post it's really clear and will help out noobs.
Click to expand...
Click to collapse
Matt I would have to ask nicely along with ljbaumer, if you wouldnt mind taking a look at the rom dev section for the MIUI D2 rom!
I know you lost your D2 and no longer have it but anything could help them w/ progress
Would be greatly appreciated! Thanks!
Someone should sticky this thread cause it is really useful information
Gingerbread won't come to the D2 until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the D2 has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.
Click to expand...
Click to collapse
This is now irrelevant, take a quick jaunt over to MDW where P3Droid has released full stock moto gingerbread builds for both D2 and DX in update.zip formats (new blur builds). Only catch with them at this time is that no one has figured out how to root them yet, but you can restore back with a previous SBF.
What differences could be expected if GB were to be paired with a .35 kernel rather than the .32 kernel of the current Moto GB leak?
bladearronwey said:
This is now irrelevant, take a quick jaunt over to MDW where P3Droid has released full stock moto gingerbread builds for both D2 and DX in update.zip formats (new blur builds). Only catch with them at this time is that no one has figured out how to root them yet, but you can restore back with a previous SBF.
Click to expand...
Click to collapse
I'm pretty sure they've rooted the GB builds... I had superuser access and could boot to recovery and everything. You do have to SBF back to them though, I learned that the hard way.
I am running the rooted Gb and loving it. I would love to see a cm7 version for the Droid 2
Sent from my DROID2 using XDA App
DX is supposedly getting the GB OTA, so the D2 should be next and soon!
First of all I did search and found some info but it wasn't really helpful... I'm new to the Charge. I've had many android phones before and have never had problems rooting and flashing roms. I've searched and I've seen the instructions on how to root and they look like they're in another language. Does anyone have more clear instructions on how to root??? Any help, asap, would be appreciated. Thanks in advance.
we are in the same page buddy....
---------- Post added at 07:10 AM ---------- Previous post was at 07:04 AM ----------
found it is at the general section not development section like most of threads.
http://forum.xda-developers.com/showthread.php?t=1172904
Sent from my SCH-I510 using xda premium
brandon2x said:
First of all I did search and found some info but it wasn't really helpful... I'm new to the Charge. I've had many android phones before and have never had problems rooting and flashing roms. I've searched and I've seen the instructions on how to root and they look like they're in another language. Does anyone have more clear instructions on how to root??? Any help, asap, would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Hey Brandon, this thread gives a great description on how to root your charge. => http://forum.xda-developers.com/showthread.php?p=14692818
If you still have questions feel free to ask, and I'll try to answer them as best as i can.
Ok, so i got it rooted and just installed a de-bloated stock Rom. Its ok, but now question is, if i decide to install a gingerbread Rom or any other Rom such as gummycharged, can i just install like i did on my bolt or x in cwm or do i have to use this odin program? if i have to use odin, how do i go about installing that way? thanks in advance...
Sent from my SCH-I510 using XDA App
brandon2x said:
Ok, so i got it rooted and just installed a de-bloated stock Rom. Its ok, but now question is, if i decide to install a gingerbread Rom or any other Rom such as gummycharged, can i just install like i did on my bolt or x in cwm or do i have to use this odin program? if i have to use odin, how do i go about installing that way? thanks in advance...
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
For most roms, like gummycharged fe 2.0 and gbe 2.0 you just need CWM. I'm sure the process is the same as your bolt but just to be clear: Place the rom's zip you want on the sd card, boot into CWM, wipe date, dalvik cache, and cache partition, and then install the rom from the sd card. =) There are also some roms that come as full-odins, where you flash the package through odin and it does the work for you. That being said, you shouldn't run into that many unless you are un-rooting your phone. Hope that made sense. let me know if it doesn't.
Sweet. Thanks alot dude. That's awesome to know. I don't really wanna get into messing with odin. I like being able to do everything from my phone and not having to hook up to the laptop.
Sent from my SCH-I510 using XDA App
LOL, I was just coming in here to ask that exact same question as the OP. The wording was almost verbatim what I was going to say. The majority of experience I have had with Android is with HTC phones. I have rooted a few tablets as well. The instructions for the charge root are super confusing compared to previous devices.
My big issue is with the terminology. Like what is EE4, EPF1? Are there certain kernels that only work with certain roms? How easy is it to completely pooch the phone if I click on the wrong button in Odin? Can I make a nandroid backup and swap roms on the fly using Rom Manager depending on my moods or is it more complex then other android phones?
I haven't checked out the posts yet in this thread but seeing as how at least one other person has been just as confused as me I'm wondering if someone out there that has experience with both Samsung and lets say HTC phones can make a simple guide that makes comparisons to other rooting processes. For people that arn't used to Samsung phones, these instructions can be very overwhelming and there doesn't seem to be a newbie thread out there that gives information on all the abbreviations used and what they mean.
trevoryour said:
LOL, I was just coming in here to ask that exact same question as the OP. The wording was almost verbatim what I was going to say. The majority of experience I have had with Android is with HTC phones. I have rooted a few tablets as well. The instructions for the charge root are super confusing compared to previous devices.
My big issue is with the terminology. Like what is EE4, EPF1? Are there certain kernels that only work with certain roms? How easy is it to completely pooch the phone if I click on the wrong button in Odin? Can I make a nandroid backup and swap roms on the fly using Rom Manager depending on my moods or is it more complex then other android phones?
Click to expand...
Click to collapse
EE4, EP1W, ect are OS build numbers. EE4 is the current official release Froyo build. EP1W is the latest leaked Gingerbread build we have. Those are pretty much the only two version you want to worry about right now. There are Froyo kernels and Gingerbread kernels. Any Froyo kernel will work with any Froyo ROM, and any GB kernel will work with any GB ROM.
Only mess with the PDA button in Odin and you'll be fine. Forget the Phone button even exists, because that's the button that can get you into trouble. You can use the PIT button as well if you have the charge.pit file, but it's not normally necessary, so only do that if you have a reason.
ROM Manager is useless with this phone. There are reports that there is a version of CWM from it that will work with the Charge, but it doesn't work nearly as well as the latest imnuts CWM. The orange CWM dated 8/17 will let you do nandroid backups...you just need to boot directly into it and do them from CWM itself and forget about ROM Manager.
shrike1978 said:
EE4, EP1W, ect are OS build numbers. EE4 is the current official release Froyo build. EP1W is the latest leaked Gingerbread build we have. Those are pretty much the only two version you want to worry about right now. There are Froyo kernels and Gingerbread kernels. Any Froyo kernel will work with any Froyo ROM, and any GB kernel will work with any GB ROM.
Only mess with the PDA button in Odin and you'll be fine. Forget the Phone button even exists, because that's the button that can get you into trouble. You can use the PIT button as well if you have the charge.pit file, but it's not normally necessary, so only do that if you have a reason.
ROM Manager is useless with this phone. There are reports that there is a version of CWM from it that will work with the Charge, but it doesn't work nearly as well as the latest imnuts CWM. The orange CWM dated 8/17 will let you do nandroid backups...you just need to boot directly into it and do them from CWM itself and forget about ROM Manager.
Click to expand...
Click to collapse
nice summation (is that a word? lol)... this is all you need to know, its not hard as Sammy phones in my experience are the easiest to root/rom/recover
blazing through on my 4G Droid Charge
This was all helpful. I installed gummycharged with no issues. One other thing. Is the install of a kernal for gingerbread roms done in cwm? And what is a standard kernal to use? Do I need to install a different radio?? Thanks.
Sent from my SCH-I510 using XDA App
brandon2x said:
This was all helpful. I installed gummycharged with no issues. One other thing. Is the install of a kernal for gingerbread roms done in cwm? And what is a standard kernal to use? Do I need to install a different radio?? Thanks.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
kernels for all roms on the Charge are installed in CWM, as for GB kernels you can't go wrong with any of Imoseyons voodoo ones... radios don't necessarily need to be updated but I've noticed a big improvement with the latest EP1W modems, however the results vary on different phones I've seen
blazing through on my 4G Droid Charge
anoninja118 said:
kernels for all roms on the Charge are installed in CWM, as for GB kernels you can't go wrong with any of Imoseyons voodoo ones... radios don't necessarily need to be updated but I've noticed a big improvement with the latest EP1W modems, however the results vary on different phones I've seen
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
Dont use 2.4.0 it bootlooped my phone. (Made it keep going through the SAMSUNG screen and not boot up)
Download 2.3.4 instead it works fine.
EDIT: I'm talking about imoseyon's voodoo kernels - just google them
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
I'd like to give it a whirl anyway.
mtnlion said:
I'd like to give it a whirl anyway.
Click to expand...
Click to collapse
ONLY with safestrap, right now. If you try to flash it with the bootstrap it will softbrick your phone.
--EDIT--
Remember safestrap is not really working right now... lfaber06 and I have some highly modified versions that really are not for the rest of the world yet, and my version has a custom compiled version of CWM, and is a little buggy.
jimbridgman said:
I have some news on my CM7 porting, good and bad.
The good new first.
Good:
I can get the FULL version including the kernel to run in safestrap, and it is like 97% working.
Bad:
I can not get the ROM, without the kernel, to boot properly when flashing it to the phone from the bootstrap. I have spoken with several experts and this may not be something we can work out until the bootloader is unlocked. There are hooks in almost every part of CM that make android calls, that are part of their own version of android (it is heavily customized, and the code is available, and how I got it) and the kernel they use. The reason this works in safestrap, is because I can load the kernel on top of our kernel, but it is slower this way. Think of running a VM on top of your current OS, and how that can have some lag if your computer is not real powerful.
The bottom line, I am not sure if we can get CM working for everyone just yet. I am not sure where lfaber06 is at with CM9 and if he has tested it directly on the phone without safestrap yet or not. Maybe he will post in here what his experience has been, with this.
Click to expand...
Click to collapse
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
lfaber06 said:
I have made quite a bit of progress on cm9 in safestrap, the only real issue i have is the radio which i am constantly trying different things with. I have not tried flashing cm9 or cm7 in the bootstrap but I have a method for it..(I think, Remember the D3 can run cm7 from the bootstrap) I have a file I have modified for cm9 that im sure will work for cm7 flashing in bootstrap. You would need to add some modified files to /system/rootfs/ and preinstall support to boot init.d and also run the fixboot.zip at boot. Really running under safestrap (i'm using the /preinstall partition) does not seem to slow it down much. But tbh I havent really "run" it while it's booted I'm usally making edits and rebooting to check for service. I'm going to tear into hashcodes cm7 for the D3 and see what I can come up with. It seems like it had the kernel included but the scripts only called for it if the safe file existed on the /data partition.
Click to expand...
Click to collapse
PM me a link to hashcodes d3 CM7 ported ROM (if you have one, I have had a hard time locating a completed one), and not the source code, that is what I used to compile my CM7 port with. I would like to test something, I have a theory on this, that I won't share with everyone here, since it really would not be very interesting here to anyone not trying to port these over.... we will talk more about this in PM.
Thanks!
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
JRW 28 said:
Jim what about taking a look at the Droid X2, they have a alpha build of CM 7.2?
http://forum.xda-developers.com/showthread.php?t=1442803
Click to expand...
Click to collapse
that is version 2.3.4 we are on 2.3.5 and we HAVE to use ports from 2.3.5 no way around it.
Missed that little details
CM9 does work when flash through bootstrap, I tried it the other day...
farshad525hou said:
CM9 does work when flash through bootstrap, I tried it the other day...
Click to expand...
Click to collapse
Care to share???? Plz.... it may be helpful.
Sent from my MB865 using Tapatalk
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
farshad525hou said:
Yeah a couple days ago I flashed CM9 through Bootstrap. Everything booted okay and and everything ran fine. Again the only problems were that the phone didn't work, due to the telephony.apk issue and market wouldn't launch. Otherwise everything else ran a-okay!
Click to expand...
Click to collapse
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
lfaber06 said:
Your right it does work but my ported verison does not!! That's actually good news BC now I know where to find the problem areas. Jim this has got to help you
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yes it sure does thanks, I flashed it, played with it, and I am taking a look at a few things with your CM9 ROM, and since we PM'd I have been digging into the D3 CM7.2 version that hashcode had created. I am not quite ready to flash it yet, but maybe something tomorrow, once I have the ROM to the point that I am happy to play with it on my phone and see what works and what does not.
It looks like the issue with my old CM7 ROM, from the logs I grabbed a little while ago, with logcat, were due to kernel driver files not found during loading, so it looks like my compile had issues linking to our kernel. I so wish I had the source for our phones kernel, it would make compiling CM7 so much easier, and NO the ME865 source will not due, so don't mention it here.
Jim
Glad I could help! Also @lfaber06, what do you mean by your ported version doesn't work? That's the one I flashed.
**Edit** Also the camera doesn't work, if you guys want in to that. Probably an incorrect driver or something...
So... any news to report on either CM7 or CM9?
farshad525hou said:
So... any news to report on either CM7 or CM9?
Click to expand...
Click to collapse
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
lfaber06 said:
By ported I mean the ones i've cooked up, their not ready for prime time so no sense in uploading them but they are good to share with jim. I don't think the camera works on any of the unofficial builds it uses a new type of "ion" driver that makes the camera uber responsive. Your post has however led me to build a few working ports for bootstrap but its still the same old radio driver issue.
Click to expand...
Click to collapse
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
farshad525hou said:
Cool Any ideas from what phone we can pull the radio drivers from? I'm assuming that it has to be a GSM phone running the TI's OMAP processor, that also has a CM9 port, right?
Click to expand...
Click to collapse
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
lfaber06 said:
Tbh, I have no idea... I have been looking at every moto phone google can find and so far I have had no luck. Call me crazy but I think our radio is more commonly found in sony's... (I'd welcome ANY input on the radio)
Click to expand...
Click to collapse
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
farshad525hou said:
What exactly should I be looking for to find a phone with a similar radio? Here's a system dump for the xperia play, you could try pulling the telephony.apk... http://rapidshare.com/files/45600580..._Play_DUMP.rar Most of the sony's though run on Qualcomm's Snapdragon Processor
Click to expand...
Click to collapse
That's the thing idk... I assumed that it was a Sony radio BC when I Google rlidu300-ril.so I get a device tree for a Sony. We need to know what radio we have then we can start checking sources.
Sent from my MB865 using Tapatalk
I want to go back to GB as I'm not satisfied with the ICS ROMs I've tried (only had this phone a few weeks). Dev board is flooded with ICS, any GB suggestions?
Sent from my Nexus S 4G using Tapatalk
I highly reccomend Oxygen, only problem I ever had with it was sending and recieving mms. Other than that I say it is lightening fast and stable.
Were you able to fix the mms issue?
Sent from my Nexus S 4G using Tapatalk
i'd say BrainMaster's MIUI 2.3.7 ROM , i was running it before i updated to ICS
qtwrk said:
i'd say BrainMaster's MIUI 2.3.7 ROM , i was running it before i updated to ICS
Click to expand...
Click to collapse
Should have mentioned I want everything to work including 4g.
Sent from my Nexus S 4G using Tapatalk
Try .CIBERGR-MOD 's GB version. It's a fast rom. Although, I'm not sure if he has a NS4G version.
Sent from my Nexus S using Tapatalk
Peter Alfonso's GPA19 ROM is the most stable one that I tried. Look for Peter Alfonso's site and click the Downloads link for crespo. I would post a link here, but XDA's nonsense won't allow it.
Download the 12-07-11 one to get the latest GB version. There aren't a lot of customizations like CM, Oxygen, MIUI, etc., but it's stable as hell. The latest Oxygen (2.3.2) has a REALLY obnoxious, and largely ignored, backlight notification bug where you have to reboot to get the lights to go out... only way I've ever found to fix it is to install another kernel. However, Peter Alfonso's got one of those too... just go to his site and it should be on the second page of the "blog."
I know you said you didn't like ICS, and I didn't either at first, but Pete's ICS ROMs are also great and very stable. The latest is 01-30-12, and you can get it from the same crespo download page.
question.
hey man i got a question, could i use peter alfonso's rooted stock rom for gingerbread (right?) when downgrading, right? instead of re rooting it.
charchuck said:
Peter Alfonso's GPA19 ROM is the most stable one that I tried. Look for Peter Alfonso's site and click the Downloads link for crespo. I would post a link here, but XDA's nonsense won't allow it.
Download the 12-07-11 one to get the latest GB version. There aren't a lot of customizations like CM, Oxygen, MIUI, etc., but it's stable as hell. The latest Oxygen (2.3.2) has a REALLY obnoxious, and largely ignored, backlight notification bug where you have to reboot to get the lights to go out... only way I've ever found to fix it is to install another kernel. However, Peter Alfonso's got one of those too... just go to his site and it should be on the second page of the "blog."
I know you said you didn't like ICS, and I didn't either at first, but Pete's ICS ROMs are also great and very stable. The latest is 01-30-12, and you can get it from the same crespo download page.
Click to expand...
Click to collapse
Loaded up the 01-30-12 ICS this morning since that would be the easiest transition. Using Apex and so far, so good. Thanks!
Sent from my Nexus S 4G using Tapatalk
I'm currently running Euroskank CM7 kangs.
Wow, really. I don't have any ICS envy seeing how sweet those kangs are. They're smooth as butter and stable too! Checking my phone, my current uptime is 132 hours (5.5 days) since my last reboot, which was to flash the latest kang back then.
allenxx said:
hey man i got a question, could i use peter alfonso's rooted stock rom for gingerbread (right?) when downgrading, right? instead of re rooting it.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking. Both of his ROMs are pre-rooted, so no, you won't have to re-/root anything. But since you're going from ICS to GB you'll have to wipe everything, so there's no real "downgrade" path.
From a rooting perspective, the only difference I've noticed, that's kind of annoying, is that his GB ROM contains busybox and his ICS ROM doesn't. It's not a deal-breaker since there are Market apps to add it in, but it's kind of annoying that the binary has to be re-linked after each update/flash.
charchuck said:
I'm not exactly sure what you're asking. Both of his ROMs are pre-rooted, so no, you won't have to re-/root anything. But since you're going from ICS to GB you'll have to wipe everything, so there's no real "downgrade" path.
From a rooting perspective, the only difference I've noticed, that's kind of annoying, is that his GB ROM contains busybox and his ICS ROM doesn't. It's not a deal-breaker since there are Market apps to add it in, but it's kind of annoying that the binary has to be re-linked after each update/flash.
Click to expand...
Click to collapse
Im asking that if i can reverted back to gingerbread version without loosing root, may i install his pre-rooted stock without loosing root. Thats all, but since you mentioned it, im relived to revert it back. but i couldnt find his link could you provide me one? Also is it regular to flash it back to gb or is there a special method to do it?
I can't post links yet because our fine friends at XDA say that I need to post more for the privilege. Pfft.
You should be able to type peter alfonso downloads crespo and get to the page. 12-07-11 is the latest GB version (GPA19).
There's no "special" method for flashing, just do what you would do when going from one incompatible ROM to another... wipe data/factory reset, format cache partition, format /system, wipe dalvik cache. There are probably a million different combinations that different people will give you for the proper install, but that's what I normally do.
Tryout CyberGR's CM7 MOD and you won't go back:
http://forum.xda-developers.com/showthread.php?t=1378469
Just read the feedback in the thread and you'll understand.
perfect, and uh before i do that it could be any rooted gb rom right? just curious, that's all.
Don't mean to hijack the thread but what if I wanted to put a custom GB ROM on top of stock GB rom. I'm curious if you can just flash without wiping? Or should I do titanium backup instead?
charchuck said:
I can't post links yet because our fine friends at XDA say that I need to post more for the privilege. Pfft.
.
Click to expand...
Click to collapse
you have only 5 posts and complaining ? I wonder when you hit 100+ post what would you do ? if you don't like the forums why you're here ?
calisoldier83 said:
Don't mean to hijack the thread but what if I wanted to put a custom GB ROM on top of stock GB rom. I'm curious if you can just flash without wiping? Or should I do titanium backup instead?
Click to expand...
Click to collapse
Wipe.
10 chars.
I just put on the Peter Alfonso rom, it's super fast. Well probably keep this until official ics is released.
Sent from my Nexus S 4G using xda premium
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there and enjoy some of the finer benefits. Stability will be better but you won't be dead-set stable. GPS has been an issue for some since the inception of the phone. Others have GREAT GPS reception.
Research the Development forums and find a CM7.2 ROM that best suits you. You can of course go CM9 (ICS) but you won't get HW Acceleration and some things just flat out don't work yet.
New2my8125 said:
If you're still using the stock ROM, and are still on 2.3.3, then you are experiencing SW suckage... Get a custom CM7 Rom on there
Click to expand...
Click to collapse
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
mog44net said:
Hi all, thanks for taking the time to read.
I have a LG G2X, love the feel, the display, the specs and the price. Hate the phone....in every other way
I am on my 4th G2X now b/c I keep taking it back to T-Mobile to get a new one based on the following things my phone does:
1. It restarts 1-2x a week, randomly with or without a power adapter plugged
2. It freezes up every other day or so and requires a hard restart (battery pull) to resume use
3. It frequently takes 5+ minutes to get a GPS lock (tried in several cities coast to coast US)
Now if it were just the first phone I could say lemon, but every G2X I have owned does this, T-Mobile told me it was a known issue with the phone but couldn't tell me if it was software or hardware in nature.
So my question to you fellow forumites is this: Is the issue hardware related (move on to another phone) or software (Rom install fixes all my worries and I'm happy forever and ever and ever)?
Click to expand...
Click to collapse
Software...........I am running Hellfire Phoenix ROM and flashed a GPS fix, and new baseband, now I get GPS locks within <>10 seconds, my phone never freezes, or reboots.
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
+1
Sent from my LG-P999 using xda premium
wmm said:
The stability and GPS performance are greatly enhanced by the stock 2.3.4 ROM, also, if you're not a CM7 fan.
Click to expand...
Click to collapse
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
mog44net said:
Thanks for the great responses guys, just another reason I love this forum.
I should have given a few more details, I am running stock 2.3.3 on T-Mobile in the US.
Few questions for a techie (but virgin ROMer):
1. Is the 2.3.4 stock available OTA? I haven't seen any available upgrades.
2. What does baseband refer to? (trying to educate myself on the terms)
3. Any favorite ROMs? My must haves are stability and speed, other than that any goodies/awesomeness is welcome but the first two are absolute.
I am tempted to stick to stock ROMs as I haven't flashed one myself yet and this phone is my lifeblood b/c of work.
On a scale of 1-10 where 1 is "I did it with on accident when I dropped it down the stairs" and 10 is "the most difficult thing you will ever do in your life" what is the difficulty for a ROM virgin to sucessfully flash to 2.3.4 (if it is not available OTA) or CM7/other ROMs,etc?
I am technical, 12 year IT professional with MCSA/CCNA, etc but haven't done much research into the ROM biz. If its not too difficult is there a "Must read" guide for noobs?
Click to expand...
Click to collapse
Difficulty is pretty low. If you can follow instructions, and understand what you're doing, then you should be good to go. If you want 2.3.4, you're gonna need to use LG's ****ty software. Either you use KDZ flasher, or LG's official PC suite. Both crashed on me constantly on Win7 x64. I was lucky/unlucky, it crashed right after writing the baseband (low level radio firmware). It hadn't even partitioned anything yet if I tried to turn it on, not even a backlight was showing. So I had to use NVflash to completely repartition it to stock. After that, I flashed CWM (clockworkmod), the custom recovery. Nowadays, TWRP is available. TWRP is awesome, and they have awesome Devs. TWRP (teamwin recovery project) is touch based rather than CWM and traditional volume key and power button navigation. There is CWM touch, but it's extremely experimental and I find it too glitchy compared to TWRP. TWRP is a work in progress however and there may be issues (I had one but it was easily fixed with one command when I spoke with the Devs on irc) I haven't had any serious ones though. IMO it's easier to NVflash in a Linux environment, because there is no messing around with drivers. But after drivers are installed on windows, the difficulty level plateaus.
As for my favorite ROM, that would currently temasek cm7 builds. They're stable, fast and they're customizable as f***.
I don't have any links right now, because I'm on my phone, (I can grab them later/soonish) you're going to want tga_gunman's thread named something along the lines of "One click recovery flasher" that's for CWM recovery. If you want TWRP, there's a thread that has TWRP in the title.
Also look for "ROM for recovery under NVflash" or something similar to that. That will take you back to complete stock 2.3.3 no matter what happened software wise, unless you somehow managed to break the baseband. The baseband is the only thing that cannot be fixed by NVflash, only can be fixed by LG's ****ty PC software.
For temasek's cm7 builds, the thread is not created by temasek, but the builds are by him. It should be at build 133 or 134.
If you need anything else, PM me maybe.
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
mog44net said:
Good deal, I'm planning on following this thread from the general section (http://forum.xda-developers.com/showthread.php?t=1594650).
I'm leaving out of state but will work on it over the weekend.
Thanks for all your help and support everybody, any additional comments are welcome before I start flashing this weekend.
Q - Do I need to get the owain's baseband flash fix or not with the ROM you sugested, the comments on the thread are confusing me a bit. If so where can I download the correct one, can't seem to find it in the Dev threads.
Click to expand...
Click to collapse
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
tahahawa said:
You only need that baseband fix if you have the latest baseband (March 2012) from v21y. It should be available in owain's hopto.
Click to expand...
Click to collapse
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
mog44net said:
Help a noobie out, what/where is owain's hopto?
Edit: I'll test without the fix, to be sure and flash the baseband if needed, i understood from the comments in the ROM's thread that its needed for Bluetooth calls.
I might have found the baseband fix link (http://forum.xda-developers.com/showthread.php?t=1776843) can anyone confirm?
Click to expand...
Click to collapse
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
tahahawa said:
That's the one
Edit: if you need Bluetooth calling on the new baseband, don't flash any cm ROMs. Stay on the old one if you need/want Bluetooth calling.
Click to expand...
Click to collapse
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
***edit***
Nix the above. I completely read it wrong, thought you were saying all CM ROMs didn't work with Bluetooth. Just so on the current Baseband.
I'm on Jul 15 2011 Baseband currently, so I'll attempt the CM7 ROM this weekend when I'm back home and able to devote more focus. Coming from stock 2.3.3 do I need to flash a kernel as well or will that be in the ROM <---showing my ROM noobness but unashamed to learn.
mog44net said:
Firstly thanks for all the good Q/A, like a good forum noobie, I'm marking thanks each reply.
I want to make sure I understand your comment. This is what I understood, let me know if I'm off/on. The CM Roms do not work with BT calling, so I should stick with stock if that's important to me? I would assume then for me to get beyond my current issues (OP) my best bet would be to Flash the 2.3.4 stock?
Thanks again for the info and time.
Click to expand...
Click to collapse
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
tahahawa said:
If you decide to get the newer baseband (you get it with 2.3.4 kdz, only way to get new baseband) and bt calling is important, do not go to cm. If you don't mind staying on the older baseband, bt calling will work fine on cm.
Click to expand...
Click to collapse
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
BTW as I haven't seen it, I get happy feelings when I look at your avatar
mog44net said:
Lol, I feel so dumb, its like learning a new language while being held underwater.
kdz=?
I'm trying to understand why I would decide to get the newer baseband? If I do I can use BT calling but can't use CM7 ROMs, if I don't I can use CM7 ROMs and BT calls should work fine. Dont see the upside to upgrading the baseband, unless it has issues?
Click to expand...
Click to collapse
KDZ = LG's proprietary file type to update their phones via PC officially. A lot of people say the new baseband gives them better gps and call quality. Basically if you don't change baseband to the new one, everything will work perfectly. If you DO switch, everything will work perfectly, but only on stock. Everything will work on cm except Bluetooth calling with the new baseband. I don't think it's worth restricting yourself to stock because of the new baseband and and bt calling. My recommendation? Don't change baseband, just go to cm. Also, soon we might start to see android 4.1.1 jelly bean. They won't be stable for a while though.
Too much fun.
Couldn't wait, just finished flashing CWM, then backed up, then wiped like 400x then dropped the CM7 ROM you sugested.
Longest 10 minutes of my life letting it sit.
Working great, I'll update here with any additional info or create a new thread.
TY TY TY all
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
cainG2x said:
If it's cm7 get the latest gb one, if it's cm9 get the latest ics one... It has gb or ics in the name of the file.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Much thanks, i'll do that now.
Any ideas on being stuck on EDGE network only?
mog44net said:
Update -
Still working great, only two issues.
* Cellular network is only showing E, played with the settings but can't seem to get any G networks.
* Google apps/play isn't installed, I think I have this one figured out to download/flash from here (http://forum.xda-developers.com/showthread.php?t=1049154) (http://goo.im/gapps/) but I'm confused about which one to DL.
help plox?
Click to expand...
Click to collapse
Yeah goo.im/gapps is the best. For the cell network, try going settings> wireless>mobile>network operators and select "select automatically"