I've been using multiple different ROMs using the 402w radio. I'm wanting to make the jump and try some of the new gingerbread ROMs. If I flash the new radio required for the gingerbread ROMs, what's the process for going back to an old non-gingerbread ROM? Do I have to flash the old radio, or just reflash one of my old nandroid backups of said ROM? Sorry for the n00b question.
Sent from my rooted Thunderbolt running **Das BAMF v1.7 Stripped**
CLoft239 said:
I've been using multiple different ROMs using the 402w radio. I'm wanting to make the jump and try some of the new gingerbread ROMs. If I flash the new radio required for the gingerbread ROMs, what's the process for going back to an old non-gingerbread ROM? Do I have to flash the old radio, or just reflash one of my old nandroid backups of said ROM? Sorry for the n00b question.
Sent from my rooted Thunderbolt running **Das BAMF v1.7 Stripped**
Click to expand...
Click to collapse
You have to flash a radio and rom both ways so a froyo radio and rom and gb radio and rom
Sent from my ThunderBolt using XDA Premium App
Leaked MR2 and MR2.5 is GB and Froyo compatible.
Ok, so to go back to a froyo ROM I'd have to reflash a froyo radio separately from the froyo ROM nandroid?
Sent from my rooted Thunderbolt running **Das BAMF v1.7 ROM**
[email protected]@ge said:
Leaked MR2 and MR2.5 is GB and Froyo compatible.
Click to expand...
Click to collapse
So this would be my best bet? Just flash MR2.5, and load up which ever ROM I choose? It seemed a little more complicated than that from what I was reading in other threads, saying you had to have both MR leak and ROM currently on SD, flash MR and then ROM without actually booting up. Or am I interpreting it to be more complicated than it really is?
Sent from my rooted Thunderbolt running **Das BAMF v1.7 ROM**
CLoft239 said:
So this would be my best bet? Just flash MR2.5, and load up which ever ROM I choose? It seemed a little more complicated than that from what I was reading in other threads, saying you had to have both MR leak and ROM currently on SD, flash MR and then ROM without actually booting up. Or am I interpreting it to be more complicated than it really is?
Sent from my rooted Thunderbolt running **Das BAMF v1.7 ROM**
Click to expand...
Click to collapse
Put rom and radio in /sdcard
wipe cache/data/davlik
flash custom rom
*after it boots notice you have no signal*
use file manager and title mr2.5 "PG05IMG".zip
shutdown
after soft key lights are off, hold vol button down then hold power.
in hboot let it recognize radio
vol button up to upgrade
*let it do its thing*
reboot phone when it tells you
*boom, you have signal*
don't forget to retitle "PG05IMG".zip to something else
Enjoy good sir! =)
[email protected]@ge said:
Put rom and radio in /sdcard
wipe cache/data/davlik
flash custom rom
*after it boots notice you have no signal*
use file manager and title mr2.5 "PG05IMG".zip
shutdown
after soft key lights are off, hold vol button down then hold power.
in hboot let it recognize radio
vol button up to upgrade
*let it do its thing*
reboot phone when it tells you
*boom, you have signal*
don't forget to retitle "PG05IMG".zip to something else
Enjoy good sir! =)
Click to expand...
Click to collapse
Thank you very much! And from there I can flash back to froyo ROMs such as BAMF 1.7 if I choose?
Sent from my rooted Thunderbolt running **Das BAMF v1.7 ROM**
Yes you can.
Also, as noted in OP post of ginger remix beta 6 please expect this.
"Having random reboots right after flash? This is "normal" for this leak, it will subside after a minute or two."
Good deal. That was my only fear was that I wouldn't be able to go back to BAMF 1.7 or VirusRom Airborne. I just downloaded the MR2.5 now to pick out a ROM
Sent from my rooted Thunderbolt running **Das BAMF v1.7 ROM**
Related
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
STEyeAndroid said:
I tried installing BAMF 3.0 RC2 on my phone, and I can't seem to get it working properly. Upon startup it force closes a bunch of things and the radio shows no signal at all. I have ran the MD5 on the download to ensure integrity. Also did a complete wipe prior to flashing. Could this be a radio problem? I haven't done any radio upgrades.
Click to expand...
Click to collapse
You need a gingerbread radio for a gingerbread rom.. so MR2 or MR2.5
Sent from my ThunderBolt using XDA Premium App
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
poloboogie said:
i have the same problem and ive been trying to flash both radios its acting like its doing it in hboot but everything still is the same and no mobile network for me. can someone please tell me a way to get it working how do i check my md5 of my rom and stuff
Click to expand...
Click to collapse
when you say everything is the same, do you mean it still has the previous radio version number?
I'd suggest that you both:
1) Wipe data/dalvik/cache and flash back to a froyo ROM where you do have a signal
2) Upgrade from froyo to the MR2/2.5 radio
3) Re-wipe data/dalvik/cache (or even do it twice for good luck ) and re-flash BAMF 3.0
If its worth doing, its worth overdoing, especially when you're messing with radios and the like. Best of luck!
That's the same problem I first had with gingeritis before flashing the correct radio.. if you are still experiencing the problems after the radio flash i would suggest confirming the radio did install by checking the version number..
if it is all correct do as MattBeyers said and wipe and reflash
Thanks, that seemed to work. I still got a couple of force closes but much less than before. Also I can see my radio now! If I wanted to restore my old my Backup (Stock Froyo - MR1), do I restore my backup then flash MR1? If so, does anyone have a link the MR1 image? TIA!
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
MattBeyers said:
I'm always one to upgrade/downgrade radios before I flash a ROM, so I would say to downgrade to MR1 and then flash the Froyo backup. Also, try going into ROM manager and using the Fix Permissions tool to see if that helps with some of the force closes.
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
I tried mr2 and mr2.5 but could only get 3g. Went back to CM7.
Sent from my ThunderBolt using XDA Premium App
Mr_Joshua said:
Any reason for flashing one before the other? Reading through several of the ROM threads, it seems like everyone has a preference, but no one explains why.
Click to expand...
Click to collapse
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Make sure u have a gb radio mr2 or mr2.5
MattBeyers said:
I just feel like the radio, being the thing that, well, controls every useful function on the phone, should be installed and present when a new ROM is flashed. I may be wrong, but it would seem logical to me that a new ROM would talk to the radio in order to make sure everything is kosher. But what if that's something that a ROM will only do once, at the first boot, and not once a new radio is flashed? Then, all of a sudden, you have the right radio, but its configured improperly by your ROM, since the ROM has already gone through its initial boot set up with the old radio. Therefore, my theory is radio > ROM (Please note, theory. )
Click to expand...
Click to collapse
This makes sense from a logical reason. Perhaps a ROM developer on this site can confirm this.
I just wanted to let everyone that with the new baseband from the update I am getting Instant locks with my GPS almost everytime even with cold start. Before it would take between 5, 15, 30 or never lock.
I flashed CM7 and I am still getting Instant locks.
Very impressed with this new baseband
Just wanted to let those of you that are having inconsistencies with the gps know that this baseband seems to turn the gps into a reliable one.
Steps I took:
-Updated through lg updater (This will give you the newest baseband)
-flash CM7 (even after flashing you'll keep your baseband)
Enjoy instant locks gps
Sent From My G2x Running CM7
Did you flash stock rom and recovery then unroot before you ran the update?
Or did you just flash stock rom recovery and run the update?
bkrill said:
Did you flash stock rom and recovery then unroot before you ran the update?
Or did you just flash stock rom recovery and run the update?
Click to expand...
Click to collapse
I restore a stock+root Nandroid I had, and I also had CWM nvflash.
The update still when through just fine.
Sent From My G2x Running CM7
The LG flasher app just reads your current build number against the one its trying to update.
All you need is the stock rom in some form or another. Root status is void.
The update just has to be newer then what you have currently for it to pass the checks.
LG G2x - CM7.1 RC1 2.3.4
www.CincyAdmins.com
www.MiiWiiChat.com
player911 said:
The LG flasher app just reads your current build number against the one its trying to update.
All you need is the stock rom in some form or another. Root status is void.
The update just has to be newer then what you have currently for it to pass the checks.
LG G2x - CM7.1 RC1 2.3.4
www.CincyAdmins.com
www.MiiWiiChat.com
Click to expand...
Click to collapse
Does recovery matter?
bkrill said:
Does recovery matter?
Click to expand...
Click to collapse
No, it doesn't matter.
Sent From My G2x Running CM7
I can confirm this fixed my gps locks on cm7 too. Almost instant and very accurate even when inside. About five feet off. I can live with that.
I restored stock rom , ran lg update, reflashed cmw , then restored cm7.
Sent from my LG-P999 using XDA Premium App
To catch you up on what I'm running
I just flashed a backup of infused 2.1.0 but i had been running infused 2.2.3. Ive been experimenting to see why I'm having certain problems with my roms that i don't believe existed when I originally started use the infused roms.*
However my first question is will gtg465x ultimate Unbricker completely take my phone back to stock out of box state and unroot it?* I ask because when I first flashed a custom rom I didn't properly make a back up of my stock configuration. So basically I'm trying to find out if that matters or will they Unbricker solve that problem?
Next I have some questions about flashing new roms (not updating them). When I first flashed the infused rom it converted my partitions to something else (I think that's the voodoo lagfix) but does this mean anything or will other roms need to be dealt with differently like by wiping the data and cache?
Oh and also would the kernel I'm running possibly be creating the problems in experiencing with my roms?
If you need anymore info in order to try and answer something just let me know.
Thanks guys
Gtg's Ultimate Unbrick will return your phone to stock and unroot your phone.
Sent from my SAMSUNG-SGH-I997
MattSoRaven said:
Gtg's Ultimate Unbrick will return your phone to stock and unroot your phone.
Sent from my SAMSUNG-SGH-I997
Click to expand...
Click to collapse
Nice. So that means if we ever get official gingerbread update I can flash back to stock and download it
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.
now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip
Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!
I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app
KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium
Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.
Hello.im having problems on flasshing this room cyanogenmod 9 RC0 for speedy beta release 2.1 .i get stuck on the htc screen . this is my first room that i have flash on the shift im on 2.2 hhhheeeeeeeeeeeeeeelp.
mex911 said:
Hello.im having problems on flasshing this room cyanogenmod 9 RC0 for speedy beta release 2.1 .i get stuck on the htc screen . this is my first room that i have flash on the shift im on 2.2 hhhheeeeeeeeeeeeeeelp.
Click to expand...
Click to collapse
I'm assuming you've rooted your phone, are successfully s-off, and have flashed a recovery:
Reboot into bootloader by pulling you battery out, putting it back in, and holding the volume down and power buttons at the same time until the screen turns on. This should get you to a white screen with a couple of options this being your bootloader. Use the volume buttons to highlight the word recovery and select by pressing the power button.
Now you should be in your recovery. Wipe everything as described in THIS thread http://forum.xda-developers.com/showthread.php?t=1266885
Afterwards reflash your ROM from recovery by selecting install zip from sd, then, choose zip from sd. Find your zip and flash. Reboot and let us know how it went.
Btw CM has a stable 7.2 release I would recommend in leiu of the one mentioned. Good luck!
Edit: Oops, I see you were flashing CM9, well at any rate flash what you want as long as it's for the Shift wipe before you flash it.
Sent from my PG06100 using XDA
Thanks for the info man
Sent from my PG06100 using xda premium
I would read about flashing and etc.on here....they have some good guides about it. Also, if this is your first flash, I would stay away from cm9 as it isn't fully functioning...it is a great start, but not for someone asking about the basics of flashing. I would try cm7.2, newsense, mikg, or supreme sense as they are the most up to date and very stable. Cm isn't sense based, so make sure you read about what it does and doesn't do...especially in terms of updating and small little quirks. Newsense, mikg, ans supreme sense are sensed based and run really well. Just read the threads and ask questions if in doubt.
Sent from my cm_tenderloin using Tapatalk 2