picked up a used m8. Which had cm11 pre installed (fine with me it's what I'm used to running on my old galaxy nexus) just picked up a new sim card today and put the new sim in and it should be active but it wont pick up any vzw service (no bars just the empty triangle like shape) Any thoughts on how to get it to pick up signal?
When I hold vol down and power on I can see the following
CID - VZW__001
HBOOT - 3.16.0.0000
RADIO - .89.20.0321
OS 1.55.605.2
Appears to have the new radios and software.....
Normally, I would just restore the backup but there was no back up on the phone.
My first thought is to try flashing the most recent radios to see if that's it, but can this be done through .zip file in cwm or twrp? Or must they be flashed via fastboot?
Second thought is to reflash the stock 4.4.2 ruu then do factory reset.
Third thought....Is there anything else that I can do?
I wanted to get input from those who are more knowledgeable than myself on what would be the best method for proceeding..
Thanks
Drootz! said:
picked up a used m8. Which had cm11 pre installed (fine with me it's what I'm used to running on my old galaxy nexus) just picked up a new sim card today and put the new sim in and it should be active but it wont pick up any vzw service (no bars just the empty triangle like shape) Any thoughts on how to get it to pick up signal?
When I hold vol down and power on I can see the following
CID - VZW__001
HBOOT - 3.16.0.0000
RADIO - .89.20.0321
OS 1.55.605.2
Appears to have the new radios and software.....
Normally, I would just restore the backup but there was no back up on the phone.
My first thought is to try flashing the most recent radios to see if that's it, but can this be done through .zip file in cwm or twrp? Or must they be flashed via fastboot?
Second thought is to reflash the stock 4.4.2 ruu then do factory reset.
Third thought....Is there anything else that I can do?
I wanted to get input from those who are more knowledgeable than myself on what would be the best method for proceeding..
Thanks
Click to expand...
Click to collapse
The info you posted isn't the new radios or the new firmware. Try flashing the 4.4.3 firmware from my firmware thread..update that an see what happens. You can find my firmware thread in Vzw m8 development.
OK I'll give that a try and report back
Ok I followed the directions and now I get signal in the triangle and an LTE connection. (Thank you Tigerstown much appreciated)
Now, When I hold vol down and power on I can see the following
CID - VZW__001
HBOOT - 3.18.0.0000
RADIO - 1.09.20.0702
OS - 2.21.605.2
but when I go to place a call it says "Mobile network not available"
After CM boots When I go into Settings > then about phone> then status everything looks normal shows verizon wireless under network but a few lines below under Service State is says "voice: Out of service, data: in service"???
Any ideas on what else I should do to get it to be able to make phone calls? Should I try flashing the radios via fastboot? Since I just used the sdcard method mentioned in your post instead of the fastboot method to update?
and strangely enough also under status a few lines below that it shows Mobile network state of connected.
feel like I'm close, just missing something.....Anyone more knowledgeable than myself have any ideas to get it to be able to make calls?
Thanks
Drootz! said:
Ok I followed the directions and now I get signal in the triangle and an LTE connection. (Thank you Tigerstown much appreciated)
Now, When I hold vol down and power on I can see the following
CID - VZW__001
HBOOT - 3.18.0.0000
RADIO - 1.09.20.0702
OS - 2.21.605.2
but when I go to place a call it says "Mobile network not available"
After CM boots When I go into Settings > then about phone> then status everything looks normal shows verizon wireless under network but a few lines below under Service State is says "voice: Out of service, data: in service"???
Any ideas on what else I should do to get it to be able to make phone calls? Should I try flashing the radios via fastboot? Since I just used the sdcard method mentioned in your post instead of the fastboot method to update?
and strangely enough also under status a few lines below that it shows Mobile network state of connected.
feel like I'm close, just missing something.....Anyone more knowledgeable than myself have any ideas to get it to be able to make calls?
Thanks
Click to expand...
Click to collapse
Flash a sense Rom...Fastboot the stock recovery I have posted. An backup all you file on your phone to a pc an remove sd card then do a factory reset an see what happens. Very good possibility this will work.. let me know what happens
Tigerstown said:
Flash a sense Rom...Fastboot the stock recovery I have posted. An backup all you file on your phone to a pc an remove sd card then do a factory reset an see what happens. Very good possibility this will work.. let me know what happens
Click to expand...
Click to collapse
So I downloaded VZW stock pre-rooted rom and as soon as I booted up everything started working as it should. Didn't even get to removing sd or re-flash stock recovery or factory reset. I might do that eventually as I do want to go back to CM or maybe viper rom. But I def. wanted to report back and say thank you for your help! I really appreciated it!
Drootz! said:
So I downloaded VZW stock pre-rooted rom and as soon as I booted up everything started working as it should. Didn't even get to removing sd or re-flash stock recovery or factory reset. I might do that eventually as I do want to go back to CM or maybe viper rom. But I def. wanted to report back and say thank you for your help! I really appreciated it!
Click to expand...
Click to collapse
Make a backup an try to flash viper. Worse case it don't work rt an you just restore your backup. Glad to hear all up an running.
Related
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Update
I was trying to flash via Clockworkmod. I used ADB FASTBOOT and the radio is now on J1.
So, if Clockworkmod isn't working, use ADB FASTBOOT.
metalgeek said:
I've tried just about everything to flash a new version of the radio firmware on my 9020a. I've used the Radio Flashing Guide and tried every version available for the 9020a. Each time, the flash reports that it was successful, but no matter which one I choose, baseband still shows I'm running i9020aucke1 when I boot it back up.
I've also flashed the stock ICS OTA update 4.04 for the 9020a, thinking "well, THAT has to do it." but still I'm stuck on cke1.
Are there permissions that may be wrong? Is there anything else I can do? I want to flash a new radio because e1 is terrible for me. It won't switch between "3g" to "H" and just spins it's wheels and I get no data. Sometimes I get ZERO signal. If I reboot or switch Airplane Mode on & off, data comes back and works for a while, but then reverts back to working like crap.
Thanks a lot.
Click to expand...
Click to collapse
What recovery and what version are you using?
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
jaker.the.skater said:
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
Click to expand...
Click to collapse
Hello,
What was the version of software on you phone before rooting, was it a T-Mobile phone? The newest version for T-Mobile has created is issues for roms that aren't the same version.
Rsotbiemrptson
Sent from my Nexus 7 using xda premium
Yep, just found out that was the issue. kinda sucks because I'd rather have jelly bean! Oh well guess I'll deal with no wifi till a fix comes out.
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
YousufWalton said:
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
Click to expand...
Click to collapse
So did you use the 1.84 ruu? And you did this after applying the tmobile ota?
Hi Guys,
Can I get some help with the following please:
Issues: When power on my Xoom(MZ601), I get the following error "Tablet is not provisioned. Please insert valid SIM card and reboot"
Steps taken to troubleshoot
1. Restore to factory settings and when reboot, I will get the above error. I wont be able to get into the tablet with that error.
2. Install custom rom - Will be able to get into the device but does not have any signal be it 2G/3G. Only can use wifi. When try to set the APN, nothing will happen.
I am suspecting I messed with the baseband version and causes this issue. I am currently on baseband 07P. I am trying to a way to fully restore back the device to factory settings include the baseband itself to see if this will fix the issue.
Is there anyway I can get a copy of the baseband N_01.100.05P file so I can try?
Thank you very much for any form of help.
Hi,
I never saw such a problem, but if the problem is really the baseband I think you can try restoring to 100% stock (find how to do it on our FAQ), then you update until the latest version in your country, then you root again (you can find it on the FAQ again), and then give me a shout to know what happens
Good luck!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Thanks for your reply!.
I have tried what you've suggested where I restore it to full stock but end up just getting the same error message. I'm using this package (MZ601_H.6.1-38-9_Other_International_Retail)
I even tried to restore it to (MZ601_H.6.1-38-1_Retail_Europe) whereby it actually allows me to setup my tablet and I'm able to get into the device finally which was a good sign BUT, I guess Europe spec's doesn't support my telco's , therefore again, I did not manage to fix the issue.
The same sim, if it were to insert to any of my other devices, it will just work fine.
And when I was doing the europe package, the baseband change to some older ones at first, then as I upgrade it with the stock patches, in the end it went back to 07P again!!!!
Is there any way I can find the baseband 05P files so I can try to flash it back and see if it works? I strongly believe I've messed up with the baseband file whereby now my device cannot find signal.
If there's anymore posibble area that you think I've posibbly messed up, please let me know. I have played with the device long enough but this time I'm really stucked. .
Appreciate your big 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.
After a tragedy with my S3, I'm having to limp along with my old One SV. Unfortunately I am having trouble getting this thing to keep a newer ROM. And before anyone says "turn s-off" I have S-Off already.
Booting to the boot menu it says:
moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-1.01.4444
RADIO-1.1250.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
Jan 16 2013, 01:26:39:-1
I've tried jellybean flashing
I tried the viper ROM (which gets stuck flashing unless I don't install all the google apps)
Post every flash, I turn the phone off and then power it back up. For a little while it'll say something "correctly" like that it's android 4.4.... buuuuut it is still the default wallpaper and goes back to saying android 4.0 and of course the bugging to update to a new stock android is still present as is the "out of storage space" error message....
I've tried updating the recovery (currently a somewhat buggy cwm where the screen is 1/8th offset half the time... v6.0.2.8) and that hasn't worked... Typing this out I decided to try flashing the recovery once more since when I first was doing it I apparently had S-ON... So I flashed the latest TWRP (3.0.1-0-k2_cl) and..... now it's bricked.... it won't boot normally nor will it boot into recovery mode, but I can get to the hboot menu.... HALP! lol
The final kicker to my scenario is that I'm on linux and don't have access to any Windows machines, but I do have heimdall and adb installed.
Okay... So because I was still able to get into the HBoot menu and then put it into the Fastboot menu with the USB cable connected I was able to flash a new recovery.
I got the TWRP 2.8.5.0 recovery from http://techerrata.com/browse/twrp2/k2_cl
I was able to install fastboot and adb thanks to http://forum.xda-developers.com/showthread.php?t=2638673
I re-tried flashing the Jelly Bean rom I had with the same result as before the bad recovery problem occurred... It boots up, but it's still Android 4.1, even though it is S-OFF-ed.... And that shouldn't be happening... I'm pulling the battery and rebooting after flashing so nothing should be overwritten... What gives?
Your best way to go:
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
As far as i remeber, there was no custom rom that was made for k2cl.
correct.. there is no custom rom for the boost variant.. there is a partition swapper changing the 4gb media with the 1gb internal storages.. romcleaner works to get rid of all the boost garbage.. twrp will fit your screen.. havent used cwm since my hero
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
I tried to get the RUU to work, but couldn't. I borrowed a friend's Windows laptop, installed adb and fastboot and it just would not connect or see my phone in the RUU. I even tried forcing the driver to be installed correctly, which never worked for some reason.
I ended up installing Link2SD and setting up a 16gb partition for apps. So at least it's not complaining about being out of space anymore. It is still wanting me to download the OTA update. Not the end of the world.
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Hathalud said:
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
Click to expand...
Click to collapse
Hm,
From the Viper Rom thread:
Modding.MyMind said:
THE VIPERSV ROM IS NOT FOR BOOST MOBILE (K2_CL) USERS!!!!!!!!
This is what could happen to you if you fail to follow instructions!
Click to expand...
Click to collapse
xpirt said:
This Rom is not compatible with Boost/Cricket variants, which model have you flashed it on?
xpirt
Click to expand...
Click to collapse
Hathalud said:
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Click to expand...
Click to collapse
This was a permission bug from updater script, when i remember.
Wiper is some wifi or network location service. If you don't need it, rename it or delete it.