I played with nvflash quite a bit back in the day with my gtab while working (loosely) with Clemsyn to do stuff there.
Rough Translation:
That's assuming you linked up your device with a Google account. Also, what's reported there is just what the OS sees from the RIL. So a much more direct method would just be to request it from the baseband processor via AT commands. We're not having a problem determining the IMEI number. Once we flash another radio, the baseband starts reporting a blacklisted IMEI number instead of the original, valid IMEI that shipped with the device.
That looks more like they're trying to get data connectivity under ubuntu not gsm voice.
I'm in a similar place although I have a couple last minute ideas before I ship the bad one off. I would expect to at least be able to do an emergency call with the bad IMEI but even that function fails. So while the RIL and the baseband are talking at a base API (interface) level there appears to be other things at play.
Assuming it wasn't just some troll trying to get people's hopes up. Anyone can create an account and claim to be able to do something. The fact that our hero hasn't returned seems to indicate that it was just all BS.
Somebody please correct me if I'm wrong. I've been following this and see the progress and am absolutely convinced this is possible via software modding (I'm waiting on the new year to get this device so I may try to lend whatever I can to this) As I know it the tegra3 is the cpu/gpu and handles those processes. The ability for telephony services are handled by the radio which is where the problem is with flashing a compatible radio. I'm failing to see the connection of his claims to the problem at hand. I know from working/learning to compile cm & aokp for the gnote2 working with source and a new device tree forked from the international note we had to change the ro.telephony ril from the default samsungexynos ril to a more compatible qualcomm ril reflecting the radio network settings properly. Just from my limited experience it seems like that may be a similar issue here where the radio settings have to reflect the hardware just right. I may be way off base but trying to throw things out to help the cause.
