CM13 firmware problem - Xiaomi Redmi Note 3 Questions & Answers

Hi,
I have a note 3 with latest development MM from and I want to pass to a custom ROM, based on cyanogen 13. My bootloader is unlocked, TWRP installed and fully functional. When I install CM13 (or any ROM based on it such as Dirty Unicorn, or other) and the recommended Gapps, my fingerprint reader doesn't work and like many, I have a settings FC. When I install the following:
CM13 firmware+ROM+Gapps, no network at all, and wifi is behaving weard, even after a reboot. So what's the trick to have everything working, I probably missed something, but I simply want CM13 with Fingerprint working and of course, my network and Data connexion and wifi.
Thanks for help.

ybregeon2016 said:
Hi,
I have a note 3 with latest development MM from and I want to pass to a custom ROM, based on cyanogen 13. My bootloader is unlocked, TWRP installed and fully functional. When I install CM13 (or any ROM based on it such as Dirty Unicorn, or other) and the recommended Gapps, my fingerprint reader doesn't work and like many, I have a settings FC. When I install the following:
CM13 firmware+ROM+Gapps, no network at all, and wifi is behaving weard, even after a reboot. So what's the trick to have everything working, I probably missed something, but I simply want CM13 with Fingerprint working and of course, my network and Data connexion and wifi.
Thanks for help.
Click to expand...
Click to collapse
Anyone can help?

So do you have kenzo or Kate
Gesendet von meinem Redmi Note 3 mit Tapatalk

Sujejsjejej said:
So do you have kenzo or Kate
Gesendet von meinem Redmi Note 3 mit Tapatalk
Click to expand...
Click to collapse
The Snapdragon one

omg keno or kate its a simple question also you probably have a goodix scanner if it docents work

Did you install CM-Radio.zip, also?

justinxfan said:
omg keno or kate its a simple question also you probably have a goodix scanner if it docents work
Click to expand...
Click to collapse
I have kenzo and my fp is not goodix

ybregeon2016 said:
I have kenzo and my fp is not goodix
Click to expand...
Click to collapse
It's FPc102x

divxmaniak said:
Did you install CM-Radio.zip, also?
Click to expand...
Click to collapse
Where to find it?

ybregeon2016 said:
Hi,
I have a note 3 with latest development MM from and I want to pass to a custom ROM, based on cyanogen 13. My bootloader is unlocked, TWRP installed and fully functional. When I install CM13 (or any ROM based on it such as Dirty Unicorn, or other) and the recommended Gapps, my fingerprint reader doesn't work and like many, I have a settings FC. When I install the following:
CM13 firmware+ROM+Gapps, no network at all, and wifi is behaving weard, even after a reboot. So what's the trick to have everything working, I probably missed something, but I simply want CM13 with Fingerprint working and of course, my network and Data connexion and wifi.
Thanks for help.
Click to expand...
Click to collapse
I'm having same problem before with CM13, right now I'm using Resurrection Remix rom, however RR rom is also based on CM13, which mean, the bug is kinda same, so I went flashing, CM13 firmware+rom+gapps, and just like you, no network at all, wifi cannot connect and etc. So what I do after that solve all issue, including some bug from RR rom.
My Solution:-
1. Download fastboot stock rom of Redmi Note 3 from MIUI. --> You can google 'where to download redmi note 3 fastboot rom'
2. I'm not sure about china rom, coz I'm using global rom.
3. Extract until you see image folder.
4. Make a backup of CM13-Firmware.zip
5. Open CM13-Firmware.zip using any zip application, or just extract.
6. Go to firmware-update folder.
7. Copy all item below from stock MIUI Rom into CM13-Firmware folder.
adspso.bin --> Copy
cmnlib.mbn --> Copy
devinfo.img --> This file doesn't exist in Stock Rom, so just ignore this
emmc_appsboot.mbn --> This contain bootloader info, if you copy this one, your bootloader may lock, so just ignore this one.
hyp.mbn --> Copy
keymaster.mbn --Copy
mdtp.img --> Copy
NON-HLOS.bin --> Copy
rpm.mbn --> Copy
sbl1.mbn --> Copy
tz.mbn --> Copy
8. Once finishing copy all item mention above, rename this new edited CM13-Firmware to others name, and copy to your sdcard or usb-otg.
9. Reboot recovery, and flash this new edited firmware, and hopefully it solve your problem.
10. For me, I did this method, and really save me, its also fix bug that already exist in Resurrection Remix rom.
Please note, this is my method of solving the problem I encounter. It may not same for everyone, however, I share this method, coz it might help someone out there that having the same problem.

onekay70 said:
I'm having same problem before with CM13, right now I'm using Resurrection Remix rom, however RR rom is also based on CM13, which mean, the bug is kinda same, so I went flashing, CM13 firmware+rom+gapps, and just like you, no network at all, wifi cannot connect and etc. So what I do after that solve all issue, including some bug from RR rom.
My Solution:-
1. Download fastboot stock rom of Redmi Note 3 from MIUI. --> You can google 'where to download redmi note 3 fastboot rom'
2. I'm not sure about china rom, coz I'm using global rom.
3. Extract until you see image folder.
4. Make a backup of CM13-Firmware.zip
5. Open CM13-Firmware.zip using any zip application, or just extract.
6. Go to firmware-update folder.
7. Copy all item below from stock MIUI Rom into CM13-Firmware folder.
adspso.bin --> Copy
cmnlib.mbn --> Copy
devinfo.img --> This file doesn't exist in Stock Rom, so just ignore this
emmc_appsboot.mbn --> This contain bootloader info, if you copy this one, your bootloader may lock, so just ignore this one.
hyp.mbn --> Copy
keymaster.mbn --Copy
mdtp.img --> Copy
NON-HLOS.bin --> Copy
rpm.mbn --> Copy
sbl1.mbn --> Copy
tz.mbn --> Copy
8. Once finishing copy all item mention above, rename this new edited CM13-Firmware to others name, and copy to your sdcard or usb-otg.
9. Reboot recovery, and flash this new edited firmware, and hopefully it solve your problem.
10. For me, I did this method, and really save me, its also fix bug that already exist in Resurrection Remix rom.
Please note, this is my method of solving the problem I encounter. It may not same for everyone, however, I share this method, coz it might help someone out there that having the same problem.
Click to expand...
Click to collapse
OK I'll try to follow the same steps and see. I'll keep you updated

ybregeon2016 said:
OK I'll try to follow the same steps and see. I'll keep you updated
Click to expand...
Click to collapse
Hopefully it will save your trouble. Do update us if success...

update with new firmware that works your network module and only flash sbl.mbn(cm13 firmware) then check and flash tz.mbn(cm13 firmware) and check again(for fingerprint sensor).
if your fingerprint sensor working in some firmware and network module is missing then only flash NON-HLOS.bin from cm14 or cm13 firmware vice versa and check.

onekay70 said:
I'm having same problem before with CM13, right now I'm using Resurrection Remix rom, however RR rom is also based on CM13, which mean, the bug is kinda same, so I went flashing, CM13 firmware+rom+gapps, and just like you, no network at all, wifi cannot connect and etc. So what I do after that solve all issue, including some bug from RR rom.
My Solution:-
1. Download fastboot stock rom of Redmi Note 3 from MIUI. --> You can google 'where to download redmi note 3 fastboot rom'
2. I'm not sure about china rom, coz I'm using global rom.
3. Extract until you see image folder.
4. Make a backup of CM13-Firmware.zip
5. Open CM13-Firmware.zip using any zip application, or just extract.
6. Go to firmware-update folder.
7. Copy all item below from stock MIUI Rom into CM13-Firmware folder.
adspso.bin --> Copy
cmnlib.mbn --> Copy
devinfo.img --> This file doesn't exist in Stock Rom, so just ignore this
emmc_appsboot.mbn --> This contain bootloader info, if you copy this one, your bootloader may lock, so just ignore this one.
hyp.mbn --> Copy
keymaster.mbn --Copy
mdtp.img --> Copy
NON-HLOS.bin --> Copy
rpm.mbn --> Copy
sbl1.mbn --> Copy
tz.mbn --> Copy
8. Once finishing copy all item mention above, rename this new edited CM13-Firmware to others name, and copy to your sdcard or usb-otg.
9. Reboot recovery, and flash this new edited firmware, and hopefully it solve your problem.
10. For me, I did this method, and really save me, its also fix bug that already exist in Resurrection Remix rom.
Please note, this is my method of solving the problem I encounter. It may not same for everyone, however, I share this method, coz it might help someone out there that having the same problem.
Click to expand...
Click to collapse
I followed your steps, copied the files to the cm13 firmware and the data connection is back but still have the settings FC and no fingerprint. I am back now to the latest MIUI development ROM.

Guys help me how to unlock my boatloader plz tell me

ybregeon2016 said:
Where to find it?
Click to expand...
Click to collapse
Check on the thread http://forum.xda-developers.com/redmi-note-3/development/fix-cm13-based-roms-t3416662

onekay70 said:
I'm having same problem before with CM13, right now I'm using Resurrection Remix rom, however RR rom is also based on CM13, which mean, the bug is kinda same, so I went flashing, CM13 firmware+rom+gapps, and just like you, no network at all, wifi cannot connect and etc. So what I do after that solve all issue, including some bug from RR rom.
My Solution:-
1. Download fastboot stock rom of Redmi Note 3 from MIUI. --> You can google 'where to download redmi note 3 fastboot rom'
2. I'm not sure about china rom, coz I'm using global rom.
3. Extract until you see image folder.
4. Make a backup of CM13-Firmware.zip
5. Open CM13-Firmware.zip using any zip application, or just extract.
6. Go to firmware-update folder.
7. Copy all item below from stock MIUI Rom into CM13-Firmware folder.
adspso.bin --> Copy
cmnlib.mbn --> Copy
devinfo.img --> This file doesn't exist in Stock Rom, so just ignore this
emmc_appsboot.mbn --> This contain bootloader info, if you copy this one, your bootloader may lock, so just ignore this one.
hyp.mbn --> Copy
keymaster.mbn --Copy
mdtp.img --> Copy
NON-HLOS.bin --> Copy
rpm.mbn --> Copy
sbl1.mbn --> Copy
tz.mbn --> Copy
8. Once finishing copy all item mention above, rename this new edited CM13-Firmware to others name, and copy to your sdcard or usb-otg.
9. Reboot recovery, and flash this new edited firmware, and hopefully it solve your problem.
10. For me, I did this method, and really save me, its also fix bug that already exist in Resurrection Remix rom.
Please note, this is my method of solving the problem I encounter. It may not same for everyone, however, I share this method, coz it might help someone out there that having the same problem.
Click to expand...
Click to collapse
you copied from marshmallow fastboot rom ?
Sent from my Redmi Note 3 using Tapatalk

nikufellow said:
you copied from marshmallow fastboot rom ?
Click to expand...
Click to collapse
Yes, because I use CM13, which is marshmallow version. If u using other version, copy from one matching ur android version.

onekay70 said:
Yes, because I use CM13, which is marshmallow version. If u using other version, copy from one matching ur android version.
Click to expand...
Click to collapse
only Santhosh cm use marshmallow right?
Sent from my Redmi Note 3 using Tapatalk

nikufellow said:
only Santhosh cm use marshmallow right?
Click to expand...
Click to collapse
No, actually official by thestrix also using marshmallow, u can go to official CyanogenMod website, in download section go to RedmiNote 3 device, both stable and nightly is using marshmallow android 6.0 version.

Related

[GUIDE] [C6802] Stock To Custom ROM [Without Losing/Recover Lost IMEI & BASEBAND]

Thanks to blueether for His very useful thread
! ATTENTION !
There is a SIMPLE SOLUTION HERE
The C6833 modem works for my C6802 [TESTED]
Thanks to Triflot​
Requirements:
*. DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANYTHING THIS WILL DO TO YOUR PHONE
1. Xperia Z Ultra (Absolutely! ) [Tested on XZU with Unlocked Bootloader]
2. FlashTool, Download link & tutorial here
3. Required FTF (NUT's *.532 & *.136)
4. Custom ROM
5. PC running Windows OS
How to get into Flash Mode:
1. Power Off your Z Ultra
2. Press & hold Vol-
3. Plug your phone to your PC (USB driver > read for intallation step here)
How to get into FastBoot Mode:
1. Power Off your Z Ultra
2. Press & hold Vol+
3. Plug your phone to your PC (USB driver > read for intallation step here)
[TRICK] Get Into FastBoot Mode/Flash Mode​
If you're having trouble getting into FastBoot Mode/Flash Mode, you can try this trick
1. You have to be on Windows
2. Make sure you opened FlashTool & installed driver for Z Ultra
3. Open Device Manager
4. Show hidden device [Not really necessary, I did this to make sure my Z Ultra driver is installed]
5. Plug your phone while holding Vol+ (FastBoot) OR Vol- (Flash)
6. If it doesn't recognized by Windows, then Scan for hardware changes (this simulate USB Unplug & Replug for me), do this while holding the Volume Rocker
7. Repeat number 6 until you got it connected
For Windows 8/8.1 Only:
When you connected Z Ultra using Flash Mode to your PC, it'll disconnect after a while, to solve this problem, try to prepare your files you want to flash first, then when FlashTool asked to connect your phone, do step 1 to 7, your phone won't disconnect at the time it being flashed
Fresh Install [RECOMMENDED]​
Steps:
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool [Default Settings, Flash Everything]
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available
Thanks to x1123 for his post here
Update Custom ROM [EXPERIMENTAL]​*Please Correct Me If I Wrong
Steps:
*. This Will Not Keep Your Google Account, So, Contacts, Mails, Hangouts Messages, etc. That Related To Google Account Will Disappear
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery [GAPPS Must Be Installed, Otherwise Google Framework Will Crash]
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available [Some Google Apps Will Disappear, You'll Need To Re-Install It]
Tested ROMs: copied from here
Carbon - Build 8: Working
SlimKat: Not tested yet
LiquidSmooth: Not tested yet
FXF CM11: Not tested yet
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe ROM: Not tested yet
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
blueether said:
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
I lost my imei yesterday so i have to go through this process. And since i'm already in a custom rom, so i don't need to flash boot.img via fastboot right? Just flash everything via recovery?
And if i do lost imei again, i just need to restore the backup of my previos rom?
Coming from a nexus, this quite confusing :/
Azra4 said:
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
Click to expand...
Click to collapse
You flash it via Flashtool. The link for the thread is in the op.
satriamau said:
You flash it via Flashtool. The link for the thread is in the op.
Click to expand...
Click to collapse
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Azra4 said:
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Click to expand...
Click to collapse
I don't think you should flash ftf to a gpe z ultra. I've read somewhere it'll brick your device.
Dang! OK, so how do I get my IMEI back then?
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
you flashed the normal togari CM11 not the togari_gpe version? is so just flash the _gpe version over top
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Riza said:
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Click to expand...
Click to collapse
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
So Carbon worked fine with no IMEI issues?
blueether said:
So Carbon worked fine with no IMEI issues?
Click to expand...
Click to collapse
No since i follow these steps while flashing carbon. I flash cm without these steps. Wanted to try cm since carbon giving me random reboots sometime. I love the features btw.
Oot : is there anyway i can turn heads up off on carbon?
Thanks.
juggz143 said:
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Click to expand...
Click to collapse
i tried this AFTER i unlocked my bootloader, so idk about XZU with locked bootloader, but i think it's safer to unlock your bootloader first, it's to avoid soft brick of the device, many thread says u must unlock your bootloader before you install any custom ROM
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
i'm afraid idk the other way, if you want to change your rom, then you must follow the fresh install guide, but if ure upgrading [from CM 11 to later CM 11] then follow upgrade guide
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Flash the attached c6833-modem.zip file for a workaround.
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
That makes perfect scene, good on you mate
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Riza said:
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Click to expand...
Click to collapse
Thanks, that's great!
Did you try the c6x02 file, too? And it didn't work? I wonder why it's included, then - I guess we should ask CM on their issue tracker. In the meantime, you can just delete the c6x02.sh file from the root of any ROM zip you want to install, and it should use functional modem files. (Or use the above zip, but it may become obsolete in the future.)
Still, this doesn't tell the full story if for example Carbon users have had the IMEI problem, since it doesn't have the script. Have you had reports of that, @blueether? Maybe they were caused by not flashing on top of a compatible stock ROM?
There was one I think. I'm not sure what the cause was though

Kate Device no /Modem partition Data not working

I've recently gotten my kate device, I've unlocked the phone via the chinese developer's fastboot rom. I've previously opened my backplate to unplug the battery pins (for booting into edl mode).
I'm able to flash to cm13, however, no matter what cm13 firmware or kate nx radios I flashed. I can't seem to get cellular data on the device, keeps saying that it's unable to search for network operator.
I checked and found out that the device does not have a modem partition. Could anyone help me get data on my Kate device crying:
Try yourself to do so:
1. Keep your Kate NX Radios file
2.Try to get the most updated international version of Kate MIUI8 ROM and then download it
3.Use WinRar to open NX Radios and MIUI8 ROM.
4.Pull files one by one from folder of "firmware-update" in Kate MIUI8 ROM and replace files one by one in NX Radios file
5.After finishing it, save new NX Radios file as another new name.
6.Enter TWRP and flashing the new NX Raios file you make.
Good luck !
scarletgod said:
I checked and found out that the device does not have a modem partition. Could anyone help me get data on my Kate device crying:
Click to expand...
Click to collapse
pls try
- flash kate firmware using twrp...if still can't help then try below
- flash fastboot room using miflash via edl...hope miflash able to create those modem partition.
abihary said:
pls try
- flash kate firmware using twrp...if still can't help then try below
- flash fastboot room using miflash via edl...hope miflash able to create those modem partition.
Click to expand...
Click to collapse
I've tried that, however there is no modem partition. The thing is that data works when I flash it to the chinese developer's rom
scarletgod said:
I've tried that, however there is no modem partition. The thing is that data works when I flash it to the chinese developer's rom
Click to expand...
Click to collapse
so, already flash chn dev rom using miflash? i guess your modem patition already repaired by flashing those chn dev rom?
then you can create by yourself miui chn dev firmware into a flashable zip for future usage, if you didn't want use that rom. the way as mentioned above by kris chen.
Kris Chen said:
Try yourself to do so:
1. Keep your Kate NX Radios file
2.Try to get the most updated international version of Kate MIUI8 ROM and then download it
3.Use WinRar to open NX Radios and MIUI8 ROM.
4.Pull files one by one from folder of "firmware-update" in Kate MIUI8 ROM and replace files one by one in NX Radios file
5.After finishing it, save new NX Radios file as another new name.
6.Enter TWRP and flashing the new NX Raios file you make.
Good luck !
Click to expand...
Click to collapse
abihary said:
so, already flash chn dev rom using miflash? i guess your modem patition already repaired by flashing those chn dev rom?
then you can create by yourself miui chn dev firmware into a flashable zip for future usage, if you didn't want use that rom. the way as mentioned above by kris chen.
Click to expand...
Click to collapse
Thank you both! I'll go try this out
Kris Chen said:
Try yourself to do so:
1. Keep your Kate NX Radios file
2.Try to get the most updated international version of Kate MIUI8 ROM and then download it
3.Use WinRar to open NX Radios and MIUI8 ROM.
4.Pull files one by one from folder of "firmware-update" in Kate MIUI8 ROM and replace files one by one in NX Radios file
5.After finishing it, save new NX Radios file as another new name.
6.Enter TWRP and flashing the new NX Raios file you make.
Good luck !
Click to expand...
Click to collapse
Hi sir!
Do you happen to know which files I should pull over? I tried pulling all of them over but I have errors even detecting the sim card now
Just only need to pull files under directory of "firmware-update" from mostly updated MIUI8 ROM.
Check attachment.
scarletgod said:
Hi sir!
Do you happen to know which files I should pull over? I tried pulling all of them over but I have errors even detecting the sim card now
Click to expand...
Click to collapse

Tutorial: Going from stock Lollipop or Marshmallow to Nougat.

I will tell you how to go from stock to a custom rom running Nougat.
Notice:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these ROMs
* before flashing them! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
First, you must go to Marshmallow from Lollipop. If you are already on stock Marshmallow, skip this step.
1. First off, you'd need to download and extract two files. SP Flash Tools and the 6.0 stock rom.. You should use the first link, but if you have an idea what you're doing, nothing's wrong with flashing with TWRP rather than SP Flash, if you already have it installed for whatever reason.
2. In SP Flash Tools, set the download agent to MTK_AllInOne_DA.bin found in the SP Flash folder, and the scatter file to MT6753_Android_scatter.txt in the extracted rom zip file.
3. Turn off and unplug your phone.
4. Click on Download in SP Flash, then plug in your phone.
5. Upon completion, boot directly to recovery by holding volume up and power until the BLU logo appears.
6. Do a factory reset with a Wipe.
7. You can skip the next part.
Click to expand...
Click to collapse
Now, you need to flash TWRP to your phone.
1. Go to this thread. I know, it's Lineage OS. The ROM you decide to flash does not matter. The recovery works for all ROMs.
2. Download SP Flash Tools if you have not already.
3. Flash the recovery to your phone with SP Flash Tools.
Click to expand...
Click to collapse
Now, you need to copy some files from your phone to your computer.
1. Boot into TWRP.
2. Under mount, enable system.
3. Under the Advanced tab, open File Manageer.
4. Copy the following folders to a folder accessible to your PC. I recommend a USB drive (/usbotg/) or the external sd card (/external_sd/).
/system/etc/firmware
/system/etc/mddb
5. Copy those folders to your PC.
Click to expand...
Click to collapse
Next, you must select your custom ROM of choice.
Lineage OS 14.1
AOSP Extended 4.6
Resurrection Remix 5.8.5
Viper OS 3.1.1 (My current ROM of choice)
Cr Droid 3.8.4
Download your ROM of choice and if you are on the following devices, download the patch as well.
BLU Vivo 5, Condor A55 slim, and Gionee s6
Click to expand...
Click to collapse
If on the BLU Vivo 5, Condor A55 slim, and Gionee s6, you open the PATCH zip file and delete the following folders.
/system/etc/firmware
and
/system/etc/mddb
Then what you do is you copy the firmware and mddb folders from your phone into the patch file, taking the place of the folders you just deleted.
Click to expand...
Click to collapse
If on the BLU Vivo 5r, Condor A8, or Gionee s6s, you open the ROM zip and delete the following folders.
/system/etc/firmware
and
/system/etc/mddb.
Then what you do is you copy the firmware and mddb folders that you copied from your phone into the patch (taking the place of the folders you just deleted).
Click to expand...
Click to collapse
Lastly, you copy the rom and patch (if applicable) files to your phone.
Then you flash through TWRP. Always make a backup before flashing anything.
Enjoy your new ROM.
I personally recommend you download the latest Magisk and Gapps micro packages and flash them too.
Thanks for this guide. I will try to get the Marshmallow firmware and upload for making the process faster.
Letrix said:
Thanks for this guide. I will try to get the Marshmallow firmware and upload for making the process faster.
Click to expand...
Click to collapse
You're welcome. Did you successfully flash the rom?
llamasking said:
You're welcome. Did you successfully flash the rom?
Click to expand...
Click to collapse
I couldn't manage to create an independent ROM of Lollipop.
Letrix said:
I couldn't manage to create an independent ROM of Lollipop.
Click to expand...
Click to collapse
What do you mean?
Is there a reason this will not work with Fastboot?
Okay, so it looks as if Fastboot is disabled on my device. I went into the Stock Rom, and I found there is a switch on the Stock Rom that turns Fastboot on and off. It says: Allow Oem Unlock.
I've heard of some folks bricking their Phones this way by flipping this switch in the stock rom. Is that true?
My choices seem to be:
1. Use SP Flash Tool to Flash TWRP. Then TWRP to load AOSP Extanded, or Lineage.
2. attempt to use that switch to see if it will let me do a fastboot oem unlock.
I'd like to try the second, but I want to know if thats a land mine to a bricked Phone if I flip the switch to allow OEM Unlock of the bootloader.
If on Android 6, use SP Flash.
If on 5, use SP flash to repair rom, upgrade to 6. Flash TWRP
Updated today. You can now upgrade directly to Marshmallow with TWRP installed using SP Flash thanks to onasre. Skips OTA entirely.

[CLOAED][GUIDE] Flash Generic System Image Using CMD Or TWRP In Nokia 6.1 Plus

Treble Flashing Guide For All nokia treble enabled phones
Note -1. Before Doing These Steps Your device bootloader should be unlocked. otherwise you may brick your device.
2.Copy img files according to GSI Android Version
Example - iam using Nokia 6.1 Plus & i want to flash Pixel-ex-periance-9
in my phone using GSI
METHOD 1 - VIA CMD
1. copy vendor.img & boot.img form Android 9 stock ota.zip or OST File
2. download gsi from aosp , lineage , pixel experiance etc but choose ab Arm 64
3. now keep 3 files in one folder
4. open cmd in that folder
5. now turn of your mobile and go to download mode
6. now type fastboot devices
7. type fastboot -w
8. type fastboot flash vendor vendor.img
9. type fastboot flash system PixelExperienceP-arm64-ab.img
10. type fastboot flash boot boot.img
11. type fastboot -w
12. fastboot reboot
METHOD 2 - VIA TWRP
1. copy Those 3 img files to your directory internal or external
2. wipe everything except your internal & sd
3. select install img
4. select vendor.img and select vendorimage in partition box swipe to flash
5. next select PixelExperienceP-arm64-ab.img and select systemimage in partition box swipe to flash
6. next select boot.img and select boot in partition box swipe to flash
7. reboot system
Download stock Vendor.img & boot.img files from the below links
Android 9 https://drive.google.com/open?id=1WC9iGS8QnnnBmG4KKL3sEcqlR8LceBUt
Android 8.1.0 https://drive.google.com/open?id=1yY3QvUCYKDXlfn9bREObS2XwCScnU-EN
Please Hit Thanks Button If You Understand My Guide. Hope Every One Will Boot GSI Successfully In Your Phones. Keep Going...!!!
Thank you
can you post 6.1plus vendor IMG and boot IMG here please
Or links
pawankonjarla said:
can you post 6.1plus vendor IMG and boot IMG here please
Or links
Click to expand...
Click to collapse
links updated now
BootLoader
Should the bootloader be unlocked to flash via CMD??
Thanks:good:
nikash07 said:
Should the bootloader be unlocked to flash via CMD??
Thanks:good:
Click to expand...
Click to collapse
yes Need to unlock your bootloader before flashing GSI Or else you may Brick your device
Raghu varma said:
yes Need to unlock your bootloader before flashing GSI Or else you may Brick your device
Click to expand...
Click to collapse
How to unlock bootloader, especially after August Security patch coz HMD doesn't allow to unlock bootloader of 6.1 plus anymore
nikash07 said:
How to unlock bootloader, especially after August Security patch coz HMD doesn't allow to unlock bootloader of 6.1 plus anymore
Click to expand...
Click to collapse
Just Go to Nearest Nokia Care Point And tell them Iam not comfort with Android Pie i want to revert back to oreo june Security Patch So Just Inform Them i mean tell them to flash DRG-229D File . This file will directly goes down to oreo june security Patch And give the mobile to them they will flash in 2minutes And request Unlock Key Just by in searching Google.
Raghu varma said:
Just Go to Nearest Nokia Care Point And tell them Iam not comfort with Android Pie i want to revert back to oreo june Security Patch So Just Inform Them i mean tell them to flash DRG-229D File . This file will directly goes down to oreo june security Patch And give the mobile to them they will flash in 2minutes And request Unlock Key Just by in searching Google.
Click to expand...
Click to collapse
I don't think Nokia is going to accept this and flash Oreo just like that.
nikash07 said:
I don't think Nokia is going to accept this and flash Oreo just like that.
Click to expand...
Click to collapse
Bro I updated to pie and went to care point and said some complaints about pie.they finally downgraded my phone . For example tell them Iam not comfort with pie so just flash DRG-229D File using ost. This file belongs to Oreo june security patch .
I have removed the Telegram link in your OP. Posting Telegram links or other ways of promoting social media is not allowed on XDA.
Forum Rules said:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Raghu varma said:
Treble Flashing Guide For All nokia treble enabled phones
Note -1. Before Doing These Steps Your device bootloader should be unlocked. otherwise you may brick your device.
2.Copy img files according to GSI Android Version
Example - iam using Nokia 6.1 Plus & i want to flash Pixel-ex-periance-9
in my phone using GSI
METHOD 1 - VIA CMD
1. copy vendor.img & boot.img form Android 9 stock ota.zip or OST File
2. download gsi from aosp , lineage , pixel experiance etc but choose ab Arm 64
3. now keep 3 files in one folder
4. open cmd in that folder
5. now turn of your mobile and go to download mode
6. now type fastboot devices
7. type fastboot -w
8. type fastboot flash vendor vendor.img
9. type fastboot flash system PixelExperienceP-arm64-ab.img
10. type fastboot flash boot boot.img
11. type fastboot -w
12. fastboot reboot
METHOD 2 - VIA TWRP
1. copy Those 3 img files to your directory internal or external
2. wipe everything except your internal & sd
3. select install img
4. select vendor.img and select vendorimage in partition box swipe to flash
5. next select PixelExperienceP-arm64-ab.img and select systemimage in partition box swipe to flash
6. next select boot.img and select boot in partition box swipe to flash
7. reboot system
Download stock Vendor.img & boot.img files from the below links
Android 9 https://drive.google.com/open?id=1WC9iGS8QnnnBmG4KKL3sEcqlR8LceBUt
Android 8.1.0 https://drive.google.com/open?id=1yY3QvUCYKDXlfn9bREObS2XwCScnU-EN
My Teligram Group Link All Are invited And Feel Free to Ask your Questions MOD EDIT: LINKS REMOVED
My Teligram Channel For the Further Information
Please Hit Thanks Button If You Understand My Guide. Hope Every One Will Boot GSI Successfully In Your Phones. Keep Going...!!!
Thank you
Click to expand...
Click to collapse
the Doctor said:
I have removed the Telegram link in your OP. Posting Telegram links or other ways of promoting social media is not allowed on XDA.
Click to expand...
Click to collapse
thanks for the information. I won't repeat this again
thank you very much
Can we unlock now?
And
How to flash stock rom
I installed AEX gsi, but without TWRP I can't install gapps. Anyone know how to install gapps another way?
paul89rulez said:
thank you very much
Click to expand...
Click to collapse
Welcome
bbcastro said:
I installed AEX gsi, but without TWRP I can't install gapps. Anyone know how to install gapps another way?
Click to expand...
Click to collapse
Well now twrp thread is up in nokia 6.1 kenel and recovery development section check it out
earlier treble gsi's had issues with Nokia phones Sim cards not being detected - has this been resolved, specifically relating to TA-1103?
So should I download From "A" only roms or "A/AB" roms?
Nokia X6 with Custom Oreo ROM - How to load stock Android Pie 6.1 plus image
Hi,
I bought a Nokia X6 in September 2018 (6GB/64GB) and would like to install the Stock Nokia 6.1 Plus Android 9 image.
I see my phone is rooted and it shows the message "Your device has loaded a different operating system." everytime I start it and I have to use Magisk to hide several banking applications.
The phone works great and I knew it was going to be relased in Europe eventually, but I am scared to brick it by loading the Android 9 Image.
I already tried attempting the update through OTA but the zip file is ignored. Nothing happens.
I am new to this forum so I don't know if my question has been asked by someone else.
Can you please help me?
Thank you!
Image size is bigger than target device..
I am using nokia 6.1 plus .. its support project treble , and its ab device..
When i try to flash a gsi rom bigger than 2.5 gb its also eror that image size is bigger than target device ...:crying:
Many popular gsi like oos, one, hydrogen, color os file size over than 2.5 gb .. so always shows this eror..
Any solution for this eror..??
---------- Post added at 04:03 PM ---------- Previous post was at 03:28 PM ----------
I am using nokia 6.1 plus .. its support project treble , and its ab device..
When i try to flash a gsi rom bigger than 2.5 gb its also eror that image size is bigger than target device ...:crying:
Many popular gsi like oos, one, hydrogen, color os file size over than 2.5 gb .. so always shows this eror..
Any solution for this eror..??

HI I just need a QUICK help!!

My Poco sensors stoped working while o was flashing some ROM I don't remember but it was maybe an sGSI.
After flashing alot of vendors on miui or pixel e, iam still facing the same issue.
Any help would really be appreciated
Stock with miflash.....and always backup...lesson learned
seems like persist.img is corrupted!
if you have fastboot rom (miui10.3.7 (2.7gb) , extract it, and further extract it, i will come something 8 gb in total!
inside images folder there will be persist.img
flash that img file, in TWRP /persist PARTITION (BE CARE FUL !!!!!!!!!!!!!!!!)
or better use ORANGE FOX RECOVERY to flash PERSIST.img
then reboot device and check!
if it still doesnt work then use miflasher, and flash this FASTBOOT rom from image folder!
REMEMBER!!!!!!!! don't tick the box, "FLASH ALL AND LOCK" this will relock your bootloader! , simply select "FLASH ALL" button in miFLASHER (down-right)
YasuHamed said:
seems like persist.img is corrupted!
if you have fastboot rom (miui10.3.7 (2.7gb) , extract it, and further extract it, i will come something 8 gb in total!
inside images folder there will be persist.img
flash that img file, in TWRP /persist PARTITION (BE CARE FUL !!!!!!!!!!!!!!!!)
or better use ORANGE FOX RECOVERY to flash PERSIST.img
then reboot device and check!
if it still doesnt work then use miflasher, and flash this FASTBOOT rom from image folder!
REMEMBER!!!!!!!! don't tick the box, "FLASH ALL AND LOCK" this will relock your bootloader! , simply select "FLASH ALL" button in miFLASHER (down-right)
Click to expand...
Click to collapse
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
lokixd4x4 said:
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
Click to expand...
Click to collapse
according to this video https://youtu.be/JKShaUdpvQw?t=374 its platform file issue,
download latest version from
https://forum.xda-developers.com/android/software/tool-platform-tools-adb-fasbootdrivers-t3061441
extract platform folder, put FASTBOOT FILES of MIUI rom in Platform folder and then try flashing
also
put everything in root C:/ and only one folder "C:\images"
long paths are not recomended for MIflasher!
@YasuHamed bro I am facing the exact same issue with a window popup on screen says find device is corrupted your device is unsafe now. Did you find a solution . Please help .brother.
abhisheksh9999 said:
@YasuHamed bro I am facing the exact same issue with a window popup on screen says find device is corrupted your device is unsafe now. Did you find a solution . Please help .brother.
Click to expand...
Click to collapse
i gave up and started using custom roms! they are closer to Stock android and have amazing customizations!
Evolution / Havoc / AeX on android 10 is amazing!
Reloaded OS (android10) is CAF based rom and its faster than others but have no customizations!
CR droid has maximum customizations but its little laggy!
you may also use
Masik13.3 and XiaomiEu roms which are Modified MIUI versions! ( google MIUI ROM BUILDER) and you can predefine features!
these roms can them be flashed via Twrp!
lokixd4x4 said:
mi flash failed to do the job and came out with error. booted fine but sensors still broken.
twrp and orange fox have no persist.img chose when flashing.
anyways thx 4 help. i hope i can get out outta this:crying::crying:
iam using miui 9.6.18 bcz i want oreo
Click to expand...
Click to collapse
Did you find any way to fix the sensors?
I think i too made the same mistake some two months back after flashed peplus rom.. i noticed it only recently.

Categories

Resources