[Q] How to Backup Baseband and Recovery (is there a need to)? - Optimus One, P500, V Q&A, Help & Troubleshooting

I have an LG P500 from a friend who upgraded, and it has the V10 baseband.
In order to install the ROM I want, I'll have to upgrade the baseband and install a custom recovery.
If I need to return to my previous setup, how to I return to the original baseband and recovery?
The phone itself is not under warranty, so the recovery image probably does not matter much, but does the baseband matter?
I mean, if I install a V10 baseband from a different country and use the original ROM, should I expect problems?

mzlapq said:
I have an LG P500 from a friend who upgraded, and it has the V10 baseband.
In order to install the ROM I want, I'll have to upgrade the baseband and install a custom recovery.
If I need to return to my previous setup, how to I return to the original baseband and recovery?
The phone itself is not under warranty, so the recovery image probably does not matter much, but does the baseband matter?
I mean, if I install a V10 baseband from a different country and use the original ROM, should I expect problems?
Click to expand...
Click to collapse
Custom recovery like CWM is a must but No need to switch basebands, there are baseband fixes available which you need to flash after flashing ROM.

myawan said:
Custom recovery like CWM is a must but No need to switch basebands, there are baseband fixes available which you need to flash after flashing ROM.
Click to expand...
Click to collapse
Thanks for the reply, but according to this http://forum.xda-developers.com/showthread.php?t=1149530&page=43
the fix does not work for JB and doesn't work with some of the recovery images, which may be recommended for the ROMs I want to install.

mzlapq said:
Thanks for the reply, but according to this http://forum.xda-developers.com/showthread.php?t=1149530&page=43
the fix does not work for JB and doesn't work with some of the recovery images, which may be recommended for the ROMs I want to install.
Click to expand...
Click to collapse
CWM 5.0.2.0 is most stable and recommended for P500, all ROMs and BBfix patches are compatible with this version. I've using it for more than a year now and never faced any issue.

myawan said:
CWM 5.0.2.0 is most stable and recommended for P500, all ROMs and BBfix patches are compatible with this version. I've using it for more than a year now and never faced any issue.
Click to expand...
Click to collapse
Have you used this ROM? http://forum.xda-developers.com/showthread.php?t=1833218
This one specifically suggests using CWM 5.0.2.7 (although it may be that the newer CWM is more stable on the new baseband)
I have searched the forums some more and found this site: http://lg-phone-firmware.com/
You need to remove the :9002 from the URL you get at the end, and it should download the original ROM for your location/provider.
I am still interested in an answer to my original questions.

mzlapq said:
Have you used this ROM? http://forum.xda-developers.com/showthread.php?t=1833218
This one specifically suggests using CWM 5.0.2.7 (although it may be that the newer CWM is more stable on the new baseband)
I have searched the forums some more and found this site: http://lg-phone-firmware.com/
You need to remove the :9002 from the URL you get at the end, and it should download the original ROM for your location/provider.
I am still interested in an answer to my original questions.
Click to expand...
Click to collapse
Yes I have used this rom too with CWM 5.0.2.0! Your questions have been answered if you read.
Sent from my LG-P500 using xda premium

Related

Flashing question

I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?
You will not need to replace anything, the Odin package is all in one. It will put you back to bare stock which means ROM, kernel, recovery, modem, you name it.
If you wouldn't mind helping could you link me to a rooting guide on a DX? Some general tips on rooting it would be very appreciated. My dad has one and I'd like to root/ROM it for him but i don't feel like studying up >_< Thanks!
Wrightperspective said:
I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?
Click to expand...
Click to collapse
Odin will replace everything, including your kernel.
Thanks for the response. I got confused because I saw posts saying that some kernels were interchangeable but I didn't know if they meant that you would have to flash the kernel after you flash the rom or if you just flash a new rom and the kernel remains. Appreciate the response.
You have to flash kernal only on cmw versions and not all of them read the pre requisites it will tell you if the cwm version either do not or do.have a kernal included for example humble 5 cwm version I.believe u.have to flash a kernal prior to rebooting or stock recovery will over write cwm happened to me and learned my.lesson the hard way !!!
Sent from my Gummy Charged GBE 2.0 using xda premium
Okay...so flashing the stock file will also get rid of CWM, right?

Lost everything after ROM

So i installed a new rom because my 2d/3D camera wasnt working so when i installed it 2D camera worked but not the 3D. so now after Rom i noticed that my IMEI saying unknown and serial and WIFI. so what up.
so if you can teach me how to fix it or get it back to stock froyo. i didnt backup
haider0009 said:
So i installed a new rom because my 2d/3D camera wasnt working so when i installed it 2D camera worked but not the 3D. so now after Rom i noticed that my IMEI saying unknown and serial and WIFI. so what up.
so if you can teach me how to fix it or get it back to stock froyo. i didnt backup
Click to expand...
Click to collapse
What rom did you flash? I mean I understand it is gingerbread but was it the stock one .kdz files or was it a custom rom? plus if it was custom rom did you first install the baseband as it was instructed in the rom's OP ( think all roms op have the advice about flashing baseband before installing rom if you are coming directly from Froyo). Which kind of model do you have? Is it a p920 or a p925? More info is required in order to get some help... Anyway look on the guide about flashing .kdz files and use that to return to Froyo or flash gingerbread as a KDZ which installs baseband automatically. PS if your failed install is cyanogenmod don't return to froyo this way. There is a guide on how to revert to froyo from cyanogenmod somewhere...
jimakos29 said:
What rom did you flash? I mean I understand it is gingerbread but was it the stock one .kdz files or was it a custom rom? plus if it was custom rom did you first install the baseband as it was instructed in the rom's OP ( think all roms op have the advice about flashing baseband before installing rom if you are coming directly from Froyo). Which kind of model do you have? Is it a p920 or a p925? More info is required in order to get some help... Anyway look on the guide about flashing .kdz files and use that to return to Froyo or flash gingerbread as a KDZ which installs baseband automatically. PS if your failed install is cyanogenmod don't return to froyo this way. There is a guide on how to revert to froyo from cyanogenmod somewhere...
Click to expand...
Click to collapse
i installed KING_3D_ROM_v2.3 using the cwm and to install zip from Sd card.
mine was 2.2 froyo. my phone is p925
haider0009 said:
i installed KING_3D_ROM_v2.3 using the cwm and to install zip from Sd card.
mine was 2.2 froyo. my phone is p925
Click to expand...
Click to collapse
ohhh. ok first of all you needed to flash the baseband first. there should be directions as to how to do that in kng3d thread along with link to the baseband. second I am not sure if the rom will work as it is supposed to seeing it is made for p920 and not thrill. Still it may. I havent done any research over the matter though. May have connection isues. But flashing baseband is essential for gb to work. Maybe at the thrill forums they have more info. Try looking there first.

[Q] JB update and custom kernel

Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible
Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2
Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse
andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!
Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.
To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:
andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?
Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!

[Q] CWM recovery issue with Rom Manager

So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc

SGS4G Android 2.2 rec 3e. Do I have to flash kernel and modem before flashing custom?

Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
AjvarXX said:
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
Click to expand...
Click to collapse
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
haridevil99 said:
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
Click to expand...
Click to collapse
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
AjvarXX said:
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
Click to expand...
Click to collapse
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
haridevil99 said:
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
Click to expand...
Click to collapse
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
AjvarXX said:
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
Click to expand...
Click to collapse
The guide seems good enough but a bit more complicated that it should be. Anyway here are two tips or info for you. First, whatever you do, have Odin and Stock Firmware ready to flash coz when everything else fails, Odin to the rescue and also flash stock firmware (Rom+kernel) whenever you change kernel as changing kernels without doing so removes root access and you cant apply root update on a custom kernel unless it has pre root access. Second, you dont need any kind of manager to flash firmwares and updates. CWM is a replacement to all. But its all your choice.

Categories

Resources