Try doing this. Go to Settings->Mobile Networks->APN or Access point names->Tap the three dots on the top-right corner->Reset to default.
Hi guys. I have a Redmi Note 3 SD and I find the device incredibly good. But I have a problem with it that has been very annoying: when I listen to music via Bluetooth after a certain time the audio comes out as if it were a few meters away from the sound, and even though I'm in front of the audio, it comes out like this. I've tried changing the kernel but nothing fixes and other devices play quietly in the sound, which is a Panasonic AKX-600. Anyone have any suggestions on how to fix the problem?
Thank you in advance!
PS: Excuse my English, I'm using the translator because I'm Brazilian and I do not speak English fluently, besides being new to XDA
Stop spamming everywhere
Yes i was noob too and im not as well but ur querry is very simple u even get answer if u search any thread... everybody have to grow up...dont be noob always... learn and get out from noob...
That's what i was doing and a simple reply to my query would have suffice. I searched for waht i wanted n i came across this forum. And as i said be cool not noob
U will always a noob if u even want a spoon feed for a such small querry ... anyway i helped u but even u want argue i will not reply u again... good by
Flash your phone using edl,you can search how to there are well explained tutorial availableNot a completely noob here, more of a semi-noob with dangerous half knowledge.
Anyway, 1.5 years ago I flashed CM13 for 'kenzo' on my 'kate', flashed the modem fot 'kate' afterwards and everything was fine, 4G was working, no problems. At least it was until last summer, when apps started crashing and after a few days my phone was stuck in a bootloop.
I made a factory reset and everything was fine again until last week, when apps started chrashing and I soon found myself in a bootloop (that was faster than the first one). After a new factory reset and installation of a few apps I had the same bootloop again.
So I decided to switch to LineageOS 14.1, which even has a build for the 'kate', at least an unofficial one, but it just showed the boot animation for hours.
Because I wanted to at least have a working phone again, I went for the official MIUI 9 ROM for the 'kate', but something went wrong flashing. Now my phone only shows the mi logo for a fraction of a second and then goes blank when trying to boot android or the recovery, I can only get to the bootloader. When trying to flash anything now, I get the error message: "Partition flashing is not allowed".
Since the ways I found online to unlock the device all require a running MIUI ROM, I want to ask, if anyone sees a way to get my phone working again?
For question 1i have REDMI NOTE 3 KENZO SNAPDRAGON VERSION 3GB
RUNNING ON latest global stable miui 220.127.116.11, android 6.0.1
i have zc -x recovery ( unlocked officially and rooted)
Q1) if i want to backup my rom which partitions should i select, in case of if i made any mistake and want to restore?
like if i flashed some wrong zip, and now facing bootloop
To get rid of bootloop, i can use twrp backup?
Q2) in case if i dont have twrp backup, and want to flash fastboot rom but dont want to lose internal storage? what should i do, there is no option for clean_all_except_storage.bat? in mi flash tool latest one
i do not to erase my internal everytime i flash with mi flash tool
Q3) if i can access twrp and want to copy backup from computer or otg how can i do it?
because if i attach phone in recovery mode, it is not showing my device internal storage in my pc! just showing phone is attached under adb interface
I was going to unlock my bootloader here but then I decided to check xda first before clicking apply on the bootloader unlock request page. I didn't seem to find any guide here on xda telling me to use that page. Why is that?
So should I use the official method or one of the guides (and if so could someone link me a good up-to-date guide). Also I assume warranty is void when unlocking the bootloader but could someone confirm that because it doesn't say that on the request unlock page.