Hello guys.
A few weeks ago i started having problems with my redmi's wifi. Without doing any kind of update or change any settings, the wifi and even the Bluetooth would go down frequently and as time passed this only got worse. Eventually, after a reboot, i couldn't turn the wifi on as showed in the image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried doing a system update, i'm using Lineage OS 14.1, and i tought that it was working again since i was able to toggle the wifi on and connect to a network. But after a few minutes it went down again. Since then i've tried to flash other roms, even the original MIUI and the problem persists. After flashing or even after an occasional reboot, i'm able to turn on and connect to a network but as always it stops working. With Bluetooth i also have a few problems, like having to forget a paired device and reboot to pair the device again. Since with a clean flash or 1 out of 10 reboots the wifi kind of works, i'm hoping that this isn't a hardware problem.
I've tried to search the internet for a solution, but almost every time that i find something with redmi 3, it's basically redmi note 3 posts/threads. Does anyone had a similar problem or have any ideia how to fix this?
Thanks in advance.
FYI phone status:
I met the same problem, hope someone knows how to fix it.
Same problem with my brother's phone, he was on miui and started getting that "MAC 02:00:00:00:00:00" on wifi
I'm trying to recover it, if it's software related then it is due to the NVRAM partition, accessed with QPTS, but that's strange because mobile network works without any issue.
I dumped my nvram and i'm trying to find the actual mac address, if i'm able to change it and successfully recover it i'll post something. The bad news is that i need a clean nvram to double check, because mine is already damaged. I may get my hands on another working redmi 3 soon, hope that will help
You need a nvram partition backup? is valid a backup of twrp? My redmi 3 is working perfect.
Related
I've bought this Coolpad 7295 phone for less than three days from China.
It seems that I couldn't flash my phone back to the state where I could get the service for calling the first day.
After the second rom flashing with my flash tool. I kind of formated the Yl-parames and NVRAM section of the phone.
I don't know these two mean! Could someone explain how they work? Are they related to the hardware or the motherboard of the phone?
After the wrong formatting action, my phone could not make any calls. (But everything works, and network works also. And later I flashed many roms, all of them work, just no signal)
So the third picture shows that this device has a different partition compared to the most smartphones in the hardware called "YL-parames".
My friend who is good at making custom roms in Taiwan said I might accidentally screw up with the hardware partition.
I just want to know with this problem appearing, is there any other way that I could get my signal back?
I've tried several methods like rewriting IMEIs, reinstalling the official roms, but none of them work.
Or should I just send it back to the dealer to get it fixed? (I'm doing it right now...)
Just want to know in case the phone is back, how should I operate this flashing tool because I'm really a tech-savy
1) The first picture represents what i chose for the outcome of no signals later on.
2) The next one is its interface
3) The next one is the official flashing tool, but I still can not flash the CPB provided by the official since my hardware seems to be broken.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would really like somebody to develop the custom rom in the English version for this device, this device is pretty good!
Or is there anybody using this phone as well? It's nice to have someone to exchange info with!!
Hello,
I've got a weird problem with my M4
I've got the phone for over 2 years, it's the E2303 version. It worked perfectly normal until at some point it started randomly crashing (Note: the phone wasn't rooted at this point and it had Android 5.0 26.1.A.3.111 (carrier version)). The crash looks like this: the phone freezes for like 2-3 seconds not responding to any input, then the screen goes black, then it boots up normally. However it isn't rare for it to crash like that, then while booting up crash again in the same way, repeat a couple of times. In System incidents it's counted as just 1 incident. I also noticed that sometimes after successfully booting up after crash wi-fi, mobile transfer or airplane mode are switched on/off, not as before the crash.
I thought the problem would go away so I waited a bit, but it kept on crashing. Sometimes it can go for a few days without crashing, sometimes it crashes a few minutes after last crash.
I've tried fixing the phone using PC Companion (it also updated it to 6.0) - didn't help. I've tried flashing a stock 5.0 ROM using Flashtool (same as before: 26.1.A.3.111, but a non-carrier version) - also didn't help. Also I've got the phone rooted by now. I don't know about bootloader, the service menu tells me Bootloader unlock allowed: No, even though I've got the OEM unlocking switched on in the Developer options (I'm not that tech savvy in case of phones and I'm getting lost a little bit).
I've got some screenshots here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope there is a way to fix this phone, this crashing is starting to get a little annoying...
Any help would be really appreciated
Install twrp. Download latest stock rom. Format phone by wiping cache, system and data in twrp wipe option. Install flashtool and use it to install latest stock rom. Watch a tutorial on youtube How to install latest stock rom through twrp
Heya, first time posting and I got this weird NVRAM problem.
Before all, here's the info of my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Also have installed TWRP MDS recovery 2.8.0.0)
So, some time ago I kinda ruined my NVRAM/IMEI (sorry, I'm really bad at this so please no hate if I don't call it correctly) while flashing my phone. But til now I was able to fix it by just taking the NVRAM folder back-up on my pc and replacing the one on my phone with it. That worked fine for a few times. But recently, I got another, kinda weird problem. I suddenly found myself not being able to use a few apps anymore as when I opened them, they froze after a few seconds and closed, without any "[APP] unfortunately stopped working.". First I tried figuring out why it might be after which apps it were which froze, but I couldn't find a clear pattern because apps like Steam or Chrome froze, while Firefox, Reddit and WhatsApp were just fine. Following I tried first removing my SD card to see if that would fix it, rebooting my phone, clearing the app cache, reinstalling them and nothing worked. So as a last resort, I factory reset my phone. After it rebooted, I had the NVRAM problem again, to no suprise and I did the same as always. Drag root explorer and the NVRAM folder on my device and replace the current NVRAM folder with the back-up. But after rebooting it, I kinda met something unused for me: The IMEI was there, but so was the NVRAM error in the Wi-Fi tab.
That pretty much confused me. The phone works perfectly fine, I can receive calls and messages, the provider is there.
So at first I didn't bother about it because the error only was showing in the Wi-Fi tab while everything seemed to be fine. But then trying to install and open the same apps as mentioned above, nothing has changed.
So, with me being a total noob in this and not being able to connect the lines I got 2 questions:
1. Are those 2 problems linked to each other?
I know that it is very unlikely, but hey, slowly getting desperate so I would believe anything.
2. Specifically, how can I fix the apps freezing?
The first problem didn't bother me too much, but I kinda need to use some of those apps like steam for the mobile authenticator so I really would be glad if I could fix this.
Thanks for any help in advance.
Morning,so i am going to try yet again for some help here with regards my mom's Nokia 1 device running on Android 10 Go. Since she updated her phone to Android 10,she has had cmstant issues with the phone. Since updating it,her messages app will not switch to dark mode at all,i have tried uninstalling it and replacing it with other versions etc but it never has a dark mode option available in the app at all.
Then her Google Chrome would not update at all. I got that sorted after a lot of trial and error,resetting the phone and so on. Now the phone has issues with her wallpapers resetting to the default wallpaper the whole time at random. She also suddenly has an issue with her camera after the recent camera related update. She can take a photo,but is unable to view it from her camera app after taking the photo. She also is unable to delete the photo after taking it.
So,i am wanting to know if anyone has any idea of how to perform a software repair or maybe a way to re-install Android 10 on her phone other than just doing a factory reset which does'nt fix any of her issues anyway. Please,we just want to get the phone working properly,so if anyone knows how we can do that,it would be appreciated.
Thank you
Just like any MTK phone use spflashtool then flash it
U should check Wich model first
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Hucin44 thank you. Have you tried this with a Nokia 1 or do you know someone that has? I do not want to try this if nobody else has and were successful. Last thing i want is to brick my mom's phone.
U can follow this
Downgrade Nokia 1 TA-1066 from Android 10 Go to Android 8.1 Go
The Nokia 1 recently got the Android 10 update. The update got lot of bugs like SD card losing write permissions, launcher3 not having widgets and shortcuts on top of other bugs in Pie. This has compelled me to look for going back to Android 8.1...
forum.xda-developers.com
It's work for more secure if afraid to brick the phone uncheck preloader in spflashtool
Thank you
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.