1. rupam95's Avatar
    Trying to install 4.4 using google's factory image but i get "Fail" after Baseband check.

    Says i have: m9615a-cefwmazm-2.0.1700.84

    but update requires m9615a-cefwmazm-2.0.1700.97

    Where can i get this?

    //I'm using Wug's Nexus Root Toolkit to push the 4.4 images to my nexus 4.

    /Extracted the image files, but there's only .84 radio file.....no .97 WTF?
    11-14-2013 04:32 PM
  2. GothBoyUK's Avatar
    I wonder if that suggests at least some locales will be getting a new radio version?

    Posted via Android Central App
    rupam95 likes this.
    11-14-2013 05:52 PM
  3. Sicily1918's Avatar
    The Galaxy SII (for one) would not work on a JB ROM unless you had the latest JB baseband; doesn't surprise me that a new OS might need a new baseband.
    rupam95 likes this.
    11-14-2013 06:28 PM
  4. rupam95's Avatar
    I wonder if that suggests at least some locales will be getting a new radio version?

    Posted via Android Central App
    I think so.
    That means no 4.4 today and have to wait for the OTA instead.
    11-14-2013 06:44 PM
  5. Phil Nickinson's Avatar
    Don't forget to flash the radio and bootloader. They're included in the factory image.
    rupam95 likes this.
    11-14-2013 08:34 PM
  6. someguy01234's Avatar
    The baseband (aka radio) is in the factory image itself. After you finished flashing the stock image you can flash back a different baseband if you want to.
    rupam95 likes this.
    11-14-2013 09:18 PM
  7. rupam95's Avatar
    Finally! After looking all over YouTube and Google i found it!
    I had to manually flash each file one by one!
    Thanks to this video:

    Other helpful Videos:



    Tips:
    Make sure your environment variables are placed correctly!
    To ensure adb is installed properly type in CMD "adb.exe" and NOT "adb".
    11-14-2013 09:45 PM
  8. jonzey231@yahoo.com's Avatar
    I remember hearing a while back on one of thses Android sites that there was a leaked FCC filing of a N4 with LTE. I wonder if the KitKat update will officially activate the radio. Since most of us use the the N4 on T-Mo anyways, LTE works flawlessly if you're in a covered area. I use it everwhere I go and it kicks HSPA+'s ***. Lol. So that'd be cool if they got it LTE certified and will activate LTE with the OTA.
    11-15-2013 11:29 AM
  9. azndoodle's Avatar
    can you provide your steps, please?

    do I need to download additional files?
    11-16-2013 03:21 AM
  10. gone down south's Avatar
    I remember hearing a while back on one of thses Android sites that there was a leaked FCC filing of a N4 with LTE. I wonder if the KitKat update will officially activate the radio. Since most of us use the the N4 on T-Mo anyways, LTE works flawlessly if you're in a covered area. I use it everwhere I go and it kicks HSPA+'s ***. Lol. So that'd be cool if they got it LTE certified and will activate LTE with the OTA.
    Sigh.

    It wasn't an FCC filling, it was an update to to the Bluetooth settings. And there was no change in the radios, just someone checked the LTE box in the phone description box.


    Sent from my Nexus 4 using AC Forums mobile app
    11-16-2013 09:44 AM
  11. MdkB's Avatar
    Hi everybody,

    I had the same the problem with my N4. i don't remember exactly the numbers but it was like "baseband X expected instead of baseband Y". I used the flash force option of NRT and didn't have problems (I did it because i wanted so much to play with kitkat). I checked my baseband version now and it's m9615a-cefwmazm-2.0.1700.84. could this be a problem for future OTA updates?

    is there an easy way to fix it? ( easy= not reinstalling everything)

    Thanks a lot
    M
    11-17-2013 09:36 AM
  12. gtanner00's Avatar
    I had the same problem. It was caused by Google's mistake of naming the new radio files (.97) the same as the old ones (.84) of you use the wugs toolkit it will try to check to make sure that the file matches the name for security reasons. Of course in this case they won't match and then file will fail to flash. The way to solve this is to turn on force flash in the toolkit options which will disable the verification and all will be fine when you're flash the stock images.

    Sent from my Nexus 4 using Tapatalk
    MdkB likes this.
    11-17-2013 11:27 AM
  13. MdkB's Avatar
    Yes that's what i did. so is it normal to see on my device now .84?
    11-17-2013 12:58 PM
  14. gtanner00's Avatar
    Yes that's what i did. so is it normal to see on my device now .84?
    If you just used the toolkit the normal way, then yes it should say .84 . what it says on the device is always the real name. The .84 radio will not function on 4.4 so that is where the problem is at.

    Sent from my Nexus 4 using Tapatalk
    MdkB likes this.
    11-17-2013 01:30 PM
  15. fernandezhjr's Avatar
    Yes that's what i did. so is it normal to see on my device now .84?
    The new radio is 97. You can download it from the first link here and flash in recovery.

    http://forum.xda-developers.com/show...php?p=34564891

    Sent from my Nexus 4 using Tapatalk
    MdkB likes this.
    11-17-2013 01:45 PM

Similar Threads

  1. Replies: 13
    Last Post: 11-18-2013, 01:34 PM
  2. [Free]-New game- Ship Parking 3D
    By isa_can in forum Android Games
    Replies: 1
    Last Post: 11-14-2013, 10:36 PM
  3. S2 stuck in roaming, and mass storage files are shortcuts
    By Goem in forum Sprint Galaxy S II Epic 4G Touch
    Replies: 0
    Last Post: 11-14-2013, 03:38 PM
  4. Quick question about direct installing APKs
    By bhough7 in forum Android 4.1 / 4.2 / 4.3 Jelly Bean
    Replies: 2
    Last Post: 11-14-2013, 02:41 PM
  5. Replies: 1
    Last Post: 11-14-2013, 01:59 PM
LINK TO POST COPIED TO CLIPBOARD