Database Info

Really messed up G2X

Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3

beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.

It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.

I am going to give this a try and see what happens, I will post results.

Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.

Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7

I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.

beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7

I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?

[Q] CM7 Root Fail

I am having some phone problems as a result of a root attempt.
Phone : LG p999
Carrier : Wind (Canada)
Here's what I did:
1. Tried superoneclick root program. It never got to completion and I couldn't figure out why. It always failed at right before finishing, even after reboots.
2. After superoneclick , I decided I would edit the adb shell manually. I did not initialize psneuter because that step was successful with Superoneclick. I loaded the superuser package. After this, I couldn't get the phone to boot, even in recovery mode.
3. Next I used One-Click ClockworkMod Recovery NvFlasher to load clockworkmod (cwm) . At first I loaded it onto internal SD. This worked fine but I couldn't get it to recognize any backups or cm7 nightlies.
4. Then I tried loading on the external SD. This worked, I couldn't see any backups but could load cm7 nightly and gapps.
5. Rebooted phone, everything fine. But within a few hours, my 3g was not working. I typed #*#*4636*#*# and saw the 3g settings were empty. Apn settings are normal though.
So here is where I'm at now. Wifi, SMS, calling all work. Cannot access 3G, sdcard (can’t take pictures).
Also, I didn't make a backup. Yea, that was stupid.

first thing were you on 2.2.2 or 2.3.3 when you first tried superoneclick? It sounds like you did the update and were on 2.3.3. The superoneclick methode does not work for rooting anymore. You have to nvflash CWM first. Then flash xboarders stock ota rooted or any Rom that is pre rooted I think will work.
So what I would do at this point is try using nvflash and flash back to stock and start over. You will probally have to reinstall CWM then I would just use the xboarders stock rooted ROM just to gain root then install CM7. You probally dont have to flash xboarders first but that is the way I know will definitly work so that is what I recomend. Also I dont know if the NVflash returns the phone to stock 2.2.2 or 2.3.3 I have never done it. maybe someone else who knows more could chime in.
Charlie

Are you already on Cyanogen Mod 7 as your title indicates? CM7 is rooted OOTB. There is no reason to try and root it again.

Yes it is running CM7 now, but with some serious problems:
1. Can't use one click to flash stock ROM -- each time I try the phone gets stuck in a rebooting loop and just eventually freezes.
2. 3G/sdcard problems with CM7
- not sure if this is just an issue with the CM7 build or whether my phone is causing this.
I have flashed CM7, but the weird thing is that the 3G works fine for about a day and then it cuts out. Its not an APN thing --> I checked the settings. Any ideas what is going on there?
Gonna try loading xboarders when I have a free evening.
Thanks

So Rusty - Need Help.

It has been FOREVER since I have messed with my G2x. But lately it has been super laggy, the keyboard never picks up what key I pressed properly, and the accelerometer is a MESS.
Im currently on March 2011 baseband, Android Version 2.3.7, and a very, very old nightly.
Im looking to update to the newest baseband as I hear it is a huge improvement, and also try out an ICS rom. I have been browsing and reading up, but am so rusty on reverting and flashing.
Would the proper, easy way to do this be as follows:? This is what I've gathered from reading, just don't want to brick my phone for a stupid reason.
1)Flash a stock ROM - Full Factory Wipe
2)Update baseband with LG Update Tool
3)Root Phone again
4)Flash Custom ROM?
Also, can you revert to stock ROM without an external SD card? I was reading a few topics stating you can't. I also have a backup of the original stock ROM(or at least I think) from a very, very long time ago. Can I just restore that?
I apologize in advance for all the questions, just trying to refresh my memory on this entire process.

from what ive seen, after getting cwm on your phone via nv flash you install one of the ics roms then before rebooting the phone you have to install a fix via cwm that owain has on one of rom pages (domination i think) then you are good to go. and yes, you have to use an external sd card for all of this.

After updating baseband you will lose root as well as CWM. You need to put it back on before you can flash a custom rom on it.

cricketAC said:
After updating baseband you will lose root as well as CWM. You need to put it back on before you can flash a custom rom on it.
Click to expand...
Click to collapse
Ahh thank you! And I can not run the tool from a custom rom, correct? I have to flash back to stock, and then the updater will update baseband as well as unroot everything.
I also dont have an external SD card, so I guess I will be buying one to flash back to stock

[Q] Help i'm a noob and need help please!

Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help I can't seem to find a working link for CWM-UXKG3-rooted-de-odexed-update-v2.zip maybe if I install the cwm the light neon blue screen will go away?

crayzze said:
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1613523

Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.

crayzze said:
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
Click to expand...
Click to collapse
rainbow screen on recovery = no gb bootloaders
blue screen on phone ...maybe bad cable connection or corrosion at contact
you might have to open it and check the connections

Working and tested CWM 1.2 ghz
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!

Fullmetal Jun said:
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Click to expand...
Click to collapse
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.

crayzze said:
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
Click to expand...
Click to collapse
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl

Help!
qkster said:
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Click to expand...
Click to collapse
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol... My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear... my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.

crayzze said:
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol...
Click to expand...
Click to collapse
no big deal..same phone..same hardware..different version of firmware..it's the APN for providers that makes the difference
crayzze said:
My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear.
Click to expand...
Click to collapse
yes..you are right. Rogers came with 2.3.3 not 2.3.4 as I previously stated.
the earlier versions of gb came with Carrier IQ that track users. It was taken out later.
I doubt Installing 2.3.6 or ICS or JB will cause any prob with the phone. I suspect your phone may have some hardware issues.
After the first flash, the os (esp ICS or JB) may need time to build cache and dalvik..sometimes it may take a few minutes. Blue or distorted screen, however, is not typical from my experience.
crayzze said:
my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
Click to expand...
Click to collapse
IMO, it doesn't matter how you get to CM10.2. Rooting is just one method. The idea is to get insecure recovery...ie..cwm.
from stock rom, you can odin or heimdall a custom kernel without rooting. boot into recovery and flash what you want.
it doesn't matter if its rogers or att. same phone..same hardware. years ago, it only mattered when a user had to return or exchange the phone for warranty...after the warranty period ended..it's not a big deal.
flash away at any method you want. it doesn't make any difference in my mind. get some practice..the infuse has many restore methods via odin or heimdall
rooting gives one access to the root directory
insecure kernel or custom recovery allows one to flash firmware without manufacturer signature

[Q] No service, tried everything

I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.

Try the old Baseband fix, that did it for me some years ago, not sure if you need the v10 baseband coming from 2.2 but the fix should work. You can find it here on the Forum.
If nothing works, use kdz to flash the Stock Rom and start over.

Bartlebyxxx said:
Try the old Baseband fix, that did it for me some years ago, not sure if you need the v10 baseband coming from 2.2 but the fix should work. You can find it here on the Forum.
If nothing works, use kdz to flash the Stock Rom and start over.
Click to expand...
Click to collapse
Thanks, I wanted to try that but when I go to download the milk_os fix at the bottom of this page
http://forum.xda-developers.com/showpost.php?p=14743798&postcount=2
I get redirected to some bull****(lp.downloadsetup.net)
And I just don't trust this thing, is this really what I'm suppose to download?

Is definitely the fault of baseband. Some rom is incompatible with any type of baseband. Try to download from play store an application with baseband-ril match...

Toxic_Ninja said:
I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.
Click to expand...
Click to collapse
Sounds like you have an old baseband phone, but you flashed a new baseband ROM on it. In that case, simply flash the zip indicated below (I suggest you mount /system in recovery before flashing, even though the script auto-mounts /system, just to be sure). I'm attaching two zips for the sake of completeness; the one you want is the Use_New_BB_ROMS.zip.
Use_New_BB_ROMS.zip -- Flash this zip if you're trying to use a new baseband ROM on a phone that uses the old baseband. If you have no network on 2.3 and above ROMS, your phone probably uses the old baseband, so this is the zip you need.
Use_Old_BB_ROMS.zip -- Flash this zip if you're trying to use an old baseband ROM on a phone that uses the new baseband. If you have no network on 2.2 and below ROMS, your phone probably uses the new baseband, so this is the zip you need.

Syd_M said:
Sounds like you have an old baseband phone, but you flashed a new baseband ROM on it. In that case, simply flash the zip indicated below (I suggest you mount /system in recovery before flashing, even though the script auto-mounts /system, just to be sure). I'm attaching two zips for the sake of completeness; the one you want is the Use_New_BB_ROMS.zip.
Use_New_BB_ROMS.zip -- Flash this zip if you're trying to use a new baseband ROM on a phone that uses the old baseband. If you have no network on 2.3 and above ROMS, your phone probably uses the old baseband, so this is the zip you need.
Use_Old_BB_ROMS.zip -- Flash this zip if you're trying to use an old baseband ROM on a phone that uses the new baseband. If you have no network on 2.2 and below ROMS, your phone probably uses the new baseband, so this is the zip you need.
Click to expand...
Click to collapse
I tried to flash it but I get an error: can't copy META-INF/com/google/android/updated-binary
Should I be wiping cache for this? Dalvik cache?
I used LGMDP-v1.5 to get bb v.20 on my phone in the first place, I tried to do the same with v.10 after v.20 didn't work but it just went back to baseband unknown. when I tried to download the milk_os fix it just linked me to some phishing page.

What recovery are you using? I've tried with AmonRa & CWM 5.0.2.0 and both work. Other CWM versions will probably work, too. Haven't tried with TWRP.
If this flashed successfully but you still don't have service, then you might have borked something when changing baseband in KDZ. If that's the case, then hopefully others will be able to help you as I've never touched KDZ myself.
____________________
Sent from the moon.

Toxic_Ninja said:
I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2616412 <-- go here..i prefer you to use twrp.. hit thanks if i helped.

Syd_M said:
What recovery are you using? I've tried with AmonRa & CWM 5.0.2.0 and both work. Other CWM versions will probably work, too. Haven't tried with TWRP.
If this flashed successfully but you still don't have service, then you might have borked something when changing baseband in KDZ. If that's the case, then hopefully others will be able to help you as I've never touched KDZ myself.
Click to expand...
Click to collapse
I was using CWM 5.0.2.0, and I've never touched KDZ.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2616412 <-- go here..i prefer you to use twrp.. hit thanks if i helped.
Click to expand...
Click to collapse
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.

Toxic_Ninja said:
I was using CWM 5.0.2.0, and I've never touched KDZ.
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2559363 dude i think you did something which is not good.. i require you to restore ur stock rom with the link i gave.. or if ur affraid of kdz use odin.
if ur back with the stock rom never upgrade your baseband again..when u flash a custom rom with new baseband needed just simply flash the baseband fix i gave you..
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Toxic_Ninja said:
I was using CWM 5.0.2.0, and I've never touched KDZ.
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.
Click to expand...
Click to collapse
dude i think you did something which is not good.. i require you to restore ur stock rom with the link i gave.. or if ur affraid of kdz use odin.
if ur back with the stock rom never upgrade your baseband again..when u flash a custom rom with new baseband needed just simply flash the baseband fix i gave you..
forum.xda-developers.com/showthread.php?t=2559363