Hello,
I searched for my 9020A the forum for several updats on 4.0.3 because the calendar crashed always and did not well sync.
Any Update i found here or via RomManager did not work in terms of the Signal. There was no Network found. instead of Bars just a blank gray triangle.
I originally had the "cm_crespo-ota-eng.kalimochoaz.a18.p1" on it and this worked fine ecxept the calender.
With the new rollout of the new 4.0.x I thought i found the Original one and updates this one http://forum.xda-developers.com/showthread.php?t=1398186, I know now, it was wrong.
Now my info looks like
Name HERRING
HW Version Rev16
Bootloader Version I9020xxKL1
Baseband Vers. I9020xxKI1
Carrier Info ATT
Unlocked
System info:
4.0.3,
Kernel:
3.0.8-gb55e9ac
[email protected]#1
Build Nummer IML74K
Status about Signal:
Network unknown
Signalstrenght -111dBM 1ASU
Network GPRS:1
The Rom runs but also NO Signal (as described before with other ROM's)
Back in the Bootloader Mode:
Bootloader yes, Recovery always the Android with the open Belly and big acclamation mark. After pressing long enough (very uncontrolled the left +/. button) i get a menu.
From there i try to load another zip, but it stops after first searching SD card, then open the zip and then abort the process
Is there anything what i can do, I'm sure it is but I just need some help
Thanks a lot in advance
Check out this thread and flash a radio for your i9020a. This will hopefully get reception back for you
As for the bootloader: Stock ROMs replace the bootloader each boot. To change this you need root and rename /etc/install-recovery.sh to /etc/install-recovery.sh.bak
Once you flash a custom bootloader again, it won't be replaced.
Problem solved THANKS
thanks, everything worked after i found the right files Recovery and SU. About the Radio, I tried a few and it works. But I still play a little wich radio version is best.
Update on the calendar issue witch brought me into this at all. calendar crashed again. I exported all calendar items on google, deleted all entries renamed the calnder (was the main calendar you can't delete) and imported the appointments back in.
everything smooth and great now
Thanks again for the HELP
Glad to help and good work getting your calendar issue fixed, something i'll keep in mind if it ever happens to me
Related
I've got an ADP1, and I'm trying to upgrade to JF's v1.5 image. I started from JFv1.43 and radio 1.22.14.11, which seems to work fine.
From there, I flashed the new radio image, wiped, and flashed the JFv1.5 image. I copied image files onto the SD card root as "update.zip" using the USB cable into a booted Android environment and then flashed them using Alt+S on the (JFv1.43) recovery screen.
Here are the files I've got:
aeecdb49b74a0d4bb67f9d8af70c1889 ota-radio-2_22_19_26I.zip
8d78b985316ec77f81c71cab0eeb9f27 JFv1.50_ADP1.5.zip
On the first boot after flashing JFv1.5, I get three bars, can go through the sign in wizard, and can surf the web. In the phone info screen, it shows the correct baseband version. On second and subsequent boots, I get absolutely no signal (zero bars with an X) and in the phone info screen it shows the baseband version as "unknown".
Reflashing the radio image has no effect with either the 2.22 or the 1.22..11 radio. Reflashing the JFv1.5 image makes it work again for a while, but breaks again with the next reboot. This isn't specific to the JF image either - Hv1.5r3 gives me the same behavior.
Further tests:
- JFv1.43 with radio 2.22 works fine.
- The HTC ADP1.5 release breaks the same way. In this test, web connectivity broke before the first reboot; I had gotten the same result in one of my JFv1.5 tests too, so the reboot may not be the key thing.
Any ideas what I might be doing wrong?
MD5sum
I can confirm that the MD5 sum of the JFv1.5 image is correct. I just installed the two images, like you, and it works fine. (After entering my PIN, it cost 10 seconds before I have bars)
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell? I don't know if the recovery will detect a corrupt image, but I always check it just in case. I downloaded the image over 3G.
I have a T-mobile G1.
tomvleeuwen said:
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell?
Click to expand...
Click to collapse
In trying to test this, it magically works now.
I hate it when that happens - if a computer decides to magically work by itself, that means it can decide to magically break again by itself whenever it wants to.
Specifically, I applied the JFv1.5 update over JFv1.43 without wiping this time and I'm now unable to replicate the unknown baseband issue by rebooting.
Edit: Apparently by "works" I mean "google maps and the market both don't work at all". But that's a new problem. Whee...
In playing with the JFv1.43 to Xv1.5 (no wipe) upgrade path, I ran into a couple more issues. That path would consistently result in no working market, and I could only get Google Maps to work on Hv1.5r3.
But I've come up with a new strategy that largely seems to work:
Wipe
Install JFv1.42_R33
Wipe
Boot, Login to Google
Install JFv1.5
When I do this, I get signal and the market works. Google Maps shows a broken icon with the class name and won't launch, but I've basically got a working v1.5 phone.
Apparently all of this stuff just works for everyone else, but I figure I might as well document the fact that it took me two days to install a point-release update on my telephone in case anyone else is equally incompetent.
Edit: Apparently I hadn't installed the new radio. Doing that last doesn't seem to have broken anything.
I managed to solve the Google Maps thing.
I deleted these files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
/data/data/com.google.android.apps.maps
/system/app/Maps.apk
Then I copied the stuff under /system over from H1.5r3.
I'm relieved - finally Android acted exactly the way I expected it to.
Update 1.5 + radio
Hey, I am also having a problem with updating my g1 when I update to the 1.5v and new radio. When I updated to the 1.5v phone was not allowing me to make calls. I updated the radio and then it started acting crazy. No gps, internet, when a phone call come in it automatically went to speaker phone and none of the buttons would work. I couldn't bring up the dial pad or get to the menu. I had to go back to the old radio and old 1.43adp1.1h build. Has anyone gotten this to work and is there a certain order to update and when to wipe. Also, do I need to have a certain build in before updating and could the copies of the radio and build I got be bad. They came in on my jf updater and downloaded ota.
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
can you install a stock rom back onto it? There is a baseband selection mode that you may have to do.
http://forum.xda-developers.com/showthread.php?t=1116884
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
Ive had to run this a few times depending on radio and rom.
after many trials I am sticking with rooted stock.
Wow that is defiantly a menu I have never seen before.
It doesn't let me select any of the preferred carrier option. When I tap on GSM auto (PRL) it just closes and defaults back Unknown.
It's ded?
Sent from my HTC Phone
thepyro6 said:
It's ded?
Sent from my HTC Phone
Click to expand...
Click to collapse
Ya, I think it is. RIP Nexus S. HTC Sensation here I come.
after you select gsm auto you hit the menu button on your phone then select the carrier. I know its not labeled what it is on the walkthrough but its similar. not phone frequency but like signal or something. then yuo jsut select usa.
reboot and it should find whatever your service is on its own.
have you tried going back to stock rom? I used this version to go back when i thought i bricked out my phone and its been great. I think my friend used it too but he wont admit he used somethign i gave him.
http://forum.xda-developers.com/showthread.php?t=1060192
http://forum.xda-developers.com/showthread.php?t=1038007
Same issue also involved the trinity kernel. Dev may need to be notified.
kmmxracer said:
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
Click to expand...
Click to collapse
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
No im absolutely sure i flashed the right ROM. Peter Alfanzo was a ROM i flashed after this issue happened. It was the CM7 nightly + Trinity kernel that did me in...
Sent from my Nexus S using XDA Premium App
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Canehdianman said:
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Click to expand...
Click to collapse
have you tried reformatting all your phones partitions?
simms22 said:
have you tried reformatting all your phones partitions?
Click to expand...
Click to collapse
I've wiped user data/factory reset a few times now. Is there a higher-level format option that I should be using?
I thought for sure that going back to stock (based on these instructions - theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/) would work, but no such luck.
I find it perplexing that the baseband shows in fastboot, but nowhere else. *#*#4636#*#* shows radio off and network type unknown, settings/about phone/ shows baseband version unknown.
I tried different methods that I've found online over the weekend, but nothing has brought my radio back.
I am certainly open to suggestions!
I'm going to provide as much additional information as possible.
I have a Nexus S I9020A, running on Fido (Canada).
My initial problem stems from when I updated to cyanogenmod 7.1 from 7.0. My first (and likely biggest) mistake was not making a backup. Oops.
I think I accidentally chose "Nexus S 4G" instead of "Nexus S". As soon as I did that, I stopped getting any cellular voice or data connection (wifi continues to work fine). Under Phone Information, it said it was a Nexus S 4G.
The phone locks itself into airplane mode now. When I try to turn airplane mode off through the settings menu, it hangs. When I hold down power and choose "turn airplane mode off" it seems to work, but then I still get no signal.
I have pushed it back down to stock. It now remembers that it is a Nexus S (not 4G), but it didn't help the baseband problem.
I have tried to reflash the baseband. no effect.
I called Fido and got them to "repush" the SIM card. No effect.
I am humbly appreciative of any and all help that anyone can provide!
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Thanks! This is similar to some other threads I saw on the android forum (and elsewhere on XDA).
I'll try this when I get home (and get to a reliable wifi signal).
Wow! I haven't looked at my post in a wile. Hopefully you all are getting some resolution to these issues. I ended up calling Samsung and they agreed to fix my Nexus under warranty. They replaced some parts that I can't remember off the top of my head, but it should arive at my door tomorrow!!!
Sent from my HTC Sensation 4G using xda premium
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Hmmm bad news... my efs folder appears to be empty. Now what?
A very frustrating day... Thought i would have it fixed pretty quick, alas....
My efs folder is empty. I guess that explains the lack of radio, but it appears that i might need to send the phone to Samsung to get the efs reflashed. Is there a way to write it back myself? Ill look tomorrow i guess.
Here is some more info:
I just tried to update to 2.3.6
Clockwork mod is giving me an error message:
Assert failed: getprop("ro.product.device") == "crespo" || get prop("rp.build.product") == "crespo"
E:error in [filename]
(Status 7)
Installation aborted
Not sure if that helps but it's another piece of thepuzzle hopefully.
*sigh*
So it appears that I need a backup of my /efs folder in order to fix this myself (which I do not have).
I know what my IMEI should be, however I have no idea if it is even possible to take someone else's backup and alter it the proper IMEI.
I fear my next option will be to submit it for repair at a Samsung repair shop (and be without a phone even longer )
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
I recently rooted and started applying roms to my nexus s. Everything was going fine until my network data stopped working.
Have tried to unroot and return to stock but cant seem to get it right. whenever I try to use clockwork recovery any update zip i apply fails. Im currently on:
version - 2.3.1
baseband - 19020AUCKF1
kernal - 2.6.35.7-g7f1638a [email protected](hash sybol that isent on my mac keyboard)1
build - GRH7
I am based in the UK and think nthat my radio could be wrong?
When I factory reset in 2.3.1 i get the official update to 4.4 which dowloads, verifies then on installation stops and wont complete.
I am confussed with all the terminoligy and find the info on here overwelming to follow correctly.
on another forum i got the response that if i dont understand the process then I shouldent be doing this. Fact is I thought I did know what I was doing until it went wrong.
Could somebody be good enough to help me through this so I can restore my nexus s to working order please?
Read this thread: http://forum.xda-developers.com/showthread.php?t=1116884
Check your phone model, behind the battery. You probably have a gt-i9020 since you are in the UK.
Probably you need to flash the correct radio. What's a good choice? If you do have 9020, anything in the list with kb3 in it.
Kb3 has no limit to how fast it can upload data, which can be a benefit depending on how you use your phone. Most people would choose kl1 which is the most recent.
Download and flash in cwm recovery. Reboot.
Let me know if that works for you.
pnut1982ad said:
I recently rooted and started applying roms to my nexus s. Everything was going fine until my network data stopped working.
Have tried to unroot and return to stock but cant seem to get it right. whenever I try to use clockwork recovery any update zip i apply fails. Im currently on:
version - 2.3.1
baseband - 19020AUCKF1
kernal - 2.6.35.7-g7f1638a [email protected](hash sybol that isent on my mac keyboard)1
build - GRH7
I am based in the UK and think nthat my radio could be wrong?
When I factory reset in 2.3.1 i get the official update to 4.4 which dowloads, verifies then on installation stops and wont complete.
I am confussed with all the terminoligy and find the info on here overwelming to follow correctly.
on another forum i got the response that if i dont understand the process then I shouldent be doing this. Fact is I thought I did know what I was doing until it went wrong.
Could somebody be good enough to help me through this so I can restore my nexus s to working order please?
Click to expand...
Click to collapse
can you make calls? if you can, check your apn settings, settings>Data and networks>More>APN and delete everything, and retype the correct values for your carrier. if calls doesn't work, follow the post above. ^
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.