[Q] radio issues cannot make recive calls,txt,data phone on roaming mode - Verizon Samsung Galaxy S III

hi every one i dont know what to do now at this point i flashed my phone to the cyanogenmod 10.1 nightly which worked but the problem i started to have was could not send txt or calls but could browse the web on 4g so i though i would just restore from my back up of recovery image i did back to original stock which i noticed the proble still ocurred then i tried flashing to another rom called smooth liquid which now at this point it was only stuck on roaming my phone does seem to have the imei still in place, ive been reading aroud and did odin flash to stock touchwiz rom but still did not correct apparantly something messed up with the radio i went to the other forum were i woul dhave to flash the radio i tried the first one which was the lates one vrlk3 modem but when i tried to flash it in clockwork mod it gave me some error saying bad install so i attemted the one below that modem which is VRLK1 which flashed successfully but still did not seem to fix my service issue i read something about RPM on that same forum but there was many options to download i didnt know which one or if i even had to please help me someone. :crying:

Which build did you odin back to? Also did you do the reprovision code in the dialer? If not odin the F2 ICS build and put this in the dialer... *2767*3855#

x714x said:
Which build did you odin back to? Also did you do the reprovision code in the dialer? If not odin the F2 ICS build and put this in the dialer... *2767*3855#
Click to expand...
Click to collapse
the build or what it says here is COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar which is the jelly bean official ota

Flash this with odin http://goo.im/devs/invisiblek/i535/HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 and then in the dialer put *2767*3855# that should fix you up. Then just odin back to the K3 JB release.

ok thanks lets hope this works im trying this right now lets see what happens would it matter if im currently rooted??

droidman89 said:
ok thanks lets hope this works im trying this right now lets see what happens would it matter if im currently rooted??
Click to expand...
Click to collapse
do i have to do any radio flashing in addition to this stock rom flash?

x714x said:
Flash this with odin http://goo.im/devs/invisiblek/i535/HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 and then in the dialer put *2767*3855# that should fix you up. Then just odin back to the K3 JB release.
Click to expand...
Click to collapse
Thanks a million man you saved my life it worked thanks again

Youre welcome!

It Worked
I just want to say this post saved me tonight. I had searched the forums and tried everything to get my phone operational after flashing Slim's 4.2.1 ROM; which I learned I should not have done ... too late. I was stuck on roaming and no matter what I tried nothing worked until I found this post.
Thank you so much for your help.

Related

Removing ClockWorkMod recovery

Hi guys, I need your help!
Yesterday I updated my phone from Froyo 2.2 to Gingerbread 2.3.5 with Kies, then I rooted it trough Odin and flashed the recovery with ClockWorkMod recovery (i followed the guide, and made everything it asked to do). I completed the task succesfully. But here comes the problems:
I turned the phone on and I wanted to use Wi-Fi connection but I couldn't! It was just saying "error" and in settings the MAC address was unavaiable. I found something on the web, like trying to dial *#*#526#*#* but it didn't work too ("Driving loading unsuccessful").
So I wanted to bring the phone back to the previous state, So i unrooted it (succesfully) but now I'm stuck with this ClockWorkMod recovery and I can't find a way to restore the original Samsung i9003 recovery because i can't find it anywhere and I don't even know if I can use another Samsung's one.
I tought that maybe reinstalling Gingerbread from zero could fix this problem, but I'm not even sure of that, neither on how to reinstall it. Damn, I'm truly an Android n00b
Thanks to everyone that will spend some time helping me!
If it can help, here some infos about my phone
I9003XXPN
Kernel Version: 2.6.35.7-CL482273 [email protected]#1
Version build: GINGERBREAD.XIKP2
Click to expand...
Click to collapse
marvin_kk said:
Hi guys, I need your help!
Yesterday I updated my phone from Froyo 2.2 to Gingerbread 2.3.5 with Kies, then I rooted it trough Odin and flashed the recovery with ClockWorkMod recovery (i followed the guide, and made everything it asked to do). I completed the task succesfully. But here comes the problems:
I turned the phone on and I wanted to use Wi-Fi connection but I couldn't! It was just saying "error" and in settings the MAC address was unavaiable. I found something on the web, like trying to dial *#*#526#*#* but it didn't work too ("Driving loading unsuccessful").
So I wanted to bring the phone back to the previous state, So i unrooted it (succesfully) but now I'm stuck with this ClockWorkMod recovery and I can't find a way to restore the original Samsung i9003 recovery because i can't find it anywhere and I don't even know if I can use another Samsung's one.
I tought that maybe reinstalling Gingerbread from zero could fix this problem, but I'm not even sure of that, neither on how to reinstall it. Damn, I'm truly an Android n00b
Thanks to everyone that will spend some time helping me!
If it can help, here some infos about my phone
Click to expand...
Click to collapse
Now, Do you want a guide on how to re-flash back to Gingerbread using ODIN? If so,It is here. And, I would like to tell you that on re-flashing the FW, you are going to void your warranty and you will be able to get rid of the CWM
Hope it helped you!
hi OP
I'm facing the same problem as you, right now waiting for dxkp9 download and reflash with Odin.
But if you somehow manage to solve this issue please share.
Hi!
I tried and I tried and I solved it! I flashed back the stock rom of I9003 with Gingerbread trough Odin. This removed ClockWorkMod and restored the phone as it was in the beginning. Problem solved, original recovery mode and wi-fi finally works!
marvin_kk said:
Hi!
I tried and I tried and I solved it! I flashed back the stock rom of I9003 with Gingerbread trough Odin. This removed ClockWorkMod and restored the phone as it was in the beginning. Problem solved, original recovery mode and wi-fi finally works!
Click to expand...
Click to collapse
+1 [Reflash, and CF-root without 'extras' and restore]

Firmware question after bad flash

So I had a completely stock Galaxy s 4g, on gingerbread. I had the bright idea of rooting to try out different builds. I was in the middle of flashing when I noticed that what I was flashing was for the Vibrant. Well, it was either let it flash with that or stop the flash, so I stopped it. After searching for hours, I couldn't find a working link for a download to flash a custom build. I was able to find a "stock" flash, but for some reason I don't think it's right. I have problems with low call volume now and have to power the phone off and on to fix it temporarily. Everything else works fine, so far. Another thing I noticed is everyone shows firmware of 2.3.6, mine says 2.3.4????? Here's my info: sigh-t959v, baseband T959VUVKG4, kernel 2.6.35.7-t959vuvkg4-cl385158, build gingerbread.vuvkg4.
Any thoughts on what I should do?
Thanks in advance
This thread has heimdall one clicks that will get you back to stock kj6. Remember to flash once then after booting until you hear the t-mo jingle pull battery and put it back in download mode and check the flash bootloaders and flash it again.
http://forum.xda-developers.com/showthread.php?t=1358498
If you want root in the second post is a one click created by me. You can flash it instead of the plain stock one by bhundeven. But you need to flash the bootloaders to make sure you get rid of all the vibrant stuff.
Ok, thanks a lot. I will flash your build tomorrow when I get home from work. I'll let you know how it goes. Thanks again.
So I flashed your build and everythingis working great, even seems to be running faster. However, the wifi says "error" when I try and activate it. Is that a rom problem? Should I start over and try again?
It is because the kernel uses a different module then what is in the rom itself. That is why it is suppose to be used as a stepping stone to flash to a different rom.
Gotcha.

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

[Q] Flashing to stock - phone force closes process com.android.phone, help

Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.
Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.

[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

Categories

Resources