hello,
I am looking for a rom that can be flashed over stock 5.1. I had bad time with slimsaber ( otherwise superb rom)
, that had not data network
I would like not to have to revert to 5.0.2 or 4.4.4 just to flash a rom, at least not now I hav'nt time and computer near me
thanks for your answers
Envoyé de mon SM-T530 en utilisant Tapatalk
Get CM12.1. Wipe system, cache, data and dalvik n then flash via TWRP and reboot to system. Done.
nilanko said:
Get CM12.1. Wipe system, cache, data and dalvik n then flash via TWRP and reboot to system. Done.
Click to expand...
Click to collapse
Is that simple ? You can ensure me that the CM 12.1 ROM and kernel are compatible with stock 5.1 modem firmware ?
My question was not how to get a android 5.1 rom flashed on my phone , I know how to do this (I flashed slimsaber rom as I said)
Will git it a try anyway it's not that long to check it, but if you can confirm data network will work it would be nice
thanks for your quick answer
oduhart said:
Is that simple ? You can ensure me that the CM 12.1 ROM and kernel are compatible with stock 5.1 modem firmware ?
My question was not how to get a android 5.1 rom flashed on my phone , I know how to do this (I flashed slimsaber rom as I said)
Will git it a try anyway it's not that long to check it, but if you can confirm data network will work it would be nice
thanks for your quick answer
Click to expand...
Click to collapse
I have been on stock 5.1 too. Following that, I flashed uncountable LP ROMs and data worked in all of them. Now I am on CM12.1. It's the smoothest ROM out there. Make sure you wipe system. Once I faced data problem and after wiping system, it was solved. Also, the following commands fix some radio related problems (GPS and all, I don't really know but running these won't harm in any way):
Code:
mfastboot erase modemst1
mfastboot erase modemst2
DO NOT RUN ANY OTHER ERASE COMMANDS OTHER THAN THE TWO ABOVE.
nilanko said:
I have been on stock 5.1 too. Following that, I flashed uncountable LP ROMs and data worked in all of them. Now I am on CM12.1. It's the smoothest ROM out there. Make sure you wipe system. Once I faced data problem and after wiping system, it was solved. Also, the following commands fix some radio related problems (GPS and all, I don't really know but running these won't harm in any way):
Code:
mfastboot erase modemst1
mfastboot erase modemst2
DO NOT RUN ANY OTHER ERASE COMMANDS OTHER THAN THE TWO ABOVE.
Click to expand...
Click to collapse
Thanks nilanko !
Have you tried slimsaber rom ? If so did you encounter data problem ? solved by the fastboot erase ?
oduhart said:
Thanks nilanko !
Have you tried slimsaber rom ? If so did you encounter data problem ? solved by the fastboot erase ?
Click to expand...
Click to collapse
No I tried SlimLP but not Slimsaber. SlimLP had bugs so I left it.
Suggestion: Go for official ROMs. They regularly get updated and bugs keep getting fixed. CM is the best. It's clean and flawless.
thanks for your suggestions nilanko ! i just flashed cm12.1 official and .... daga network is ok. but i am o holiday with poor gsm network and receiving google 2 factor code by sms to activate google play is pure madness .... will have to wait to be back at work in few days to install it real
Envoyé de mon SM-T530 en utilisant Tapatalk
oduhart said:
thanks for your suggestions nilanko ! i just flashed cm12.1 official and .... daga network is ok. but i am o holiday with poor gsm network and receiving google 2 factor code by sms to activate google play is pure madness .... will have to wait to be back at work in few days to install it real
Envoyé de mon SM-T530 en utilisant Tapatalk
Click to expand...
Click to collapse
Why don't u disable 2 factor authentication?
it could be a solution but i can be kinda a paranoiac sometimes. and i'm not that hurry.....
Ans at l'East i know now that cm12 works with m'y moto e ans that's what i was looking for [emoji3]
Envoyé de mon SM-T530 en utilisant Tapatalk
oduhart said:
thanks for your suggestions nilanko ! i just flashed cm12.1 official and .... daga network is ok. but i am o holiday with poor gsm network and receiving google 2 factor code by sms to activate google play is pure madness .... will have to wait to be back at work in few days to install it real
Envoyé de mon SM-T530 en utilisant Tapatalk
Click to expand...
Click to collapse
Glad to know things work fine!
nilanko said:
I have been on stock 5.1 too. Following that, I flashed uncountable LP ROMs and data worked in all of them. Now I am on CM12.1. It's the smoothest ROM out there. Make sure you wipe system. Once I faced data problem and after wiping system, it was solved. Also, the following commands fix some radio related problems (GPS and all, I don't really know but running these won't harm in any way):
Code:
mfastboot erase modemst1
mfastboot erase modemst2
DO NOT RUN ANY OTHER ERASE COMMANDS OTHER THAN THE TWO ABOVE.
Click to expand...
Click to collapse
How is Stock android 5.1 as compared to CM12.1 and what difference did you found in both?
Please share the link of Stock 5.1 as I am on 4.4.4 and would like to give it a try before putting CM12.1 as 12.1 is still not stable ROM?
regards
Related
Hi Guys!
Today I need your help. My moto e runs perfectly on kitkat roms only. When I flash lp or mm roms, it's system ui starts force closing. This is how the problem started:
I was on cm13 nightly and I decided to update my twrp from play store. So, I downloaded the twrp manager app from play store and updated my recovery to 3.0.0. And the phone worked perfectly until the next day, when it started giving Fc's all of a sudden. I rebooted to recovery and made a full wipe including internal storage. Then I flashed cm11 and flashed gapps. The ROM booted up perfectly and had no fc's at all. So I decided to flash mm again. I flashed AOKP marshmallow but it again started giving me FC's. So, I reverted back to cm11and found no fc's again.
Here's the list of ROMs I tried and was unsuccessful each time:
AOKP(MM)
AOSP(MM and LP)
Cm13
Cm12.1
Blisspop(MM and LP)
Tesla ROM(LP)
Crdroid(MM)
ZephyrOS(MM)
AICP(MM)
Here's the list of ROMs I flashed and the device didn't give any fc's:
Cm11 nightly
Stock ROM Optimized
Stock ROM Full
CrDroid(kitkat)
Please guys I am in need of Deliberate help. Please do not post condolence comments like,"Strange issue mate, Sorry I don't know, Best of Luck". Please post only if you know the method or you have any links to the method.
In need of your help,
Regards,
PoseidonKing
I had the same issue with other MM roms. I got no fc error on CM13 and Resurrection Remix MM rom. Only these two mm Roms worked for me.
It's surely a device hardware issue. If only kitkat based roms work in your condor, then maybe it doesn't properly support art framework. So your last resort maybe going to service center
Sent from my Moto E
Try flashing factory image
Sent from my Moto E using Tapatalk
i think the problem is in the recovery. download cwm recovery img and flash it with fastboot and after that wipe everything including internal storage (do not reboot recovery at that tyme or before installing rom ) do not wipe ur sd card and then install rom without gapps and boot up after sucessful boot then again boot to recovery and install gapps... if problems remains same then try downloading other gapps package for 6.0 (preferred open gapps).
no need all of this, just record the logcat and post here, surely you'll get proper fix!
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Agreed! Custom recoveries known to, often cause these sort of problems.. Give the twrp 3.0.2 by magdoez or 2.8.7 a try.. These are the ones that work perfectly for me.
Try updating recovery from your current recovery itself & reboot.. Then try the aforementioned mm roms..
piku 123 said:
I think Twrp 3.0 is causing this revert to old 2.8 version.It is nothing to do with hardware if it is a hardware related problem then you can't even switch on phone.
Click to expand...
Click to collapse
Thanks bro, but the method ain't working. I am currently on TWRP 2.7.1.0 and I still face the same problem...
Adarsh1998 said:
no need all of this, just record the logcat and post here, surely you'll get proper fix!
Click to expand...
Click to collapse
Okay, thanks! But how the hell do I record a logcat??
PoseidonKing said:
Okay, thanks! But how the hell do I record a logcat??
Click to expand...
Click to collapse
Refer this thread: http://forum.xda-developers.com/showthread.php?t=1726238&page=28
Sent from my Moto E using Tapatalk
Hi guys,
Thank You everyone for your generous and quick help. My Moto E is fixed now. I flashed cyanpop mm and then tried the adopted sd option. Rebooted the device and now it is working perfectly. Though it wouldn't have been possible without my brother's help @Andy1911. Thank you once again to all of them who helped me.
Regards,
PoseidonKing.
Hi guys, can anyone tell me how to do it? I have a kate device here, and I'm dying to have cyanogenmod installed on it. Wish there's a non-too-complicated way to get it done.
Update:
Official CyanogenMod 13 for Kenzo works well on Kate too! Everything seems good right now.
Hey can you please Dump your device with twrp and share it with us so we can try to unlock Band 20
Edit: i think banmeifyouwant did it the others way around. Guess you have to repartition your internal memory to have the Layout of kenzo. Also someone in miui Forum posted he has flashed kenzo fastboot to his Kate device but Radio is not working anymore.
wtfjajaja said:
Hi guys, can anyone tell me how to do it? I have a kate device here, and I'm dying to have cyanogenmod installed on it. Wish there's a non-too-complicated way to get it done.
Update:
Official CyanogenMod 13 for Kenzo works well on Kate too! Everything seems good right now.
Click to expand...
Click to collapse
Can you please advise where you got TWRP from? Without TWRP, there's no CM or even root for XMIUI and MIUI Tweaks.
Also looking for a compatible TWRP method for the Kate/prime version. Been scouring the net for hours but can't find anything concrete
Hemphiz said:
Also looking for a compatible TWRP method for the Kate/prime version. Been scouring the net for hours but can't find anything concrete
Click to expand...
Click to collapse
Cofface seems to be a reasonable choice. Otherwise, Alka.
Pumpino said:
Cofface seems to be a reasonable choice. Otherwise, Alka.
Click to expand...
Click to collapse
You have working twrp on Redmi Note 3 pro prime?
Hemphiz said:
You have working twrp on Redmi Note 3 pro prime?
Click to expand...
Click to collapse
I'm still waiting for mine to arrive. Others have used Cofface for Kenzo on their Kate.
Pumpino said:
I'm still waiting for mine to arrive. Others have used Cofface for Kenzo on their Kate.
Click to expand...
Click to collapse
Ditto. Mine is due tomorrow. Thought I'd try and do some revision before flashing but the info I'm finding isn't quite enough for me to gain the confidence to try... May I follow you and feed off your knowledge?
Hemphiz said:
May I follow you and feed off your knowledge?
Click to expand...
Click to collapse
I'll be flashing Cofface TWRP and Xposed, but not CM at this stage. If that's helpful to you, I'll post how I go (if I ever get my hands on it).
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Pumpino said:
I'll be flashing Cofface TWRP and Xposed, but not CM at this stage. If that's helpful to you, I'll post how I go (if I ever get my hands on it).
Click to expand...
Click to collapse
Any info/guides would be greatly appreciated. If you stumble across anything you think might be of help for me then feel free to pm me links. I don't know much but read plenty prior to the task ahead. And thanks
DOMRuan said:
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Click to expand...
Click to collapse
Perhaps you could post more info. Which TWRP did you use and did you have to modify partition sizes, etc? Or was it as simple as flashing the firmware file and then the ROM itself?
Pumpino said:
Perhaps you could post more info. Which TWRP did you use and did you have to modify partition sizes, etc? Or was it as simple as flashing the firmware file and then the ROM itself?
Click to expand...
Click to collapse
Hi guys! I helped him to get this working. All things started with He didn't know that him device is Kate in first time and flashed Kenzo 7.1.8 Lollipop with modified emmc... in MiFlash to get unofficial bootloader unlock with fastboot oem unlock-go command. He got 5.1.1 Kenzo ROM working but without SIM Card detected due to flashed Kenzo modem. After it, he just flashed latest ALKA TWRP with all partitions support in fastboot and flashed latest CM nightly + GAPPS + CM13-Radios zip. It boots fine but with NO SIM Card detected too and unknown Baseband version. Don't worry. To solve it, just boot in fastboot and flash Kate modem from Kate MIUI Fastboot ROM and voila, fully working CM in Kate device! You guys with flashed TWRP can try to flash CM ROM without modify Partition sizes because CM use less space then MIUI and Kate partition sizes are same from Kenzo. Only system is bigger than Kenzo system but it works, prof of it is flashing Kenzo ROM in Kate with MiFlash don't give error like flashing Kate ROM in Kenzo.
andersonaragao said:
After it, he just flashed latest ALKA TWRP with all partitions support in fastboot and flashed latest CM nightly + GAPPS + CM13-Radios zip.
Click to expand...
Click to collapse
Thanks for the info. What does flashing CM13-Radios.zip do? If we don't flash that, would it leave Kate's default modem active? Would we need to flash the Kate modem each time we install a new nightly? Having to connect the phone to the computer every time would be a pain.
Pumpino said:
Thanks for the info. What does flashing CM13-Radios.zip do? If we don't flash that, would it leave Kate's default modem active? Would we need to flash the Kate modem each time we install a new nightly? Having to connect the phone to the computer every time would be a pain.
Click to expand...
Click to collapse
You can try it. Download CM last nightly and copy to internal storage, unlock your bootloader officially, flash ALKA TWRP recovery, go to backup and select ENTIRE PARTITIONS and do a full backup of your phone then wipe SYSTEM + DATA + CACHE + DALVIK CACHE, flash CM13 + GAPPS and reboot. This will keep your modem and all firmware partitions save. If it don't work and you get bootloop, boot in ALKA TWRP again, click in RESTORE, UNCHECK ONLY FIRMWARE PARTITION and start the restore process. This will boot MIUI again. Then start the process again but now this time, flash CM13-Radios.zip after GAPPS flash and try to boot it. When it boot, restart in bootloader and flash Kate modem and you will get fully working ROM. Or you can replace non-hlos.bin with Kate on in CM13-Radios.zip before flash it.
And no, you don't need to flash Kate modem at each new nightly because CM ROM don't comes with Modem files in it. After you get fully working CM nightly, you will get all OTA's without need a PC connect.
DOMRuan said:
Hy guys.. My de vice is kate. But running cm13 fine, stable and no bugs! Please check baseband for confirm, this device is Kate.
Click to expand...
Click to collapse
Hy, please call us...how did you unlock the bootloader from your Kate? Offical or Unofficial?
Which TWRP do you use?
Which CM13 do you flash on your Kate? The official CM13 for Kenzo?
A little instructions would be so good...Thanks!
@andersonaragao would you suggest a forum for unofficial bootloader unlock please? I'm getting network dropouts and need to flash the modems but xiaomi can take up to 7 and a half years to send an unlock code
Hemphiz said:
@andersonaragao would you suggest a forum for unofficial bootloader unlock please? I'm getting network dropouts and need to flash the modems but xiaomi can take up to 7 and a half years to send an unlock code
Click to expand...
Click to collapse
Unfortunately, to unlock bootloader unofficialy in Kate, you need to flash 5.1.1 MIUI ROM for Kenzo with modified bootloader. I think the better is stay with your stock ROM and wait more for unlock code.
andersonaragao said:
Unfortunately, to unlock bootloader unofficialy in Kate, you need to flash 5.1.1 MIUI ROM for Kenzo with modified bootloader. I think the better is stay with your stock ROM and wait more for unlock code.
Click to expand...
Click to collapse
Ok. Will do. A factory reset fixed the network issue so I can't live with that. Cheers
1. All Recoveries built for Kenzo will work without any issue on Kate as well, You can just stay with official TWRP or CM Recovery as you're pleased.
2. You can always flash the official rom back with MiFlash in EDL mode, if you happen to brick your phone.
Official ROM for Kate
Stable: http://bigota.d.miui.com/V7.3.9.0.M...DE_20160523.0000.23_6.0_global_f7170696d8.tgz
Developer: http://bigota.d.miui.com/6.8.25/kate_global_images_6.8.25_20160805.0000.29_6.0_global_195d892285.tgz
3. To install Official Cyanogenmod 13 for Kenzo on Kate (coming from MIUI), you would have to modify the build.prop and then flash the supported firmwares .zip file. One thing worth mentioning here is that, you must remove or replace NON-HLOS.bin found inside the .zip file, otherwise your phone wouldn't be able to detect the sim card. Still, you can flash only NON-HLOS.bin for Kate (from official rom) on fastboot later if you prefer to skip all the trouble modifying the firmwares .zip file. In my case, the only required files from the firmwares .zip for CM13 to run properly are just emmc_appsboot.mbn and file_contexts.
clean flashing 0415 build giving me bootloops. after 20 mins, the nitrogen boot animation still ongoing, no welcome screen or nothing.
pls somebody help if 0415 build flashed successfully...
i tried both with latest gapps/dynamic apps. still stuck at nitrogen boot animation
(ps: i had the 0331 build downloaded, clean flashing that build boots normally, no issue. but 0415 giving me bootloop. even dirty flashing over 0331 build)
is ResetScreenLockv2.zip flashing mandatory? i only skipped that part as i was clean flashing.
PLEASE REPLY IF ANYONE IS ABLE TO FLASH 0415 (LATEST) BUILD
+1 I have this problem also on kate, cannot boot this rom, with or without gapps...
Sent from my Redmi Note 3 SE
My posts are not sending on forms page.anybody help me
yes , that build seems odd, I'm having same problem too
LoL people..it has been answered 100 times.
You need to be on MM bootloader for new builds...
If you never flashed MM fastboot ROM on your device, then you are still on LP bootloader.
You must flash fastboot rom and then unlock it officialy...in that case it will work fine and you dont need to flash anything
Easy way is to flash MM bootloader;
https://forum.xda-developers.com/re...11-01-2017-t3536211/post71942715#post71942715
Denis:) said:
LoL people..it has been answered 100 times.
You need to be on MM bootloader for new builds...
If you never flashed MM fastboot ROM on your device, then you are still on LP bootloader.
You must flash fastboot rom and then unlock it officialy...in that case it will work fine and you dont need to flash anything
Easy way is to flash MM bootloader;
https://forum.xda-developers.com/re...11-01-2017-t3536211/post71942715#post71942715
Click to expand...
Click to collapse
MM fastboot rom was flashed many days ago.
nos 7.1.1 builds work perfectly. i dont know what happened to later builds.
LOS, RR, AEX all 7.1.2 roms working. only NOS is stuck at the very first boot animaton
I have successfully flashed and have been using the 15th April build, for the last 3 days.
I am also using build
theincognito said:
I have successfully flashed and have been using the 15th April build, for the last 3 days.
Click to expand...
Click to collapse
pls share some detail
1. which rom were u using befor flashing nos
2. which twrp
3. flashing steps
Simoom Sadik said:
pls share some detail
1. which rom were u using befor flashing nos
2. which twrp
3. flashing steps
Click to expand...
Click to collapse
1. 13th April test build of NOS
2. Dadi11's unofficial twrp. 3.1.0
3. Simple dirty flash.
I'm also using 15.04 build. Installed clean, after formatted everything, except sd card. Everything is working. I'm using Unofficial 7.1.2. Dynamic Gapps found in NOS thread. Came from RR 7.1.1.
Flash ROM then boot into it. After that reboot to twrp and flash the gapps.
THIS IS FOR ROOTED/Bootloader unlocked users - You can simply flash this over previous TWRP bootstack/stocksystems
Install procedure in TWRP :
1.flash N-B09 bootstack : https://androidfilehost.com/?fid=673791459329066133
2.flash N-B09 stocksystem : https://androidfilehost.com/?fid=962021903579497339
3.flash SU2.79 (or 2.82) again !!! DO NOT FORGET !!! : link in DownloadCenter A2017G
4.reboot again (...and give it some time...)
Btw, install Magisk at will. No problem there.
E N J O Y
Thnx @tron1 for his initial work on it :good:
raystef66 said:
THIS IS FOR ROOTED/Bootloader unlocked users - You can simply flash this over previous TWRP bootstack/stocksystems
Install procedure in TWRP :
1.flash N-B09 bootstack : https://androidfilehost.com/?fid=673791459329066133
2.flash N-B09 stocksystem : coming sooooooon....
3.flash SU2.79 (or 2.82) again !!! DO NOT FORGET !!! : link in DownloadCenter A2017G
4.reboot again (...and give it some time...)
E N J O Y
Click to expand...
Click to collapse
I guess Magisk does the same thing?
It has the no-verity script too, so, just sayin'
raystef66 said:
2.flash N-B09 stocksystem : coming sooooooon....
Click to expand...
Click to collapse
So wheeeeen....?)
Choose an username... said:
I guess Magisk does the same thing?
It has the no-verity script too, so, just sayin'
Click to expand...
Click to collapse
Sure. Magisk can be used too. No problem there.
I have a question.I am on stock B32 and unlocked bootloader on my G .If I flash universal B15 bootloader,Does the bootloader lock then ?
Hi guys, what's the purpose of flashing the bootstack? I came from Nexus 6 / LG G2, I am used to just dirty flashing the new builds over.
atakan33 said:
I have a question.I am on stock B32 and unlocked bootloader on my G .If I flash universal B15 bootloader,Does the bootloader lock then ?
Click to expand...
Click to collapse
No, it should remain unlocked.
Updated OP with stock system
Here you go and E N J O Y !!! :good:
raystef66 said:
Here you go and E N J O Y !!! :good:
Click to expand...
Click to collapse
Thanks a lot, downloading it now! My internet is quite slow and so it's going to take over 3 hours to download this ROM, but it'll be worth it in the end.
is it better to upgrade with stock system ?
@raystef66
Dear friend, I really enjoy your work because I actually own a A2017 version but with your images I'm able to simply flash the update without any modem fuss. Also it is great that there is neither force encryption nor unlocked bootloader warning present in your builds. Do you remove it by yourself?
sas.mar said:
@raystef66
Dear friend, I really enjoy your work because I actually own a A2017 version but with your images I'm able to simply flash the update without any modem fuss. Also it is great that there is neither force encryption nor unlocked bootloader warning present in your builds. Do you remove it by yourself?
Click to expand...
Click to collapse
Much appreciated !
These files are made that things like fastboot,... are left as they were. So no "unlocked bl warnings: whatsoever.
These bootstacks contain also the proper G modem in it (not as Universal B15, where you have to flash it afterwards)
Alright, I updated to this version from B04 and I honestly can't find any difference save the Dec 1 security patch...
hello if you can install this rom on a2017?
one silly question.
its possible to dirty flash?
If I flash bootstack I lost data decryption?
So I need to backup, flash, boot, then restore?
thanks
raystef66 said:
1.flash N-B09 bootstack : https://androidfilehost.com/?fid=673791459329066133
Click to expand...
Click to collapse
I'm running the latest Resurrection Remix (A version of LOS) on my A2017G. can I also just flash this new bootstack without doing anything else? I only want the new modem and such because I'd like to try out if it fixes my horrible SOT of about 2 hours
vadsvads said:
I'm running the latest Resurrection Remix (A version of LOS) on my A2017G. can I also just flash this new bootstack without doing anything else? I only want the new modem and such because I'd like to try out if it fixes my horrible SOT of about 2 hours
Click to expand...
Click to collapse
Yeah you can use the files as it is for G model.
But first take twrp backup! Use 3110 to be sure.
Btw, you can try out the different G modems in Download Center. No harm done flashing them. Just try and see what's best.
But then again, 2h SOT... Mmmmm, advice looking for some draining apps, check all permissions on app settings for battery saving and so on.
does this rom work on b15 bootstack?
mario32 said:
does this rom work on b15 bootstack?
Click to expand...
Click to collapse
When you're on B15 universal, just flash B09 bootstack. Or what is your purpose ?
my phone is A2017 chinese version and I ask if you can install it on this phone.
Sorry my English translator
Hi Everyone, I am currently using AEX O latest build with stock kernel. The problem is after making a call from 1st slot sim (Jio), the 2nd slot sim(Airtel) is not detecting the network. And a reboot fixes it up. So each and every time I need to reboot to fix this.
This problem started after I flashed the MIUI N ported version by Dalphana and still exists in AEX O even after the clean flash.
So whats the permanent solution guys? Please help me:crying:
bikash.sahu94 said:
Hi Everyone, I am currently using AEX O latest build with stock kernel. The problem is after making a call from 1st slot sim (Jio), the 2nd slot sim(Airtel) is not detecting the network. And a reboot fixes it up. So each and every time I need to reboot to fix this.
This problem started after I flashed the MIUI N ported version by Dalphana and still exists in AEX O even after the clean flash.
So whats the permanent solution guys? Please help me:crying:
Click to expand...
Click to collapse
Are u latest miui firmware?
Did u clean flash . format data wipe data.?
Are u on custom kernel?
naik2902 said:
Are u latest miui firmware?
Did u clean flash . format data wipe data.?
Are u on custom kernel?
Click to expand...
Click to collapse
Yup, I've already mentioned that I made clean flash. and I'm on stock kernel.
Try to use NETWORK GURU to lock band. Or change to airplane mode.
To fix this really... I dont know u.u