Low in call volume after OOS 3.1 BL & Radio Update - OnePlus X Q&A, Help & Troubleshooting

Hi,
I recently updated by BL & Radio by this perfect guide: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
With the new BL I flashed the latest nightly of CM13 which was released on 28.10.2016.
Currently I am having very low in call volume even after I max. out using the hardware buttons and also having network fluctuations. Old BL with radio had no such issue and I am not sure what is causing this.
Thanks

Its cm13 issue not bootloader. Flash different ROM or stick with 3.1.3.

Exodusche said:
Its cm13 issue not bootloader. Flash different ROM or stick with 3.1.3.
Click to expand...
Click to collapse
Please suggest me some ROM's that supports the new BL and has the customization of such as CM13.
Isn't @matwaking one is 3.1.3?

tausifahmed said:
Please suggest me some ROM's that supports the new BL and has the customization of such as CM13.
Isn't @matwaking one is 3.1.3?
Click to expand...
Click to collapse
Matwaking's is stock debloated. Very good if you want to run 3.1.3 without all the extra bloat. If you want nougat experience Tesla N is daily driver for sure. Many of the ROMs have updated bootloader just read the thread to make sure.

Related

[Q] Rooted, Flashed recovery, now what?

I rooted my P765 using LGPwn.apk and flashed recovery using artas' app. Now i can just download zips on my sd card and flash them in recovery?
Also, are CM and PACman roms bugfree now? Which rom do you prefer? thanks!
Please just tell me if i could flash Cm10 for P760 on my device now, without any problems?
makjack said:
I rooted my P765 using LGPwn.apk and flashed recovery using artas' app. Now i can just download zips on my sd card and flash them in recovery?
Also, are CM and PACman roms bugfree now? Which rom do you prefer? thanks!
Click to expand...
Click to collapse
first of all make backup with CWM because if anything go wrong you can atleast restore it ...
and install rom whatever you like because everyone have different taste!!!
----------------------------------------------------
i am totally a newbee don't know anything about here but know how to help people:highfive:
press thanks if i helped you
----------------------------------------------------
currently using xperia u with locked bootloader and have JB eXperience v2 rom
makjack said:
Please just tell me if i could flash Cm10 for P760 on my device now, without any problems?
Click to expand...
Click to collapse
You have to unlock bootloader first to install any custom ROM. It's not bugfree. Max sound volume of the speaker is lower than in stock. This is only thing which annoys me so far in CM. PACMAN has problem with wifi, wait for update. It should be made soon but probably sound of the speaker will be quiet as in CM. Of course 1080p video recording is not working too but I don't care about it.
Actually there are some roms for locked bootloader like I have jb experience v2.1
And unlocking bootloader can hard brick your phone
Press thanks if I helped
sauravrockable said:
Actually there are some roms for locked bootloader like I have jb experience v2.1
And unlocking bootloader can hard brick your phone
Press thanks if I helped
Click to expand...
Click to collapse
It's based on stock ROM and you don't have changed kernel. In that case you can find changed theme and some tweaks. It's modified stock ROM and it's not big diffrence from stock. For custom ROMs such as CM or PACMAN you need to unlock bootloader and he asked about them.
anirion said:
It's based on stock ROM and you don't have changed kernel. In that case you can find changed theme and some tweaks. It's modified stock ROM and it's not big diffrence from stock. For custom ROMs such as CM or PACMAN you need to unlock bootloader and he asked about them.
Click to expand...
Click to collapse
thanks to make things clear....i am totally new here!!!
so just trying to learn things

[Q] Is CM firmware necessary after unlocking Kenzo? Need help!

Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Edit- solved
Flash CM firmware if your ROM is CM based at all, of course. If not, look for something in the ROM thread.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Personally I always flash it anyway. Fixes a few bugs like settings FC etc.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
iTaisHi said:
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
Click to expand...
Click to collapse
yes, that was live display bug in old kernels. fixed after a week of this post.

New owner of a Kate, which files should I use ?

Hi all,
I'm a glad owner of a Redmi Note 3 Pro SE "Kate", and I'm a bit lost with all the threads, roms, TWRP versions, methods to unlock the bootloader...
I've read a lot, but there is many many threads and files here, sometimes with outdated info, and I don't want to make the bad choices !
I have already flashed the latest Global Dev ROM and waiting for official unlock at MIUI.
Now, I want to install a custom ROM (like CM or RR) and it's where it begins to be complicated....
So I have two questions:
- Which TWRP version is best for my use ?
- Do I have to flash radio firmware, or some other firmware file if I flash CM or other custom ROM ?
In the CM thread there is firmware file, but I suppose it's for Kenzo, and not Kate, am I right ?
Thanks for reading.
Use Alka TWRP, M4, or official.
Firmware for CM14.1 http://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Firmware for CM13 is around.
theoneofgod said:
Use Alka TWRP, M4, or official.
Click to expand...
Click to collapse
OK thanks.
theoneofgod said:
Firmware for CM14.1 http://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
Click to expand...
Click to collapse
I had already downloaded this file, but if I'm understanding well, this is the same I have on my phone right ? (MIUI 8 Global dev 6.12.22, latest beta)
theoneofgod said:
Firmware for CM13 is around.
Click to expand...
Click to collapse
Where please ? I haven't found the CM13 official thread...
Do you think there will be issues if I keep the firmwares I have on MIUI 8 Global dev 6.12.22 and flash CM13?
If I flash other custom ROM, (aosp one or cm based), can I use the same firmware file ?
The firmware is for Nougat based for kate
A good thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
CM13 thread
http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-t3431866

[HELP] Kenzo stuck on Boot on latest Nougat ROMS.

I have observed that my RN3 kenzo is not able to boot on any Nougat ROM built after 2nd april.
I have tried the following ROMS :
1. XenonHD (2nd and 7th april builds - Working fine)
2. Xenon HD 5th May - STUCK ON BOOT
3. Nitrogen OS - STUCK ON BOOT (I dont remember the build date but I downloaded it in april )
4. Resurrection Remix 3rd May - STUCK ON BOOT
5. Cosmic OS - 6th May - STUCK ON BOOT
All the installations were clean flashes. Installed CM14.1_Firmware_kenzo_12.04.2017, still no luck.
What is the reason behind this ? How Can I solve it ?
A7omiz3r said:
I have observed that my RN3 kenzo is not able to boot on any Nougat ROM built after 2nd april.
I have tried the following ROMS :
1. XenonHD (2nd and 7th april builds - Working fine)
2. Xenon HD 5th May - STUCK ON BOOT
3. Nitrogen OS - STUCK ON BOOT (I dont remember the build date but I downloaded it in april )
4. Resurrection Remix 3rd May - STUCK ON BOOT
5. Cosmic OS - 6th May - STUCK ON BOOT
All the installations were clean flashes. Installed CM14.1_Firmware_kenzo_12.04.2017, still no luck.
What is the reason behind this ? How Can I solve it ?
Click to expand...
Click to collapse
did your bootloader unlocked?
is it officially unlocked or unofficially?
driss.tuning said:
did your bootloader unlocked?
is it officially unlocked or unofficially?
Click to expand...
Click to collapse
my bootloader is unlocked.
I installed an older build of XenonHD and it is working fine. All the newer builds are getting stuck.
Edit : Unofficially unlocked.
Flash latest firmware from Official LOS thread and flash your rom. Here is the direct link https://www.androidfilehost.com/?fid=817550096634767927
And Read this.
Some nougat roms won`t boot if you don`t format data after you`ve flashed the rom. So try this: if you are coming from miui, you don`t need to flash any firmware, then wipe system+data+dalvik cache+cache, install rom+gapps and last thing, Format Data (you`ll find it under advanced wipe) and reboot to system. Save your files to sdcard or computer before do that, because this will erase all internal storage, but twrp will remain.
A7omiz3r said:
my bootloader is unlocked.
I installed an older build of XenonHD and it is working fine. All the newer builds are getting stuck.
Edit : Unofficially unlocked.
Click to expand...
Click to collapse
This.
Some of the Newer ROMs need MM bootloader. If you've unofficially unlocked then that means you're on LP bootloader.
Try Flashing the latest MIUI dev ROM and unlocking officially.
Yeah that's exactly what @bloodytolits said flash the latest developer rom i think the Chinese roms get unlocked easily so you can go with it until you unlocked officially then you don't need to flash any firmware again your already on the latest then flash the rom and your ready to go good look
H
bloodytolits said:
This.
Some of the Newer ROMs need MM bootloader. If you've unofficially unlocked then that means you're on LP bootloader.
Try Flashing the latest MIUI dev ROM and unlocking officially.
Click to expand...
Click to collapse
Hey @bloodytolits ,I'm facing the same problem. Can I flash latest global stable ROM and unlock my bootloader on it OR do I need to flash global dev ROM?
atharvpotdar007 said:
Hey @bloodytolits ,I'm facing the same problem. Can I flash latest global stable ROM and unlock my bootloader on it OR do I need to flash global dev ROM?
Click to expand...
Click to collapse
Most of the latest ROMs only works on firmwares 7.5.4 - 7.6.7. I don't know if they already changed that. So you can install(and unlock) MIUI dev 7.5.4 - 7.6.7 or the latest and just flash the 7.5.4 - 7.6.7 firmware afterwards before trying to flash any custom rom.
Most people says it should be dev ROM, as I haven't officially unlocked mine I don't know. I'm using Kate and following this guide, you won't really need to officially unlock. I can't guarantee if this would work on kenzo though.
bloodytolits said:
Most of the latest ROMs only works on firmwares 7.5.4 - 7.6.7. I don't know if they already changed that. So you can install(and unlock) MIUI dev 7.5.4 - 7.6.7 or the latest and just flash the 7.5.4 - 7.6.7 firmware afterwards before trying to flash any custom rom.
Most people says it should be dev ROM, as I haven't officially unlocked mine I don't know. I'm using Kate and following this guide, you won't really need to officially unlock. I can't guarantee if this would work on kenzo though.
Click to expand...
Click to collapse
Okay. Now I'm planning to flash MIUI fastboot from RR 5.8.3. and lock my bootloader. Will it cause any bootloop problem?
atharvpotdar007 said:
Okay. Now I'm planning to flash MIUI fastboot from RR 5.8.3. and lock my bootloader. Will it cause any bootloop problem?
Click to expand...
Click to collapse
Sorry haven't tried reverting but it should be safe using Miflash. If it somehow didn't work, found this
Thanks bud @bloodytolits, succesfully flashed MIUI8 global stable yesterday !
hello guys...any fix for this?
im am stuck as well
tried flashing lineage os stuck on the booting screen
kaishin said:
tried flashing lineage os stuck on the booting screen
Click to expand...
Click to collapse
U must have latest miui firmware and latest bootloader. Also format data in twrp before flashing.
naik2902 said:
U must have latest miui firmware and latest bootloader. Also format data in twrp before flashing.
Click to expand...
Click to collapse
hello mate
can you please give the link to this?
tnks
naik2902 said:
U must have latest miui firmware and latest bootloader. Also format data in twrp before flashing.
Click to expand...
Click to collapse
thanks i figured it out i need to update MIUI > MM then unlock bootloader officially then install TWRP > WIN WIN
shaca said:
hello mate
can you please give the link to this?
tnks
Click to expand...
Click to collapse
Official or unofficial unlock bootloader?
to be honest i cant remember on this phone...atm i can only boot the phone in fastboot mode, any way to check it?
shaca said:
to be honest i cant remember on this phone...atm i can only boot the phone in fastboot mode, any way to check it?
Click to expand...
Click to collapse
Did u apply for permission from xiaomi to unlock this phone and unlocked it using Miunlock tool and pressed unlock button to unlock?
Or
Did u used fastboot oem unlock-go command to unlock ?
If u don't know which one? That means this phone is stolen one.:laugh:

Cannot Boot Custom ROMs Anymore. Just Bootloops

Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.

Categories

Resources