Search results


  1. H

    [RADIO] All xiaomi mi2 radio thread

    I never installed 3.3.29. I believe the packages are including all firmwares and drivers. So flashing the whole package means upgrading/downgrading all the drivers and even the radio (baseband), which is on the lowest level. Also there is nothing about touchscreen firmware mentioned in 3.3.29...
  2. H

    [RADIO] All xiaomi mi2 radio thread

    Is it safe to replace NON-HLOS.bin from v5 with older versions from v4?
  3. H

    [RADIO] All xiaomi mi2 radio thread

    Ok I'll try to downgrade to latest v4 to see for myself. Or try to hack V4 baseband to V5.
  4. H

    [RADIO] All xiaomi mi2 radio thread

    Ok :) So is there anything I can do? Inspect more? File a bug report somewhere?
  5. H

    [RADIO] All xiaomi mi2 radio thread

    Can you please be specific? Are you directing me to try the stuff mentioned in the first post? Sorry, I don't quite understand.
  6. H

    [RADIO] All xiaomi mi2 radio thread

    No change with 3.5.3 :-/ kekkejoker90, what do you mean?
  7. H

    [RADIO] All xiaomi mi2 radio thread

    Hi there, I'm still experiencing this issue. I'm now trying to flash 3.5.3 but I don't believe anything will change. I'm very close to ditching the phone as it is unusable :( I live in Czech Republic. So far I have been able to find (using Netmonitor) that in case of problems there is a BTS...
  8. H

    [RADIO] All xiaomi mi2 radio thread

    Yes, please...also is there some way for me to debug / dig deeper into this issue? Recently I upgraded to 3.4.12, seems to be better, but not gone, though. Radio problems seem to be worse when battery set to power saving mode. My baseband version reported is M9615A-CEFWMAZM-2.0.128017
  9. H

    [RADIO] All xiaomi mi2 radio thread

    Hello, I'm having the same problems. Came after flasing 3.4.5 multilang, but sometimes this (phone losing signal, emergency calls only, asks for PIN) happened before on stock ROM (JLB13 iirc). Now it happens almost every day many times, very annoying. It seems to happen when the signal is weak...